I faced this issue a few times, so I thought I will ask here. When I
am done with the vimdiff mode, I normally just close the windows or
switch to other files. The problem is that Vim seems to remember that
those buffers participate in the diff mode, so the next time I start a
new vimdiff on
-Original Message-
From: Hari Krishna Dara [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 29, 2006 2:53 PM
To: vim@vim.org
Subject: a question about 'diff' setting
...
Can anyone explain why and what I should do to avoid
this (other than remembering to run :diffoff before
The documentation says the 'diff' setting is local to window, so closing
the windows show cancel the setting out, but when I try the below
sequence on two related files say, x.old and x.new, it seems otherwise.
Vim seems to keep the 'diff' information around in the same way
it keeps marks in a
On 6/29/06, Hari Krishna Dara [EMAIL PROTECTED] wrote:
When I
am done with the vimdiff mode, I normally just close the windows or
switch to other files. The problem is that Vim seems to remember that
those buffers participate in the diff mode
I just do :bw twice when I want to normally edit
Hi David,
On 6/29/06, David Fishburn [EMAIL PROTECTED] wrote:
-Original Message-
From: Hari Krishna Dara [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 29, 2006 2:53 PM
To: vim@vim.org
Subject: a question about 'diff' setting
...
Can anyone explain why and what I should do
On Thu, 29 Jun 2006 at 2:59pm, David Fishburn wrote:
-Original Message-
From: Hari Krishna Dara [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 29, 2006 2:53 PM
To: vim@vim.org
Subject: a question about 'diff' setting
...
Can anyone explain why and what I should do to avoid
On Thu, 29 Jun 2006 at 2:07pm, Tim Chase wrote:
The documentation says the 'diff' setting is local to window, so closing
the windows show cancel the setting out, but when I try the below
sequence on two related files say, x.old and x.new, it seems otherwise.
Vim seems to keep the 'diff'
