Re: Is the mercurial mirror not getting updated?

On So, 06 Dez 2015, Ron Aaron wrote: > The last patch I see is 944... Not it is not. Please look at the commits page: https://bitbucket.org/vim-mirror/vim/commits/all The repository is getting updated automatically and should receive updates almost at the same time as the main github

Re: Odd result for sort([ '1', '5', '48', '25', '5', '28', '6'], 'n')

Tony Mechelynck wrote: > After applying the recent patches (up to 7.4.960) I notice a > duplication in the help, as follows (eval.txt lines 5818 to 5828): > > > The sort is stable, items which compare equal (as number or as > string) will keep their relative position. E.g.,

Re: [vim] Fix test_listlbr_utf8 (#518)

Christian Brabandt wrote: > Bram, > this pull request fixes the occasional test_listlbr_utf8 failure on > travis and appveyor: > > - make sure encoding is in utf8 > - do not use multibyte char literally, but use u > format to make sure fullwidth sign is created correctly > - fix

Re: Patch 7.4.949

Hirohito Higashi wrote: > 2015-12-4$(Fri) 4:58:00 UTC+9 Manuel Ortega: > > On Thu, Dec 3, 2015 at 2:14 PM, Bram Moolenaar wrote: > > > > > > Kenichi Ito wrote: > > > > > After this patch, test_listlbr_utf8 fails on travis-ci. > > >

Patch 7.4.963

Patch 7.4.963 Problem:test_listlbr_utf8 sometimes fails. Solution: Don't use a literal multibyte character but u. Do not dump the screen highlighting. (Christian Brabandt, closes #518) Files: src/testdir/test_listlbr_utf8.in, src/testdir/test_listlbr_utf8.ok ***

Re: Patch 7.4.949 (was Re: Fullwidth sign characters, misaligned colorcolumn, and missing visual highlighting)

2015/12/06 22:53, Bram Moolenaar wrote: > Christian made a fix. Thanks, the test passes OK now. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Re: [vim] doesn't work in insert mode (#519)

On 2015-12-06, Viacheslav Lotsmanov wrote: > Command I use to start (I redefine HOME for use default vim configs): > env HOME=/dev/null vim > > :verbose set cp? cpo? bs? > compatible > cpoptions=aAbBcCdDeEfFgHiIjJkKlLmMnoOpPqrRsStuvwWxXyZ$!%*-+<>; > backspace= > > ts?=8 > sts?=0 > sw?=8 >

Re: [patch] 'linebreak' does not work properly, When set listchars-spaces

Hirohito Higashi wrote: > Hi Bram and List, > > How to reproduce: > - Start Vim with some setting. > $ vim -N -u NONE -c "set listchars=space:_ list linebreak" > - Input below: > ia ayl80p > > Expected behavior: > - The Line is wrapped. And cursor move to the last character of the last >

Re: [patch] support for bin nrformat

Jason Schulz wrote: > Since C++ (Java, Python, etc...) have support for binary literals now, > I'm trying to add support for a 'bin' nrformat. So far, I've been > able to add it to sort, increment/decrement, key parsing, and some > other various functions. > > I would still need to add some

Re: Fullwidth sign characters, misaligned colorcolumn, and missing visual highlighting

Hi Jun! On So, 06 Dez 2015, Jun T. wrote: > First of all, what is the encoding used in test_listlbr_utf8.{in,ok}? It is supposed to be utf8 > Was this (wrongly) converted into U+00EF U+00BC U+008B ? I think, when I was sending the mail, it got mangled. This seems to have happened more often

Re: Patch 7.4.949 (was Re: Fullwidth sign characters, misaligned colorcolumn, and missing visual highlighting)

2015/12/06 21:21 I wrote: > test_listlbr_utf8 fails on Mac OS X as follows: Sorry, the problem has been reported already by a couple of people. Anyway, what is the encoding used in test_listlbr_utf8.{in,ok}? -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type

Re: Windows 64bit build in 32bit command prompt

Hi, Another week, another diff. After some discussion with Ken and Taro I offer up the following diff to cope with and (attempt to) tidy up cross compilation across architectures with Visual Studio. diff --git a/src/Make_mvc.mak b/src/Make_mvc.mak --- a/src/Make_mvc.mak +++

[vim] Fix test_listlbr_utf8 (#518)

Bram, this pull request fixes the occasional test_listlbr_utf8 failure on travis and appveyor: - make sure encoding is in utf8 - do not use multibyte char literally, but use u format to make sure fullwidth sign is created correctly - fix incorrect ok file to the correct expected output -

Re: Fullwidth sign characters, misaligned colorcolumn, and missing visual highlighting

test_listlbr_utf8 fails on Mac OS X as follows: # Check if the test.out file matches test.ok. 54,56c54,56 < ¶ < a b c¶ < a b c¶ --- > ¶ > ＋a b c¶

Is the mercurial mirror not getting updated?

The last patch I see is 944... -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google

Re: Is the mercurial mirror not getting updated?

Thanks. It looks like my mercurial clone was messed up for some reason. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message

Re: bug: if an autogroup has the name of an autocommand event, the autocommand does not trigger

Christian Brabandt wrote: > On Sa, 05 Dez 2015, Bram Moolenaar wrote: > > > That exe command has an error, the quoting is wrong. > > Yes, posting a bad example > > > The second command doesn't work as you expect: > > filetypegroup > > * event > > :echom

Re: [patch] 'linebreak' does not work properly, When set listchars-spaces

On So, 06 Dez 2015, Bram Moolenaar wrote: > Hirohito Higashi wrote: > > > Hi Bram and List, > > > > How to reproduce: > > - Start Vim with some setting. > > $ vim -N -u NONE -c "set listchars=space:_ list linebreak" > > - Input below: > > ia ayl80p > > > > Expected behavior: > > - The Line

Re: [patch] support for bin nrformat

> ​I would actually suggest to not use vim_str2nr for this feature the way it > is used now.​ Neovim has received the complain that some rather large > numbers cannot be incremented/decremented with ``, and the same > problem applies to vim as well. It is better to do the following instead: > >

Re: Testing on non-Unix systems

On 12/6/2015 4:41 PM, Bram Moolenaar wrote: Michael Soyka wrote: On 12/5/2015 1:47 PM, Bram Moolenaar wrote: Michael Soyka wrote: On 12/4/2015 5:27 PM, Bram Moolenaar wrote: Michael Soyka wrote: On 12/3/2015 4:13 PM, Bram Moolenaar wrote: I have added "new style" testing for Unix. It

Re: [patch] support for bin nrformat

Hi Bram, I appreciate you reviewing the patch so far. > I don't think there is much use for binary in Vim script, but it doesn't > hurt either. I do use something similar in VimL to convert between radixes (https://github.com/uxcn/vim-x2x). It's strictly text in, text out though. > I suggest

Re: [vim] doesn't work in insert mode (#519)

On 2015-12-06, Gary Johnson wrote: > To fix these issues, start Vim as > > HOME=/dev/null vim -N Correction: HOME=/dev/null vim -N -c 'set bs=2' Regards, Gary -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

Re: Testing on non-Unix systems

Michael Soyka wrote: > On 12/5/2015 1:47 PM, Bram Moolenaar wrote: > > Michael Soyka wrote: > > > >> On 12/4/2015 5:27 PM, Bram Moolenaar wrote: > >>> Michael Soyka wrote: > >>> > On 12/3/2015 4:13 PM, Bram Moolenaar wrote: > > I have added "new style" testing for Unix. It appears to