> John Gellene wrote:
> > 1. Click in the table cell for "Primary Shortcut" or
> "Alternative Shortcut"
> > and the relevant command or macro. You should see a dialog
> window with a
> > read-only text field.
> My jEdit (3.02 on WinNT) only has 'Command' and 'Keyboard Shortcut.'
> Slava said a while back that you could provide two shortcuts for a
> binding but never described how to do that. Is this something new in the
> 3.1pre versions?
Yes -- see below
> > 2. For each element of your shortcut, type the desired key or
> keys as you
> > would while typing in the main window. If you want '4' on the
> number pad,
> > type Shift+Numpad4 or whatever you normally do to cause the
> number pad to
> > produce '4'. Same thing with Alt and Ctrl key combinations. Don't try
> > "TAB" or Ctrl+I; Java will grab them as requests to change
> focus and "TAB"
> > is hard-coded in jEdit anyway.
> This also doesn't work. I have to type in the values by hand.
> > I just tried "NUMPAD4" and "A+NUMPAD4" and they work.
> Finally, it would be nice if all of these were listed in a reference in
> the manual somewhere.
> Jeremy Wadsack
> Wadsack-Allen Digital Group
Tod and I have been talking past each other because I was describing the
procedure on 3.1. It's a lot easier to use than 3.0. I downloaded 3.0.2
and saw the differences. You must manually type the shortcut combo.
Here are combinations that work (there may be more, but unprefixed ASCII
keys do not work):
F-keys (e.g., 'F5')
LEFT, RIGHT, UP, DOWN, HOME, END
Unfortunately, an invalid assignment is not deleted from the table. It
remains in the one-column table without replacing the old assignment during
the editing session. When jEdit is restarted, the bogus assignment remains
visible in the table but the old assignment no longer functions.
Version 3.1 makes this process a whole lot easier (and yes, you can assign
to NUMPAD4). In general, the pre-release itself is very stable; the only
major issues I encounter in using it arise where the application API has
changed and a plugin hasn't caught up. Usually the plugin author or
somebody else posts a interim jar file or patch to take care of that.
Sorry for all the confusion.