mike.irons@lynx.northeastern.edu (10/27/90)
What I proposed was to make elle use the arrow keyes et el WITH OUT THE USE OF .ELLEPRO IN ANY FORM. Build it into the DEFAULT system. I know you can add arrow key support by using a .ellepro file, it would be nice if you didn't HAVE to. Doing that TAKES AWAY THE FEATURE FROM THE KEY THAT HAD IT ORIGINALLY! This is the biggest complaint with people using it here, the arrow keys don't work like the emacs they use on the big system. You can't just change a few keys, you have to reset them all, and people don't want to go through the hassle of making bindings for all the keys, especially if they only want to change a few. Another suggestion would be a local change / init script that is read in be elle to rebind a few keys at startup. Sort of like a mini .ellepro or a save/restore setup command (where you could save buffer config etc. as well). Sorry to be-labor the point; mike.irons%lynx@heilos.northeastern.edu
tgcpwd@rwc.urc.tue.nl (Wim van Dorst) (10/28/90)
In article <34754@nigel.ee.udel.edu> mike.irons@lynx.northeastern.edu writes: > What I proposed was to make elle use the arrow keyes et el WITH OUT THE >USE OF .ELLEPRO IN ANY FORM. Build it into the DEFAULT system. I know you can >add arrow key support by using a .ellepro file, it would be nice if you didn't >HAVE to. Doing that TAKES AWAY THE FEATURE FROM THE KEY THAT HAD IT ORIGINALLY! The feature of the arrow keys is to move the cursor. By using the default .ellepro, which only one guru has to create, Elle does exactly that. Without any .ellepro.b1 file Elle works only half as good as possible. >This is the biggest complaint with people using it here, the arrow keys don't >work like the emacs they use on the big system. My arrow keys work exactly the same on all systems I use Emacs on, just as ^F, ^B, ^N and ^P work on all system alike. I was the guru and I made it that way. >You can't just change a few >keys, you have to reset them all, and people don't want to go through the >hassle of making bindings for all the keys, especially if they only want to >change a few. You can change only a few if you want to. Just make a small .ellepro.e file with the few adjustments in mind. I think it just as easy to see the complete list of definitions and twiggle with the few you want changed. >Another suggestion would be a local change / init script that is >read in be elle to rebind a few keys at startup. Sort of like a mini .ellepro >or a save/restore setup command (where you could save buffer config etc. as >well). What is the .ellepro.b1 if it is not completely that: a init script to be read in at startup in order to rebind a few keys? Now there are indeed a few points which could be improved. Like better use of the termcap file (eg for arrowkeys :-) or a little more speed (especially if you compare it with Elvis). > Sorry to be-labor the point; The point is not yet clear. As far as I can see it you only need one guru one time to set it up properly. For the rest everybody (it's dead easy) can handle all the twiggling she wants. Now where is the problem? Met vriendelijke groeten, Wim -b-b- van Dorst -- --------------------------------------------------------------------- Blue Baron = Wim van Dorst, Voice (+31) 074-443937, (+31) 02152-42319 (-: baron@wiesje.hobby.nl tgcpwd@urc.tue.nl :-) ---------------------------------------------------------------------