On Wednesday, November 23, 2016 at 4:39:24 AM UTC-6, Efraim Yawitz wrote:
> I had the following problem and I think it is a bug in some fold-related code:
>
> I was trying to use the NarrowRegion plugin to do diffs between two functions
> in the same file by creating narrowed buffers for each fun
> Using the magic numbers is hard to understand. New options are probably
> better done with string values, such as "on", "off", and empty for not
> set. Perhaps in this case "number", "line" and "both"? But then naming
> it 'cursorlineopt' would be better.
I have tried making out 'cursorlineop
Hello,
I think there might be an issue with the backupext option after the
latest patches were applied. My Vim version is version 8.0 which
includes patches 1 through 104.
I use to be able to set backupext with "set backupext=;1". Now I get a
E474 error.
E474: Invalid argument: backupext=;1
A
Patch 8.0.0105
Problem:When using ch_read() with zero timeout, can't tell the difference
between reading an empty line and nothing available.
Solution: Add ch_canread().
Files: src/evalfunc.c, src/channel.c, src/proto/channel.pro,
src/testdir/test_channel.vim, sr
Patch 8.0.0106 (after 8.0.0100)
Problem:Cannot use a semicolon in 'backupext'. (Jeff)
Solution: Allow for a few more characters when "secure" isn't set.
Files: src/option.c
*** ../vim-8.0.0105/src/option.c2016-11-26 17:45:50.040909819 +0100
--- src/option.c2016-11-29 2
Jeff wrote:
> I think there might be an issue with the backupext option after the
> latest patches were applied. My Vim version is version 8.0 which
> includes patches 1 through 104.
>
> I use to be able to set backupext with "set backupext=;1". Now I get a
> E474 error.
>
> E474: Invalid arg
Hi
Attached patch fixes a typo in runtime/doc/channel.txt
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 mess
Thanks for the clarification. I guess what threw me was that the
backupext documentation says that only "/\*?[|<>" are illegal. So
according to that a semicolon should be good :)
On 11/29/2016 4:11 PM, Bram Moolenaar wrote:
>
> Jeff wrote:
>
>> I think there might be an issue with the backupex
Bram Moolenaar wrote：
> Patch 8.0.0105
> Problem:When using ch_read() with zero timeout, can't tell the difference
> between reading an empty line and nothing available.
> Solution: Add ch_canread().
> Files: src/evalfunc.c, src/channel.c, src/proto/channel.pro,
>
