Am 2016-09-13 23:15, schrieb Bram Moolenaar:
Christian Brabandt wrote:
Bram,
I think this is a bug:
:echo function('tr')
-> returns tr
:echo function('tr()')
-> errors: E475: Invalid argument: [NULL]
0
You mean that it says NULL? That can be fixed.
Yes, I meant the NULL. That error message
Hi,
I found some typos in version8.txt.
And I also found inconsistency (or mistakes) in some contributor names.
E.g.:
* Lcd, lcd47, etc.
* Nikolai Pavlov, Nikolay Pavlov (Does he prefer ZyX?)
* ZyX, Zyx
* Jürgen Krämer, Jurgen Kramer
* Jun Takimoto, Jun T.
* Shougo Matsu, Shougo
* Dominique Pelle
On Tuesday, 13 September 2016 23:21:01 UTC+1, mcepl wrote:
> On 2016-08-08, 12:50 GMT, Tony Mechelynck wrote:
> > You should see, in that order, the glyphs for ff fi fl ft st
> > ffi ffl.
> > I absolutely don't like them (in the monospaced fonts that
> > have them; in serif or sans-serif fonts i
2016-09-14 6:09 GMT+09:00 Matěj Cepl :
> On 2016-08-11, 15:40 GMT, Kazunobu Kuriyama wrote:
> >> Screenshot attached. (I haven't try PragmataPro.)
> >
> > I don't either for an obvious reason..Isn't there a free version? :)
>
> Would https://github.com/tonsky/FiraCode/ work?
>
> Matěj
>
Thank yo
Ken Takata wrote:
> Hi,
>
> I found some typos in version8.txt.
> And I also found inconsistency (or mistakes) in some contributor names.
> E.g.:
>
> * Lcd, lcd47, etc.
> * Nikolai Pavlov, Nikolay Pavlov (Does he prefer ZyX?)
> * ZyX, Zyx
> * Jürgen Krämer, Jurgen Kramer
> * Jun Takimoto, Jun T.
In Vim version 7.4.2066
When repeating the command :diffput using @: or a mapping containing :diffput
each change to the buffer that is being put to is lumped into one big undo
block. I would expect that either of the uses of indirect calls to :diffput
would produce a new undo block like repeat
On Mi, 14 Sep 2016, Ken Takata wrote:
> I found them when I tried to create patch contributor ranking ;-)
> https://gist.github.com/k-takata/628ff1103f92b9135041a15c43c85b32
Interesting read, thanks!
Best,
Christian
--
Frage an Radio Eriwan:
"Ist es wahr, daß der liebe Gott Parteigenosse werden
On Wednesday, September 14, 2016 at 2:41:42 PM UTC-4, nor...@googlegroups.com
wrote:
> I am not sure, what you are seeing, probably some kind of this:
> dcpurton/regfont#1
>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
Yep,was an issue
On 2016-09-14, 13:28 GMT, manuelschiller.pimail via vim_dev wrote:
> It allows users to hand-tune for which characters they want to
> bypass the glyph cache by putting a line in .vimrc, e.g.
>
> let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801]
>
> This contains a bitmap for each
Santiago Agüero wrote:
> The script's output is being used as a way to check for any syntax error,
> it should print (and it is, in bash):
>
> /bin/sh errors.sh
> errors.sh: line 5: syntax error near unexpected token `newline'
> errors.sh: line 5: `foo('
>
> And yes, the job exits quickly, in f
Ken Takata wrote:
> I found some typos in version8.txt.
> And I also found inconsistency (or mistakes) in some contributor names.
> E.g.:
>
> * Lcd, lcd47, etc.
> * Nikolai Pavlov, Nikolay Pavlov (Does he prefer ZyX?)
> * ZyX, Zyx
> * Jürgen Krämer, Jurgen Kramer
> * Jun Takimoto, Jun T.
> * Sho
On 2016-09-14, 13:28 GMT, manuelschiller.pimail via vim_dev wrote:
> It allows users to hand-tune for which characters they want to
> bypass the glyph cache by putting a line in .vimrc, e.g.
>
> let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801]
Tell me, please, you have never eve
Hi,
On Mi, 14 Sep 2016, manuelschiller.pimail via vim_dev wrote:
>
> let g:gtk_nocache=[0x, 0xfc00, 0xf801, 0x7801]
>
> This contains a bitmap for each character < 128, which has the
> corresponding bit set if the glyph cache is to be bypassed (which in
> turn enables ligatu
On So, 11 Sep 2016, Christian Brabandt wrote:
> On Fr, 09 Sep 2016, Yegappan Lakshmanan wrote:
>
> > Hi Christian,
> >
> > On Fri, Sep 9, 2016 at 12:08 AM, Christian Brabandt
> > wrote:
> > > How did you create that report?
> > >
> >
> > I use the following steps to run static analysis using t
Patch 8.0.0004
Problem:A string argument for function() that is not a function name
results in an error message with NULL. (Christian Brabandt)
Solution: Use the argument for the error message.
Files: src/evalfunc.c, src/testdir/test_expr.vim
*** ../vim-8.0.0003/src/evalfu
exists() result is sometimes misleading for a command.
Example (with GTK3 gvim linked with GTK 3.16.7):
:echo exists(':tearoff')
2
:tearoff &Help
E319: Sorry, the command is not available in this version
So for example the following code in my vimrc would produce the exact
I'm using vim 8.0.4 on Windows 7 compiled with MinGW.
When doing gx on an url I get:
E117: Unknown function: netrw#CheckIfRemote
E116: Invalid arguments for function netrw#BrowseX
Many thanks in advance,
--
Cesar
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Typ
17 matches
Mail list logo