The plugin I'm working on updates the buffer after every change and uses
:undojoin. Unfortunately, sometimes the change *is* an undo, in which
case, :undojoin kills the history. What's the best way to detect whether
the operation is an undo or redo for this purpose?
The only thoughts I have are
Tim Chase wrote:
> To reproduce:
>
> $ vim -u NONE
> :syntax on
> :set spell cpo+=J
>
> to let vim know I always put two spaces after a sentence. However,
> if I enter text like
>
> Call Bob re. the faucet.
>
> or
>
> Take Main St. the whole way down.
>
> vim's syntax
David Demelier wrote:
> On Sun, 2018-04-15 at 12:43 +0200, Bram Moolenaar wrote:
> > For a long time Vim code was made to be compiled with ANSI C (also
> > known
> > as C89 and ISO C90). This means it can also be compiled on very old
> > systems. And since it wasn't too much work to support
On Sun, 2018-04-15 at 12:43 +0200, Bram Moolenaar wrote:
> For a long time Vim code was made to be compiled with ANSI C (also
> known
> as C89 and ISO C90). This means it can also be compiled on very old
> systems. And since it wasn't too much work to support it, that was
> the
> choice.
>
C99
