guy keren wrote:
>>
>>* Is jed the editor you settled on?
>>
>>
>
>yes. that'll be the editor.
>
>
I gave it a try.
It seems good enough (fast, on-screen keyboard tips & menus, has python
highlighting), and feels surprisingly natural to me (I guess that's
because it comes with emacs emulation mode turned on by default...).
The default keybinding also has the arrows, pageup and pagedown keys
mapped correctly.
One thing I thought would be useful to beginners (and took me *way* too
much time to find out how to do), is setting the Home & End keys to
behave nice as well (not that there's anything wrong with ^a and ^e, but
I suppose nowadays people would expect keys to act according to their
label).
So, hoping this might save precious time for other people - I'll
describe what finally worked for me (might be a bit different for other
distros, but hopefully can get you started on keybinding).
* First thing to do is locate the system jed.rc and copy it to ~/.jedrc
(In Debian it's in /usr/share/jed/lib/jed.rc )
This is because if you just setup a clean ~/.jedrc, it would not run
the original file, and stick to the raw jed defaults - which are not
very friendly.
(On the other hand, if your'e sysadmin and think "you know best" for
your users - youre welcome to just edit it inplace).
* At the beginning of the file add
require ("keydefs");
This is a module which magicly defines some keyboard constants - such
as Key_Home and Key_End.
If you don't have it in your jed distro, you can determine the key
codes from inside jed. Type:
ESC-x quoted_insert <Enter>,
then press the "Home" or "End" key to have the key code inseted into
your buffer. The major problem with this method is that the correct key
codes depend on your terminal type - it's different in xterm than in a
console.
* Somewhere else in the .jedrc, add:
setkey ("beg_of_line", Key_Home);
setkey ("eol_cmd", Key_End);
save the .jedrc, and restart jed...
