From: Elijah Newren <newren@gmail.com>
To: Mike Ralphson <mike.ralphson@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [ANNOUNCE] EasyGit (eg) 0.97
Date: Fri, 30 Jan 2009 11:35:50 -0700 [thread overview]
Message-ID: <51419b2c0901301035g6867b9d8l2d4de9590035bd4e@mail.gmail.com> (raw)
In-Reply-To: <e2b179460901300859r438a4230hc990305688b4f29e@mail.gmail.com>
On Fri, Jan 30, 2009 at 9:59 AM, Mike Ralphson <mike.ralphson@gmail.com> wrote:
> 2009/1/30 Elijah Newren <newren@gmail.com>:
>> [5] The bug I can only occasionally trigger and which I don't know the
>> cause of yet: when exiting from eg log the terminal settings sometimes
>> are messed up (with echo off and such), requiring a "reset" to get the
>> terminal back to normal.
>
> Are you sure that isn't this bug in git.git ?
>
> pager: do wait_for_pager on signal death
> http://article.gmane.org/gmane.comp.version-control.git/106728
Interesting. I just went and tried out next (git version
1.6.1.2.418.gd79e6), which I believe has this patch...and after a
while I was still able to duplicate the eg bug on one of my
machines[1]. So it doesn't seem to be that particular issue, at
least.
Thanks for the pointer.
Elijah
[1] Output of stty after I trigger the eg/git bug:
speed 38400 baud; line=0;
lnext = <undef>; min = 1; time = 0;
-icrnl
-icanon -echo
next prev parent reply other threads:[~2009-01-30 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 16:42 [ANNOUNCE] EasyGit (eg) 0.97 Elijah Newren
2009-01-30 16:59 ` Mike Ralphson
2009-01-30 18:35 ` Elijah Newren [this message]
2009-01-30 19:47 ` Jeff King
2009-01-30 20:03 ` Jeff King
2009-01-30 20:22 ` Elijah Newren
2009-01-30 20:21 ` Elijah Newren
2009-01-30 20:29 ` Jeff King
2009-01-30 22:55 ` Elijah Newren
2009-01-31 7:25 ` Jeff King
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=51419b2c0901301035g6867b9d8l2d4de9590035bd4e@mail.gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=mike.ralphson@gmail.com \
--cc=peff@peff.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).