From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 21605@debbugs.gnu.org, Nikolas De Giorgis <bznein@gmail.com>
Subject: bug#21605: 24.3; Eshell not using stderr
Date: Fri, 13 May 2022 14:38:23 +0200 [thread overview]
Message-ID: <87r14xvc8w.fsf@gnus.org> (raw)
In-Reply-To: <9b1d2162-2fa6-16fb-6fd0-50a45b0b88e5@gmail.com> (Jim Porter's message of "Thu, 12 May 2022 19:14:46 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
> I think this is just a missing feature, partly due to the fact that
> the redirection operators don't let you redirect a specific fd. That's
> in the "Bugs and Ideas" section of the Eshell manual though:
>
> Support ‘2>&1’ and ‘>&’ and ‘2>’ and ‘|&’
>
> The syntax table for parsing these should be customizable, such that
> the user could change it to use rc syntax: ‘>[2=1]’.
>
> Doing that is probably the hardest part. The other bit that would need
> to be fixed is (I think) to modify `eshell-gather-process-output' to
> use `make-process' instead of `start-file-process', and then give it a
> :stderr argument so that Emacs doesn't write both stdout and stderr to
> a single temp buffer.
I see; thanks.
> I agree that this would definitely be nice to have though.
Yup.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-13 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 12:23 bug#21605: 24.3; Eshell not using stderr Nikolas De Giorgis
2022-05-12 12:26 ` Lars Ingebrigtsen
2022-05-13 2:14 ` Jim Porter
2022-05-13 12:38 ` Lars Ingebrigtsen [this message]
2022-08-30 3:29 ` bug#21605: [PATCH] " Jim Porter
2022-08-30 10:31 ` Lars Ingebrigtsen
2022-08-31 4:25 ` Jim Porter
2022-09-04 23:05 ` Jim Porter
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=87r14xvc8w.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21605@debbugs.gnu.org \
--cc=bznein@gmail.com \
--cc=jporterbugs@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 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.