Re: job_info returns invalid JSON

2017-01-28 6:23 GMT+03:00 David Fishburn : > On Fri, Jan 27, 2017 at 8:42 PM, Nikolay Aleksandrovich Pavlov > wrote: >> >> 2017-01-28 4:33 GMT+03:00 David Fishburn : >> > Running on Windows using: >> > >> > :ver >> > VIM - Vi

Re: job_info returns invalid JSON

On Fri, Jan 27, 2017 at 8:42 PM, Nikolay Aleksandrovich Pavlov < zyx@gmail.com> wrote: > 2017-01-28 4:33 GMT+03:00 David Fishburn : > > Running on Windows using: > > > > :ver > > VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 24 2017 13:37:57) > > MS-Windows 32-bit

Re: job_info returns invalid JSON

2017-01-28 4:33 GMT+03:00 David Fishburn : > Running on Windows using: > > :ver > VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 24 2017 13:37:57) > MS-Windows 32-bit GUI version with OLE support > Included patches: 1-233 > > job_info(...) returned the following: > > { >

job_info returns invalid JSON

Running on Windows using: :ver VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 24 2017 13:37:57) MS-Windows 32-bit GUI version with OLE support Included patches: 1-233 job_info(...) returned the following: { 'status': 'run', 'stoponexit': 'term', 'exitval': 0, 'exit_cb': 0, 'channel': channel

Re: pythonx patch - :pyx command

Hi Bram, 2017/1/26 Thu 0:56:50 UTC+9 Ken Takata wrote: > Hi Bram, > > 2017/1/25 Wed 1:49:14 UTC+9 Bram Moolenaar wrote: > > Ken Takata wrote: > > > > > > Hmm, having a has() call have side effects is unexpected. I would think > > > > that has('pythonx') just returns 1 if python 2 or 3 is

Re: Feedback for virtcol(), issue 277

Bram Moolenaar wrote: >> [...] >> >> I did some tests with virtcol() and compared the results with my >> expectations (which may be plain wrong), see also Issue 277. >> [...] > > You are passing in an invalid position, halfway a character, thus the > returned value is undefined. Thank you for

Re: failing travis Mac OSX builds

On Fr, 27 Jan 2017, Bram Moolenaar wrote: > Aha, this has bothered me for a long time. I thought it was a problem > with Travis. Hopefully this avoids a lot of redness in the history. > Thanks! Yeah, Travis performance seems to have gotten worse in the past (perhaps more projects are using

Re: failing travis Mac OSX builds

Christian Brabandt wrote: > It looks like the Travis Mac OSX Builds take very long to start and when > they start, they usually fail with: > > The command "git checkout -qf d9c60648e50a82dcb85b8dffb47f6416c3d56972" > failed and exited with 128 during . > > I think this happens, because

Patch 8.0.0249

Patch 8.0.0249 Problem:When two submits happen quick after each other, the tests for the first one may error out. Solution: Use a git depth of 10 instead of 1. (Christian Brabandt) Files: .travis.yml *** ../vim-8.0.0248/.travis.yml 2017-01-26 21:23:44.583641679 +0100 ---

Re: [vim/vim] vim_strcat: Allow overlap in both branches. (#1415)

Justin M. Keyes wrote: > On Jan 27, 2017 21:53, "Bram Moolenaar" wrote: >> >> Thanks. Was this breaking anything? >> > > Not that I am aware of. I thought I would leave it up for debate :) Since we already know the length of the string, it's

Re: [vim/vim] vim_strcat: Allow overlap in both branches. (#1415)

On Jan 27, 2017 21:53, "Bram Moolenaar" wrote: > > Thanks. Was this breaking anything? > Not that I am aware of. I thought I would leave it up for debate :) --- Justin M. Keyes -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your

failing travis Mac OSX builds

Hi, It looks like the Travis Mac OSX Builds take very long to start and when they start, they usually fail with: The command "git checkout -qf d9c60648e50a82dcb85b8dffb47f6416c3d56972" failed and exited with 128 during . I think this happens, because Travis clones the vim repository with

Patch 8.0.0248

Patch 8.0.0248 Problem:vim_strcat() cannot handle overlapping arguments. Solution: Use mch_memmove() instead of strcpy(). (Justin M Keyes, closes #1415) Files: src/misc2.c *** ../vim-8.0.0247/src/misc2.c 2017-01-26 22:51:51.997875762 +0100 --- src/misc2.c 2017-01-27

Patch 8.0.0247

Patch 8.0.0247 Problem:Under some circumstances, one needs to type Ctrl-N or Ctrl-P twice to have a menu entry selected. (Lifepillar) Solution: call ins_compl_free(). (Christian Brabandt, closes #1411) Files: src/edit.c, src/testdir/test_popup.vim ***

Re: [vim/vim] Sometimes, I need to type / twice to select a menu entry (#1411)

Christian Brabandt wrote: > > This looks good to me. Thanks! > > Here is a proper patch including a test. Thanks! -- "Hegel was right when he said that we learn from history that man can never learn anything from history." (George Bernard Shaw) /// Bram Moolenaar --

Patch 8.0.0246

Patch 8.0.0246 Problem:Compiler warnings for int to pointer conversion. Solution: Fix macro for mch_memmove(). (John Marriott) Files: src/vim.h *** ../vim-8.0.0245/src/vim.h 2017-01-26 21:36:29.610733183 +0100 --- src/vim.h 2017-01-27 21:17:49.904677081 +0100 *** ***

Re: Patch 8.0.0241

Jonn Marriott wrote: > On 27-Jan-2017 07:36, Bram Moolenaar wrote: > > Patch 8.0.0241 > > Problem:Vim defines a mch_memmove() function but it doesn't work, thus > > is > > always unused. > > Solution: Remove the mch_memmove implementation. (suggested by Dominique > >

Re: Feedback for virtcol(), issue 277

Christian Ludwig wrote: > I apologize if this is the wrong list/place for the following concern: > > I did some tests with virtcol() and compared the results with my > expectations (which may be plain wrong), see also Issue 277. > > Here is one example of the test-set for the line: > a >

Re: [doc] :let _PS="\e[200~" fails

Ken Takata wrote: > I tried `:let _PS="\e[200~"` to set 't_PS' without using the raw > escape code, but it failed with E355. I didn't know that there are > two types of 't_*' > options: output code options and key code options. I found the following > comment in option.c: > /* terminal key

Patch 8.0.0245

Patch 8.0.0245 Problem:The generated zh_CN.cp936.po message file is not encoded properly. Solution: Instead of using zh_CN.po as input, use zh_CN.UTF-8.po. Files: src/po/Makefile *** ../vim-8.0.0244/src/po/Makefile 2014-06-12 17:45:19.0 +0200 --- src/po/Makefile

Patch 8.0.0244

Patch 8.0.0244 Problem:When the user sets t_BE empty after startup to disable bracketed paste, this has no direct effect. Solution: When t_BE is made empty write t_BD. When t_BE is made non-empty write the new value. Files: src/option.c ***

[doc] :let _PS="\e[200~" fails

Hi, I tried `:let _PS="\e[200~"` to set 't_PS' without using the raw escape code, but it failed with E355. I didn't know that there are two types of 't_*' options: output code options and key code options. I found the following comment in option.c: /* terminal key codes are not in here */

Re: YML formatting inconsistent bug

I do not see any problems with that file, it indents to ```YAML sudo: required language: generic services: - docker before_install: - sudo apt-get update - sudo apt-get install -o Dpkg::Options::="--force-confold" --force-yes -y docker-engine - docker build -t $REPO --build-arg

Re: [vim/vim] Sometimes, I need to type / twice to select a menu entry (#1411)

> This looks good to me. Thanks! Here is a proper patch including a test. Best, Christian -- Der Witz der Theologie besteht darin, daß sie ein höheres Wesen erfand, um sich selbst ins Leben zu rufen. -- Martin Kessel -- -- You received this message from the "vim_dev"

Re: YML formatting inconsistent bug

> On 14 January 2017 at 22:21, Bram Moolenaar > wrote: > > Is this about the indent file? It's maintained by Nikolai Pavlov, who > > is always very active. > > This autoindenting when editing YAML file is error prone for me. Could > be just me as no one has voted for the