On 2016-10-26, 22:23 GMT, Tony Mechelynck wrote:
> Don't make the too frequent error to believe that everyone
> else, or at least most of them, has the same preferences as
> you. The fact that we hardly ever see a post about whether or
> not vimballs are the way to go does not necessarily mean
On Wed, Oct 26, 2016 at 8:32 PM, Matěj Cepl wrote:
> On 2016-10-26, 17:26 GMT, Charles E Campbell wrote:
>> If you're using utf-8, its easy to get the glyph transform
>> with mathmenu.vim (comes with
>> http://www.drchip.org/astronaut/vim/index.html#MATH): type >=, select
>> with
Hi ChrisBra, Lifepillar and list,
2016-10-27(Thu) 5:19:43 UTC+9 Christian Brabandt:
> If that is really the case, I wonder if we can't just get rid of those lines
> https://github.com/vim/vim/blob/master/src/popupmnu.c#L585-L593
>
>
> I could prepare a patch.
How about an attached patch?
--
2016-10-26 23:05 GMT+03:00 Dominique Pellé :
> Christian Brabandt wrote:
>
>> On Mi, 26 Okt 2016, LCD 47 wrote:
>>
>>> * There is even a segfault:
>>>
>>> json_decode(repeat('[', 10))" segfault
>>>
>>
>> Oh, that one is nasty. I just
Lcd wrote:
> Today I stumbled upon this article about JSON:
>
> http://seriot.ch/parsing_json.php
>
> The article links to a set of tests:
>
> https://github.com/nst/JSONTestSuite
>
> A quick run of the "y" and "n" tests against Vim's json_decode()
> finds a few
Christian Brabandt wrote:
> On Mi, 26 Okt 2016, LCD 47 wrote:
>
>> * There is even a segfault:
>>
>> json_decode(repeat('[', 10))" segfault
>>
>
> Oh, that one is nasty. I just made a backtrace:
> #0 0x74d0bbab in _int_malloc
2016-10-26 19:27 GMT+03:00 LCD 47 :
> Today I stumbled upon this article about JSON:
>
> http://seriot.ch/parsing_json.php
>
> The article links to a set of tests:
>
> https://github.com/nst/JSONTestSuite
>
> A quick run of the "y" and "n" tests
Hi Dominique!
On Mi, 26 Okt 2016, Dominique Pellé wrote:
> http://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg208512.html
>
> 12 years after opening this ticket, I see that both clang and gcc still
> crash when trying to compile the c file attached in above bug.
Interesting read.
BTW: Your
On Mi, 26 Okt 2016, LCD 47 wrote:
> * There is even a segfault:
>
> json_decode(repeat('[', 10))" segfault
>
Oh, that one is nasty. I just made a backtrace:
#0 0x74d0bbab in _int_malloc (av=av@entry=0x7502bb00 ,
bytes=bytes@entry=88) at malloc.c:3384
#1
On 2016-10-26, 17:26 GMT, Charles E Campbell wrote:
> If you're using utf-8, its easy to get the glyph transform
> with mathmenu.vim (comes with
> http://www.drchip.org/astronaut/vim/index.html#MATH): type >=, select
> with visual-block (ctrl-v), then press the "&" key. Same sort of thing
>
Matěj Cepl wrote:
> So, for example how to make >= and <= be included so that they
> translate into (glyphs from :digraphs):
>
> =< ≤ 8804
> >= ≥ 8805
>
> Matěj
>
Hello:
If you're using utf-8, its easy to get the glyph transform with
mathmenu.vim (comes with
Additionally;
https://github.com/vim/vim/blob/46fceaa/runtime/doc/channel.txt#L601
> Vim checks about every 10 seconds for jobs that ended.
Maybe we can drop this line :)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
Today I stumbled upon this article about JSON:
http://seriot.ch/parsing_json.php
The article links to a set of tests:
https://github.com/nst/JSONTestSuite
A quick run of the "y" and "n" tests against Vim's json_decode()
finds a few problems. Not particularly
Am Mittwoch, den 26.10.2016, 02:13 -0700 schrieb Konfekt:
> The highlighting stops if an entry contains an escaped `$`, for
> example
> ```tex
> @Book{book
> title ={book},
> year = {2000},
> author = {author}
> howpublished = {editor DM 72.00; \$ 34.30 (1981)}
> }
>
14 matches
Mail list logo