From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jonathan del Strother <maillist@steelskies.com>
Cc: "Michele Ballabio" <barra_cuda@katamail.com>,
git@vger.kernel.org, "André Goddard Rosa" <andre_rosa@lge.com>
Subject: Re: [REGRESSION] git-gui
Date: Thu, 3 Apr 2008 21:27:23 -0400 [thread overview]
Message-ID: <20080404012723.GL10274@spearce.org> (raw)
In-Reply-To: <57518fd10804031615m5c299df6hf31de3c689e16521@mail.gmail.com>
Jonathan del Strother <maillist@steelskies.com> wrote:
> On Thu, Apr 3, 2008 at 10:04 PM, Michele Ballabio
> <barra_cuda@katamail.com> wrote:
> > On Thursday 03 April 2008, Jonathan del Strother wrote:
> > > On Thu, Apr 3, 2008 at 2:43 PM, André Goddard Rosa <andre_rosa@lge.com> wrote:
> > > >
> > > > # git gui
> > > > Error in startup script: bad event type or keysym "["
> > > > while executing
> > > > "bind $ui_comm <$M1B-Key-\[> {show_less_context;break}"
> > >
> > > Doh, I broke git :(
You and me both Jonathan. I tested it on both Mac OS X and Win32,
and on Tcl/Tk 8.4.1, 8.4.10, 8.4.15, and 8.5.0. Never ran into
this failure. So the original poster must be running 8.4.0, and
8.4.0 must not support this binding. Added in 8.4.1? *sigh*
> > These changes should help (haven't tried):
> > \[ -> bracketleft
> > \] -> bracketright
> > but some European keyboards do not have easy access to brackets, so
> > other keys would be preferable (comma and period, for example, or 1 and 2).
>
> Anyone else got any opinions on an appropriate shortcut? How about
> '=' and '-' (+ and - without the shift), or are those not necessarily
> together either? (Are there really layouts where '[' and ']' aren't
> next to each other?)
I don't know, [ and ] seem reasonable to me. Git is mostly a source
code control system. A lot of languages use [ and ] as part of
their syntax. If you are typing on a keyboard that is difficult to
access these keys on, you are probably already used to contorting
your fingers. :-|
I wrote up a patch today based on Michele's suggested change.
It works everywhere I can test, but I don't have an 8.4.0
installation like the original poster.
Unless someone posts a patch to change the keys away from [ and ]
I say leave them as-is. But I'm willing to entertain a change if
someone who cares writes a patch for it.
--
Shawn.
next prev parent reply other threads:[~2008-04-04 1:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:43 [REGRESSION] git-gui André Goddard Rosa
2008-04-03 14:00 ` Jonathan del Strother
2008-04-03 14:34 ` RES: " André Goddard Rosa
2008-04-03 21:04 ` Michele Ballabio
2008-04-03 23:15 ` Jonathan del Strother
2008-04-04 1:27 ` Shawn O. Pearce [this message]
2008-04-04 1:33 ` Shawn O. Pearce
2008-04-04 11:02 ` Marco Roeland
2008-04-04 11:20 ` RES: " André Goddard Rosa
2008-04-04 21:04 ` Michele Ballabio
2008-04-05 4:01 ` Shawn O. Pearce
2008-04-07 7:38 ` David Kågedal
2008-04-07 8:10 ` Teemu Likonen
2008-04-08 2:18 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2008-04-04 17:58 Brett Schwarz
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=20080404012723.GL10274@spearce.org \
--to=spearce@spearce.org \
--cc=andre_rosa@lge.com \
--cc=barra_cuda@katamail.com \
--cc=git@vger.kernel.org \
--cc=maillist@steelskies.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).