Re: Strange ksh history behaviour

2013-01-07 Thread Andres Perera
I've been using a patch I made months ago. I haven't submitted it to tech@ since I believe people actually want to keep it. I can't post it at the moment because it's just on the CVS checkout and I have other ksh changes that I have to split first.

Re: Strange ksh history behaviour

2013-01-07 Thread john slee
On 8 January 2013 03:56, Jan Stary wrote: > e.g. mutt: > > EDITOR Specifies the editor to use if VISUAL is unset. > VISUAL Specifies the editor to use when composing messages. If in vi mode and have set $VISUAL, it will be used when you press v to edit the commandline in an editor. At least

Re: Strange ksh history behaviour

2013-01-07 Thread Chris Bennett
On Mon, Jan 07, 2013 at 05:56:00PM +0100, Jan Stary wrote: > On Jan 07 14:36:53, s...@spacehopper.org wrote: > > On 2013-01-07, Sébastien Marie wrote: > > >> What am I missing here? Can someone confirm this? > > > > > > You need to set your command-line editing mode to "emacs". > > > > > > In orde

Re: Strange ksh history behaviour

2013-01-07 Thread Jan Stary
On Jan 07 14:36:53, s...@spacehopper.org wrote: > On 2013-01-07, Sébastien Marie wrote: > >> What am I missing here? Can someone confirm this? > > > > You need to set your command-line editing mode to "emacs". > > > > In order to keep EDITOR to vi, you should set VISUAL to "emacs" in your > > .pr

Re: Strange ksh history behaviour

2013-01-07 Thread Lars von den Driesch
Hi, On Mon, Jan 7, 2013 at 2:54 PM, Sébastien Marie wrote: > It is the documented behaviour in ksh(1) :-) > > You could see the EDITOR variable comment in ksh(1): Well, what can I say :-) It was late and I was tired or my english is crap and didn't understand... ;-) > > EDITOR >If the VISU

Re: Strange ksh history behaviour

2013-01-07 Thread Alexander Polakov
* Anthony J. Bentley [130107 18:44]: > Stefan Sperling writes: > > On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: > > > However, I like vim and as soon as I set the EDITOR env variable to it > > > the "arrow up/down" functionality is gone. In fact even if EDITOR is > > > set

Re: Strange ksh history behaviour

2013-01-07 Thread Stuart Henderson
On 2013-01-07, Sébastien Marie wrote: >> What am I missing here? Can someone confirm this? > > You need to set your command-line editing mode to "emacs". > > In order to keep EDITOR to vi, you should set VISUAL to "emacs" in your > .profile: > > VISUAL=emacs > EDITOR=vi > export VISUAL EDITOR Ma

Re: Strange ksh history behaviour

2013-01-07 Thread Bruno Flueckiger
On 07.01.2013 14:54, Sébastien Marie wrote: In order to keep EDITOR to vi, you should set VISUAL to "emacs" in your .profile: VISUAL=emacs EDITOR=vi export VISUAL EDITOR Thanks a lot. You just solved one of those small problems I've had for years on all my OpenBSD systems. It was a pain in

Re: Strange ksh history behaviour

2013-01-07 Thread Anthony J. Bentley
Stefan Sperling writes: > On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: > > However, I like vim and as soon as I set the EDITOR env variable to it > > the "arrow up/down" functionality is gone. In fact even if EDITOR is > > set with "export EDITOR=" the functionality is gone

Re: Strange ksh history behaviour

2013-01-07 Thread Sébastien Marie
On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: > Hello, > > I just discovered a strange behaviour with ksh-history that I cannot > explain. So I hope you can probably help. I read some man pages and > used google but didn't find anything useful. If this is is just a RTFM > p

Re: Strange ksh history behaviour

2013-01-07 Thread Stefan Sperling
On Mon, Jan 07, 2013 at 02:09:01PM +0100, Lars von den Driesch wrote: > However, I like vim and as soon as I set the EDITOR env variable to it > the "arrow up/down" functionality is gone. In fact even if EDITOR is > set with "export EDITOR=" the functionality is gone. Commands typed in > still appe