Patch 7.4.1761
Problem:Coverity complains about ignoring return value.
Solution: Add "(void)" to get rid of the warning.
Files: src/eval.c
*** ../vim-7.4.1760/src/eval.c 2016-04-20 17:37:02.102439516 +0200
--- src/eval.c 2016-04-21 08:54:26.939119030 +0200
***
*** 13178,
Manuel Ortega wrote:
> On OS X 10.11.4, Vim 7.4.1759 after a fresh clone of the git repo, I get
> this:
>
> >From test_alot.vim:
> Found errors in Test_strcharpart():
> function RunTheTest[9]..Test_strcharpart line 8: Expected '' but got 'a'
> function RunTheTest[9]..Test_strcharpart line 9: Exp
Hi,
> test_expand_dllpath.vim is not executed.
> Because, there is no function that starts with `Test_`.
> I fixed in the attaching patch.
Doubt!
Functions that begin with the `Test_' had been generated by the
s:generate_test_if_exists().
Sorry for noise.
--
Best regards,
Hirohito Higashi (a.k.
Hi Bram and Kiichi!
2016-4-20(Wed) 23:21:26 UTC+9 Bram Moolenaar:
> Patch 7.4.1756
> Problem:"dll" options are not expanded.
> Solution: Expand environment variables. (Ozaki Kiichi)
> Files: src/option.c, src/testdir/test_alot.vim,
> src/testdir/test_expand_dllpath.vim
>
>
Nicola wrote:
> To reproduce, use this vimrc_minimal:
>
> set nocompatible
> fun! MyFun()
> silent !ls
> endf
> nmap o MyFun()
>
> Then:
>
> vim -u vimrc_minimal
> :Ex
> :enew
> \o
>
> (:enew is optional). You should get the following error:
>
> Error detected while processing function 28_LocalBro
On OS X 10.11.4, Vim 7.4.1759 after a fresh clone of the git repo, I get
this:
>From test_alot.vim:
Found errors in Test_strcharpart():
function RunTheTest[9]..Test_strcharpart line 8: Expected '' but got 'a'
function RunTheTest[9]..Test_strcharpart line 9: Expected '' but got 'a'
function RunTheT
John Marriott wrote:
> On 21-Apr-2016 4:20 AM, Bram Moolenaar wrote:
> > Patch 7.4.1759
> > Problem:When using feedkeys() in a timer the inserted characters are not
> > used right away.
> > Solution: Break the wait loop when characters have been added to typebuf.
> >
Patch 7.4.1760 (after 7.4.1759)
Problem:Compiler warning for unused variable.
Solution: Add #ifdef. (John Marriott)
Files: src/os_win32.c
*** ../vim-7.4.1759/src/os_win32.c 2016-04-20 20:18:16.957270339 +0200
--- src/os_win32.c 2016-04-20 20:51:41.725134834 +0200
***
On 21-Apr-2016 4:20 AM, Bram Moolenaar wrote:
Patch 7.4.1759
Problem:When using feedkeys() in a timer the inserted characters are not
used right away.
Solution: Break the wait loop when characters have been added to typebuf.
use this for testing CursorHoldI.
Files
Ben Fritz wrote:
> On Wednesday, April 20, 2016 at 9:24:18 AM UTC-5, b...@airbladesoftware.com
> wrote:
> > I've just realised I wrote CursorMovedI when I meant CursorHoldI. Sorry
> > about that.
> >
> > > Would it be sufficient to not trigger CursorMovedI when the user pressed
> > > CTRL-X ?
Patch 7.4.1759
Problem:When using feedkeys() in a timer the inserted characters are not
used right away.
Solution: Break the wait loop when characters have been added to typebuf.
use this for testing CursorHoldI.
Files: src/gui.c, src/os_win32.c, src/os_unix.c,
2016-04-21 2:06 GMT+09:00 Christian Ludwig :
> Hello Kazunobu Kuriyama,
>
> > Thank you for checking.
> >
> >> if I make then the gtk3vim-Window active
> >
> > What do you mean by "active"? Raising the window on top of the another
> > window, or restarting the vim process that had been stopped th
Hello Kazunobu Kuriyama,
> Thank you for checking.
>
>> if I make then the gtk3vim-Window active
>
> What do you mean by "active"? Raising the window on top of the another
> window, or restarting the vim process that had been stopped then?
Raising the window on top of the others (=bring to fro
On Wednesday, April 20, 2016 at 9:24:18 AM UTC-5, b...@airbladesoftware.com
wrote:
> I've just realised I wrote CursorMovedI when I meant CursorHoldI. Sorry
> about that.
>
> > Would it be sufficient to not trigger CursorMovedI when the user pressed
> > CTRL-X ? What submode would it be in? O
Sorry, typo.
> "keeping it somewhere in memory was of use."
should read "keeping it somewhere in memory was of *no* use."
2016-04-21 0:38 GMT+09:00 Kazunobu Kuriyama :
> Thank you for checking.
>
> > if I make then the gtk3vim-Window active
>
> What do you mean by "active"? Raising the windo
Patch 7.4.1758
Problem:Triggering CursorHoldI when in CTRL-X mode causes problems.
Solution: Do not trigger CursorHoldI in CTRL-X mode. Add "!" flag to
feedkeys() (test with that didn't work though).
Files: src/edit.c, src/eval.c
*** ../vim-7.4.1757/src/edit.c 2016-04-20
Thank you for checking.
> if I make then the gtk3vim-Window active
What do you mean by "active"? Raising the window on top of the another
window, or restarting the vim process that had been stopped then?
Apparently, it looks like the gvim stopped and was unable to redraw itself.
And how did yo
Patch 7.4.1757
Problem:When using complete() it may set 'modified' even though nothing
was inserted.
Solution: Use Down/Up instead of Next/Previous match. (Shougo, closes #745)
Files: src/edit.c
*** ../vim-7.4.1756/src/edit.c 2016-04-20 12:01:49.540584913 +0200
--- src/ed
On 19/04/16 11:42, Kazunobu Kuriyama wrote:
> 2016-04-19 15:49 GMT+09:00 Bram Moolenaar :
>
>>
>> The GUI cursor blinking restarts the timer every time. That's a
>> separate problem though.
>>
>
> Year, that's true. In addition to that, I think the irregularity of the
> cursor blinking pace is
I've just realised I wrote CursorMovedI when I meant CursorHoldI. Sorry about
that.
> Would it be sufficient to not trigger CursorMovedI when the user pressed
> CTRL-X ? What submode would it be in? Or are you saying that this
> depends on whether the completion uses a popup menu or not?
Yes,
Patch 7.4.1756
Problem:"dll" options are not expanded.
Solution: Expand environment variables. (Ozaki Kiichi)
Files: src/option.c, src/testdir/test_alot.vim,
src/testdir/test_expand_dllpath.vim
*** ../vim-7.4.1755/src/option.c2016-04-20 12:01:49.548584830 +0200
---
Patch 7.4.1755
Problem:When using getreg() on a non-existing register a NULL list is
returned. (Bjorn Linse)
Solution: Allocate an empty list. Add a test.
Files: src/eval.c, src/testdir/test_expr.vim
*** ../vim-7.4.1754/src/eval.c 2016-04-14 22:54:20.818618214 +0200
--- s
Nikolay Pavlov wrote:
> 2016-04-20 14:46 GMT+03:00 Bram Moolenaar :
> >
> > Björn Linse wrote:
> >
> >> > The NULL is supposed to be the same as an empty, mutable list. This is
> >> > tricky, because code that expects a list needs to check for the NULL and
> >> > create the list if needed.
> >>
Björn Linse wrote:
> > OK, yes, in that case it is different from a real empty list.
> > Do we really case about that?
>
> Anyway, the fix is simple:
>
> --- a/eval.c
> +++ b/eval.c
> @@ -10096,9 +10096,10 @@ static void f_getreg(typval_T *argvars, typval_T
> *rettv)
> rettv->v_type = VAR
> OK, yes, in that case it is different from a real empty list.
> Do we really case about that?
Anyway, the fix is simple:
--- a/eval.c
+++ b/eval.c
@@ -10096,9 +10096,10 @@ static void f_getreg(typval_T *argvars, typval_T
*rettv)
rettv->v_type = VAR_LIST;
rettv->vval.v_list =
2016-04-20 14:46 GMT+03:00 Bram Moolenaar :
>
> Björn Linse wrote:
>
>> > The NULL is supposed to be the same as an empty, mutable list. This is
>> > tricky, because code that expects a list needs to check for the NULL and
>> > create the list if needed.
>>
>> how could this be possible?
>>
>> let
Björn Linse wrote:
> > The NULL is supposed to be the same as an empty, mutable list. This is
> > tricky, because code that expects a list needs to check for the NULL and
> > create the list if needed.
>
> how could this be possible?
>
> let x = getreg("a",1,1) " returns NULL
> let y = x
> cal
Andrew Stewart wrote:
> I posted this question a while back on vim_use but didn't receive any
> replies so I thought I would try here.
>
> https://groups.google.com/forum/#!topic/vim_use/EsISt5b-tnM/discussion
>
> I have a CursorMovedI autocommand which runs some Vimscript.
> Unfortunately if t
Patch 7.4.1754
Problem:When 'filetype' was set and reloading a buffer which does not
cause it to be set, the syntax isn't loaded. (KillTheMule)
Solution: Remember whether the FileType event was fired and fire it if not.
(Anton Lindqvist, closes #747)
Files: src/f
Patch 7.4.1753
Problem:"noinsert" in 'completeopt' is sometimes ignored.
Solution: Set the variables when the 'completeopt' was set. (Ozaki Kiichi)
Files: src/edit.c, src/option.c, src/proto/edit.pro
*** ../vim-7.4.1752/src/edit.c 2016-04-14 16:22:01.161150961 +0200
--- src/edit.c 2
2016-04-20 12:35 GMT+03:00 Bram Moolenaar :
>
> Bjorn Linse wrote:
>
>> > Internally a list with a NULL pointer is supposed to be handled like an
>> > empty list. This is efficient, but tricky. Nikolai just sent a patch,
>> > hopefully that helps.
>>
>> Good, but I wonder if it is not better for
> The NULL is supposed to be the same as an empty, mutable list. This is
> tricky, because code that expects a list needs to check for the NULL and
> create the list if needed.
how could this be possible?
let x = getreg("a",1,1) " returns NULL
let y = x
call add(x, "text")
now x is created, bu
Hello!
I posted this question a while back on vim_use but didn't receive any replies
so I thought I would try here.
https://groups.google.com/forum/#!topic/vim_use/EsISt5b-tnM/discussion
I have a CursorMovedI autocommand which runs some Vimscript. Unfortunately if
the user is in the CTRL-X su
Martin Lundberg wrote:
> What's the preferred way of reporting spelling mistakes or just uses
> of the wrong words (Status instead of Statement) in the help files?
>
> Sometimes I read the help file and find a single error but never
> report it because it seems wasteful to create an issue or a
>
Bjorn Linse wrote:
> > Internally a list with a NULL pointer is supposed to be handled like an
> > empty list. This is efficient, but tricky. Nikolai just sent a patch,
> > hopefully that helps.
>
> Good, but I wonder if it is not better for getreg("a",1,1) to always
> return a mutable list (a
> Internally a list with a NULL pointer is supposed to be handled like an
> empty list. This is efficient, but tricky. Nikolai just sent a patch,
> hopefully that helps.
Good, but I wonder if it is not better for getreg("a",1,1) to always return a
mutable list (an empty mutable list in this cas
Björn Linse wrote:
> To reproduce:
>
> vim -u NONE -i NONE
> :let x = getreg("a",1,1)
> :call setreg("0",x)
>
> gives SIGSEGV on master vim (huge build). "-i NONE" is needed to make sure
> registers are undefined.
>
> it seems like getreg returns a NULL list (I don't know if that is supposed
37 matches
Mail list logo
