On 2016-02-08, Bram Moolenaar wrote:
> One problem that I haven't figured out yet: When starting a job using a
> shell, we get the PID of the shell. So we can kill the shell, but not
> the process that it started.
> E.g. "/bin/sh python demoserver.py there". A shell is also
> useful for expandi
On 09-Feb-16, Bram Moolenaar wrote:
>
> Olaf Dabrunz wrote:
>
> > On 08-Feb-16, Bram Moolenaar wrote:
> > > Some parts that we still need that require some thougths:
> > >
> > > - Communicating over a socket requires knowing the port number. For a
> > > deamon this would be a known number. F
On Monday, February 8, 2016 at 11:27:31 PM UTC-2, Diego Viola wrote:
> I've just compiled vim from git and tried the new job functionality.
>
> I tried playing a song in the background first, as in:
>
> :call job_start('mpv /path/to/song.ogg')
>
> But it just slowed down the editor a lot, I got
I've just compiled vim from git and tried the new job functionality.
I tried playing a song in the background first, as in:
:call job_start('mpv /path/to/song.ogg')
But it just slowed down the editor a lot, I got some output back in the editor
though.
I also tried:
:call job_start('ls')
And
On Tue, Feb 09, 2016 at 01:57:32AM +0100, Bram Moolenaar wrote:
>
> Olaf Dabrunz wrote:
>
> > On 08-Feb-16, Bram Moolenaar wrote:
> > > Some parts that we still need that require some thougths:
> > >
> > > - Communicating over a socket requires knowing the port number. For a
> > > deamon this
Olaf Dabrunz wrote:
> On 08-Feb-16, Bram Moolenaar wrote:
> > Some parts that we still need that require some thougths:
> >
> > - Communicating over a socket requires knowing the port number. For a
> > deamon this would be a known number. For a server started by Vim it's
> > best to let th
On 08-Feb-16, Bram Moolenaar wrote:
> Some parts that we still need that require some thougths:
>
> - Communicating over a socket requires knowing the port number. For a
> deamon this would be a known number. For a server started by Vim it's
> best to let the server pick an available port.
On Mon, 8 Feb 2016, Bram Moolenaar wrote:
Christian J. Robinson wrote:
I discovered that Vim will crash if I have used ch_sendexpr() with a
handler callback and manage to call ch_close() while still waiting for
a message reply.
Can you give a sequence of commands, so that we can add a test c
On Tue, Feb 9, 2016 at 6:08 AM, Bram Moolenaar wrote:
>
> Takuya Fujiwara wrote:
>
>> On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
>> >
>> > [adjusted the subject, it was "Why is v:none needed"]
>> >
>> > Takuya Fujiwara wrote:
>> >
>> >> > [...]
>> >> >
>> >> > > >> let json = jsone
Hi Bram,
2016/2/9 Tue 7:24:10 UTC+9 Bram Moolenaar wrote:
> Patch 7.4.1293
> Problem:Sometimes a channel may hang waiting for a message that was
> already discarded. (Ken Takata)
> Solution: Store the ID of the message blocking on in the channel.
> Files: src/channel.c
Than
Patch 7.4.1293
Problem:Sometimes a channel may hang waiting for a message that was
already discarded. (Ken Takata)
Solution: Store the ID of the message blocking on in the channel.
Files: src/channel.c
*** ../vim-7.4.1292/src/channel.c 2016-02-07 22:21:15.718056931 +
Ken Takata wrote:
> I found another problem with channel on Win32 GUI.
> When executing the following line in test_channel.vim, Vim sometimes hangs up:
>
> call assert_equal('ok', ch_sendexpr(handle, 'make change'))
>
> When test_channnel.vim receives 'make change', it send two responses
> '[
On Monday, February 8, 2016 at 6:08:52 PM UTC-3, Bram Moolenaar wrote:
> Thanks for the feedback. I think it's time to sketch the upcoming work.
> It appears some thought that sockets was the end of it, that's not so.
Bram
I suggest to only focus on the job control feature, at least for now. The
Gary Johnson wrote:
> The current documentation of the stlnc item of the 'fillchars'
> option (i.e., ":help 'fillchars'") shows the fill character used
> when there is no highlighting to be '-' when it is actually '='.
> The attached patch fixes the documentation.
>
> The patch is based on Vim 7
Patch 7.4.1292
Problem:Some compilers complain about uninitialzed variable, even though
all possible cases are handled. (Dominique Pelle)
Solution: Add a default initialization.
Files: src/eval.c
*** ../vim-7.4.1291/src/eval.c 2016-02-07 22:30:42.296100155 +0100
--- src/e
Anton Lindqvist wrote:
> This is a result of a previous discussion[1] which concluded that a
> more general Error autocmd event would be a better addition than the
> proposed TagNotFound event.
>
> Questions and comments regarding the patch in no particular order:
>
> - Is the addition to the m
Christian Brabandt wrote:
> Hi Bram!
>
> On Sa, 06 Feb 2016, Bram Moolenaar wrote:
>
> > There are a few more places in the docs that need to point to this flag.
> >
> > Is there a better character than "_" to use for this?
>
> Updated patch uses 'z'
>
> Also added some more references to it
Ken Takata wrote:
> 2016/2/4 Thu 8:12:02 UTC+9 Bram Moolenaar wrote:
> > Patch 7.4.1256
> > Problem:On Mac sys.exit(0) doesn't kill the test server.
> > Solution: Use self.server.shutdown(). (Jun Takimoto)
> > Files: src/testdir/test_channel.py
>
> After this patch, test_channel.py do
Christian J. Robinson wrote:
> I discovered that Vim will crash if I have used ch_sendexpr() with a
> handler callback and manage to call ch_close() while still waiting for
> a message reply.
Can you give a sequence of commands, so that we can add a test case?
--
hundred-and-one symptoms of
Patch 7.4.1291
Problem:On MS-Windows the channel test server doesn't quit.
Solution: Use return instead of break. (Ken Takata)
Files: src/testdir/test_channel.py
*** ../vim-7.4.1290/src/testdir/test_channel.py 2016-02-07 16:53:08.783395062
+0100
--- src/testdir/test_channel.py 2016-0
I have read your thoughts about msgpack vs. JSON and I just want to
take this chance and propose to use S-expressions instead, JSON
without the syntactic bloat.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For m
2016-02-09 0:08 GMT+03:00 Bram Moolenaar :
>
> Takuya Fujiwara wrote:
>
>> On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
>> >
>> > [adjusted the subject, it was "Why is v:none needed"]
>> >
>> > Takuya Fujiwara wrote:
>> >
>> >> > [...]
>> >> >
>> >> > > >> let json = jsonencode({"key"
On 8 February 2016, Nikolay Aleksandrovich Pavlov wrote:
> 2016-02-08 21:06 GMT+03:00 LCD 47 :
> > On 8 February 2016, Bram Moolenaar wrote:
> >> There is a balance between being backwards compatible and doing what is
> >> expected. Spaces can be relevant, but that doesn't help for backwards
> >
Thanks for the feedback. I think it's time to sketch the upcoming work.
It appears some thought that sockets was the end of it, that's not so.
For jobs the most useful are probably:
- A deamon, serving several Vim instances, connect by socket.
- One server working with one Vim instance, asynchr
Takuya Fujiwara wrote:
> On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
> >
> > [adjusted the subject, it was "Why is v:none needed"]
> >
> > Takuya Fujiwara wrote:
> >
> >> > [...]
> >> >
> >> > > >> let json = jsonencode({"key": v:none})
> >> > > >> if json is v:none
> >> > > >>
Alejandro Exojo wrote:
> El Saturday 06 February 2016, Bram Moolenaar escribió:
> > I don't want to spend much time discussing this. v:null and v:none are
> > needed just like JavaScript has null and undefined.
>
> Having too many falsey types/values (null, undefined, NaN...) is considered
> o
Hi Bram!
On Sa, 06 Feb 2016, Bram Moolenaar wrote:
> There are a few more places in the docs that need to point to this flag.
>
> Is there a better character than "_" to use for this?
Updated patch uses 'z'
Also added some more references to it in the documentation.
> Also, plugin writers mus
2016-02-08 21:06 GMT+03:00 LCD 47 :
> On 8 February 2016, Bram Moolenaar wrote:
>> There is a balance between being backwards compatible and doing what is
>> expected. Spaces can be relevant, but that doesn't help for backwards
>> compatibility.
>>
>> One thing to keep in mind, why would you ever
Hi,
See the new patch[1].
[1] https://groups.google.com/d/msg/vim_dev/3_Mn38Jk3N0/W3TQ0g1WDQAJ
On Sat, Feb 06, 2016 at 03:28:37PM +0100, Bram Moolenaar wrote:
>
> Anton Lindqvist wrote:
>
> > On Thu, Feb 04, 2016 at 09:36:21PM +0100, Christian Brabandt wrote:
> > > While I agree that this is us
Hi,
This is a result of a previous discussion[1] which concluded that a more general
Error autocmd event would be a better addition than the proposed TagNotFound
event.
Questions and comments regarding the patch in no particular order:
- Is the addition to the main_loop function at a suitable loc
I discovered that Vim will crash if I have used ch_sendexpr() with a
handler callback and manage to call ch_close() while still waiting for
a message reply.
- Christian
--
If at first you fricassee, fry, fry again.
Christian J. Robinson http://christianrobinson.name/
Hi Bram!
On Mo, 08 Feb 2016, Bram Moolenaar wrote:
> Perhaps we should just change that and see who complains?
+1
Best,
Christian
--
Wie man sein Kind nicht nennen sollte:
Marga Quark
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
On 8 February 2016, Bram Moolenaar wrote:
> There is a balance between being backwards compatible and doing what is
> expected. Spaces can be relevant, but that doesn't help for backwards
> compatibility.
>
> One thing to keep in mind, why would you ever write:
> "a" . 1.1
> If you can wri
On 09-Feb-16, tyru wrote:
> On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
> >
> > [adjusted the subject, it was "Why is v:none needed"]
> >
> > Takuya Fujiwara wrote:
> >
> >> > [...]
> >> >
> >> > > >> let json = jsonencode({"key": v:none})
> >> > > >> if json is v:none
> >> > > >
El Saturday 06 February 2016, Bram Moolenaar escribió:
> I don't want to spend much time discussing this. v:null and v:none are
> needed just like JavaScript has null and undefined.
Having too many falsey types/values (null, undefined, NaN...) is considered
one of the flaws of JavaScript. Crockf
Lcd wrote:
> > > Summary: it would be nice if floating point numbers in a string
> > > context would be stringified to printf('%g', number).
> >
> > Yes and no. There have been cases where automatic conversion causes
> > unexpected behavior. I think the main one is converting a string to a
On Mon, Feb 8, 2016 at 3:22 AM, Bram Moolenaar wrote:
>
> Tyru wrote:
>
> On Sun, Feb 7, 2016 at 10:27 PM, Bram Moolenaar wrote:
>>
>> Patch 7.4.1274
>> Problem:Cannot run a job.
>
> Please don't quote the whole patch!
>
>> This is a really big news :)
>> Do you have a plan to add more channe
On Mon, Feb 8, 2016 at 6:48 PM, Bram Moolenaar wrote:
>
> [adjusted the subject, it was "Why is v:none needed"]
>
> Takuya Fujiwara wrote:
>
>> > [...]
>> >
>> > > >> let json = jsonencode({"key": v:none})
>> > > >> if json is v:none
>> > > >> echoerr 'error!'
>> > > >> ret
On 8 February 2016, Thiago Arruda wrote:
> > NeoVim is free to follow. It appears NeoVim's ideas about jobs and
> > channels are quite different. And it seems to be quite complicated.
[...]
> But in the context of an editor like Vim, the main use case for
> background jobs is to allow implementa
On 8 February 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > Summary: it would be nice if floating point numbers in a string
> > context would be stringified to printf('%g', number).
>
> Yes and no. There have been cases where automatic conversion causes
> unexpected behavior. I think th
Lcd wrote:
> On 7 February 2016, Bram Moolenaar wrote:
> >
> > Patch 7.4.1285
> > Problem:Cannot measure elapsed time.
> > Solution: Add reltimefloat().
> [...]
>
> This is useful, thank you.
>
> Going on a tangent: it would be nice if floating point numbers had
> automatic stri
Ken Takata wrote:
> 2016/2/7 Sun 22:28:08 UTC+9 Bram Moolenaar wrote:
> > Patch 7.4.1274
> > Problem:Cannot run a job.
> > Solution: Add job_start(), job_status() and job_stop(). Currently only
> > works
> > for Unix.
> > Files: eval.c, structs.h, runtime/doc/eval.txt, src
Hi,
I found another problem with channel on Win32 GUI.
When executing the following line in test_channel.vim, Vim sometimes hangs up:
call assert_equal('ok', ch_sendexpr(handle, 'make change'))
When test_channnel.vim receives 'make change', it send two responses
'["ex","call append(\\"$\\",\\"
Hi,
2016/2/4 Thu 8:12:02 UTC+9 Bram Moolenaar wrote:
> Patch 7.4.1256
> Problem:On Mac sys.exit(0) doesn't kill the test server.
> Solution: Use self.server.shutdown(). (Jun Takimoto)
> Files: src/testdir/test_channel.py
After this patch, test_channel.py doesn't exit when it receives '
Hi Bram,
2016/2/7 Sun 22:28:08 UTC+9 Bram Moolenaar wrote:
> Patch 7.4.1274
> Problem:Cannot run a job.
> Solution: Add job_start(), job_status() and job_stop(). Currently only works
> for Unix.
> Files: eval.c, structs.h, runtime/doc/eval.txt, src/os_unix.c,
> s
> NeoVim is free to follow. It appears NeoVim's ideas about jobs and
> channels are quite different. And it seems to be quite complicated.
Bram
I'd love to see Neovim and Vim have the same API for shared features, in fact I
have read the documentation about Vim's new channel feature and saw it
On 7 February 2016, Bram Moolenaar wrote:
>
> Patch 7.4.1285
> Problem:Cannot measure elapsed time.
> Solution: Add reltimefloat().
[...]
This is useful, thank you.
Going on a tangent: it would be nice if floating point numbers had
automatic stringification. Example:
:le
Tony Mechelynck wrote:
> The example given at line 4401 of eval.txt is incorrect: the statement
>
> :echo jsencode([1, v:none, {"one":1}], v:none)
>
> gives error E118: Too many arguments for function: jsencode
> followed by E15: Invalid expression
>
> The closing square bracket for the Li
The example given at line 4401 of eval.txt is incorrect: the statement
:echo jsencode([1, v:none, {"one":1}], v:none)
gives error E118: Too many arguments for function: jsencode
followed by E15: Invalid expression
The closing square bracket for the List should immediately precede the
closing
[adjusted the subject, it was "Why is v:none needed"]
Takuya Fujiwara wrote:
> > [...]
> >
> > > >> let json = jsonencode({"key": v:none})
> > > >> if json is v:none
> > > >> echoerr 'error!'
> > > >> return ...
> > > >> endif
> > > >
> > > > Well, let's just return a
The current documentation of the stlnc item of the 'fillchars'
option (i.e., ":help 'fillchars'") shows the fill character used
when there is no highlighting to be '-' when it is actually '='.
The attached patch fixes the documentation.
The patch is based on Vim 7.4.1290.
Regards,
Gary
--
--
Y
51 matches
Mail list logo
