Hello vim_dev,
I was always struck by the inconsistency of file ordere as returned by `:find
lost.file` and command completion, e.g. `:e **/lost.file^d`. If there are
multiple files of with name `lost.file` `:find` will explore them in different
order than what completion will suggest. Maybe
On Wednesday, June 5, 2019 at 1:08:03 AM UTC+12, Bram Moolenaar wrote:
> I have been wondering if it would help if Vim could play a sound.
I'm a fan. More bandwidth from vim to me is always good. But people wanting to
turn off beeps from vim are very vocal, those wanting to turn them on are no
Patch 8.1.1467 (after 8.1.1465)
Problem:Cscope test fails.
Solution: Update expected text.
Files: src/testdir/test_cscope.vim
*** ../vim-8.1.1466/src/testdir/test_cscope.vim 2019-05-28 23:08:12.080648632
+0200
--- src/testdir/test_cscope.vim 2019-06-04 23:17:11.635163146 +0200
*
Yegappan wrote:
> On Mon, Jun 3, 2019 at 10:12 AM Daniel Hahler
> wrote:
> >
> > https://github.com/vim/vim/blob/98fb65cb051f625f4ce291a9f9cdb2e54ac1e688/runtime/doc/sign.txt#L185-L187:
> >
> > The priority is used to determine the
> > highlight group used when multiple signs are placed on the
Patch 8.1.1466
Problem:Not updating priority on existing sign.
Solution: Set the sign priority. Add a test. (Yegappan Lakshmanan)
Files: src/sign.c, src/testdir/test_signs.vim, runtime/doc/eval.txt,
runtime/doc/sign.txt
*** ../vim-8.1.1465/src/sign.c 2019-05-28 23:08:12
Patch 8.1.1465
Problem:Allocating wrong amount of memory. (Yegappan Lakshmanan)
Solution: Use sizeof() for right type of struct.
Files: src/memfile_test.c
*** ../vim-8.1.1464/src/memfile_test.c 2019-05-28 23:08:12.068648696 +0200
--- src/memfile_test.c 2019-06-04 22:25:02.116924696
Yegappan wrote:
> I see the following warning message when running "make test"
> in a MacOS system:
>
> memfile_test.c:70:7: warning: incompatible pointer types assigning to
> 'mf_hashitem_T *' (aka 'struct mf_hashitem_S *') from 'mf_hashtab_T *'
> (aka 'struct mf_hashtab_S *') [-Wi
On 04/06/2019 19:18, Bram Moolenaar wrote:
>
> Mike Williams wrote:
>
>> It looks like the change to Windows for resolve() in 8.1.1417 was a
>> breaking change. I use the NERDtree plugin and any build after than
>> change results in NERDtree reports plain files on Windows as links. See
>> attac
‐‐‐ Original Message ‐‐‐
On Tuesday, 4 June 2019 22:18, Marcin Szamotulski wrote:
> Hello vim_dev,
>
> I was always struck by the inconsistency of file ordere as returned by `:find
> lost.file` and command completion, e.g. `:e **/lost.file^d`. If there are
> multiple files of with n
Hello vim_dev,
I was always struck by the inconsistency of file ordere as returned by `:find
lost.file` and command completion, e.g. `:e **/lost.file^d`. If there are
multiple files of with name `lost.file` `:find` will explore them in different
order than what completion will suggest. Maybe s
Patch 8.1.1464
Problem:Only 4-digit rgb termresponse is recognized.
Solution: Also recognize 2-digit rgb response. (closes #4486)
Files: src/term.c, src/test_termcodes.vim
*** ../vim-8.1.1463/src/term.c 2019-05-28 23:08:12.080648632 +0200
--- src/term.c 2019-06-04 21:23:11.50857096
Mike Williams wrote:
> It looks like the change to Windows for resolve() in 8.1.1417 was a
> breaking change. I use the NERDtree plugin and any build after than
> change results in NERDtree reports plain files on Windows as links. See
> attached image.
>
> I guess the question is. is this wro
Ken Takata wrote:
> GCC 9.1 warns this:
>
> In file included from textprop.c:30:
> textprop.c: In function 'join_prop_lines':
> vim.h:1688:37: warning: 'props' may be used uninitialized in this function
> [-Wmaybe-uninitialized]
> 1688 | # define mch_memmove(to, from, len) memmove((char*)(to)
Patch 8.1.1463
Problem:Gcc warns for uninitialized variable.
Solution: Put usage inside "if". (Ken Takata)
Files: src/textprop.c
*** ../vim-8.1.1462/src/textprop.c 2019-05-28 23:08:12.080648632 +0200
--- src/textprop.c 2019-06-04 19:14:23.975238456 +0200
***
**
> I have tried to contact the author of hitest.vim a few days ago, but didn’t
> get any answer yet. Anyway, hopefully it’s on this list, too.
>
> I get E348 with runtime syntax/hitest.vim when whichwrap is set to a value
> different from the default. To reproduce:
>
> 1. create vimrc-hitest w
Hi,
It looks like the change to Windows for resolve() in 8.1.1417 was a
breaking change. I use the NERDtree plugin and any build after than
change results in NERDtree reports plain files on Windows as links. See
attached image.
I guess the question is. is this wrong in VIM or a bad assumption i
Hi,
On Mon, Jun 3, 2019 at 10:12 AM Daniel Hahler wrote:
>
> https://github.com/vim/vim/blob/98fb65cb051f625f4ce291a9f9cdb2e54ac1e688/runtime/doc/sign.txt#L185-L187:
>
> The priority is used to determine the
> highlight group used when multiple signs are placed on the
> same line.
>
> I assume it
Hi,
On Mon, Jun 3, 2019 at 10:12 AM Daniel Hahler wrote:
>
> https://github.com/vim/vim/blob/98fb65cb051f625f4ce291a9f9cdb2e54ac1e688/runtime/doc/sign.txt#L185-L187:
>
> The priority is used to determine the highlight group used when
> multiple signs are placed on the same line.
>
> I assume it i
Paul Jolly wrote:
> With the popup support coming along nicely, might it be an idea to put
> together some sort of showcase of the various popup options available?
>
> Perhaps a help-like file which gives some commentary of the various
> options, and demos for each option which are activated wh
On Di, 04 Jun 2019, Bram Moolenaar wrote:
>
> I have been wondering if it would help if Vim could play a sound. Think
> of a gentle "ping" to indicate the cursor can't move there, or a
> "tadaa" when a background build finishes successfully. At least I have
> had times where I didn't notice s
my first reaction is "useless cruft" -- sorry
my 2nd is, find the "vim way": don't build the sound into vim, use an
external voice
synthesizer that vim would send text messages to with informative
error info -- the
user would be left to assign their own voice to whatever synthesizer
they came up
I have been wondering if it would help if Vim could play a sound. Think
of a gentle "ping" to indicate the cursor can't move there, or a
"tadaa" when a background build finishes successfully. At least I have
had times where I didn't notice something that was going on, because I
was looking in t
Hi all,
Despite the documentation being quite clear, I was a little surprised
that setqflist did not trigger QuickFixCmdPre|QuickFixCmdPost.
This is hardly surprising: setqflist is a function, not a command.
Not only that, if we ignore the fact it's not a command, the very
example given in Quick
Hi,
GCC 9.1 warns this:
In file included from textprop.c:30:
textprop.c: In function 'join_prop_lines':
vim.h:1688:37: warning: 'props' may be used uninitialized in this function
[-Wmaybe-uninitialized]
1688 | # define mch_memmove(to, from, len) memmove((char*)(to), (char*)(from),
(size_t)(len
Hi Christian,
> How about a wiki page on https://github.com/vim/vim/ ah that is not
> enabled at the moment. Perhaps that should be enabled?
That's a good idea, hadn't thought of that.
My initial thought had been something that I can run "live" within a
Vim instance... but that's certainly not m
On Di, 04 Jun 2019, Paul Jolly wrote:
> Hi all,
>
> With the popup support coming along nicely, might it be an idea to put
> together some sort of showcase of the various popup options available?
>
> Perhaps a help-like file which gives some commentary of the various
> options, and demos for e
Hi all,
With the popup support coming along nicely, might it be an idea to put
together some sort of showcase of the various popup options available?
Perhaps a help-like file which gives some commentary of the various
options, and demos for each option which are activated when the mouse
hovers/cl
27 matches
Mail list logo
