[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: unfinished command executed when TTY is closed
From: |
Chet Ramey |
Subject: |
Re: unfinished command executed when TTY is closed |
Date: |
Thu, 18 Dec 2014 10:42:59 -0500 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 12/17/14, 4:08 PM, Steve Simmons wrote:
>
> On Dec 17, 2014, at 3:23 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
>
>> On Wed, Dec 17, 2014 at 03:16:53PM -0500, Steve Simmons wrote:
>>> Advance apologies if I'm misunderstanding, but the described bug looks like
>>> reasonable behavior to me.
>>
>> It would be more reasonable for bash (or ssh, I'm not sure at what level
>> this handling should occur) to discard the partially typed line. Not
>> to execute it.
>
> You're right - I'd missed the fact that the user hadn't completed typing the
> command when the session dropped. My error.
The real question is the circumstances under which read will return EOF
without SIGHUP being delivered, and whether readline can reliably detect
those circumstances.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
Re: unfinished command executed when TTY is closed, Piotr Grzybowski, 2014/12/18