From: David Hansen <david.hansen@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: eshell pipelines
Date: Wed, 13 Aug 2008 23:01:32 +0200 [thread overview]
Message-ID: <87ljz0fx3n.fsf@localhorst.mine.nu> (raw)
In-Reply-To: 74r68s6gnw.fsf@fencepost.gnu.org
On Wed, 13 Aug 2008 12:09:07 -0400 Glenn Morris wrote:
> David Hansen wrote:
>
>> [For emacs-devel:
>>
>> In gnu.emacs.help there is a discussion about some little eshell,
>> eshell/ls bug.
>
> http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=699
>
> (now on three separate mailing lists...)
I find gmane.emacs.bug incredible "hard" to read. Threads seem to
randomly stop and start again (w/o gnus finding the parents) and purely
administrative messages pop up every now and then.
Back to the topic: not giving the pipelined processes a TTY will
prevent similar problems w/ non eshell builtins. And in most cases it
should be faster as well, e.g. GNU libc uses line buffering on a TTY.
But probably we should first find a way to disable this for the last
command in the pipeline. This is already done in
`eshell-do-pipelines-synchronously' (do we really need compat code for
Emacsen w/o `start-process'?). I'll try to figure out how to do it
right.
David
next prev parent reply other threads:[~2008-08-13 21:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16366.1218454746.18990.help-gnu-emacs@gnu.org>
2008-08-11 13:30 ` Optimal emacs shell for coding Xah
2008-08-11 15:24 ` Lennart Borgman (gmail)
[not found] ` <mailman.16375.1218468298.18990.help-gnu-emacs@gnu.org>
2008-08-11 15:49 ` Xah
2008-08-11 16:47 ` Lennart Borgman (gmail)
[not found] ` <mailman.16385.1218473260.18990.help-gnu-emacs@gnu.org>
2008-08-12 8:06 ` Tim X
2008-08-12 12:06 ` Lennart Borgman (gmail)
2008-08-12 18:33 ` Eli Zaretskii
2008-08-12 18:40 ` Lennart Borgman (gmail)
2008-08-12 18:52 ` Eli Zaretskii
2008-08-12 19:02 ` Lennart Borgman (gmail)
2008-08-12 19:11 ` ken
2008-08-12 19:28 ` Lennart Borgman (gmail)
2008-08-12 19:16 ` Eli Zaretskii
[not found] ` <mailman.16490.1218568567.18990.help-gnu-emacs@gnu.org>
2008-08-13 1:01 ` Chris F.A. Johnson
2008-08-13 8:20 ` Tim X
2008-08-13 11:21 ` Thierry Volpiatto
2008-08-13 12:21 ` eshell pipelines (Was: Re: Optimal emacs shell for coding) David Hansen
2008-08-13 13:15 ` eshell pipelines Thierry Volpiatto
2008-08-13 16:09 ` Glenn Morris
2008-08-13 21:01 ` David Hansen [this message]
2008-08-12 18:30 ` Optimal emacs shell for coding Eli Zaretskii
2008-08-12 19:14 ` David Hansen
[not found] ` <mailman.16492.1218569015.18990.help-gnu-emacs@gnu.org>
2008-08-12 20:08 ` Rupert Swarbrick
2008-08-11 19:18 ` Eli Zaretskii
2008-08-12 8:02 ` Tim X
2008-08-15 9:38 ` M-x terminal-emulator vs M-x term (was: Re: Optimal emacs shell for coding) Jonathan Groll
2008-08-11 13:40 ` Optimal emacs shell for coding Mike Treseler
2008-08-11 16:44 ` weber
2008-08-12 6:33 ` Mike Treseler
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=87ljz0fx3n.fsf@localhorst.mine.nu \
--to=david.hansen@gmx.net \
--cc=emacs-devel@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.