Re: jed in a pipe :-)

[Jörg Sommer <joerg@xxxxxxxxxxxx>]

Hello Marc,

Marc Haber <mh+jed-users@xxxxxxxxxxxx> wrote:
> On Tue, Oct 10, 2006 at 12:18:02AM -0400, John E. Davis wrote:
>> In this case, xargs is jed's parent process.  By pressing ^G, you end
>> up sending it SIGINT causing xargs to die leaving jed an orphaned
>> process unable to access its controlling terminal.  When jed tries to
>> read from the terminal (/dev/tty), the read fails with errno set to
>> EIO.  Jed then exits with an error message and, in the process,
>> attempts to reset the terminal. This again fails and sets EIO to -1.
>> Unfortunately I see no workaround other than to disable this use
>> altogether, which I do not want to do.  For this reason, I do not
>> regard this as a jed bug.
>
> Agreed. This should, however, be documented for jed.

Why? It's a misusage and many other programs behave like jed.

echo http://www.test.de/ | xargs lynx
echo 1 | xargs top -p

Bye, Jörg.
-- 
“Unfortunately, the current generation of mail programs do not have
 checkers to see if the sender knows what he is talking about”
         -- Andrew S. Tanenbaum

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.