Hi Marius and Carlos,
I just sent the pull request on GitHub that should fix this issue without
affecting other syntax highlighting.
https://github.com/vim/vim/pull/651
Please try it and see how it works for you.
Thanks!
Zvezdan
> On Aug 2, 2015, at 11:28 PM, Marius Gedminas wrote:
>
On Windows 7, without a server to connect to, this will echo a "9"
every time:
:let open_config = {'mode': 'json', 'timeout': 2000, 'waittime': 2000}
:let handle = ch_open('localhost:9876', open_config)
:echomsg type(handle)
- Christian
--
"Take sides! Always take sides! You will somet
2016-02-21 1:09 GMT+03:00 Matthew Winn :
> On 20/02/16 19:17, Olaf Dabrunz (Vim Github Repository) wrote:
>>
>>
>> This may work if there is a way to keep the external program running
>> (maybe attached via Vim's new channel facility). Haven't seen a server mode
>> for gpg though. (Batch mode is mo
On 20/02/16 19:17, Olaf Dabrunz (Vim Github Repository) wrote:
This may work if there is a way to keep the external program running
(maybe attached via Vim's new channel facility). Haven't seen a server
mode for gpg though. (Batch mode is more like an unattended mode that
does only one operat
Patch 7.4.1376
Problem:ch_setoptions() cannot set all options.
Solution: Support more options.
Files: src/channel.c, src/eval.c, src/structs.h, runtime/doc/channel.txt,
src/testdir/test_channel.vim
*** ../vim-7.4.1375/src/channel.c 2016-02-20 21:38:58.770661562 +0100
On Thu, Feb 18, 2016 at 10:48 AM, Christian Brabandt
wrote:
> ...
>
> I can't for the life of me find this now, but I think I have run into
> this same
> > problem before. It really annoys me and someone (thought it was
> Christian)
> > pointed out there is an option to control this behaviour.
>
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 mes
Christian J. Robinson wrote:
> After this patch, sending an eval channel command never gets a return
> message. I don't get an error either. Has the syntax changed? The
> documentation isn't updated.
Sorry, documentation update will follow later.
As the note mentions, "expr" and "eval" have
After this patch, sending an eval channel command never gets a return
message. I don't get an error either. Has the syntax changed? The
documentation isn't updated.
On Sat, Feb 20, 2016 at 1:39 PM, Bram Moolenaar wrote:
>
> Patch 7.4.1373
> Problem:Calling a Vim function over a channel re
Patch 7.4.1375
Problem:Still some Win16 code.
Solution: Remove FEAT_GUI_W16.(Hirohito Higashi)
Files: src/eval.c, src/ex_cmds.h, src/feature.h, src/gui.h, src/menu.c,
src/misc1.c, src/option.c, src/proto.h, src/structs.h, src/term.c,
src/vim.h, runtime/doc/gui_w1
Hirohito Higashi wrote:
> Hi Bram and list,
>
> 2016-2-20(Sat) 23:51:14 UTC+9 Bram Moolenaar:
> > Patch 7.4.1368
> > Problem:One more Win16 file remains.
> > Solution: Delete it.
> > Files: src/proto/os_win16.pro
[...]
> I have removed the part that refers FEAT_GUI_W16 macro.
> I at
Patch 7.4.1374
Problem:Channel test hangs on MS-Windows.
Solution: Disable the ch_read() that is supposed to time out.
Files: src/testdir/test_channel.vim
*** ../vim-7.4.1373/src/testdir/test_channel.vim2016-02-20
21:38:58.770661562 +0100
--- src/testdir/test_channel.vim
Patch 7.4.1373
Problem:Calling a Vim function over a channel requires turning the
arguments into a string.
Solution: Add the "call" command. (Damien) Also merge "expr" and "eval"
into one.
Files: src/channel.c, src/testdir/test_channel.py,
src/testdi
Hi Bram and list,
2016-2-20(Sat) 23:51:14 UTC+9 Bram Moolenaar:
> Patch 7.4.1368
> Problem:One more Win16 file remains.
> Solution: Delete it.
> Files: src/proto/os_win16.pro
>
>
> *** ../vim-7.4.1367/src/proto/os_win16.pro2016-01-19 13:21:55.845334290
> +0100
> --- src/proto/os_
Patch 7.4.1372
Problem:channel read implementation is incomplete.
Solution: Add ch_read() and options for ch_readraw().
Files: src/channel.c, src/eval.c, src/structs.h, src/proto/channel.pro,
src/testdir/test_channel.vim
*** ../vim-7.4.1371/src/channel.c 2016-02-20 1
Patch 7.4.1371
Problem:X11 GUI callbacks don't specify the part of the channel.
Solution: Pass the fd instead of the channel ID.
Files: src/channel.c
*** ../vim-7.4.1370/src/channel.c 2016-02-20 18:18:51.753033202 +0100
--- src/channel.c 2016-02-20 18:41:40.770605004 +0100
Patch 7.4.1370
Problem:The Python test script may keep on running.
Solution: Join the threads. (Yasuhiro Matsumoto)
Files: src/testdir/test_channel.py
*** ../vim-7.4.1369/src/testdir/test_channel.py 2016-02-18 22:23:21.173660406
+0100
--- src/testdir/test_channel.py 2016-02-20 18:22:
Yasuhiro Matsumoto wrote:
> When not using threading, job_stop kill python.exe correctly. But when
> using threading, it need to call job_stop(job, "kill"). I'm thinking
> this is an issue of test suite.
Thanks.
--
Nothing is impossible for the man who doesn't have to do it.
/// Bram Moolena
Patch 7.4.1369
Problem:Channels don't have a queue for stderr.
Solution: Have a queue for each part of the channel.
Files: src/channel.c, src/eval.c, src/structs.h, src/netbeans.c,
src/gui_w32.c, src/proto/channel.pro
*** ../vim-7.4.1368/src/channel.c 2016-02-19 23:2
Patch 7.4.1368
Problem:One more Win16 file remains.
Solution: Delete it.
Files: src/proto/os_win16.pro
*** ../vim-7.4.1367/src/proto/os_win16.pro 2016-01-19 13:21:55.845334290
+0100
--- src/proto/os_win16.pro 1970-01-01 01:00:00.0 +0100
***
*** 1,12
Danek Duvall wrote:
> 274 case VAR_UNKNOWN:
> 275 EMSG2(_(e_intern2), "json_encode_item()"); break;
> 276 return FAIL;
>
> Line 276 triggers the warning. Notice the "hidden" break at the end of the
> previous line. I suspect the break is the erroneous statement?
Patch 7.4.1367
Problem:Compiler warning for unreachable code.
Solution: Remove a "break". (Danek Duvall)
Files: src/json.c
*** ../vim-7.4.1366/src/json.c 2016-02-13 23:22:35.093363549 +0100
--- src/json.c 2016-02-20 15:25:18.076659627 +0100
***
*** 272,278
Patch 7.4.1366
Problem:Typo in test and resulting error in test result.
Solution: Fix the typo and correct the result. (James McCoy, close #650)
Files: src/testdir/test_charsearch.in, src/testdir/test_charsearch.ok
*** ../vim-7.4.1365/src/testdir/test_charsearch.in 2016-01-03
22
Patch 7.4.1365
Problem:Cannot execute a single test function.
Solution: Add an argument to filter the functions with. (Yasuhiro Matsumoto)
Files: src/testdir/runtest.vim
*** ../vim-7.4.1364/src/testdir/runtest.vim 2016-02-18 22:25:37.464230986
+0100
--- src/testdir/runtest.vim
Yasuhiro Matsumoto wrote:
> On Saturday, February 20, 2016 at 5:02:17 AM UTC+9, Bram Moolenaar wrote:
> > Thanks. However, when I include the part of this change around
> > channel_wait() then the tests fail. It appears this is because of the
> > comment:
> > * Always returns OK for FEAT_GU
Yasuhiro Matsumoto wrote:
> This patch change to run part of tests.
>
> ../vim -u NONE -U NONE -S runtest.vim test_channel.vim channel
>
> Last argument is the pattern to match the name of test function.
Nice idea. I'll include it.
--
** Hello and Welcome to the Psychiatric Hotline
Marcin Szamotulski wrote:
> > > > > > > That's a really great feature. I am trying to implemented a gulp
> > > > > > > plugin
> > > > > > > (gulp is a node package used to build web apps) based on channels
> > > > > > > and
> > > > > > > there are two things that I has a problem with:
> > > >
Kazunobu -
I wonder if it's about time we include the GTK 3 changes?
I read that several people say it's working for them.
Keeping your patch in sync with the code changes can be avoided if we
include them. We can always make further improvements.
I assume that the default would still be GTK 2
Patch 7.4.1363
Problem:Compiler warnings with tiny build.
Solution: Add #ifdefs.
Files: src/gui_w48.c, src/gui_w32.c
*** ../vim-7.4.1362/src/gui_w48.c 2016-02-19 21:04:57.904318201 +0100
--- src/gui_w48.c 2016-02-20 13:04:35.920364490 +0100
***
*** 138,144
Hi,
I ran into two different behaviors when completing a word using "" and
"". Assume the following content of a new buffer with "set
completeopt+=noinsert":
hello
h
The expected behavior is produced by pressing "" followed by "xxx"
which results in the message "Back at original" because no
Thank you for checking. I guess that was time consuming.
Then, wouldn't a-right-clicking-gives-the-black-border be an expected
behavior?
By that particular operation, you induced the selection mechanism of Vim.
But there was nothing to select at that time and hence Vim didn't know what
to do bu
On Fri, Feb 19, 2016 at 11:11:45PM +0900, Kazunobu Kuriyama wrote:
> 2016-02-19 22:37 GMT+09:00 Marius Gedminas :
>
> > I use Adwaita, which is the default GNOME 3 theme (and I think also the
> > default GTK+ 3 theme).
>
> Hmm. Then the theme has nothing to do with the border draw. And Vim
> co
32 matches
Mail list logo
