From: Jeff King <peff@peff.net>
To: Elijah Newren <newren@gmail.com>
Cc: Mike Ralphson <mike.ralphson@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] EasyGit (eg) 0.97
Date: Fri, 30 Jan 2009 14:47:27 -0500 [thread overview]
Message-ID: <20090130194727.GA31927@coredump.intra.peff.net> (raw)
In-Reply-To: <51419b2c0901301035g6867b9d8l2d4de9590035bd4e@mail.gmail.com>
On Fri, Jan 30, 2009 at 11:35:50AM -0700, Elijah Newren 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.
There is also a related set of fixes for spawning externals via fork,
which fixes a bug with the pager not getting cleaned up. But it looks
like it is also in the version you tested.
Can you give a more complete recipe for reproducing? Since I was just
touching this area in git, I want to make sure it isn't a git bug you
are triggering. :)
As an aside, I found some related weirdness. In my git repo, if I do
this:
$ git checkout next
$ eg log -p
I get log output, but the diff is not colorized (and I have color.diff
set to "auto" in my ~/.gitconfig). But if I detach my HEAD and show the
log:
$ git checkout next^0
$ eg log -p
then I _do_ get color in the patch. I also get this error:
Use of uninitialized value $branch in concatenation (.) or string at
/home/peff/eg line 2854.
eg: command (git rev-parse refs/heads/) failed
eg: received signal 13
The error is easy to explain. The offending code is:
my $branch = RepoUtil::current_branch();
my ($ret, $revision) =
ExecUtil::execute_captured("git rev-parse refs/heads/$branch");
So it is clear that you just need to handle the case of there being no
current branch. But the color thing is certainly exotic. :)
-Peff
next prev parent reply other threads:[~2009-01-30 19:49 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
2009-01-30 19:47 ` Jeff King [this message]
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=20090130194727.GA31927@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=mike.ralphson@gmail.com \
--cc=newren@gmail.com \
/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).