All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brett Schwarz <brett_schwarz@yahoo.com>
To: "Shawn O. Pearce" <spearce@spearce.org>,
	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: Fri, 4 Apr 2008 10:58:06 -0700 (PDT)	[thread overview]
Message-ID: <488311.34417.qm@web38904.mail.mud.yahoo.com> (raw)


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

Just for the record, the correct keysym should be used, especially for "special" characters, as above (i.e. bracketleft). It's probably more of a fluke that \[ worked. Here's an exerpt from http://tcl.activestate.com/man/tcl8.4/TkCmd/bind.htm (note "Key" is synonymous with KeyPress):

"If the event type is KeyPress or KeyRelease, then detail may be specified in the form of an X keysym. Keysyms are textual specifications for particular keys on the keyboard; they include all the alphanumeric ASCII characters (e.g. ``a'' is the keysym for the ASCII character ``a''), plus descriptions for non-alphanumeric characters (``comma'' is the keysym for the comma character), plus descriptions for all the non-ASCII keys on the keyboard (``Shift_L'' is the keysym for the left shift key, and ``F1'' is the keysym for the F1 function key, if it exists). The complete list of keysyms is not presented here; it is available in other X documentation and may vary from system to system. If necessary, you can use the %K notation described below to print out the keysym name for a particular key. If a keysym detail is given, then the type field may be omitted; it will default to KeyPress. For example, <Control-comma> is equivalent to <Control-KeyPress-comma>."

HTH,
    --brett





      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

             reply	other threads:[~2008-04-04 18:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 17:58 Brett Schwarz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 13:43 [REGRESSION] git-gui André Goddard Rosa
2008-04-03 14:00 ` Jonathan del Strother
2008-04-03 21:04   ` Michele Ballabio
2008-04-03 23:15     ` Jonathan del Strother
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 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

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=488311.34417.qm@web38904.mail.mud.yahoo.com \
    --to=brett_schwarz@yahoo.com \
    --cc=andre_rosa@lge.com \
    --cc=barra_cuda@katamail.com \
    --cc=git@vger.kernel.org \
    --cc=maillist@steelskies.com \
    --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 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.