Saturday, June 7, 2014

Re: vimdiff noob question

On 07/06/14 21:11, wolfv wrote:
> I am following the example in the vim user manual: 08.7 Viewing differences with vimdiff
> My vimdiff is either broken or I am not understanding something.
>
> In this example, a.txt has serveral lines of text.
> I open vimdiff from the command prompt:
> vim -d a.txt~ a.txt
> ~
> ~
> ~
> ~
> vimdiff displays both files as having no lines, and there are no folds.
> Is this how vimdiff is supposed to work? I was expecting to see some text.
> If I save the file (:w) at this point, the file is overwritten with an empty file.
> Otherwise vimdiff seems to work normally; I am able to insert text into a.txt and save it.
>
> This is my first attempt learning vimdiff and I appreciate your advice.
> Thank you.
>

In order for vimdiff to work, you need to have where Vim can find it
(usually in your $PATH, or maybe in $VIMRUNTIME) a diff program which
understands the arguments that vimdiff will send it to find the
differences between the files. This is usually the case if you run on a
Unix-like OS, including Linux, Mac OSX, BeOS, etc. On Windows it may or
may not be the case.

See in particular ":help diff-diffexpr" and the last paragraph before
":help diff-patchexpr" (without the double quotes in both cases).


Best regards,
Tony.
--
meeting, n.:
An assembly of people coming together to decide what person or
department not represented in the room must solve a problem.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment