[sclug] Vim Query

Glyn glynj at blueyonder.co.uk
Sat May 27 12:01:28 UTC 2006

> On Sat, 27 May 2006, Alex  wrote the following in response to my "Vim
> Query" posting:

> There's nothing magical about vi(m); it's just a boring text editor. If
> it's
> taking you two hours to make a simple edit, then it's obviously the wrong
> tool for you right now, and there's no shame in using an editor that you
> find easier to use; I've been using UNIX for 14 years and only know enough
> vi to repair damaged boot files if that's all I've got available. I do all
> my real text editing in more friendly editors ('joe' by choice, but I've
> used emacs and pico at times also, as well as various things under
> OpenLook).
> Best Regards,
> Alex.

Firstly many thanks for replying to my post Alex.

I guess that I may well have hit, early on in my GNU/Linux journey, a
problem which illustrates the efficacy of the unix way - use the right tool
for the job. However at the risk of appearing like a dog with a bone I have
a suspicion that I should be able to achieve the cut and paste/insert using
Vim. The impression I have formed from various sources on the web is that
learning Vim is a steep curve but well worth the climb so if anybody out
there can help me up the face here a little it would be much appreciated.

On Sat, 27 May 2006, ed  wrote the following in response to my "Vim
> Query" posting

>What I suspect happens when you paste your text, is that you paste it in
>command mode where vi reads parses the text you paste as if it were
>commands, until it finds a 'i' or 'o' and then operates in insert or
>overwrite mode, where the remainder of your input is displayed.

Thanks for the reply Ed.
I had figured along these lines the other night Ed but was still getting 
strange results even when in insert mode. However I was a little tired and 
frustrated t'other night and have just retried copy and paste in insert 
mode. I am still getting a strange result in that I am getting @ lines (as 
opposed to ~ lines) appearing on the screen. The @ lines seem to be empty in 
that they don't have line numbers. I thought I'd banished them by issuing 
the J command (join current line with next) but when I scrolled down and up 
the file they'd re-appeared. any ideas?


More information about the Sclug mailing list