From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ernesto Alfonso <erjoalgo@gmail.com>
Cc: 35187@debbugs.gnu.org
Subject: bug#35187: 26.1; call-process should accept a buffer as stdin. or its doc should reference call-process-region
Date: Tue, 09 Jul 2019 18:00:37 +0200 [thread overview]
Message-ID: <877e8rtcyi.fsf@mouse.gnus.org> (raw)
In-Reply-To: <877ec5qyul.fsf@debian-x1g4.i-did-not-set--mail-host-address--so-tickle-me> (Ernesto Alfonso's message of "Sun, 07 Apr 2019 14:39:30 -0700")
Ernesto Alfonso <erjoalgo@gmail.com> writes:
> When looking at the call-process doc, I didn't see a way to pass a
> buffer to stdin without creating a temporary file. It looks like
> the DESTINATION argument already supports either a file-name or a
> buffer, but passing a buffer to INFILE does not seem supported:
>
> (call-process "cat" (get-buffer "*Messages*") nil)
> *** Eval error *** Wrong type argument: stringp, #<buffer *Messages*>
>
> Can this be supported? Could call-process-region be merged into
> the INFILE argument to call-process?
I think it's probably too late to merge these two functions...
> As a short-term fix, it would be useful if the call-process referred to
> call-process-region.
... but I've now mentioned the latter in the former's doc string on the
Emacs trunk.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-07-09 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 21:39 bug#35187: 26.1; call-process should accept a buffer as stdin. or its doc should reference call-process-region Ernesto Alfonso
2019-07-09 16:00 ` Lars Ingebrigtsen [this message]
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=877e8rtcyi.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=35187@debbugs.gnu.org \
--cc=erjoalgo@gmail.com \
/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).