Issue 219 in vim: Noticed 2 issues with netrw v151

2014-04-20 Thread vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 219 by henrycha...@gmail.com: Noticed 2 issues with netrw v151 http://code.google.com/p/vim/issues/detail?id=219 Noticed 2 netrw issues in the new update of vim with netrw V151. 1. Got an error E382 when trying to save a re

Re: [BUG] Inconsistent number in Invalid operation error messages

2014-04-20 Thread Bram Moolenaar
ZyX wrote: > Consider the following two operations: > > echo {} > {} > echo [] > [] > > . In first case Vim will report > > E736: Invalid operation for Dictionary > > (singular form). In the second case Vim will report > > E692: Invalid operation for Lists > > (*plural* form

gcc compilation warning

2014-04-20 Thread François Gannaz
Hi Compiling vim with gcc 4.8 and "-Wall -Wextra" gave one warning. In src/eval.c, the line 18322 "char_u *p;" hides a similar declaration and, after a quick glance at the code, I believe it should be removed, or the other declaration moved into a sub-block. Regards -- François -- -- You recei

gvim and ASCII glyphs

2014-04-20 Thread François Gannaz
Hello In a few words, here is a patch that makes gvim work better with ligatures in fonts, which can be useful even for programmers. Details follow. I tried to use a Hasklig[^1], a font with ligatures intended for the Haskell language. It serves the same objective as the Haskell Conceal script[^2

Re: gcc compilation warning

2014-04-20 Thread Bram Moolenaar
François Gannaz wrote: > Compiling vim with gcc 4.8 and "-Wall -Wextra" gave one warning. In > src/eval.c, the line 18322 "char_u *p;" hides a similar declaration and, > after a quick glance at the code, I believe it should be removed, or the > other declaration moved into a sub-block. Thanks, I

Re: gvim and ASCII glyphs

2014-04-20 Thread Bram Moolenaar
François Gannaz wrote: > In a few words, here is a patch that makes gvim work better with ligatures > in fonts, which can be useful even for programmers. Details follow. > > I tried to use a Hasklig[^1], a font with ligatures intended for the > Haskell language. It serves the same objective as t