Hi,
Since Vim.8.2.2082, it appears that this notation of dict' keys used for
example in FZF plugin is depreciated.
g:fzf_colors = { fg: ['fg', 'Normal'],
\ bg: ["bg", "Normal"],
\ hl: ["fg", "IncSearch"],
\ fg+: ["fg", "CursorLine", "CursorColum
This, as a bypass, seems to work:
g:fzf_colors = { fg: ['fg', 'Normal'],
\ bg: ["bg", "Normal"],
\ hl: ["fg", "IncSearch"],
\ info:["fg", "IncSearch"],
\ border: ["fg", "Ignore"],
\ prompt: ["fg", "Comment"],
I've never done anything stronger than aspirin, could you post a screen
shot of this experience?
On Monday, November 30, 2020 at 1:42:26 PM UTC-5 tu...@posteo.de wrote:
> Hi,
>
> I often come across markdown files - mostly wth github repos.
> When browsing those with vim I often feel like I had
> This, as a bypass, seems to work:
>
> g:fzf_colors = { fg: ['fg', 'Normal'],
>\ bg: ["bg", "Normal"],
>\ hl: ["fg", "IncSearch"],
>\ info:["fg", "IncSearch"],
>\ border: ["fg", "Ignore"],
>\ prompt: ["fg
On Thursday, December 3, 2020 at 5:34:04 AM UTC-6 Bram Moolenaar wrote:
> Looks like your problem is with the "fg+" key, the plus character is not
> allowed in a literal key. You can use the Javascript notation, using
> square brackets:
...
['fg+']: ["fg", "CursorLine", "CursorColumn", "No
It's okay with this new notation and thank you for less chars as backslash.
Do profiler show performance gain for vimscript migrated in vim9 ?
g:fzf_colors = { fg: ['fg', 'Normal'],
bg: ["bg", "Normal"],
hl: ["fg", "IncSearch"],
info: ["fg", "IncSearch"],
border: ["fg", "Ignore"],
prompt: ["fg",
On Do, 03 Dez 2020, Ni Va wrote:
> It's okay with this new notation and thank you for less chars as backslash.
>
> Do profiler show performance gain for vimscript migrated in vim9 ?
You can profile a vim9 script version and a legacy vimscript version.
That's what I did with the switch on vim-
Okay thank you for feedback.
if I were joking I would say that all it takes is an advanced substitute to
migrate the vimscript dictionaries to vim9. In my plugins, certainly not in
vim-airline :)
Le jeudi 3 décembre 2020 à 14:00:26 UTC+1, cbl...@256bit.org a écrit :
>
> On Do, 03 Dez 2020, Ni
Vocabulary pedant writing here.
Though the meaning is obvious in this context, "depreciate" means to lose
value, e.g. when a new car is driven off the lot, its value depreciates
25% or so.
To express disapproval of something, "deprecate" it.
There's just an iota of difference between "deprecat
Filipe Contreras wrote:
> On Thursday, December 3, 2020 at 5:34:04 AM UTC-6 Bram Moolenaar wrote:
>
> > Looks like your problem is with the "fg+" key, the plus character is not
> > allowed in a literal key. You can use the Javascript notation, using
> > square brackets:
>
> ['fg+']: ["fg", "
> It's okay with this new notation and thank you for less chars as backslash.
>
> Do profiler show performance gain for vimscript migrated in vim9 ?
>
> g:fzf_colors =3D { fg: ['fg', 'Normal'],
> bg: ["bg", "Normal"],
> hl: ["fg", "IncSearch"],
> info: ["fg", "IncSearch"],
> border: ["fg", "Ign
On Thu, Dec 3, 2020 at 1:55 PM Ni Va wrote:
> Do profiler show performance gain for vimscript migrated in vim9 ?
You can see vim9 benchmarks at:
https://github.com/vim/vim/blob/master/README_VIM9.md
That README_VIM9.md file contains the sources of the
benchmarks, so you can run them yourself if
On Thu, Dec 3, 2020 at 10:10 AM Bram Moolenaar wrote:
> Oh, you mean using single quotes without the brackets works. Double
> quotes too. That is simpler. Somehow I didn't find this in the
> specification. I see questions on stack overflow from more people who
> are confused about this. Only
On 12/02 04:33, Felipe Contreras wrote:
>
>
> On Wednesday, December 2, 2020 at 9:54:22 AM UTC-6 tu...@posteo.de wrote:
>
> >
> > 1) felipec
> >
>
> Hello :)
>
>
> > 2) set all used colors for syntax elements to red - same effect than
> > :setl syntax=
> >
>
> There must be something wron
Hi,
sorry...the subject is somehow weird...
When compiling things containing error the compiler spits out
someting like:
ERROR: Using Freedom() before declaration. File ../source/People.c:12:5
where 12 is the line number and 5 the olumn where the error is
detected by the compiler.
Vim would un
15 matches
Mail list logo