Re: Vi Guru..
- From: Stephen Andert <andert@xxxxxxxxx>
- To: bobmetelsky@xxxxxxxxxxx
- Date: Sun, 13 Feb 2005 08:19:04 -0700
Bob,
Sorry I didn't reply sooner, I was just catching up on the list.
A couple things come to mind.
1. you can set vi to be your default command mode. I'm not at work
right now, but I'm pretty certain the command is:
set -o vi
2. When using "vi mode", to get your previous command, <Esc>-K brings
up the last command. If you want the last command with "foo" in it,
<Esc>-K / foo [Enter]
Then to change foo to bar
s/foo/bar
And pressing [Enter] will run the newly revised command.
HTH
Stephen
On Fri, 11 Feb 2005 22:09:28 -0500, Bob Metelsky
<bobmetelsky@xxxxxxxxxxx> wrote:
> Vi Water Walkers
>
> In plain vanilla vi on tru 64, how does one access the the
> command/search history
> eg
> :1,$ s/this/that/g
> then
> :1,$ s/then/this/g
> go edit the search you have to retype the whole line
>
> apparently n is supposed to get the command history but it doesn't
> In VIM on Linux the command history is conveniently available using the
> up arrow
>
> vi on tru 64 gets all wigged out... making life very painful
>
> You have to be in edit mode even when your in the --> : search thingy
>
> any pain relief for vi on tru 64 shared with the same UID ?
>
> something in the way of ... set -o emacs
> set vi -lesspain
>
> TIA
> bob
>
> --
> "Oracle error messages being what they are, do not
> highlight the correct cause of fault, but will identify
> some other error located close to where the real fault lies."
>
> --
> //www.freelists.org/webpage/oracle-l
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
