git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonathan del Strother" <maillist@steelskies.com>
To: "Michele Ballabio" <barra_cuda@katamail.com>, spearce@spearce.org
Cc: git@vger.kernel.org, "André Goddard Rosa" <andre_rosa@lge.com>
Subject: Re: [REGRESSION] git-gui
Date: Fri, 4 Apr 2008 00:15:39 +0100	[thread overview]
Message-ID: <57518fd10804031615m5c299df6hf31de3c689e16521@mail.gmail.com> (raw)
In-Reply-To: <200804032304.17054.barra_cuda@katamail.com>

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:
>  > > Hi, all!
>  > >
>  > >     After updating to git version 1.5.5.rc3 I always get the error below
>  > >  when starting "git gui".
>  > >     Linux distributions used are opensuse 10 and opensuse Factory.
>  > >
>  > >  # git gui
>  > >  Error in startup script: bad event type or keysym "["
>  > >     while executing
>  > >  "bind $ui_comm <$M1B-Key-\[> {show_less_context;break}"
>  > >     file "/usr/bin/git-gui" linux 2718)
>  > >
>  > >     I think it's related to git-gui 0.10 recently added into the tree.
>  >
>  > Doh, I broke git :(
>  >
>  > The problem is in c91ee2bd61 (Add shortcut keys for Show More/Less Context).
>  > Works fine on my OS X 10.5 installation with tcl 8.4.7 - can anyone
>  > suggest an alternative way of binding the left/right brackets?  I'm
>  > not familiar with Tcl, and didn't manage to find a list of key names.
>
>  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).
>
>  See
>         man keysyms
>  for a list of key names.
>

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?)

  reply	other threads:[~2008-04-03 23:16 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 [this message]
2008-04-04  1:27       ` Shawn O. Pearce
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=57518fd10804031615m5c299df6hf31de3c689e16521@mail.gmail.com \
    --to=maillist@steelskies.com \
    --cc=andre_rosa@lge.com \
    --cc=barra_cuda@katamail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).