On Mon, November 23, 2009 4:47 am, bill lam wrote:
> Not sure if the author follows this thread. It sometime show error
> message like this (vim under debian)
>
> u_rundo: undo file corruption detected: invalid uh_seq.
> Press ENTER or type command to continue
You should probably reply to the th
On Mon, 16 Nov 2009, Christian Brabandt wrote:
> You could possibly also try out the persistent undo feature. But for
> this you need to patch the vim source and compile yourself. See
> http://groups.google.com/group/vim_dev/browse_frm/thread/b23d563bffcec9b5
Not sure if the author follows this t
On Mon, 16 Nov 2009, Christian Brabandt wrote:
> Disclaimer: I haven't compiled the patch yet myself, 'cause I do not
> have a development machine with a recent Internet connection at the
> moment, so this would be the method, I would use.
I tried and it work as advertised, my observations.
1.
On Mon, November 16, 2009 7:16 pm, Christian Brabandt wrote:
> Disclaimer: I haven't compiled the patch yet myself, 'cause I do not
> have a development machine with a recent Internet connection at the
> moment, so this would be the method, I would use.
:s/recent/decent/
regards,
Christian
--
:
Hi Efraim!
On Mo, 16 Nov 2009, Efraim Yawitz wrote:
> On Mon, Nov 16, 2009 at 11:51 AM, Christian Brabandt
> wrote:
> > You could possibly also try out the persistent undo feature. But for
> > this you need to patch the vim source and compile yourself. See
> > http://groups.google.com/group/vim
On Mon, Nov 16, 2009 at 11:51 AM, Christian Brabandt wrote:
>
>
> You could possibly also try out the persistent undo feature. But for
> this you need to patch the vim source and compile yourself. See
> http://groups.google.com/group/vim_dev/browse_frm/thread/b23d563bffcec9b5
> for the thread at v
On Sat, November 14, 2009 10:47 pm, John Beckett wrote:
> Tim Chase wrote:
>>:%d
>>:r %
>>:1d
>>
>> which (1) deletes all the content, (2) reads in the content
>> from disk below the one blank line remaining, and then (3)
>> deletes the spurious blank line.
>>
>> The above could be wra
John Beckett wrote:
> Tim Chase wrote:
>>:%d
>>:r %
>>:1d
>
> That's exactly what this tip does:
> http://vim.wikia.com/wiki/Reload_file_without_losing_undo_history
So yeah...do what John suggests ;-)
I'm not much of a "wiki'er", whereas John seems to have most of
the wiki memorize
Tim Chase wrote:
>:%d
>:r %
>:1d
>
> which (1) deletes all the content, (2) reads in the content
> from disk below the one blank line remaining, and then (3)
> deletes the spurious blank line.
>
> The above could be wrapped in a function/command/mapping and
> then used in place of ":e!
>>> Sometimes even after I save my changes to a file using :w, I
>>> can undo these changes (using u). But sometimes I cannot undo
>>> after I have saved the file with :w. In both cases, I don't
>>> close the file or exit vim.
>
>> - something (possibly a plugin) is reloading the buffer after
>>
On Nov 14, 7:46 am, Tim Chase wrote:
> > Sometimes even after I save my changes to a file using :w, I
> > can undo these changes (using u). But sometimes I cannot undo
> > after I have saved the file with :w. In both cases, I don't
> > close the file or exit vim.
>
> - something (possibly a pl
> Sometimes even after I save my changes to a file using :w, I
> can undo these changes (using u). But sometimes I cannot undo
> after I have saved the file with :w. In both cases, I don't
> close the file or exit vim.
A couple possibilities occur to me, some of which stem from the
ambiguity of
12 matches
Mail list logo
