On Tue, 12 Mar 2019, Bram Moolenaar wrote:
Something went wrong with committing the patch, it was incomplete.
Not sure how to re-tag the commits.
There's instructions on google about "moving tags" but it's not
suggested unless you can get everyone who checks out to make sure they
all cleanly c
On 15/03/19 05:37, Bram Moolenaar wrote:
> Andre Sihera wrote:
>
>> I'm using a fairly old version of ViM (7.3) on Ubuntu so I wondered if
>> this problem
>> isalready known about and maybe fixed in a newer version.
>>
>> The problem is that the clipboard contents appear to be getting
>> corrupted
Andre Sihera wrote:
> I'm using a fairly old version of ViM (7.3) on Ubuntu so I wondered if
> this problem
> isalready known about and maybe fixed in a newer version.
>
> The problem is that the clipboard contents appear to be getting
> corrupted during a
> cut/paste using the '*' register.
Patch 8.1.1008
Problem:MS-Windows: HAVE_STDINT_H only defined for non-debug version.
Solution: Move definition of HAVE_STDINT_H up. (Taro Muraoka, closes #4109)
Files: src/Make_mvc.mak
*** ../vim-8.1.1007/src/Make_mvc.mak2019-02-18 21:41:34.477750367 +0100
--- src/Make_mvc.mak
On 2019-03-14, Robert Webb wrote:
> Ah, thanks Gary,
>
> Actually I already set 'fo' in my vimrc, but I set it with "autocmd BufRead".
> I suppose the file-type commands happen after that?
Yes. The BufRead and BufNewFile events trigger the FileType event
through the autocommands in $VIMRUNTIME/
Hi all,
I'm using a fairly old version of ViM (7.3) on Ubuntu so I wondered if
this problem
isalready known about and maybe fixed in a newer version.
The problem is that the clipboard contents appear to be getting
corrupted during a
cut/paste using the '*' register.
Way to reproduce:
1) Open
Patch 8.1.1007
Problem:Using closure may consume a lot of memory.
Solution: unreference items that are no longer needed. Add a test. (Ozaki
Kiichi, closes #3961)
Files: src/testdir/Make_all.mak, src/testdir/test_memory_usage.vim,
src/userfunc.c
*** ../vim-8.1.
Ah, thanks Gary,
Actually I already set 'fo' in my vimrc, but I set it with "autocmd
BufRead". I suppose the file-type commands happen after that?
So 'fo' is the right way to set this.
Is the "O:" option in 'comments' meant to do the same thing? It still
seems like a bug that it only changes b
