From: Samer Masterson <samer@samertm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12689@debbugs.gnu.org
Subject: bug#12689: 24.2; Eshell ${cmd} substitution
Date: Wed, 04 Mar 2015 04:14:07 -0800 [thread overview]
Message-ID: <1425471247.1450.2@mail.samertm.com> (raw)
In-Reply-To: <83bnkaqdp9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Tue, Mar 3, 2015 at 7:54 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> Does this have any effect on the feature where Eshell can run several
> commands simultaneously via a shell-like pipe?
>
> Thanks.
I don't know what feature you're describing. Here is the output from
running regular pipes:
~ $ echo hello | /bin/echo there | /bin/echo hey | echo hi # Without
patch
hi
hey
~ $ echo hello | /bin/echo there | /bin/echo hey | echo hi # With patch
hi
hey
there
hello
First, we should ignore the fact that echo does nothing with stdin, and
the above commands print "hi" in bash. I do not understand why the
command without the patch only prints out "hey\nhi", but it printed
that consistently on my computer. The second output is incorrect (or at
the very least unexpected?), but less incorrect than the first. If this
is what you were talking about, then the commands may have appeared to
be simultaneous because they were racing, but I'm not sure if that's
intentional.
[-- Attachment #2: Type: text/html, Size: 1215 bytes --]
next prev parent reply other threads:[~2015-03-04 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 8:06 bug#12689: 24.2; Eshell ${cmd} substitution Aidan Gauland
2014-12-14 12:44 ` samer
2015-02-24 10:56 ` Samer Masterson
2015-03-03 15:54 ` Eli Zaretskii
2015-03-04 12:14 ` Samer Masterson [this message]
2015-03-04 17:38 ` Eli Zaretskii
2015-03-05 10:34 ` Samer Masterson
2015-04-06 3:41 ` Samer Masterson
2015-04-06 4:19 ` John Wiegley
2015-04-06 4:54 ` Samer Masterson
2022-02-09 9:12 ` Lars Ingebrigtsen
2022-02-09 19:01 ` Jim Porter
2022-02-09 20:12 ` Lars Ingebrigtsen
2022-05-03 3:52 ` Jim Porter
2022-05-03 10:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1425471247.1450.2@mail.samertm.com \
--to=samer@samertm.com \
--cc=12689@debbugs.gnu.org \
--cc=eliz@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 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.