procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; * lisp/simple.el (async-shell-command): Doc fix. (Bug#63432)

Browse source
This commit is contained in:
Eli Zaretskii 2023-05-14 10:13:39 +03:00
parent b96dc472bc
commit 5c8864fab4
1 changed files with 13 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

17
lisp/simple.el
View file

@ -4460,11 +4460,13 @@ whose `car' is BUFFER."
Like `shell-command', but adds `&' at the end of COMMAND Like `shell-command', but adds `&' at the end of COMMAND
to execute it asynchronously. to execute it asynchronously.
The output appears in the buffer whose name is stored in the The output appears in OUTPUT-BUFFER, which could be a buffer or
variable `shell-command-buffer-name-async'. That buffer is in the name of a buffer, and defaults to `shell-command-buffer-name-async'
shell mode. if nil or omitted. That buffer is in shell mode. Note that, unlike
with `shell-command', OUTPUT-BUFFER can only be a buffer, a buffer's
name (a string), or nil.
You can configure `async-shell-command-buffer' to specify what to do You can customize `async-shell-command-buffer' to specify what to do
when the buffer specified by `shell-command-buffer-name-async' is when the buffer specified by `shell-command-buffer-name-async' is
already taken by another running shell command. already taken by another running shell command.
@ -4473,6 +4475,10 @@ configure `display-buffer-alist' to use the action
`display-buffer-no-window' for the buffer given by `display-buffer-no-window' for the buffer given by
`shell-command-buffer-name-async'. `shell-command-buffer-name-async'.
Optional argument ERROR-BUFFER is for backward compatibility; it
is ignored, and error output of the async command is always
mingled with its regular output.
In Elisp, you will often be better served by calling `start-process' In Elisp, you will often be better served by calling `start-process'
directly, since it offers more control and does not impose the use of directly, since it offers more control and does not impose the use of
a shell (with its need to quote arguments)." a shell (with its need to quote arguments)."
@ -4491,6 +4497,9 @@ a shell (with its need to quote arguments)."
(dired-get-filename nil t))))) (dired-get-filename nil t)))))
(and filename (file-relative-name filename)))) (and filename (file-relative-name filename))))
nil nil
;; FIXME: the following argument is always ignored by 'shell-commnd',
;; when the command is invoked asynchronously, except, perhaps, when
;; 'default-directory' is remote.
shell-command-default-error-buffer)) shell-command-default-error-buffer))
(unless (string-match "&[ \t]*\\'" command) (unless (string-match "&[ \t]*\\'" command)
(setq command (concat command " &"))) (setq command (concat command " &")))