From: LdBeth <andpuke@foxmail.com>
To: 52509@debbugs.gnu.org
Subject: bug#52509: 27.2; `call-process-region' won't accept nil as START argument
Date: Wed, 15 Dec 2021 18:59:59 +0800 [thread overview]
Message-ID: <tencent_450C1A1D1AABDBBF25B7BAEE4747819E0C07@qq.com> (raw)
The docstring of `call-process-region' writes:
START and END are normally buffer positions specifying the part of the
buffer to send to the process.
If START is nil, that means to use the entire buffer contents; END is
ignored.
If START is a string, then send that string to the process
instead of any buffer contents; END is ignored.
The remaining arguments are optional.
Delete the text if fourth arg DELETE is non-nil.
To reproduce this bug, define these functions:
```
(defun this-works ()
(call-process-region (point-min) (point-max) "/bin/cat"
t t))
(defun this-wont ()
(call-process-region nil 0 "/bin/cat"
t t))
```
and use `M-:` to execute these two function. The second one would give
the error trace:
```
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
call-process-region(nil 0 "/bin/cat" t t)
this-wont()
eval((this-wont) t)
eval-expression((this-wont) nil nil 127)
funcall-interactively(eval-expression (this-wont) nil nil 127)
call-interactively(eval-expression nil nil)
command-execute(eval-expression)
```
While if my understanding to the docstring is right, these two should
give identical effect.
The Emacs version I'm using is 27.2, however I suspect this can also
be reproduced in master branch.
--
LDB
next reply other threads:[~2021-12-15 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 10:59 LdBeth [this message]
2021-12-15 14:09 ` bug#52509: 27.2; `call-process-region' won't accept nil as START argument Stephen Berman
2021-12-15 15:26 ` LdBeth
2021-12-15 14:24 ` Eli Zaretskii
2021-12-19 12:46 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_450C1A1D1AABDBBF25B7BAEE4747819E0C07@qq.com \
--to=andpuke@foxmail.com \
--cc=52509@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).