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 ap
> 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:
>
> 1.
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 y
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 wo
2015-12-06 21:50 GMT+03:00 Bram Moolenaar :
>
> 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 v
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
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 replyin
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
>
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 tes
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
> et?=noe
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 http://www.vim.org/maillist.php
---
Y
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., when
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 l
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 incorrect
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.
> > > https://travis-ci.org/vim/vim/builds/94633493
> > >
> > > 54,
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
*** ../vim
Jun T. wrote:
> 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}?
Christian made a fix.
--
panic("Fod fight!");
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
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 yo
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¶
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 b
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
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
+++ b/src/Make_mvc.m
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 repository.
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 Gr
25 matches
Mail list logo