Re: [vim/vim] Verbose messages aren't line buffered? (#919)

2016-07-13 3:44 GMT+03:00 Rafal : > I'm using ex/vi with vagrant and each time when I'm printing verbose > messages, they're scrambled across multiple lines, e.g. > > $ vagrant provision > ==> default: Running provisioner: shell... > default: Running: inline script > ==> default: stdin: is not

Re: [vim/vim] vim.org is down (#916)

On Tue, Jul 12, 2016 at 11:15 PM, Bram Moolenaar wrote: > > > > dig reveals no A record. Perhaps ns.42.org is misconfigured at the moment? > > The problem is with SourceForge, vim.sf.net has the same problem. > Shell service is also down. > > -- > Facepalm statement #5: "Petrol getting more expens

Patch 7.4.2031

Patch 7.4.2031 Problem:The list_lbr_utf8 test fails if ~/.vim/syntax/c.vim sets 'textwidth' to a non-zero value. (Oyvind A. Holm) Solution: Add a setup.vim file that sets 'runtimepath' and $HOME to a safe value. (partly by Christian Brabandt, closes #912) Files:

Make maximum integer size accessible in vimscript?

The recent updates to Vim to support 64-bit integers broke a plugin I was using that provides a vimscript implementation of a pseudorandom number generator, by sending it into a near-infinite loop. The problem was that the plugin assumes 32-bit integers, so I "fixed" it with a bitwise and() in

Re: Using file name with quickfix commands

Ramel Eshed wrote: [...] > > > 2) The following script: > > > > > > func! Setbv() > > > let rt = reltime() > > > for i in range (1, 4) > > > call setbufvar('mybuf', 'myvar', 2) > > > endfor > > > echo reltimestr(reltime(rt)) > > > endfunc > > > > > > Before setting any qu

Patch 7.4.2030

Patch 7.4.2030 Problem:ARCH must be set properly when using MinGW. Solution: Detect the default value of ARCH from the current compiler. (Ken Takata) Files: src/Make_cyg_ming.mak *** ../vim-7.4.2029/src/Make_cyg_ming.mak 2016-07-10 13:57:35.889542273 +0200 --- src/M

Re: [patch][win32] Detect ARCH on MinGW

Ken Takata wrote: > Currently ARCH must be set properly when using MinGW (especially when > compiling for x86_64). This patch detects the default value of ARCH > from the current compiler if ARCH is not set. Thanks! -- He was not in the least bit scared to be mashed into a pulp O

Patch 7.4.2029

Patch 7.4.2029 Problem:printf() does not work with 64 bit numbers. Solution: use the "L" length modifier. (Ken Takata) Files: src/message.c, src/testdir/test_expr.vim *** ../vim-7.4.2028/src/message.c 2016-07-09 17:05:49.207222368 +0200 --- src/message.c 2016-07-12 20:43:5

Re: [patch] printf() doesn't support 64-bit Numbers

Ken Takata wrote: > 2016/7/13 Wed 0:10:46 UTC+9 Ken Takata wrote: > > Hi, > > > > The printf() function on Vim script doesn't support 64-bit Numbers. > > E.g.: > > > > :echo 100 > > 100 > > :echo printf('%d', 100) > > 276447232 > > > > Attached patch

Re: lambda again

Ken Takata wrote: > 2016/7/12 Tue 4:59:40 UTC+9 Bram Moolenaar wrote: > > Ken Takata wrote: > > > > > > [...] > > > > > > > > > > I do think that the backslash (or any other special character that > > > > > > might > > > > > > be available) makes it ugly. > > > > > > > > > > > > Although we c

Re: [vim/vim] ib and ab motions are not able to detect parentheses (#915)

On Tuesday, July 12, 2016 at 12:34:43 PM UTC-5, Henrik Giesel wrote: > Given: I open vim -u NONE a.c > > When: I type ifoo('bar','(','(');F,vib > > Then I expect: have ('bar','(','(') selected > > What actually happens: Nothing is selected > > > I always thought this was weird. Why are those s

Re: Using file name with quickfix commands

> > > > Before setting any quickfix list it takes 0.22s. After setting a > > quickfix list with 8 entries it takes 6.5 seconds, which is > > actually worse than how it was before the last patches (it took then > > 3.56s). > > Strange. Oh, perhaps it's because this "mybuf" is near the start o

Re: Why isn't shelltemp=0 the default?

On Mon, Jul 11, 2016 at 12:40 AM, Manuel Ortega wrote: > On Sun, Jul 10, 2016 at 1:23 PM, Bram Moolenaar > wrote: > >> >> Manuel Ortega wrote: >> >> > On Saturday, June 14, 2014 at 11:51:59 AM UTC-4, Justin M. Keyes wrote: >> > > With shelltemp=0, Vim automatically falls back to using temp files

Re: [vim/vim] Make test_listlbr_utf8 succeed when textwidth != 0 (#912)

On 2016-07-11 23:36, Bram Moolenaar wrote: > Øyvind A. Holm wrote: > > Around one month ago, the test suite started to fail. It was around > > the same day as I installed a new kernel, so I thought that > > something was wrong locally. But when I noticed today that it also > > fails on a server wi

Re: [patch] printf() doesn't support 64-bit Numbers

Hi, 2016/7/13 Wed 0:10:46 UTC+9 Ken Takata wrote: > Hi, > > The printf() function on Vim script doesn't support 64-bit Numbers. > E.g.: > > :echo 100 > 100 > :echo printf('%d', 100) > 276447232 > > Attached patch fixes the problem. A test is added. P

[patch] printf() doesn't support 64-bit Numbers

Hi, The printf() function on Vim script doesn't support 64-bit Numbers. E.g.: :echo 100 100 :echo printf('%d', 100) 276447232 Attached patch fixes the problem. Regards, Ken Takata -- -- You received this message from the "vim_dev" maillist. Do not

Re: lambda again

Hi Bram, 2016/7/12 Tue 4:59:40 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > > [...] > > > > > > > > I do think that the backslash (or any other special character that > > > > > might > > > > > be available) makes it ugly. > > > > > > > > > > Although we can find the end of the express

Re: Patch 7.4.1890

On Monday, July 11, 2016 at 12:33:28 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > > > I'm not sure if this patch was supposed to fix the issue completely, > > > > but there are still issues with the gui cursor. > > > > > > > > 1) When job output is redirected to a buffer: > > > >

Re: Using file name with quickfix commands

On Monday, July 11, 2016 at 12:33:28 PM UTC+3, Bram Moolenaar wrote: > Ramel Eshed wrote: > > > On Sunday, July 10, 2016 at 8:23:15 PM UTC+3, Bram Moolenaar wrote: > > > Lcd wrote: > > > > > > > [...] > > > > > > Currently an error item from loclist looks like this: > > > > > > > > > > > >