On 17/04/09 19:36, David C. wrote:
Hi everyone,
Long time user, first time caller.
In this case I'm using gvim on windows xp, but I think this applies to
most vim situations.
When you attempt to open a text file that was closed abnormally
before, leaving a hidden .swp file, your open is
On 18/04/09 01:35, John Beckett wrote:
David C. wrote:
When you attempt to open a text file that was closed
abnormally before, leaving a hidden .swp file, your open is
interrupted by something like:
Swap file filename.txt.swp already exists!
Sorry, but I'm going to deliver some advice
On 18/04/09 03:15, David C. wrote:
John, believe it or not, I respect where you're coming from. Even
though Windows XP was a vast improvement over previous (and future)
Microsoft OS's, I agree it's still Windows, and it does suck to use
Windows instead of Linux.
But I know of 2 good
Ben Schmidt wrote:
Adding the ability to easily diff the recovered buffer
against the on-disk file (the action recommended to the user)
is a valid request.
I'm not proposing the following as a solution, but I will
mention that there is a related tip:
On 18/04/09 13:52, Michael Henry wrote:
[...]
When I first started using Vim and got the 'Swap file exists' message, I
found it very hard to understand the difference between the options
presented. Several things were unclear to me:
- If a previous Vim session crashed, did I lose any
Hi everyone,
Long time user, first time caller.
In this case I'm using gvim on windows xp, but I think this applies to
most vim situations.
When you attempt to open a text file that was closed abnormally
before, leaving a hidden .swp file, your open is interrupted by
something like:
Swap file
David C. wrote:
When you attempt to open a text file that was closed
abnormally before, leaving a hidden .swp file, your open is
interrupted by something like:
Swap file filename.txt.swp already exists!
Sorry, but I'm going to deliver some advice from a previous
occasion when this was
On Sat, Apr 18, 2009 at 09:35:50AM +1000, John Beckett wrote:
Sorry, but I'm going to deliver some advice from a previous
occasion when this was discussed. You really should NOT be
seeing these errors!
Vim creates swapfiles expressly to ease the process of recovering from
problems. Whether
me too, +1 to the original feature request.
Sorry, but I'm going to deliver some advice from a previous
occasion when this was discussed. You really should NOT be
seeing these errors! Your effort should be spent on finding out
what is going wrong. If your hardware or software is crashing,
James Vega wrote:
Vim creates swapfiles expressly to ease the process of
recovering from problems. Whether they be the power going
out while they were editing, or their system crashing
(BSOD?), or even forgetting to close their Vim session and
needing to do more work from a remote
Adding the ability to easily diff the recovered buffer
against the on-disk file (the action recommended to the user)
is a valid request.
I'm not proposing the following as a solution, but I will
mention that there is a related tip:
11 matches
Mail list logo
