From: Nicholas Drozd <nicholasdrozd@gmail.com>
To: 34274@debbugs.gnu.org
Subject: bug#34274: [PATCH] * src/callproc.c (call-process/region): Fix docstring arg formatting
Date: Fri, 1 Feb 2019 08:13:10 -0600 [thread overview]
Message-ID: <CABAiW0rhJzVhLFDd_oESUKLk7UYk2VaiXW2TbA=Q5aimNdr5Aw@mail.gmail.com> (raw)
---
src/callproc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/callproc.c b/src/callproc.c
index d4558387cf..f8036f51ef 100644
--- a/src/callproc.c
+++ b/src/callproc.c
@@ -237,7 +237,7 @@ DESTINATION can also have the form (REAL-BUFFER
STDERR-FILE); in that case,
t (mix it with ordinary output), or a file name string.
Fourth arg DISPLAY non-nil means redisplay buffer as output is inserted.
-Remaining arguments are strings passed as command arguments to PROGRAM.
+Remaining ARGS are strings passed as command arguments to PROGRAM.
If executable PROGRAM can't be found as an executable, `call-process'
signals a Lisp error. `call-process' reports errors in execution of
@@ -1033,7 +1033,7 @@ STDERR-FILE may be nil (discard standard error output),
t (mix it with ordinary output), or a file name string.
Sixth arg DISPLAY non-nil means redisplay buffer as output is inserted.
-Remaining args are passed to PROGRAM at startup as command args.
+Remaining ARGS are passed to PROGRAM at startup as command arguments.
If BUFFER is 0, `call-process-region' returns immediately with value nil.
Otherwise it waits for PROGRAM to terminate
--
2.17.1
next reply other threads:[~2019-02-01 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 14:13 Nicholas Drozd [this message]
2019-02-01 15:14 ` bug#34274: [PATCH] * src/callproc.c (call-process/region): Fix docstring arg formatting Eli Zaretskii
2019-02-04 23:55 ` Nicholas Drozd
2019-02-08 8:47 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABAiW0rhJzVhLFDd_oESUKLk7UYk2VaiXW2TbA=Q5aimNdr5Aw@mail.gmail.com' \
--to=nicholasdrozd@gmail.com \
--cc=34274@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.