From: Aaron Plattner <aplattner@nvidia.com>
To: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>, Joe Kain <JKain@nvidia.com>
Subject: Re: [PATCH] checkout: add a space between the commit and "..."
Date: Tue, 28 Sep 2010 16:38:32 -0700 [thread overview]
Message-ID: <20100928233832.GA20224@soprano.nvidia.com> (raw)
In-Reply-To: <tNUxsuXC1ZklaaYn-pkW6hae44B_tB2hStuto66EU4k9w2Q79GA6LQ@cipher.nrlssc.navy.mil>
On Tue, Sep 28, 2010 at 03:40:11PM -0700, Brandon Casey wrote:
> On 09/28/2010 05:23 PM, Aaron Plattner wrote:
> > Switching to a detached head prints something like
> >
> > HEAD is now at 9d14017... dir.c: squelch false uninitialized memory warning
> >
> > These dots get selected when you double-click on the abbreviated
> > commit hash, which makes it annoying to copy and paste.
>
> This must be another gnome-terminal/konsole "innovation".
>
> xterm still does the "right thing"(tm) _and_ it doesn't eat my
> alt keystrokes like alt-b to move the cursor back a word. /rant
How is your xterm configured? On my stock Ubuntu 9.10 system, it doesn't
do the "right thing"... the dots are selected. Gvim gets it right.
Also, Alt-B appears to work fine in gnome-terminal. I don't have Konsole
to try.
-- Aaron
next prev parent reply other threads:[~2010-09-28 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 22:23 [PATCH] checkout: add a space between the commit and "..." Aaron Plattner
2010-09-28 22:40 ` Brandon Casey
2010-09-28 23:34 ` Kevin Ballard
2010-09-28 23:38 ` Aaron Plattner [this message]
2010-09-29 0:45 ` Brandon Casey
2010-09-29 7:20 ` Johannes Sixt
2010-09-29 13:13 ` Brandon Casey
2010-09-29 21:48 ` Andreas Schwab
2010-09-29 1:49 ` Santi Béjar
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=20100928233832.GA20224@soprano.nvidia.com \
--to=aplattner@nvidia.com \
--cc=JKain@nvidia.com \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
/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).