Re: Vim 8.0 released!
Thank you for this new Vim release! I am loving the new features. https://github.com/w0rp/ale I have already started working on a plugin for linting while you type which uses the new asynchronous execution features. It seems to work now for flake8 and eslint. I'll add more tools as I need them, or as people as for them. Hopefully this will be useful for others, and other plugins will start taking advantage of asynchronous execution too. -- -- 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 and ASCII glyphs
On 2016-08-11, 15:40 GMT, Kazunobu Kuriyama wrote: >> Screenshot attached. (I haven't try PragmataPro.) > > I don't either for an obvious reason..Isn't there a free version? :) Would https://github.com/tonsky/FiraCode/ work? Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 ..every Man has a Property in his own Person. This no Body has any Right to but himself. The Labour of his Body, and the Work of his Hands, we may say, are properly his. The great and chief end therefore, of Mens uniting into Commonwealths, and putting themselves under Government, is the Preservation of their Property. -- John Locke, "A Treatise Concerning Civil Government" -- -- 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 8.0 released!
Thanks a bunch! I finally got my head out of my and sent 0.1 Bitcoins to The Cause™:-) I care about the people in Uganda too. Keep up the good work! - bahner -- -- 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 and ASCII glyphs
On 2016-08-08, 12:50 GMT, Tony Mechelynck wrote: > You should see, in that order, the glyphs for ff fi fl ft st > ffi ffl. > I absolutely don't like them (in the monospaced fonts that > have them; in serif or sans-serif fonts it's different, > especially in serif italic). OTOH, I think that expanding them > to two or three character cells would be ugly the opposite > way. It could be the problem with your font. I use https://github.com/tonsky/FiraCode/ and it seems to work for me just fine. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 May you come to the attention of those in authority. May you find what you are looking for. May you live in interesting times. -- claimed to be a Chinese proverb, but its origin is disputed first documented use Frederic R. Coudert, Proceedings of the Academy of Political Science, 1939 -- -- 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 and ASCII glyphs
On 2016-08-07, 11:27 GMT, manuelschiller.pimail via vim_dev wrote: > Please let me know if it would be possible to include this, > and if not, at least the patch is public now where people can > find it if they want it. https://github.com/vim/vim/issues/418#issuecomment-246748135 and the (completely unofficial) build for RHEL/CentOS-7 is on http://koji.fedoraproject.org/koji/taskinfo?taskID=15617207 Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Quod fuimus, estis; quod sumus, vos eritis. -- -- 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 with function()
Christian Brabandt wrote:
> Bram,
> I think this is a bug:
> :echo function('tr')
> -> returns tr
> :echo function('tr()')
> -> errors: E475: Invalid argument: [NULL]
> 0
You mean that it says NULL? That can be fixed.
--
Women are probably the main cause of free software starvation.
/// 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: Possible problem when running a job immediately followed by a sleep
The script's output is being used as a way to check for any syntax error,
it should print (and it is, in bash):
/bin/sh errors.sh
errors.sh: line 5: syntax error near unexpected token `newline'
errors.sh: line 5: `foo('
And yes, the job exits quickly, in fact, if you use a short sleep (ie:
sleep 1m) it works, not all the times, though.
I've been looking at the ch_logfile messages and got:
- RubJob # works
133.807009 : Starting job: /bin/sh errors.sh
133.807064 on 8: Created channel
133.807414 on 7: Freeing job
133.807501 : looking for messages on channels
133.807506 on 7: Closing channel
133.807508 on 7: Clearing channel
133.807511 on 7: Freeing channel
133.807534 : looking for messages on channels
133.808933 RECV on 8: 'errors.sh: line 5: syntax error near unexpected
token `newline'
errors.sh: line 5: `foo('
'
133.808941 on 8: Invoking channel callback HandlerCallback
133.809058 on 8: Invoking channel callback HandlerCallback
133.809108 ERR on 8: channel_select_check(): Cannot read from channel, will
close it soon
133.809112 : looking for messages on channels
133.809114 on 8: Closing channel because of previous read error
133.809116 on 8: Closing channel
133.809122 on 8: Invoking callbacks before closing
133.809124 on 8: Invoking close callback HandlerClose
134.309137 : looking for messages on channels
144.312764 on 8: Job ended
- RunJob | sleep 50m # doesn't work
151.694974 : Starting job: /bin/sh errors.sh
151.695013 on 9: Created channel
151.695387 on 8: Freeing job
151.745598 ERR on 9: channel_select_check(): Cannot read from channel, will
close it soon
151.745623 : looking for messages on channels
151.745628 on 9: Closing channel because of previous read error
151.745631 on 9: Closing channel
151.745650 on 9: Invoking callbacks before closing
151.745655 on 9: Invoking close callback HandlerClose
151.745764 on 8: Closing channel
151.745767 on 8: Clearing channel
151.745771 on 8: Freeing channel
151.745792 : looking for messages on channels
162.255837 on 9: Job ended
On Tue, Sep 13, 2016 at 4:59 PM, Bram Moolenaar wrote:
>
> Santiago Alejandro Agüero wrote:
>
> > While I was trying to write some vim code for testing a (async)
> > functionality for Neomake plugin, I've noticed the following scenario:
> >
> >
> > - Having the following shell script (with errors):
> >
> > #!/bin/sh
> >
> > a='$var'
> >
> > foo(
> >
> >
> > - And the next vim test code:
> >
> > function! StartJob()
> > let g:job = job_start(['/bin/sh', 'errors.sh'], {
> > \ 'callback': 'HandlerCallback',
> > \ 'close_cb': 'HandlerClose',
> > \ 'exit_cb': 'HandlerExit'
> > \ })
> > endfunction
> >
> > function! HandlerCallback(channel, line) abort
> > call Debug('[Callback] channel: ' . a:channel . ', line: ' . a:line
> . ', channelStatus: ' . ch_status(a:channel))
> > endfunction
> >
> > function! HandlerClose(channel) abort
> > call Debug('[Close] channel: ' . a:channel . ', channelStatus: ' .
> ch_status(a:channel))
> > endfunction
> >
> > function! HandlerExit(job, status) abort
> > call Debug('[Exit] job: ' . a:job . ', status: ' . a:status . ',
> jobStatus: ' . job_status(a:job))
> > endfunction
> >
> > function! Debug(msg) abort
> > call writefile([a:msg], 'output.log', 'a')
> > endfunction
> >
> > command! -bar RunJob call StartJob()
> >
> >
> > - Then the following thing happens:
> >
> > - RunJob # Works OK, both HandlerCallback (with data) and HandlerClose
> are called
>
> What data is received? The shell script doesn't write anything.
>
> > - RunJob | sleep 50m # Does not work, only HandlerClose and
> HandlerExit are being called (no buffered data)
> >
> >
> > The reason I need the sleep is that I want to check every 50m for the
> job_status in order to continue with some test assertions.
> >
> > Also, I've noticed that this does not happen with other commands... Is
> there something special about /bin/sh?
>
> This might be related to a problem that was reported but I could not
> reproduce: When the job exits quickly, Vim doesn't read the output,
> because the channel handle gets an error before reading.
>
> You should be able to get more information with ch_logfile().
>
> --
> hundred-and-one symptoms of being an internet addict:
> 269. You wonder how you can make your dustbin produce Sesame Street's
> Oscar's the Garbage Monster song when you empty it.
>
> /// 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
> ///
>
--
Santiago Alejandro Agüero
aguerosanti...@gmail.com
--
--
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
Re: Possible problem when running a job immediately followed by a sleep
Santiago Alejandro Agüero wrote:
> While I was trying to write some vim code for testing a (async)
> functionality for Neomake plugin, I've noticed the following scenario:
>
>
> - Having the following shell script (with errors):
>
> #!/bin/sh
>
> a='$var'
>
> foo(
>
>
> - And the next vim test code:
>
> function! StartJob()
> let g:job = job_start(['/bin/sh', 'errors.sh'], {
> \ 'callback': 'HandlerCallback',
> \ 'close_cb': 'HandlerClose',
> \ 'exit_cb': 'HandlerExit'
> \ })
> endfunction
>
> function! HandlerCallback(channel, line) abort
> call Debug('[Callback] channel: ' . a:channel . ', line: ' . a:line . ',
> channelStatus: ' . ch_status(a:channel))
> endfunction
>
> function! HandlerClose(channel) abort
> call Debug('[Close] channel: ' . a:channel . ', channelStatus: ' .
> ch_status(a:channel))
> endfunction
>
> function! HandlerExit(job, status) abort
> call Debug('[Exit] job: ' . a:job . ', status: ' . a:status . ',
> jobStatus: ' . job_status(a:job))
> endfunction
>
> function! Debug(msg) abort
> call writefile([a:msg], 'output.log', 'a')
> endfunction
>
> command! -bar RunJob call StartJob()
>
>
> - Then the following thing happens:
>
> - RunJob # Works OK, both HandlerCallback (with data) and HandlerClose are
> called
What data is received? The shell script doesn't write anything.
> - RunJob | sleep 50m # Does not work, only HandlerClose and HandlerExit are
> being called (no buffered data)
>
>
> The reason I need the sleep is that I want to check every 50m for the
> job_status in order to continue with some test assertions.
>
> Also, I've noticed that this does not happen with other commands... Is there
> something special about /bin/sh?
This might be related to a problem that was reported but I could not
reproduce: When the job exits quickly, Vim doesn't read the output,
because the channel handle gets an error before reading.
You should be able to get more information with ch_logfile().
--
hundred-and-one symptoms of being an internet addict:
269. You wonder how you can make your dustbin produce Sesame Street's
Oscar's the Garbage Monster song when you empty it.
/// 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] Trivial :help syn-iskeyword fix
Doug Kearns wrote: > Please see attached. Thanks. -- hundred-and-one symptoms of being an internet addict: 268. You get up in the morning and go online before getting your coffee. /// 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 8.0 released!
Tumbler Terrall wrote: > > Announcing: Vim (Vi IMproved) version 8.0 > > > > > > This the first major Vim release in ten years. There are interesting > > new features, many small improvements and lots of bug fixes. > > Awesome! Thanks for everything! > > Oh, just curious. Are you going to update the download link on vim.org > since 8.0.0 doesn't work with with netrw? ;) I already updated download links. I don't think any one points specifically to 8.0.0, I replaced the files with 8.0.2. That was within an hour or so. -- Two fish in a tank. One says to the other: "Do you know how to drive this thing?" /// 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.
Bug with function()
Bram,
I think this is a bug:
:echo function('tr')
-> returns tr
:echo function('tr()')
-> errors: E475: Invalid argument: [NULL]
0
Best,
Christian
--
Jeder glaubt gern, was er wünscht, die Dinge aber sind oft anders
beschaffen.
-- Demosthenes
--
--
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 8.0 released!
Hi Bram, On Mon, Sep 12, 2016 at 5:53 AM, Bram Moolenaar wrote: > > Hello Vim users! > > Announcing: Vim (Vi IMproved) version 8.0 > Congratulations on releasing the 25th anniversary edition of Vim. Thanks for spending 25 years of your life on improving developer productivity across the world. Regards, Yegappan -- -- 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 8.0 released!
> Announcing: Vim (Vi IMproved) version 8.0 > > > This the first major Vim release in ten years. There are interesting > new features, many small improvements and lots of bug fixes. Awesome! Thanks for everything! Oh, just curious. Are you going to update the download link on vim.org since 8.0.0 doesn't work with with netrw? ;) -- -- 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: [doc] Improve the document
Kenichi Ito wrote: > This patch fix: > - Fix typo > - Add the link to channel.txt Thanks. -- hundred-and-one symptoms of being an internet addict: 260. Co-workers have to E-mail you about the fire alarm to get you out of the building. /// 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.
[doc] Improve the document
Hi, This patch fix: - Fix typo - Add the link to channel.txt --- diff --git a/runtime/doc/help.txt b/runtime/doc/help.txt index 60b65b5..c7d3a56 100644 --- a/runtime/doc/help.txt +++ b/runtime/doc/help.txt @@ -152,6 +152,7 @@ Special issues ~ |ft_sql.txt| about the SQL filetype plugin |hangulin.txt| Hangul (Korean) input mode |rileft.txt| right-to-left editing mode +|channel.txt| Inter-process communication GUI ~ |gui.txt| Graphical User Interface (GUI) diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index 3ec648b..8d80056 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -2633,7 +2633,7 @@ A jump table for the options with a short description can be found at |Q_op|. uhexShow unprintable characters hexadecimal as instead of using ^C and ~C. - When neither "lastline" or "truncate" is included, a last line that + When neither "lastline" nor "truncate" is included, a last line that doesn't fit is replaced with "@" lines. *'eadirection'* *'ead'* --- Regards, Kenichi Ito -- -- 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 8.0 released!
Congrats and thanks for the work! Marcin On 14:53 Mon 12 Sep , Bram Moolenaar wrote: > > > Hello Vim users! > > > Announcing: Vim (Vi IMproved) version 8.0 > > > This the first major Vim release in ten years. There are interesting > new features, many small improvements and lots of bug fixes. > > Among the new features are: > - Asynchronous I/O support, channels, JSON > - Jobs > - Timers > - Partials, Lambdas and Closures > - Packages > - New style testing > - Viminfo merged by timestamp > - GTK+ 3 support > - MS-Windows DirectX support > > > Once you have installed Vim 8.0 you can find details about the changes > since Vim 7.4 with: > :help version8 > Or view it online: > https://raw.githubusercontent.com/vim/vim/master/runtime/doc/version8.txt > > > Gratitude > - > > If you like Vim, please consider helping poor children in the south of > Uganda: http://iccf-holland.org > > > Where to get it > --- > > The best way to obtain the latest Vim is using Git. Summary: > git clone https://github.com/vim/vim.git > More information here: http://www.vim.org/git.php > > For MS-Windows most of you will want the self-installing executable: > ftp://ftp.vim.org/pub/vim/pc/gvim80.exe > > Information about which files to download for what system: > http://www.vim.org/download.php > > A list of mirror sites can be found here: > http://www.vim.org/mirrors.php > > > The files available for download: > > UNIX: > sources + runtime files, bzip2 compressed: > ftp://ftp.vim.org/pub/vim/unix/vim-8.0.tar.bz2 > > VARIOUS: > help files converted to HTML: > ftp://ftp.vim.org/pub/vim/doc/vim80html.zip > > MS-WINDOWS one-size-fits-all: > Self-installing, includes all runtime files, loads libraries dynamically: > ftp://ftp.vim.org/pub/vim/pc/gvim80.exe > > MS-WINDOWS separate files: > Runtime files: > ftp://ftp.vim.org/pub/vim/pc/vim80rt.zip > GUI binary for Windows 95/98/NT/2000/XP/7: > ftp://ftp.vim.org/pub/vim/pc/gvim80.zip > GUI binary with OLE support: > ftp://ftp.vim.org/pub/vim/pc/gvim80ole.zip > Console version for Windows NT/2000/XP/7: > ftp://ftp.vim.org/pub/vim/pc/vim80w32.zip > Sources for PC (with CR-LF): > ftp://ftp.vim.org/pub/vim/pc/vim80src.zip > > For debugging: > ftp://ftp.vim.org/pub/vim/pc/gvim80.pdb > ftp://ftp.vim.org/pub/vim/pc/gvim80ole.pdb > ftp://ftp.vim.org/pub/vim/pc/vim80w32.pdb > > AMIGA: > Only runtime and sources are provided, no binary: > ftp://ftp.vim.org/pub/vim/amiga/vim80rt.tgz > ftp://ftp.vim.org/pub/vim/amiga/vim80src.tgz > > > Omitted in this version are: > - The 16-bit DOS, OS/2 and Amiga versions, these are obsolete. > - The 32-bit console version for MS-DOS/Windows 95/98 > - The 16 bit MS-Windows version > > > Mailing lists > - > > For user questions you can turn to the Vim mailing list. There are a > lot of tips, scripts and solutions. You can ask your Vim questions, but > only if you subscribe. See http://www.vim.org/maillist.php#vim > > If you want to help Vim development, discuss new features or get the > latest patches, subscribe to the vim-dev mailing list. See > http://www.vim.org/maillist.php#vim-dev > > Subject specific lists: > Macintosh issues: http://www.vim.org/maillist.php#vim-mac > > Before you ask a question you should search the archives, someone may > already have given the answer. > > > Reporting bugs > -- > > Send them to . Please describe the problem precisely. > All the time spent on answering mail is subtracted from the time that is > spent on improving Vim! Always give a reproducible example and try to > find out which settings or other things influence the appearance of the > bug. Try starting without your own vimrc file: "vim -u NONE". Try > different machines if possible. See ":help bugs" in Vim. > > Alternatively, create an issue at github and/or a pull request. > Please try to write a test that reproduces the problem and will pass > once it is fixed. See https://github.com/vim/vim > > > Happy Vimming! > > > -- > "Marriage is a wonderful institution... > but who wants to live in an institution?" > - Groucho Marx > > /// 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 opt
