From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59545@debbugs.gnu.org, milan.zimmermann@gmail.com,
michael.albinus@gmx.de
Subject: bug#59545: 29.0.50; Eshell fails to redirect output of sourced eshell file
Date: Fri, 23 Dec 2022 23:29:04 -0800 [thread overview]
Message-ID: <13f7119d-9960-1936-9014-2147e9bd1db9@gmail.com> (raw)
In-Reply-To: <0dfbb64b-1828-903e-9630-12c29f21efc1@gmail.com>
reopen 59545
thanks
On 12/22/2022 12:02 PM, Jim Porter wrote:
> Merged to master as 17bf6a829ca2fd2920c01e1aee30ab16b9c672eb. (I guess
> that was only a day and not "a couple days", but I think it would be
> good to get this on the master branch so that a wider audience can test
> it to verify that everything is ok.)
I found a problem with the patch on master:
~ $ {echo hello; echo world} | rev
olleh ;; "dlrow" is missing!
This happens because the way I'm copying output handles around results
in EOF being sent to "rev" after "echo hello". To be fair, this didn't
work correctly before either, but the problem was different. Prior to my
patch:
~ $ {echo hello; echo world} | rev
hello
dlrow
(Only "echo world" is actually piped through "rev".) I'll try to come up
with a fix in the next couple days.
next prev parent reply other threads:[~2022-12-24 7:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 15:49 bug#59545: 29.0.50; Eshell fails to redirect output of sourced eshell file Milan Zimmermann
2022-12-21 0:18 ` Jim Porter
2022-12-21 0:29 ` Jim Porter
2022-12-21 9:54 ` Michael Albinus
2022-12-21 18:48 ` Jim Porter
2022-12-21 19:26 ` Eli Zaretskii
2022-12-22 1:20 ` Jim Porter
2022-12-22 20:02 ` Jim Porter
2022-12-24 7:29 ` Jim Porter [this message]
2022-12-25 1:36 ` Jim Porter
2022-12-25 21:49 ` Jim Porter
2022-12-26 19:50 ` Jim Porter
2022-12-30 6:40 ` Jim Porter
2022-12-21 12:01 ` 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=13f7119d-9960-1936-9014-2147e9bd1db9@gmail.com \
--to=jporterbugs@gmail.com \
--cc=59545@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=milan.zimmermann@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.