Syntax Regions, Javascript, and Lamdba Definitions

So this is a post that is in regards to what I think may be an overall limitation in the syntax region API, or perhaps there is some sort of workaround that I am not thinking of, but I figured I would post here to get thoughts. I have a theory that it's not possible, but I would love to hear you

Re: [patch] 'guicolors' option name does not intuitive.

Hi Bram and List! 2016-4-25(Mon) 5:03:24 UTC+9 Bram Moolenaar: > Hirohito Higashi wrote: > > > I think that 'guicolors' option name does not intuitive. > > This option for terminal, but prefix is 'gui' > > I think it's unnatural. > > > > I propose to rename option name to 'termtruecolor'. (Shor

Re: Patch 7.4.1783

2016-04-25 5:03 GMT+09:00 Bram Moolenaar : > I do not see a clue why this would be different on OS/X. As the failure message above indicates, it looks the functions isalpha(), isalnum() and ispunct() of OS X accept a wider range of 8-bit characters as class members. In other words, in contrast to

Re: Patch 7.4.1783

On Sun, Apr 24, 2016 at 4:03 PM, Bram Moolenaar wrote: > > I do not see a clue why this would be different on OS/X. > Patch 1785 didn't fix this? Something rings a bell about OS X being unusual in some way regarding precomposition of unicode chars. I'm not an expert or even really a beginner o

Re: Patch 7.4.1783

On Sun, Apr 24, 2016 at 4:03 PM, Bram Moolenaar wrote: > > Manuel Ortega wrote: > > > On Sun, Apr 24, 2016 at 8:40 AM, Bram Moolenaar > wrote: > > > > > > > > Patch 7.4.1783 > > > Problem:The old regexp engine doesn't handle character classes > > > correctly. > > > (Manuel Ortega

Re: [patch] 'guicolors' option name does not intuitive.

2016-04-24 23:17 GMT+03:00 Dominique Pellé : > Bram Moolenaar wrote: > >> Hirohito Higashi wrote: >> >>> I think that 'guicolors' option name does not intuitive. >>> This option for terminal, but prefix is 'gui' >>> I think it's unnatural. >>> >>> I propose to rename option name to 'termtruecolor'

Re: [patch] 'guicolors' option name does not intuitive.

Bram Moolenaar wrote: > Hirohito Higashi wrote: > >> I think that 'guicolors' option name does not intuitive. >> This option for terminal, but prefix is 'gui' >> I think it's unnatural. >> >> I propose to rename option name to 'termtruecolor'. (Short name is 'ttc') >> How about this? >> >> NOTE:

Re: Possible 'gq' bug, seemingly related to 'for' keyword

Hirohito Higashi wrote: > Hi Glenn and Bram, > > 2016-4-24(Sun) 9:53:30 UTC+9 Glenn Golden: > > Hirohito, Gary, > > > > Thanks for your responses. > > > > h_east [2016-04-23 17:23:00 -0700]: > > > > > > When the `smartindent` option to off, the result of your expectations will > > > be obtaine

Re: [patch] 'guicolors' option name does not intuitive.

Hirohito Higashi wrote: > I think that 'guicolors' option name does not intuitive. > This option for terminal, but prefix is 'gui' > I think it's unnatural. > > I propose to rename option name to 'termtruecolor'. (Short name is 'ttc') > How about this? > > NOTE: > This has been first propose

Re: Patch 7.4.1783

Manuel Ortega wrote: > On Sun, Apr 24, 2016 at 8:40 AM, Bram Moolenaar wrote: > > > > > Patch 7.4.1783 > > Problem:The old regexp engine doesn't handle character classes > > correctly. > > (Manuel Ortega) > > Solution: Use regmbc() instead of regc(). Add a test. > > Files:

Re: [vim/vim] Half rendered emojis on macvim (#732)

2016-04-24 18:31 GMT+03:00 Adelar da Silva Queiróz < vim-dev-git...@256bit.org>: > @crazymaster I did create there ( > macvim-dev/macvim#267 ). > But I think that is something about vim, since on GVim on Windows has

Re: [patch] 'guicolors' option name does not intuitive.

2016-04-24 21:54 GMT+03:00 Christian J. Robinson : > On Sun, 24 Apr 2016, h_east wrote: > >> I think that 'guicolors' option name does not intuitive. >> This option for terminal, but prefix is 'gui' >> I think it's unnatural. > > > I understand the logic behind the current naming, but I still agree

Re: [patch] 'guicolors' option name does not intuitive.

On Sun, 24 Apr 2016, h_east wrote: I think that 'guicolors' option name does not intuitive. This option for terminal, but prefix is 'gui' I think it's unnatural. I understand the logic behind the current naming, but I still agree that it's confusing. I propose to rename option name to 'ter

[patch] 'guicolors' option name does not intuitive.

Hi Bram and list. I think that 'guicolors' option name does not intuitive. This option for terminal, but prefix is 'gui' I think it's unnatural. I propose to rename option name to 'termtruecolor'. (Short name is 'ttc') How about this? NOTE: This has been first proposed by Ken Takada. Patch a

Re: Possible 'gq' bug, seemingly related to 'for' keyword

h_east [2016-04-23 19:00:47 -0700]: > Hi Glenn and Bram, > > 2016-4-24(Sun) 9:53:30 UTC+9 Glenn Golden: > > > > [ ... ] > > > > The behavior I'm seeking is exactly that seen on Paragraph A when > > smartindent is enabled, i.e. all lines are indented in accordance with the > > indent of the first

Re: Patch 7.4.1783

On Sun, Apr 24, 2016 at 8:40 AM, Bram Moolenaar wrote: > > Patch 7.4.1783 > Problem:The old regexp engine doesn't handle character classes > correctly. > (Manuel Ortega) > Solution: Use regmbc() instead of regc(). Add a test. > Files: src/regexp.c, src/testdir/test_regexp_

Patch 7.4.1786

Patch 7.4.1786 Problem:Compiled-in colors do not match rgb.txt. Solution: Use the rgb.txt colors. (Kazunobu Kuriyama) Files: src/term.c *** ../vim-7.4.1785/src/term.c 2016-04-22 21:11:03.836844513 +0200 --- src/term.c 2016-04-24 15:39:50.558186914 +0200 *** *** 1274,1291

Re: Lack of integer overflow handling in range() and for

Nikolay Pavlov wrote: > 2016-04-24 15:35 GMT+03:00 Bram Moolenaar : > > > > John Little wrote: > > > >> On Friday, April 22, 2016 at 8:13:21 PM UTC+12, Lekare wrote: > >> > >> > When entering something really big, like > >> > > >> > :put =range(300,3) > >> > > >> > Vim

Re: Patch 7.4.1770

Kazunobu Kuriyama wrote: > I'm going to report a bug on the feature termtruecolor and propose a minor > modification to its implementation. > > 1. Bug > > Probably, the bug is most easily reproduced with the command: > > $ vim -N -u guicolors-test.vim -c 'runtime syntax/colortest.vim' >

Patch 7.4.1785

Patch 7.4.1785 (after 7.4.1783) Problem:Regexp test fails on windows. Solution: set 'isprint' to the right value for testing. Files: src/testdir/test_regexp_utf8.vim *** ../vim-7.4.1784/src/testdir/test_regexp_utf8.vim2016-04-24 14:40:04.099244752 +0200 --- src/testdir/test_regex

Patch 7.4.1784

Patch 7.4.1784 Problem:The termtruecolor feature is enabled differently from many other features. Solution: Enable the termtruecolor feature for the big build, not through configure. Files: src/configure.in, src/config.h.in, src/auto/configure, src/fe

Re: Lack of integer overflow handling in range() and for

2016-04-24 15:35 GMT+03:00 Bram Moolenaar : > > John Little wrote: > >> On Friday, April 22, 2016 at 8:13:21 PM UTC+12, Lekare wrote: >> >> > When entering something really big, like >> > >> > :put =range(300,3) >> > >> > Vim quits with message >> > >> > Vim: Caught dead

Patch 7.4.1783

Patch 7.4.1783 Problem:The old regexp engine doesn't handle character classes correctly. (Manuel Ortega) Solution: Use regmbc() instead of regc(). Add a test. Files: src/regexp.c, src/testdir/test_regexp_utf8.vim *** ../vim-7.4.1782/src/regexp.c2016-04-08 17:07:09

Re: feature-list lacks "termtruecolor"

Manuel Ortega wrote: > I can't seem to use has("termtruecolor") accurately. It returns 0 even on > a vim that really does have +termtruecolor compiled in. I don't see this problem: echo has('termtruecolor') 1 > Also, +termtruecolor isn't listed under :h feature-list. I will s

Re: Old regex engine broke

Manuel Ortega wrote: > On Sun, Apr 24, 2016 at 2:37 AM, Manuel Ortega > wrote: > > > Well this is fairly recent, but I don't know which patch did it. The old > > regex engine's behavior broke. > > > > To reproduce: > > > > vim -u NONE -N -c "set re=1" > > > > Put this text in a buffer: Motörhe

Re: Lack of integer overflow handling in range() and for

John Little wrote: > On Friday, April 22, 2016 at 8:13:21 PM UTC+12, Lekare wrote: > > > When entering something really big, like > > > > :put =range(300,3) > > > > Vim quits with message > > > > Vim: Caught deadly signal SEGV > > Vim: Finished. > > [1]75479 se

Re: feature-list lacks "termtruecolor"

On Sat, Apr 23, 2016 at 10:06:57AM -0400, Manuel Ortega wrote: > I can't seem to use has("termtruecolor") accurately.  It returns 0 even on a > vim that really does have +termtruecolor compiled in. Do you need it? Check that the 'guicolors' option works, exists('+guicolors'). Cheers, -- James G

Re: Signed integer overflow 67108864 * 32 when running test49 on 32-bits Linux x86

Hi Dominique, 2016/4/24 Sun 16:57:39 UTC+9 Dominique Pelle wrote: > There is a pending patch from Ken Takata to use 64-bits > integers which should fix it when 64-bits integers are available: > > https://groups.google.com/forum/#!searchin/vim_dev/num64/vim_dev/p8Fl_vJDGy8/KSvvZK9zHgAJ > > The pa

Signed integer overflow 67108864 * 32 when running test49 on 32-bits Linux x86

Hi Running tests with vim-7.4.1782 (and older) on 32-bits Linux x86 and with ubsan (undefined behavior sanitizer), all tests pass but I noticed this error from ubsan: eval.c:5032:10: runtime error: signed integer overflow: 67108864 * 32 cannot be represented in type 'long int' It happens when ru

Re: Patch 7.4.1770

Hi, I'm going to report a bug on the feature termtruecolor and propose a minor modification to its implementation. 1. Bug Probably, the bug is most easily reproduced with the command: $ vim -N -u guicolors-test.vim -c 'runtime syntax/colortest.vim' on a true color capable terminal, where

Re: Lack of integer overflow handling in range() and for

On Friday, April 22, 2016 at 8:13:21 PM UTC+12, Lekare wrote: > When entering something really big, like > > :put =range(300,3) > > Vim quits with message > > Vim: Caught deadly signal SEGV > Vim: Finished. > [1]75479 segmentation fault \vim On my x86-64 with 1

Re: Patch 7.4.1779

Hirohito Higashi wrote: > Hi Bram and List, > > 2016-4-23(Sat) 20:56:05 UTC+9 Bram Moolenaar: > > Patch 7.4.1779 > > Problem:Using negative index in strcharpart(). (Yegappan Lakshmanan) > > Solution: Assume single byte when using a negative iindex. > > Files: src/eval.c > > > > > >

Re: Patch 7.4.1770

Christ van Willegen wrote: > another small nit-pick > > On Thu, Apr 21, 2016 at 9:11 PM, Bram Moolenaar wrote: > > *** ../vim-7.4.1769/runtime/doc/term.txt2015-03-31 > > 18:30:09.135370959 +0200 > > --- runtime/doc/term.txt2016-04-21 20:47:54.498251130 +0200 > > ***