Thread View: gnu.bash.bug
2 messages
2 total messages
Started by Steven Grady
Tue, 14 Nov 1989 06:38
slight readline modification
Author: Steven Grady
Date: Tue, 14 Nov 1989 06:38
Date: Tue, 14 Nov 1989 06:38
34 lines
2208 bytes
2208 bytes
First thing I want to say is that I'm way impressed with the input
editing features of bash (ie the readline library). I'm very appreciative
of the work that went into making a good vi mode, especially. And it
even has multiple undo! Now, on to the suggestions...
I currently use tcsh, and one thing it does that bash's readline doesn't
is put the cursor at the _end_ of the line when you start moving through
the history (in either vi or emacs mode). Having the cursor at the end
is slightly better since you're more likely to be editing the arguments
of an input line, or adding a redirection, than changing the program itself.
(At least that's true with me.) Either method fits within the editing
paradigm (if you look at it as though the cursor is at the end of the
current (empty) line before you start editing). Perhaps it can be
configurable in the .inputrc?
While I'm here, how about if the display of the '*' at the beginning
of modified history lines could be turned off. Emacs users may be
used to it, but vi users aren't, and even when I use the emacs mode,
I find it kind of distracting. The same goes for the current arg count.
Oh, and one more thing I suggested before but didn't see any response to.
Tcsh's prompt allows you to have something that's like bash's "\W"
(ie show only the tail of the current directory), but it also presents
your home directory as '~' (like the polite_directory_format of "\w"
in bash). I'd like to see this in bash. (If you want a new character,
perhaps "\.", which is similar to what tcsh uses ("%.")).
As Bartles and Jaymes say, "Thank you for your support".
Steven
...!ucbvax!grady
grady@postgres.berkeley.edu
"...just when I had you wriggling in the crushing grip of reason, too..."
Re: slight readline modification
Author: Jeff Sparkes
Date: Wed, 15 Nov 1989 12:26
Date: Wed, 15 Nov 1989 12:26
30 lines
2082 bytes
2082 bytes
>>>>> On 14 Nov 89 06:38:18 GMT, grady@fxgrp.fx.com (Steven Grady) said: grady> First thing I want to say is that I'm way impressed with the grady> input editing features of bash (ie the readline library). I'm grady> very appreciative of the work that went into making a good vi grady> mode, especially. And it even has multiple undo! Now, on to grady> the suggestions... Actually, multiple undos are a sort of side effect. Both multiple and vi style will be in my next bunch. I've even added undoable undos. grady> I currently use tcsh, and one thing it does that bash's grady> readline doesn't is put the cursor at the _end_ of the line grady> when you start moving through the history (in either vi or grady> emacs mode). Having the cursor at the end is slightly better grady> since you're more likely to be editing the arguments of an grady> input line, or adding a redirection, than changing the program grady> itself. (At least that's true with me.) Either method fits grady> within the editing paradigm (if you look at it as though the grady> cursor is at the end of the current (empty) line before you grady> start editing). Perhaps it can be configurable in the grady> .inputrc? Well, it's currently done the way that ksh does it, which is what *I* expect. Shouldn't be too hard to add a variable. It does have to go in the .inputrc, and not be yet another magic shell variable. -- Jeff Sparkes jeff1@garfield.mun.edu || uunet!garfield!jeff1 Humans couldn't have invented golf without alien intervention--Kids in the Hall
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads