Eric Blake redhat.com> writes:
> And can this possibly be related to the previously reported issue where
> bash's choice of terminal control functions would cause execution of
> gitk as a background process to exit bash?
>
If I start mintty with vt100 as the termtype, then the problem seems to
On 12/08/2010 10:28 AM, Christopher Faylor wrote:
>> After ctrl+C during a grep which is redirecting output to a file:
>>
>> $ speed 38400 baud; line = 0;
>> start = ; stop = ; lnext = ; min = 1; time = 0;
>> -icrnl -imaxbel
>> -icanon -echo -echoe -echok -echoctl -echoke
>
> Can anyone duplicate
On Wed, Dec 08, 2010 at 04:06:35PM +, TJ Anthony wrote:
>Andy Koppe gmail.com> writes:
>
>>
>> On 2 December 2010 20:28, Heath Kehoe wrote:
>> >> FWIW, I can't reproduce this, even if I kill the tail or less with
>> >> SIGKILL, thus giving them no chance to do any cleanup. (I assume you
>> >>
Andy Koppe gmail.com> writes:
>
> On 2 December 2010 20:28, Heath Kehoe wrote:
> >> FWIW, I can't reproduce this, even if I kill the tail or less with
> >> SIGKILL, thus giving them no chance to do any cleanup. (I assume you
> >> use 'less -K' to allow it to be ctrl-c'ed?)
> >>
> >> Which shell
On 2 December 2010 20:49, Illia Bobyr wrote:
> On 12/2/2010 2:28 PM, Heath Kehoe wrote:
>> [...]
>> Also, the OP said the problem was happening on pipelines like 'tail | grep'.
>> Neither tail nor grep muck with tty settings (that I know of), so if the tty
>> is ending up with echo disabled, it's
On 2 December 2010 20:28, Heath Kehoe wrote:
>> FWIW, I can't reproduce this, even if I kill the tail or less with
>> SIGKILL, thus giving them no chance to do any cleanup. (I assume you
>> use 'less -K' to allow it to be ctrl-c'ed?)
>>
>> Which shell do people who've seen the problem use? Is it an
Spiro Trikaliotis-12 wrote:
>
> Hello,
>
> * On Thu, Dec 02, 2010 at 12:51:22PM -0600 Thrall, Bryan wrote:
>> Charles Wilson wrote on 2010-12-02:
>> > On 12/2/2010 1:27 PM, David Rothenberger wrote:
>> >> Illia Bobyr wrote:
>> >>> On 12/1/2010 8:53 PM, David Rothenberger wrote:
>> Try typ
Heath Kehoe wrote on 2010-12-02:
> On Dec 2, 2010, at 1:59 PM, Andy Koppe wrote:
>> On 2 December 2010 18:40, Charles Wilson wrote:
>>> On 12/2/2010 1:27 PM, David Rothenberger wrote:
Illia Bobyr wrote:
> On 12/1/2010 8:53 PM, David Rothenberger wrote:
>> Try typing "reset" or "stty s
On 12/2/2010 2:28 PM, Heath Kehoe wrote:
> [...]
> Also, the OP said the problem was happening on pipelines like 'tail | grep'.
> Neither tail nor grep muck with tty settings (that I know of), so if the tty
> is ending up with echo disabled, it's got to be the shell leaving it that
> way. Perhap
On Dec 2, 2010, at 1:59 PM, Andy Koppe wrote:
> On 2 December 2010 18:40, Charles Wilson wrote:
>> On 12/2/2010 1:27 PM, David Rothenberger wrote:
>>> Illia Bobyr wrote:
On 12/1/2010 8:53 PM, David Rothenberger wrote:
> Try typing "reset" or "stty sane" (without the quotes) and pressing
On 2 December 2010 18:40, Charles Wilson wrote:
> On 12/2/2010 1:27 PM, David Rothenberger wrote:
>> Illia Bobyr wrote:
>>> On 12/1/2010 8:53 PM, David Rothenberger wrote:
Try typing "reset" or "stty sane" (without the quotes) and pressing
Enter. You won't see what you're typing, but afte
On 2 December 2010 18:51, Thrall, Bryan wrote:
> Charles Wilson wrote on 2010-12-02:
>> On 12/2/2010 1:27 PM, David Rothenberger wrote:
>>> Illia Bobyr wrote:
On 12/1/2010 8:53 PM, David Rothenberger wrote:
> Try typing "reset" or "stty sane" (without the quotes) and pressing
> Enter.
Hello,
* On Thu, Dec 02, 2010 at 12:51:22PM -0600 Thrall, Bryan wrote:
> Charles Wilson wrote on 2010-12-02:
> > On 12/2/2010 1:27 PM, David Rothenberger wrote:
> >> Illia Bobyr wrote:
> >>> On 12/1/2010 8:53 PM, David Rothenberger wrote:
> Try typing "reset" or "stty sane" (without the quot
Charles Wilson wrote on 2010-12-02:
> On 12/2/2010 1:27 PM, David Rothenberger wrote:
>> Illia Bobyr wrote:
>>> On 12/1/2010 8:53 PM, David Rothenberger wrote:
Try typing "reset" or "stty sane" (without the quotes) and pressing
Enter. You won't see what you're typing, but after the shell
On 12/2/2010 1:27 PM, David Rothenberger wrote:
> Illia Bobyr wrote:
>> On 12/1/2010 8:53 PM, David Rothenberger wrote:
>>> Try typing "reset" or "stty sane" (without the quotes) and pressing
>>> Enter. You won't see what you're typing, but after the shell should work
>>> again.
>>
>> Would you, pl
Illia Bobyr wrote:
> On 12/1/2010 8:53 PM, David Rothenberger wrote:
>> orbita wrote:
>>> hi,
>>> I've been experiencing this problem for quite some time. Whenever I do a
>>> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
>>> can't type in new commands to the command p
On 12/1/2010 8:53 PM, David Rothenberger wrote:
> orbita wrote:
>> hi,
>> I've been experiencing this problem for quite some time. Whenever I do a
>> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
>> can't type in new commands to the command prompt anymore.
>>
>> All I
On 12/1/2010 8:53 PM, David Rothenberger wrote:
> orbita wrote:
>> hi,
>> I've been experiencing this problem for quite some time. Whenever I do a
>> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
>> can't type in new commands to the command prompt anymore.
>>
>> All I
orbita wrote:
>
> hi,
> I've been experiencing this problem for quite some time. Whenever I do a
> tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
> can't type in new commands to the command prompt anymore.
>
> All I could do is close that window and open another cyg
hi,
I've been experiencing this problem for quite some time. Whenever I do a
tail (eg. "tail -f abc.txt | grep abc"), and then Ctrl-C to exit the tail, I
can't type in new commands to the command prompt anymore.
All I could do is close that window and open another cygwin session.
Can anybody he
20 matches
Mail list logo
