Re: Patch 7.4.1285

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

Re: Do we want sticky type checking?

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!'

Re: Patch 7.4.1274

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 :)

Re: Documentation error about jsencode()

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

Documentation error about jsencode()

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

[patch] Fix documentation of stlnc in 'fillchars'

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 -- --

Re: Channel & job design

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.

Re: Channel & job design

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

Re: Patch 7.4.1274

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

Re: Patch 7.4.1274

> 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

Re: Patch 7.4.1285

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

Re: Patch 7.4.1256

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

Re: Some problems with channel

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

Re: Patch 7.4.1274

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, >

Re: Why is v:none needed?

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.

Re: Do we want sticky type checking?

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

Re: Patch 7.4.1285

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

Re: Patch 7.4.1285

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.

Re: Feature or bug? dw oddities

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

Re: Patch 7.4.1285

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

Re: Feature or bug? dw oddities

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

Re: Do we want sticky type checking?

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: >> > >> >> > [...] >> >> > >>

Re: Channel & job design

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

Re: Do we want sticky type checking?

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

Re: Why is v:none needed?

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 >

Channel & job design

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,

Re: ch_close while waiting for a message reply crashes vim

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

Re: Patch 7.4.1285

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

Re: Patch 7.4.1285

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" .

ch_close while waiting for a message reply crashes vim

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

Re: [patch] Add TagNotFound autocmd event

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

Re: Patch 7.4.1293

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

Re: [patch] Add Error autocmd event

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

Re: Channel & job design

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.

Patch 7.4.1293

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

Re: Channel & job design

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.

Re: Do we want sticky type checking?

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: >> > >> >> > [...]

Re: ch_close while waiting for a message reply crashes vim

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

Re: Channel & job design

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

Re: Channel & job design

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

Re: Patch 7.4.1274

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