From: Johannes Sixt <j.sixt@viscovery.net>
To: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Cc: Aaron Plattner <aplattner@nvidia.com>,
git@vger.kernel.org, jkain@nvidia.com
Subject: Re: [PATCH] checkout: add a space between the commit and "..."
Date: Wed, 29 Sep 2010 09:20:39 +0200 [thread overview]
Message-ID: <4CA2E8C7.4040100@viscovery.net> (raw)
In-Reply-To: <tNUxsuXC1ZklaaYn-pkW6hae44B_tB2hStuto66EU4k9w2Q79GA6LQ@cipher.nrlssc.navy.mil>
Am 9/29/2010 0:40, schrieb Brandon Casey:
> 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
You must be running an xterm with settings from the stone ages. I had the
impression that modern installations have the selection configured such
that a file path can be selected with a mere double-click, without
dragging. For this, the dot must be in the same class as letters and
digits. Just for reference (I don't know how to read this):
$ appres XTerm | grep charClass
*charClass: 33:48,37:48,43:48,45-47:48,64:48,126:48,95:48
That said, I welcome this change, though I'd just have dropped ... or
replaced with a colon (preference for the second).
-- Hannes
next prev parent reply other threads:[~2010-09-29 7:22 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
2010-09-29 0:45 ` Brandon Casey
2010-09-29 7:20 ` Johannes Sixt [this message]
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=4CA2E8C7.4040100@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=aplattner@nvidia.com \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=jkain@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.