unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Nikolas De Giorgis <bznein@gmail.com>
Cc: 21605@debbugs.gnu.org
Subject: bug#21605: 24.3; Eshell not using stderr
Date: Thu, 12 May 2022 19:14:46 -0700	[thread overview]
Message-ID: <9b1d2162-2fa6-16fb-6fd0-50a45b0b88e5@gmail.com> (raw)
In-Reply-To: <877d6rym1e.fsf@gnus.org>

On 5/12/2022 5:26 AM, Lars Ingebrigtsen wrote:
> This seems to be the case in Emacs 29, too, but I'm not sure whether
> this is by design or not.  I've added Jim to the CCs; perhaps he has
> some input here.

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 agree that this would definitely be nice to have though.





  reply	other threads:[~2022-05-13  2:14 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 [this message]
2022-05-13 12:38     ` Lars Ingebrigtsen
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

  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=9b1d2162-2fa6-16fb-6fd0-50a45b0b88e5@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=21605@debbugs.gnu.org \
    --cc=bznein@gmail.com \
    --cc=larsi@gnus.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).