[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: Nvi recovery program please shove off

In what was is vimdiff stunnning?

Should one open vimdiff with two files that are close to identical, all the
large sections which are identical will be automaticall collapsed, and the
remaining areas are coloored to indicate the differences, including helping
you to the point in the line where the difference begins.

Ctrl-W Ctrl-W seems to skip between windows.

Once you are there
:help vimdiff
will introduce you to the vim documentation on it (considerably more
verbose, but also leaving many more unanswered questions)

works, also, to get a feel for how VIM's documentation works

Best o' Luck

/bin/ed indeed.

-----Original Message-----
From: Pigeon [mailto:jah.pigeon@ukonline.co.uk] 
Sent: Tuesday, December 17, 2002 10:42 PM
To: debian-user@lists.debian.org
Subject: Re: Nvi recovery program please shove off

On Tue, Dec 17, 2002 at 03:45:18PM -0500, sean finney wrote:
> heya
> looking at the script that's producing this (/etc/init.d/nviboot), it 
> seems that the directory you want to look at is /var/tmp/vi.recover. 
> anything in there?
> 	sean

Ah-HA! Yes. There it was! Two files, named recover.a00396 and vi.a00396 - no
wonder the find didn't show anything. Just deleted them, and ran the script
by hand for a check. No annoying messages. Thanks!

On Tue, Dec 17, 2002 at 15:41:44 -0500, Narins, Josh wrote:
> Hi Pigeon,
> 	Does your `find` find dot files?

(experiments) WHEEE!! Thanks for that. No, it doesn't. Not the problem here,
but might well be somewhere else in the future. Useful to know. Whenever
I've needed to find a dot file so far I've known what directory to look in,
so ls -a does the trick.

> 	I use another vi-clone, vim, which saves the temporary files as 
> .filename.swp
> 	vimdiff (part of the vim package) is really quite stunning, and 
> perhaps a reason to learn VI

Tell me more - in what way is it stunning?

My first ever contact with vi was on my first ever contact with Unix, on a
VAX 11/780. The choice was ed or vi. I used ed.

Now, on my Linux box, I still use ed for little changes and for things where
I want to retain the context of what I'm doing and not have it wiped out by
a full-screen editor; a basic customisation of jed for small-to-medium jobs
(that's what I'm in at the moment), and rhide for coding, which is a Linux
clone of the Borland Turbo C IDE - I love that IDE. There's some dispute as
to how 'free' it is, since it uses a Linux port of the Borland Turbo Vision
library whose 'free' status is disputable, but I have a pukka copy of Turbo
C anyway so no problem.



To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact

This message is intended only for the personal and confidential use of the designated recipient(s) named above.  If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.  This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such.  All information is subject to change without notice.

Reply to: