On 12/3/2015 4:13 PM, Bram Moolenaar wrote:
I have added "new style" testing for Unix. It appears to work well, so
now we also need this for other platforms. The Unix Makefile only
needed a few extra lines, hopefully it's also simple for others.
I would prefer someone who knows the platform
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 sorting
on numbers, text
On Wed, Dec 02, 2015 at 05:24:03PM -0800, Jörn Engel wrote:
> On Thu, Dec 03, 2015 at 01:20:22AM +0100, Tony Mechelynck wrote:
> > On Thu, Dec 3, 2015 at 12:39 AM, Jörn Engel wrote:
> > > Retry after subscribing to the list. I hope this works and I can
> > > unsubscribe
Patch 7.4.948
Problem:Can't build when the insert_expand feature is disabled.
Solution: Add #ifdefs. (Dan Pasanen, closes #499)
Files: src/eval.c, src/fileio.c
*** ../vim-7.4.947/src/eval.c 2015-12-01 15:32:50.817574177 +0100
--- src/eval.c 2015-12-03 13:36:42.998025242 +0100
Patch 7.4.949
Problem:When using 'colorcolumn' and there is a sign with a fullwidth
character the highlighting is wrong. (Andrew Stewart)
Solution: Only increment vcol when in the right state. (Christian Brabandt)
Files: src/screen.c, src/testdir/test_listlbr_utf8.in,
> On Di, 01 Dez 2015, b...@airbladesoftware.com wrote:
> > Hello!
> >
> > Under certain circumstances the colorcolumn becomes misaligned by one
> > character:
> >
> > 1. A lign has a sign whose text is a fullwidth character.
> > 2. The colorcolumn is a column after the end of the text on the
Hello,
I'm not sure whether sort() can be applied with 'n' parameter on lists of
strings that encode numbers.
Right now (v7.4-908) the result produced is: ['1', '5', '48', '25', '5', '28',
'6'] which is really odd.
Is this a vim bug, or an undefined behaviour?
Regards,
--
Luc Hermitte
--
Hi Jürgen,
- Mail original -
> > [...]
> > Is this a vim bug, or an undefined behaviour?
>
> see the fifth paragraph of ":help sort()". Note that Strings are
> explicitly mentioned "to be considered as being 0". Also read the
> second to last paragraph which explains why the order of the
Thinca wrote:
> diff --git a/src/eval.c b/src/eval.c
> index a2a9986..d890d39 100644
> --- a/src/eval.c
> +++ b/src/eval.c
> @@ -900,6 +900,7 @@ eval_init()
> set_vim_var_nr(VV_SEARCHFORWARD, 1L);
> set_vim_var_nr(VV_HLSEARCH, 1L);
> set_vim_var_dict(VV_COMPLETED_ITEM,
Patch 7.4.950
Problem:v:errors is not initialized.
Solution: Initialze it to an empty list. (Thinca)
Files: src/eval.c
*** ../vim-7.4.949/src/eval.c 2015-12-03 13:52:48.439584211 +0100
--- src/eval.c 2015-12-03 14:52:58.568671030 +0100
***
*** 900,905
--- 900,906
Hirohito Higashi wrote:
> Hi Bram and Vimmer,
>
> I am trying to add new feature to Vim.
> It's CLPUM(Command-line mode PopUp Menu)
>
> Implementation is complete. Now, I am debugging.
>
> Please check following site.
> http://h-east.github.io/vim/
>
> Is this interesting?
> I want to be
Hi,
Luc Hermitte schrieb am 03.12.2015 um 14:52:
>
> I'm not sure whether sort() can be applied with 'n' parameter on lists of
> strings that encode numbers.
>
> Right now (v7.4-908) the result produced is: ['1', '5', '48', '25', '5',
> '28', '6'] which is really odd.
>
> Is this a vim bug,
Jörn Engel wrote:
> On Thu, Dec 03, 2015 at 02:12:08AM +, Random832 wrote:
> > On 2015-12-02, Jörn Engel wrote:
> > > The vim bug is to try "$TMPDIR" even though the environment variable
> > > isn't set. Arguably that could become a security-issue if I can create
> >
Patch 7.4.954
Problem:When using Lua there may be a crash. (issue #468)
Solution: Avoid using an unitialized tv. (Yukihiro Nakadaira)
Files: src/if_lua.c
*** ../vim-7.4.953/src/if_lua.c 2015-11-02 15:27:03.438325506 +0100
--- src/if_lua.c2015-12-03 17:40:24.264249563 +0100
Hi list,
test_tagcase fails like this.
3,4c3,4
< E474: 無効な引数です: tc=
< E474: 無効な引数です: tc=
---
> E474: Invalid argument: tc=
> E474: Invalid argument: tc=
This patch fixes it.
diff --git a/src/testdir/test_tagcase.in b/src/testdir/test_tagcase.in
index 6e68111..d76dbab 100644
---
Hi list,
After this patch, test_listlbr_utf8 fails on travis-ci.
https://travis-ci.org/vim/vim/builds/94633493
54,56c54,56
< ¶
< a b c¶
< a b c¶
---
> ¶
Patch 7.4.952
Problem:'lispwords' is tested in the old way.
Solution: Make a new style test for 'lispwords'.
Files: src/testdir/test_alot.vim, src/testdir/test_lispwords.vim,
src/testdir/test100.in, src/testdir/test100.ok,
src/testdir/Make_amiga.mak,
On 1 Dec 2015, at 21:31, Christian Brabandt wrote:
> Attached is a patch.
Thanks!
I applied the patch to MacVim 7.4.947 and I can confirm it solved both problems
for me.
Thanks again,
Yours,
Andrew
--
--
You received this message from the "vim_dev" maillist.
Do not
Patch 7.4.953
Problem:When a test script navigates to another buffer the .res file is
created with the wrong name.
Solution: Use the "testname" for the .res file. (Damien)
Files: src/testdir/runtest.vim
*** ../vim-7.4.952/src/testdir/runtest.vim 2015-11-29
Luc Hermitte wrote:
> I'm not sure whether sort() can be applied with 'n' parameter on lists of
> strings that encode numbers.
>
> Right now (v7.4-908) the result produced is: ['1', '5', '48', '25', '5',
> '28', '6'] which is really odd.
>
> Is this a vim bug, or an undefined behaviour?
As
Patch 7.4.951
Problem:Sorting number strings does not work as expected. (Luc Hermitte)
Solution: Add the 'N" argument to sort()
Files: src/eval.c, runtime/doc/eval.txt, src/testdir/test_alot.vim,
src/testdir/test_sort.vim, src/testdir/Makefile
***
On Thu, Dec 03, 2015 at 05:43:33PM +0100, Bram Moolenaar wrote:
>
> Does this patch fix your problem:
>
>
> --- a/fileio.c2015-12-03 13:52:48.451584080 +0100
> +++ b/fileio.c2015-12-03 17:31:53.457770134 +0100
> @@ -7390,8 +7390,9 @@
>
> /* expand $TMP, leave room
Patch 7.4.956
Problem:A few more file name extensions not recognized.
Solution: Add .asciidoc, .bzl, .gradle, etc.
Files: runtime/filetype.vim
*** ../vim-7.4.955/runtime/filetype.vim 2015-12-03 20:14:07.547768295 +0100
--- runtime/filetype.vim2015-12-03 20:10:00.826467327
Patch 7.4.959
Problem:When setting 'term' the clipboard ownership is lost.
Solution: Do not call clip_init(). (James McCoy)
Files: src/term.c
*** ../vim-7.4.958/src/term.c 2015-11-24 18:15:46.381122073 +0100
--- src/term.c 2015-12-03 21:13:55.028389836 +0100
***
***
Patch 7.4.957
Problem:Test_tagcase fails when using another language than English.
Solution: Set the messages language to C. (Kenichi Ito)
Files: src/testdir/test_tagcase.in
*** ../vim-7.4.956/src/testdir/test_tagcase.in 2015-11-25 23:52:58.564379894
+0100
---
Kenichi Ito wrote:
> test_tagcase fails like this.
> 3,4c3,4
> < E474: 無効な引数です: tc=
> < E474: 無効な引数です: tc=
> ---
> > E474: Invalid argument: tc=
> > E474: Invalid argument: tc=
>
>
> This patch fixes it.
Thanks! We could strip the text after the error number, but this is
simpler.
--
A bad
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,56c54,56
> > < ¶
> > < a b c¶
> > < a b c¶
> > ---
> > > ¶
> >
Jörn Engel wrote:
> > Does this patch fix your problem:
> >
> >
> > --- a/fileio.c 2015-12-03 13:52:48.451584080 +0100
> > +++ b/fileio.c 2015-12-03 17:31:53.457770134 +0100
> > @@ -7390,8 +7390,9 @@
> >
> > /* expand $TMP, leave room for "/v110/9" */
> >
Kenichi Ito wrote:
> After this patch, test_listlbr_utf8 fails on travis-ci.
> https://travis-ci.org/vim/vim/builds/94633493
>
> 54,56c54,56
> < ¶
> < a b c¶
> < a b c¶
> ---
> > ¶
Patch 7.4.955
Problem:Vim doesn't recognize .pl6 and .pod6 files.
Solution: Recognize them as perl6 and pod6. (Mike Eve, closes #511)
Files: runtime/filetype.vim
*** ../vim-7.4.954/runtime/filetype.vim 2015-09-08 19:13:17.568494100 +0200
--- runtime/filetype.vim2015-12-03
Patch 7.4.958
Problem:Vim checks if the directory "$TMPDIR" exists.
Solution: Do not check if the name starts with "$".
Files: src/fileio.c
*** ../vim-7.4.957/src/fileio.c 2015-12-03 13:52:48.439584211 +0100
--- src/fileio.c2015-12-03 20:53:35.725775742 +0100
***
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 tests, but I was hoping to get
On Thu, Dec 03, 2015 at 09:02:47PM +0100, Bram Moolenaar wrote:
> Jörn Engel wrote:
>
> > But fundamentally this patch is still wrong. If I run
> > export TMPDIR='$TMPDIR' vim
> > then vim should very much try '$TMPDIR' because I explicitly asked it
> > to do so. Might be a silly choice,
On Dec 3, 2015 16:00, "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
I have added "new style" testing for Unix. It appears to work well, so
now we also need this for other platforms. The Unix Makefile only
needed a few extra lines, hopefully it's also simple for others.
I would prefer someone who knows the platform to make a patch for this.
We need this for:
Patch 7.4.960
Problem:Detecting every version of nmake is clumsy.
Solution: Use a tiny C program to get the version of _MSC_VER. (Ken Takata)
Files: src/Make_mvc.mak
*** ../vim-7.4.959/src/Make_mvc.mak 2015-07-21 20:22:07.331615818 +0200
--- src/Make_mvc.mak2015-12-03
On Thu, Dec 03, 2015 at 11:03:19AM -0800, Jörn Engel wrote:
> On Thu, Dec 03, 2015 at 05:43:33PM +0100, Bram Moolenaar wrote:
> >
> > Does this patch fix your problem:
> >
> >
> > --- a/fileio.c 2015-12-03 13:52:48.451584080 +0100
> > +++ b/fileio.c 2015-12-03 17:31:53.457770134 +0100
37 matches
Mail list logo