Re: Patch 7.4.1818

2016-05-05 Fir de Conversatie Ken Takata 
Hi Bram,

2016/5/6 Fri 2:14:57 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
> 
> > 2016/5/6 Fri 0:19:06 UTC+9 Bram Moolenaar wrote:
> > > Patch 7.4.1818
> > > Problem:Help completion adds @en to all matches except the first one.
> > > Solution:   Remove "break", go over all items.
> > > Files:  src/ex_getln.c
> > 
> > This patch has a problem when help files with multiple languages are 
> > installed.
> > E.g. When @ja and @en are installed and 'helplang' is set to ja,
> > 
> >   :h screenrow()
> >   screenrow() screenrow()
> > 
> > But this should be:
> > 
> >   :h screenrow()
> >   screenrow() screenrow()@en
> > 
> > Or, when 'helplang' is not ja, this should be:
> > 
> >   :h screenrow()
> >   screenrow()@ja screenrow()@en
> > 
> > @en should not be removed, when there is a same help item for another
> > language.
> 
> I guess the problem is that it depends on the order, the check for a
> duplicate help tag in another language can happen after a language was
> already removed.

Do you have any ideas to fix this?
I don't have it, but the following behavior is totally useless:

  :h screenrow()
  screenrow() screenrow()


> > BTW, I think that adding @en to all matches is harmless.
> 
> Although this would be harmless, the @en should not be added when it's
> not needed, the matches look different from the actual help tag.

Wasn't setting 'helplang' to en enough?

Regards,
Ken Takata

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: move tabs using mouse in gvim

2016-05-05 Fir de Conversatie kamaraju kusumanchi 
On Thu, May 5, 2016 at 5:34 PM, Ben Fritz  wrote:
> On Thursday, May 5, 2016 at 6:17:08 AM UTC-5, kamaraju kusumanchi wrote:
>> I ask because I do not see any pull request for this in the official github
>> https://github.com/vim/vim/pulls . So may be it is integrated already?
>>
>
> Nope, it's still in the todo list. You probably won't ever see a pull request 
> for it since Bram has a patch instead.
>
> The good news is, it still applies cleanly, if you're willing to compile your 
> own Vim.

Thanks Ben. I compile my own vim version with this patch at home. But
at work it is a bit difficult as I do not have all the development
libraries, dependencies installed. Also, at home I use Debian Linux
and at work it is RedHat Enterprise. So I am not sure if I can just
copy the executable from one machine to another. I have not tried it
but may be I should give it a try.

thanks
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: move tabs using mouse in gvim

2016-05-05 Fir de Conversatie Ben Fritz 
On Thursday, May 5, 2016 at 6:17:08 AM UTC-5, kamaraju kusumanchi wrote:
> A while ago I asked about moving tabs in gvim using mouse (
> https://groups.google.com/forum/#!topic/vim_use/CfwgkVRm1jY ). In that
> thread Ken Takata mentioned that there is a patch available to do
> this.
> 
> I am wondering what is the current status of this patch? Is it
> integrated into gvim code base or is there a plan to do so in the
> future?
> 
> I ask because I do not see any pull request for this in the official github
> https://github.com/vim/vim/pulls . So may be it is integrated already?
> 

Nope, it's still in the todo list. You probably won't ever see a pull request 
for it since Bram has a patch instead.

The good news is, it still applies cleanly, if you're willing to compile your 
own Vim.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gvim crashes with ABRT & SEGV under AwesomeWM

2016-05-05 Fir de Conversatie Jeroen Budts 
On Thursday, May 5, 2016 at 9:55:21 AM UTC+2, Dominique Pelle wrote:
> Jeroen Budts  wrote:
> 
> > Hi All,
> >
> > (First off, I hope this is the correct mailinglist to report this. I first 
> > tried
> > vim_use but didn't get any response, sorry if I'm wrong here.)
> >
> > A few days ago I started using AwesomeWM (running as the WM inside
> > XFCE) and started seeing Gvim crashes (SEGV & ABRT) when I resize
> > the Gvim window (by changing the size of the master pane in the
> > tile-layout and by switching layouts). From what I understand these
> > indicate bugs?
> > I have been using Gvim for a few years now without much problems
> > under XFCE + XFWM (default Xubuntu). I also used Xmonad for one
> > week without problems.
> 
> Hi Jeron
> 
> I tried to reproduce the crash but I could not. My setup is a bit
> different since I used xubuntu-15.10 and my own build of vim-7.4.1817.
> I cloned your https://github.com/teranex/dotvim repo + added pathogen.
> I got errors when starting vim with your .vimrc so it seems
> that your git repo is missing a plugin:

Wow thanks for going through all those trouble. Is it possible that you did not 
initialize the git submodules (git submodule update --init)? All plugins, 
including pathogen, are submodules in my config.

> I installed awesome but I did not see any crash in vim.
> I resized Vim, also pressed Window+Space to change
> the layout in awesome and did not see crash.  But you
> might be doing something else that cause the crash.
> I'm not familiar with the awesome window manager so
> I only tried basic things.

The crash seems to be a bit random, but I trigger it as follows:
1. I switch to the tiling layout, which is the second layout in default Awesome.
2. Then I start Gvim and open a file, such as /etc/xdg/awesome/rc.lua
3. Then I start another Gvim and open another file (a markdown file for example)
4. Then I resize the master pane. Sometimes I have to do it just a few times, 
sometimes I have to hit Mod4+h and Mod4+l at random 50 times and/or switch 
layouts a few times.
5. One of both Gvim instances crashes.

I also tried to trigger the crash when Gvim is floating (Mod4 + Control + 
Space) and resizing Gvim with the mouse (Mod4+button3), but I can't seem to 
trigger the crash in this scenario.

Kind regards,
Jeroen

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gvim crashes with ABRT & SEGV under AwesomeWM

2016-05-05 Fir de Conversatie Jeroen Budts 
On Thursday, May 5, 2016 at 7:10:31 AM UTC+2, Dominique Pelle wrote:
> Jeroen Budts  wrote:
> 
> > Hi All,
> >
> > (First off, I hope this is the correct mailinglist to report this. I first 
> > tried
> > vim_use but didn't get any response, sorry if I'm wrong here.)
> >
> > A few days ago I started using AwesomeWM (running as the WM inside
> > XFCE) and started seeing Gvim crashes (SEGV & ABRT) when I resize
> > the Gvim window (by changing the size of the master pane in the
> > tile-layout and by switching layouts). From what I understand these
> > indicate bugs?
> > I have been using Gvim for a few years now without much problems
> > under XFCE + XFWM (default Xubuntu). I also used Xmonad for one
> > week without problems.
> >
> > I tried running Gvim without any of my own configuration [1] and can't
> > seem to replicate the crashes, so I guess it's either a specific setting
> > in my .vimrc or a plugin (or combination of) in combination with
> > Awesome. I'm not sure however how I can find the culprit other then
> > commenting my entire Vimrc and disabling all plugins and one-by-one
> > disable everything again, which seems a rather tedious task... So
> > any guidance on how I can find the real problem would be very helpful.
> 
> I suggest that you compile your own vim from the latest version
> from github, and you can build with symbols, so the stack trace
> will be more meaningful.
> Then try to reproduce the problem.

Thank you for the detailed explanation. I was able to build and run Gvim and 
trigger the crash.
I ran Gvim using the following command:
strace gvim -f -V9log.txt file.tex > stdout.txt 2> stderr.txt

And got the following output:
log.txt: http://budts.be/static/tmp/vim/strace-log.txt
stderr.txt: http://budts.be/static/tmp/vim/strace-stderr.txt
Last lines of stderr.txt indicate the SIGABRT:
rt_sigaction(SIGABRT, {SIG_DFL, [], SA_RESTORER, 0x7fd12e79d4a0}, {0x53c239, 
[], SA_RESTORER, 0x7fd12e79d4a0}, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [ABRT], [ABRT USR1], 8) = 0
kill(13934, SIGABRT)= 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_USER, si_pid=13934, si_uid=1000} ---
+++ killed by SIGABRT (core dumped) +++

> I also suggest to try running vim with valgrind
> with something like this:
> 
> $ valgrind --log-file=vg.log --check-origins=yes --num-callers=50 vim
valgrind told me it didn't know the check-origins option. Man page also only 
mentioned track-origins.
When I ran Gvim with the following command:
valgrind --log-file=vg.log  --num-callers=50 gvim -f
I got the following vg.log: http://budts.be/static/tmp/vim/valgrind.log
Last lines indicate a SIGSEGV:
==6042== Invalid read of size 4
==6042==at 0x5C951D: in_id_list (syntax.c:6180)
==6042==by 0x5C03FF: syn_current_attr (syntax.c:2096)
==6042==by 0x5BFC8C: get_syntax_attr (syntax.c:1868)
==6042==by 0x57E2E9: win_line (screen.c:4385)
==6042==by 0x57666B: update_single_line (screen.c:824)
==6042==by 0x6234AD: main_loop (main.c:1306)
==6042==by 0x622EC8: main (main.c:1051)
==6042==  Address 0x15582d14 is not stack'd, malloc'd or (recently) free'd
==6042== 
==6042== 
==6042== Process terminating with default action of signal 11 (SIGSEGV)
==6042==at 0x7BF5757: kill (syscall-template.S:84)
==6042==by 0x53E72F: may_core_dump (os_unix.c:3297)
==6042==by 0x53E6D3: mch_exit (os_unix.c:3263)
==6042==by 0x6238E3: getout (main.c:1540)
==6042==by 0x4F61B8: preserve_exit (misc1.c:9488)
==6042==by 0x53C3DC: deathtrap (os_unix.c:1110)
==6042==by 0x7BF549F: ??? (in /lib/x86_64-linux-gnu/libc-2.23.so)
==6042==by 0x5C951C: in_id_list (syntax.c:6180)
==6042==by 0x5C03FF: syn_current_attr (syntax.c:2096)
==6042==by 0x5BFC8C: get_syntax_attr (syntax.c:1868)
==6042==by 0x57E2E9: win_line (screen.c:4385)
==6042==by 0x57666B: update_single_line (screen.c:824)
==6042==by 0x6234AD: main_loop (main.c:1306)
==6042==by 0x622EC8: main (main.c:1051)

Thanks again for your help so far,
Jeroen

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run a job asynchronously?

2016-05-05 Fir de Conversatie Andrew Stewart 
> On 5 May 2016, at 5:14 pm, Bram Moolenaar  wrote:
> 
> Andrew Stewart wrote:
>> 
>> I've just realised that every time a job runs, a new process is
>> spawned as a child of vim's process, and they're all in the zombie
>> state.  They only disappear once I quit Vim or it crashes.
> 
> This must be a Mac specific problem, it doesn't call waitpid() to get
> the status of the child.  You can try using Vim as it's build on Unix,
> should also work on Mac in a terminal.

I get this behaviour using "pure" Vim (built with homebrew on OS X 10.11.4), 
not MacVim.  v7.4.1817 this time.

I'm watching the processes using htop in tree view.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch 7.4.1818

2016-05-05 Fir de Conversatie Gary Johnson 
On 2016-05-05, Bram Moolenaar wrote:
> Ken Takata wrote:
> 
> > 2016/5/6 Fri 0:19:06 UTC+9 Bram Moolenaar wrote:
> > > Patch 7.4.1818
> > > Problem:Help completion adds @en to all matches except the first one.
> > > Solution:   Remove "break", go over all items.
> > > Files:  src/ex_getln.c
> > 
> > This patch has a problem when help files with multiple languages are 
> > installed.
> > E.g. When @ja and @en are installed and 'helplang' is set to ja,
> > 
> >   :h screenrow()
> >   screenrow() screenrow()
> > 
> > But this should be:
> > 
> >   :h screenrow()
> >   screenrow() screenrow()@en
> > 
> > Or, when 'helplang' is not ja, this should be:
> > 
> >   :h screenrow()
> >   screenrow()@ja screenrow()@en
> > 
> > @en should not be removed, when there is a same help item for another
> > language.
> 
> I guess the problem is that it depends on the order, the check for a
> duplicate help tag in another language can happen after a language was
> already removed.
> 
> > BTW, I think that adding @en to all matches is harmless.
> 
> Although this would be harmless, the @en should not be added when it's
> not needed, the matches look different from the actual help tag.

It would also add clutter to the list, making it harder to read and
to identify interesting matches.

Thank you for fixing the problem.  My help tag completion lists look
much better now.

Regards,
Gary

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch 7.4.1818

2016-05-05 Fir de Conversatie Bram Moolenaar 

Ken Takata wrote:

> 2016/5/6 Fri 0:19:06 UTC+9 Bram Moolenaar wrote:
> > Patch 7.4.1818
> > Problem:Help completion adds @en to all matches except the first one.
> > Solution:   Remove "break", go over all items.
> > Files:  src/ex_getln.c
> 
> This patch has a problem when help files with multiple languages are 
> installed.
> E.g. When @ja and @en are installed and 'helplang' is set to ja,
> 
>   :h screenrow()
>   screenrow() screenrow()
> 
> But this should be:
> 
>   :h screenrow()
>   screenrow() screenrow()@en
> 
> Or, when 'helplang' is not ja, this should be:
> 
>   :h screenrow()
>   screenrow()@ja screenrow()@en
> 
> @en should not be removed, when there is a same help item for another
> language.

I guess the problem is that it depends on the order, the check for a
duplicate help tag in another language can happen after a language was
already removed.

> BTW, I think that adding @en to all matches is harmless.

Although this would be harmless, the @en should not be added when it's
not needed, the matches look different from the actual help tag.

-- 
Communication is one of the most compli..., eh, well, it's hard.
You know what I mean.  Not?

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch 7.4.1818

2016-05-05 Fir de Conversatie Ken Takata 
Hi Bram,

2016/5/6 Fri 0:19:06 UTC+9 Bram Moolenaar wrote:
> Patch 7.4.1818
> Problem:Help completion adds @en to all matches except the first one.
> Solution:   Remove "break", go over all items.
> Files:  src/ex_getln.c

This patch has a problem when help files with multiple languages are installed.
E.g. When @ja and @en are installed and 'helplang' is set to ja,

  :h screenrow()
  screenrow() screenrow()

But this should be:

  :h screenrow()
  screenrow() screenrow()@en

Or, when 'helplang' is not ja, this should be:

  :h screenrow()
  screenrow()@ja screenrow()@en

@en should not be removed, when there is a same help item for another language.
BTW, I think that adding @en to all matches is harmless.

Regards,
Ken Takata

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run a job asynchronously?

2016-05-05 Fir de Conversatie Bram Moolenaar 

Andrew Stewart wrote:

> On Thursday, 5 May 2016 10:25:19 UTC+1, Andrew Stewart  wrote:
> > >> When I edit a file my job runs.  When I trigger a second run, Vim
> > >> always crashes with a segfault:
> > >> 
> > >> Vim: Caught deadly signal SEGV
> > >> Vim: Finished.
> > >> Segmentation fault: 11
> 
> I've just realised that every time a job runs, a new process is
> spawned as a child of vim's process, and they're all in the zombie
> state.  They only disappear once I quit Vim or it crashes.

This must be a Mac specific problem, it doesn't call waitpid() to get
the status of the child.  You can try using Vim as it's build on Unix,
should also work on Mac in a terminal.

-- 
"I love deadlines.  I especially like the whooshing sound they
make as they go flying by."
 -- Douglas Adams

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run a job asynchronously?

2016-05-05 Fir de Conversatie Bram Moolenaar 

Andrew Stewart wrote:

> > On 4 May 2016, at 8:49 pm, Bram Moolenaar  wrote:
> >> Regarding redrawing: adding a redraw! as the last line of my close
> >> handler doesn't redraw the screen.  Should I be doing this somewhere
> >> else?
> > 
> > Hmm, does it redraw the moment you type something?
> 
> Yes it does.  In my case the signs are suddenly displayed.
> 
> > It looks like the function to redraw after a callback is not invoked
> > after using the close_cb.  I'll make a patch for that.
> 
> Thanks.  I upgraded to Vim 7.4.1817 and reinstated the redraw! as the
> last line of my close_cb handler.  Unfortunately the problem remains.

It looks like it works for me, with this test:


func! CloseCb(chan)
  syn match Error "foo"
endfunc

call ch_logfile('channellog', 'w')

call job_start('echo nothing', {'close_cb': 'CloseCb'})


The "foo" gets highlighted right away.


-- 
INSPECTOR END OF FILM: Move along.  There's nothing to see!  Keep moving!
   [Suddenly he notices the cameras.]
INSPECTOR END OF FILM: (to Camera) All right, put that away sonny.
   [He walks over to it and puts his hand over the lens.]
 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Patch 7.4.1819

2016-05-05 Fir de Conversatie Bram Moolenaar 

Patch 7.4.1819
Problem:Compiler warnings when sprintf() is a macro.
Solution:   Don't interrupt sprintf() with an #ifdef. (Michael Jarvis,
closes #788)
Files:  src/fileio.c, src/tag.c, src/term.c


*** ../vim-7.4.1818/src/fileio.c2016-04-20 12:49:43.518961695 +0200
--- src/fileio.c2016-05-05 18:06:03.284933558 +0200
***
*** 5230,5243 
  if (insert_space)
*p++ = ' ';
  if (shortmess(SHM_LINES))
-   sprintf((char *)p,
  #ifdef LONG_LONG_OFF_T
!   "%ldL, %lldC", lnum, (long long)nchars
  #else
/* Explicit typecast avoids warning on Mac OS X 10.6 */
!   "%ldL, %ldC", lnum, (long)nchars
  #endif
-   );
  else
  {
if (lnum == 1)
--- 5230,5243 
  if (insert_space)
*p++ = ' ';
  if (shortmess(SHM_LINES))
  #ifdef LONG_LONG_OFF_T
!   sprintf((char *)p,
!   "%ldL, %lldC", lnum, (long long)nchars);
  #else
+   sprintf((char *)p,
/* Explicit typecast avoids warning on Mac OS X 10.6 */
!   "%ldL, %ldC", lnum, (long)nchars);
  #endif
  else
  {
if (lnum == 1)
***
*** 5248,5261 
if (nchars == 1)
STRCPY(p, _("1 character"));
else
-   sprintf((char *)p,
  #ifdef LONG_LONG_OFF_T
!   _("%lld characters"), (long long)nchars
  #else
/* Explicit typecast avoids warning on Mac OS X 10.6 */
!   _("%ld characters"), (long)nchars
  #endif
-   );
  }
  }
  
--- 5248,5261 
if (nchars == 1)
STRCPY(p, _("1 character"));
else
  #ifdef LONG_LONG_OFF_T
!   sprintf((char *)p,
!   _("%lld characters"), (long long)nchars);
  #else
+   sprintf((char *)p,
/* Explicit typecast avoids warning on Mac OS X 10.6 */
!   _("%ld characters"), (long)nchars);
  #endif
  }
  }
  
*** ../vim-7.4.1818/src/tag.c   2016-04-18 19:45:13.463066926 +0200
--- src/tag.c   2016-05-05 18:09:27.254809026 +0200
***
*** 2264,2269 
--- 2264,2270 
if (ga_grow(_match[mtt], 1) == OK)
{
int len;
+   int heuristic;
  
if (help_only)
{
***
*** 2293,2305 
p[len] = '@';
STRCPY(p + len + 1, help_lang);
  #endif
!   sprintf((char *)p + len + 1 + ML_EXTRA, "%06d",
!   help_heuristic(tagp.tagname,
!   match_re ? matchoff : 0, !match_no_ic)
  #ifdef FEAT_MULTI_LANG
!   + help_pri
  #endif
!   );
}
*tagp.tagname_end = TAB;
}
--- 2294,2307 
p[len] = '@';
STRCPY(p + len + 1, help_lang);
  #endif
! 
!   heuristic = help_heuristic(tagp.tagname,
!   match_re ? matchoff : 0, !match_no_ic);
  #ifdef FEAT_MULTI_LANG
!   heuristic += help_pri;
  #endif
!   sprintf((char *)p + len + 1 + ML_EXTRA, "%06d",
!  heuristic);
}
*tagp.tagname_end = TAB;
}
*** ../vim-7.4.1818/src/term.c  2016-04-29 22:58:25.626876587 +0200
--- src/term.c  2016-05-05 18:11:31.709542849 +0200
***
*** 2630,2641 
  || STRCMP(s + i + 1, "%dm") == 0)
  && (s[i] == '3' || s[i] == '4'))
  {
-   sprintf(buf,
  #ifdef TERMINFO
!   "%s%s%%p1%%dm",
  #else
!   "%s%s%%dm",
  #endif
i == 2 ? IF_EB("\033[", ESC_STR "[") : "\233",
s[i] == '3' ? (n >= 16 ? "38;5;" : "9")
: (n >= 16 ? "48;5;" : "10"));
--- 2630,2641 
  || STRCMP(s + i + 1, "%dm") == 0)
  && (s[i] == '3' || s[i] == '4'))
  {
  #ifdef TERMINFO
!   char *format = "%s%s%%p1%%dm";
  #else
!   char *format = "%s%s%%dm";
  #endif
+   sprintf(buf, format,
i == 2 ? IF_EB("\033[", ESC_STR "[") : "\233",
s[i] == '3' ? (n >= 16 ? "38;5;" : "9")
: (n >= 16 ? "48;5;" : "10"));
*** ../vim-7.4.1818/src/version.c   2016-05-05 17:18:36.963948500 +0200
--- src/version.c   2016-05-05 18:12:10.129151221 +0200
***
*** 755,756 
--- 755,758 
  {   /* Add new patch number below this line */
+ /**/
+ 1819,
  /**/

-- 
NEIL INNES PLAYED: THE FIRST SELF-DESTRUCTIVE MONK, ROBIN'S LEAST FAVORITE
   MINSTREL, THE PAGE CRUSHED BY A RABBIT, THE OWNER OF A DUCK

Re: Bug in 7.4.1786: command-line completion list entries end with "@en"

2016-05-05 Fir de Conversatie Bram Moolenaar 

Hirohito Higashi wrote:

> Hi Gary,
> 
> 2016-5-5(Thu) 16:28:58 UTC+9 Gary Johnson:
> > When performing command-line completion of help tags, all but the
> > first entry in the completion list is appended with "@en".  For
> > example, after starting vim as
> > 
> > $ vim -N -u NONE
> > 
> > type ":help screen" and Ctrl-D:
> > 
> > :help screen^D
> > screencol()   screenchar()@en   xterm-save-screen@en
> > screenrow()@enxterm-screens@en  'restorescreen'@en
> > screenattr()@en   posix-screen-size@en  'norestorescreen'@en
> > :help screen
> > 
> > This seems to be related to the locale.  My locale is usually the
> > following,
> > 
> > LANG=en_US.UTF-8
> > LANGUAGE=
> > LC_CTYPE="en_US.UTF-8"
> > LC_NUMERIC="en_US.UTF-8"
> > LC_TIME="en_US.UTF-8"
> > LC_COLLATE=C
> > LC_MONETARY="en_US.UTF-8"
> > LC_MESSAGES="en_US.UTF-8"
> > LC_PAPER="en_US.UTF-8"
> > LC_NAME="en_US.UTF-8"
> > LC_ADDRESS="en_US.UTF-8"
> > LC_TELEPHONE="en_US.UTF-8"
> > LC_MEASUREMENT="en_US.UTF-8"
> > LC_IDENTIFICATION="en_US.UTF-8"
> > LC_ALL=
> > 
> > If I set LANG=C before starting vim, the @en suffixes no longer
> > appear in completion lists.
> > 
> > I am running vim 7.4.1786 on Linux.  This started recently, but I
> > didn't notice exactly when.
> 
> Change point is Vim 7.4.1671.
> https://groups.google.com/forum/#!searchin/vim_dev/7.4.1671/vim_dev/JXQEvU9AUtw/SFfl6eJbHAAJ
> 
> 
> $ LANG=en_us.utf-8 vim -Nu NONE
> 
> Vim 7.4.1670 or older:
> :h scree
> screencol()screenchar()   xterm-save-screen
> screenrow()xterm-screens  'restorescreen'
> screenattr()   posix-screen-size  'norestorescreen'
> :h scree
> 
> Vim 7.4.1671 or newer
> :h scree
> screencol()   screenchar()@en   xterm-save-screen@en
> screenrow()@enxterm-screens@en  'restorescreen'@en
> screenattr()@en   posix-screen-size@en  'norestorescreen'@en
> :h scree
> 
> It's only reporting.  sorry :-)

Thanks for pointing to that patch.  I see it adds a "break" that should
not be there.

-- 
ARTHUR: CHARGE!
   [The mighty ARMY charges.  Thundering noise of feet.  Clatter of coconuts.
   Shouts etc.   Suddenly there is a wail of a siren and a couple of police
   cars roar round in front of the charging ARMY and the POLICE leap out and
   stop them.  TWO POLICEMAN and the HISTORIAN'S WIFE.  Black Marias skid up
   behind them.]
HISTORIAN'S WIFE: They're the ones, I'm sure.
 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Patch 7.4.1818

2016-05-05 Fir de Conversatie Bram Moolenaar 

Patch 7.4.1818
Problem:Help completion adds @en to all matches except the first one.
Solution:   Remove "break", go over all items.
Files:  src/ex_getln.c


*** ../vim-7.4.1817/src/ex_getln.c  2016-03-28 19:58:59.155781382 +0200
--- src/ex_getln.c  2016-05-05 17:16:37.817306285 +0200
***
*** 3189,3196 
  #endif
  
  /*
!  * this function is called when the screen size changes and with incremental
!  * search
   */
  void
  redrawcmdline(void)
--- 3189,3197 
  #endif
  
  /*
!  * This function is called when the screen size changes and with incremental
!  * search and in other situations where the command line may have been
!  * overwritten.
   */
  void
  redrawcmdline(void)
***
*** 4505,4511 
  char_ubuf[4];
  char_u*p = buf;
  
! if (p_hlg[0] != NUL)
  {
*p++ = '@';
*p++ = p_hlg[0];
--- 4506,4512 
  char_ubuf[4];
  char_u*p = buf;
  
! if (p_hlg[0] != NUL && (p_hlg[0] != 'e' || p_hlg[1] != 'n'))
  {
*p++ = '@';
*p++ = p_hlg[0];
***
*** 4518,4527 
len = (int)STRLEN(file[i]) - 3;
if (len <= 0)
continue;
!   if (i == 0 && STRCMP(file[i] + len, buf) == 0)
{
file[i][len] = NUL;
-   break;
}
else if (STRCMP(file[i] + len, "@en") == 0)
{
--- 4519,4528 
len = (int)STRLEN(file[i]) - 3;
if (len <= 0)
continue;
!   if (STRCMP(file[i] + len, buf) == 0)
{
+   /* remove the default language */
file[i][len] = NUL;
}
else if (STRCMP(file[i] + len, "@en") == 0)
{
***
*** 4533,4542 
&& STRNCMP(file[i], file[j], len + 1) == 0)
break;
if (j == num_file)
!   {
file[i][len] = NUL;
-   break;
-   }
}
  }
  }
--- 4534,4541 
&& STRNCMP(file[i], file[j], len + 1) == 0)
break;
if (j == num_file)
!   /* item only exists with @en, remove it */
file[i][len] = NUL;
}
  }
  }
*** ../vim-7.4.1817/src/version.c   2016-05-04 21:49:15.004075133 +0200
--- src/version.c   2016-05-05 17:17:50.420479043 +0200
***
*** 755,756 
--- 755,758 
  {   /* Add new patch number below this line */
+ /**/
+ 1818,
  /**/

-- 
   [The rest of the ARMY stand around looking at a loss.]
INSPECTOR END OF FILM: (picks up megaphone) All right!  Clear off!  Go on!
 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

2016-05-05 Fir de Conversatie Charles Campbell 
Nick James wrote:
>
> If I invoke vim without a file |vim| then type |:Man vim| I get |E492:
> Not an editor command: Man vim|. I /think/ this is expected.
>
> If I invoke vim without a file |vim| then type |:set filetype=man|
> followed by |:Man vim| it opens correctly. On my system (RHEL 6.5)
> |man| is at |/usr/bin/man|.
>
> It seems the issue is only when invoking via |tcsh|. I also gave it a
> quick test in |bash| with the same result.
>
>
With ManPageView
(http://www.drchip.org/astronaut/vim/index.html#MANPAGEVIEW) you'll get:

vim without a file, then :Man vim  : a manual page for vim  (tried this
with ksh, tcsh, bash, on a Scientific Linux, 6.7)
vim without a file, then :set ft=man, then :Man vim : a manual page for
vim  (tried this with ksh, tcsh, bash, on a Scientific Linux, 6.7)

Regards,
Chip Campbell

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run a job asynchronously?

2016-05-05 Fir de Conversatie boss 
On Thursday, 5 May 2016 10:25:19 UTC+1, Andrew Stewart  wrote:
> >> When I edit a file my job runs.  When I trigger a second run, Vim
> >> always crashes with a segfault:
> >> 
> >> Vim: Caught deadly signal SEGV
> >> Vim: Finished.
> >> Segmentation fault: 11

I've just realised that every time a job runs, a new process is spawned as a 
child of vim's process, and they're all in the zombie state.  They only 
disappear once I quit Vim or it crashes.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

move tabs using mouse in gvim

2016-05-05 Fir de Conversatie kamaraju kusumanchi 
A while ago I asked about moving tabs in gvim using mouse (
https://groups.google.com/forum/#!topic/vim_use/CfwgkVRm1jY ). In that
thread Ken Takata mentioned that there is a patch available to do
this.

I am wondering what is the current status of this patch? Is it
integrated into gvim code base or is there a plan to do so in the
future?

I ask because I do not see any pull request for this in the official github
https://github.com/vim/vim/pulls . So may be it is integrated already?

thanks
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

The other "INSERT VISUAL" mode.

2016-05-05 Fir de Conversatie Björn Linse 
When entering visual mode from insert mode v vim is in "(insert) VISUAL" 
mode and will reenter insert mode after a finished operator. However there 
seems to be another "INSERT VISUAL" mode that can be entered like so:


let g:modal = ""
function! Modal()
if g:modal != ""
execute "normal! ".g:modal
let g:modal = ""
endif
endfunction
autocmd! InsertEnter * call Modal()

nnoremap ,i :let g:modal = "v"i
nnoremap ,s :let g:modal = "gh"i

now ,i in normal mode will enter an insert mode, where  goes to visual 
mode with the just inserted text selected. Now this seems useful, but drawing 
is quite buggy in "INSERT VISUAL" mode. However "INSERT SELECT" entered by ,s 
seems less useful: the user types some text, press , now the typed text is 
selected and will be overwritten by the next thing the user types.

Sending ["ex", "normal! v"] over a channel to a vim being in insert mode has 
the same effect.

Are these modes intentional behavior? I can't find them in the documentation.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run a job asynchronously?

2016-05-05 Fir de Conversatie Andrew Stewart 
> On 4 May 2016, at 8:49 pm, Bram Moolenaar  wrote:
>> Regarding redrawing: adding a redraw! as the last line of my close
>> handler doesn't redraw the screen.  Should I be doing this somewhere
>> else?
> 
> Hmm, does it redraw the moment you type something?

Yes it does.  In my case the signs are suddenly displayed.

> It looks like the function to redraw after a callback is not invoked
> after using the close_cb.  I'll make a patch for that.

Thanks.  I upgraded to Vim 7.4.1817 and reinstated the redraw! as the last line 
of my close_cb handler.  Unfortunately the problem remains.

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

gvim movement is slow when enable cursorline

2016-05-05 Fir de Conversatie 驼峰 
If I set the environment variable "__COMPAT_LAYER=Win7RTM" in Windows cmd.exe, 
the gvim movement will be very slow when enable cursorline. 

The issue will be gone if I either remove that environment variable or turn off 
cursorline. 

do you guys know the cause of this issue?

Thanks,
-Mike Guo

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bug in 7.4.1786: command-line completion list entries end with "@en"

2016-05-05 Fir de Conversatie h_east 
Hi Gary,

2016-5-5(Thu) 16:28:58 UTC+9 Gary Johnson:
> When performing command-line completion of help tags, all but the
> first entry in the completion list is appended with "@en".  For
> example, after starting vim as
> 
> $ vim -N -u NONE
> 
> type ":help screen" and Ctrl-D:
> 
> :help screen^D
> screencol()   screenchar()@en   xterm-save-screen@en
> screenrow()@enxterm-screens@en  'restorescreen'@en
> screenattr()@en   posix-screen-size@en  'norestorescreen'@en
> :help screen
> 
> This seems to be related to the locale.  My locale is usually the
> following,
> 
> LANG=en_US.UTF-8
> LANGUAGE=
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE=C
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
> 
> If I set LANG=C before starting vim, the @en suffixes no longer
> appear in completion lists.
> 
> I am running vim 7.4.1786 on Linux.  This started recently, but I
> didn't notice exactly when.

Change point is Vim 7.4.1671.
https://groups.google.com/forum/#!searchin/vim_dev/7.4.1671/vim_dev/JXQEvU9AUtw/SFfl6eJbHAAJ


$ LANG=en_us.utf-8 vim -Nu NONE

Vim 7.4.1670 or older:
:h scree
screencol()screenchar()   xterm-save-screen
screenrow()xterm-screens  'restorescreen'
screenattr()   posix-screen-size  'norestorescreen'
:h scree

Vim 7.4.1671 or newer
:h scree
screencol()   screenchar()@en   xterm-save-screen@en
screenrow()@enxterm-screens@en  'restorescreen'@en
screenattr()@en   posix-screen-size@en  'norestorescreen'@en
:h scree

It's only reporting.  sorry :-)
--
Best regards,
Hirohito Higashi (a.k.a. h_east)

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gvim crashes with ABRT & SEGV under AwesomeWM

2016-05-05 Fir de Conversatie Dominique Pellé 
Jeroen Budts  wrote:

> Hi All,
>
> (First off, I hope this is the correct mailinglist to report this. I first 
> tried
> vim_use but didn't get any response, sorry if I'm wrong here.)
>
> A few days ago I started using AwesomeWM (running as the WM inside
> XFCE) and started seeing Gvim crashes (SEGV & ABRT) when I resize
> the Gvim window (by changing the size of the master pane in the
> tile-layout and by switching layouts). From what I understand these
> indicate bugs?
> I have been using Gvim for a few years now without much problems
> under XFCE + XFWM (default Xubuntu). I also used Xmonad for one
> week without problems.

Hi Jeron

I tried to reproduce the crash but I could not. My setup is a bit
different since I used xubuntu-15.10 and my own build of vim-7.4.1817.
I cloned your https://github.com/teranex/dotvim repo + added pathogen.
I got errors when starting vim with your .vimrc so it seems
that your git repo is missing a plugin:

Error detected while processing /home/pel/.vimrc:
line  280:
E117: Unknown function: Pl#Theme#InsertSegment
line  281:
E117: Unknown function: Pl#Theme#RemoveSegment
line  282:
E117: Unknown function: Pl#Theme#RemoveSegment
line  284:
E117: Unknown function: Pl#Theme#RemoveSegment
line  285:
E117: Unknown function: Pl#Theme#RemoveSegment
line  286:
E117: Unknown function: Pl#Theme#RemoveSegment
line  287:
E117: Unknown function: Pl#Theme#ReplaceSegment
line  288:
E117: Unknown function: Pl#Theme#ReplaceSegment
line  289:
E117: Unknown function: Pl#Theme#InsertSegment

When doing  :e .vimrc I also get errors:

Error detected while processing BufRead Auto commands for "*":
E492: Not an editor command: Rooter
E492: Not an editor command: :DetectIndent

I installed awesome but I did not see any crash in vim.
I resized Vim, also pressed Window+Space to change
the layout in awesome and did not see crash.  But you
might be doing something else that cause the crash.
I'm not familiar with the awesome window manager so
I only tried basic things.

Please try to build the latest vim with debug symbols so
we have good stack traces, and try with valgrind as
suggested earlier email.

Regards
Dominique

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bug in 7.4.1786: command-line completion list entries end with "@en"

2016-05-05 Fir de Conversatie Gary Johnson 
When performing command-line completion of help tags, all but the
first entry in the completion list is appended with "@en".  For
example, after starting vim as

$ vim -N -u NONE

type ":help screen" and Ctrl-D:

:help screen^D
screencol()   screenchar()@en   xterm-save-screen@en
screenrow()@enxterm-screens@en  'restorescreen'@en
screenattr()@en   posix-screen-size@en  'norestorescreen'@en
:help screen

This seems to be related to the locale.  My locale is usually the
following,

LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

If I set LANG=C before starting vim, the @en suffixes no longer
appear in completion lists.

I am running vim 7.4.1786 on Linux.  This started recently, but I
didn't notice exactly when.

Regards,
Gary

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Fix clang/OS X warnings about embedded directives within macro arguments to sprintf (#788)

2016-05-05 Fir de Conversatie Michael Jarvis 
On Thursday, May 5, 2016 at 12:57:14 AM UTC-5, Michael Jarvis wrote:
> Also, I've submitted patches to the list before, but this is my first attempt 
> at using a Github pull request instead of just writing a post directly to 
> vim-dev. Hopefully this works!  :-)


It worked!  

-- 
-- 
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 Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.