diff options
| author | Basil L. Contovounesios | 2018-02-03 23:27:13 +0200 |
|---|---|---|
| committer | Juri Linkov | 2018-02-03 23:27:13 +0200 |
| commit | a893924fd17c8d0422fccfcb5f373df49a6a1511 (patch) | |
| tree | b92953417b7524ac8d9700ee3646ad199785d29e | |
| parent | 699081f0516b057ce9319383b244a8e1e8e88516 (diff) | |
| download | emacs-a893924fd17c8d0422fccfcb5f373df49a6a1511.tar.gz emacs-a893924fd17c8d0422fccfcb5f373df49a6a1511.zip | |
* lisp/simple.el (async-shell-command, shell-command): Fix grammar
| -rw-r--r-- | lisp/simple.el | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/lisp/simple.el b/lisp/simple.el index e2deceb4c26..b7ad6ebd799 100644 --- a/lisp/simple.el +++ b/lisp/simple.el | |||
| @@ -3351,15 +3351,15 @@ to execute it asynchronously. | |||
| 3351 | The output appears in the buffer `*Async Shell Command*'. | 3351 | The output appears in the buffer `*Async Shell Command*'. |
| 3352 | That buffer is in shell mode. | 3352 | That buffer is in shell mode. |
| 3353 | 3353 | ||
| 3354 | You can configure `async-shell-command-buffer' to specify what to do in | 3354 | You can configure `async-shell-command-buffer' to specify what to do |
| 3355 | case when `*Async Shell Command*' buffer is already taken by another | 3355 | when the `*Async Shell Command*' buffer is already taken by another |
| 3356 | running shell command. To run COMMAND without displaying the output | 3356 | running shell command. To run COMMAND without displaying the output |
| 3357 | in a window you can configure `display-buffer-alist' to use the action | 3357 | in a window you can configure `display-buffer-alist' to use the action |
| 3358 | `display-buffer-no-window' for the buffer `*Async Shell Command*'. | 3358 | `display-buffer-no-window' for the buffer `*Async Shell Command*'. |
| 3359 | 3359 | ||
| 3360 | In Elisp, you will often be better served by calling `start-process' | 3360 | In Elisp, you will often be better served by calling `start-process' |
| 3361 | directly, since it offers more control and does not impose the use of a | 3361 | directly, since it offers more control and does not impose the use of |
| 3362 | shell (with its need to quote arguments)." | 3362 | a shell (with its need to quote arguments)." |
| 3363 | (interactive | 3363 | (interactive |
| 3364 | (list | 3364 | (list |
| 3365 | (read-shell-command "Async shell command: " nil nil | 3365 | (read-shell-command "Async shell command: " nil nil |
| @@ -3428,8 +3428,8 @@ In an interactive call, the variable `shell-command-default-error-buffer' | |||
| 3428 | specifies the value of ERROR-BUFFER. | 3428 | specifies the value of ERROR-BUFFER. |
| 3429 | 3429 | ||
| 3430 | In Elisp, you will often be better served by calling `call-process' or | 3430 | In Elisp, you will often be better served by calling `call-process' or |
| 3431 | `start-process' directly, since it offers more control and does not impose | 3431 | `start-process' directly, since they offer more control and do not |
| 3432 | the use of a shell (with its need to quote arguments)." | 3432 | impose the use of a shell (with its need to quote arguments)." |
| 3433 | 3433 | ||
| 3434 | (interactive | 3434 | (interactive |
| 3435 | (list | 3435 | (list |