Re: strange difference in UI for identical .vimrc

Colorschemes were changed, now all of them define Normal highlight. To make it transparent, you can follow :h :colorscheme (several paragraphs down): If a color scheme is almost right, you can add modifications on top of it by using the |ColorScheme| autocommand. For example, to remove the back

Re: Import vim9 script as that and map that.func fails

*> nnoremap n n*that.HLNext(80) remove to see messages, also `:` is not needed. Also in the gif you are importing with the full path, not sure if it matters. среда, 3 августа 2022 г. в 20:31:47 UTC+7, niva...@gmail.com: > Thank you Bram, > >- I added as described. >- Can you just

Re: strange difference in UI for identical .vimrc

On Wed, Aug 3, 2022 at 9:30 PM 'Grant Taylor' via vim_use wrote: > > On 8/3/22 5:37 PM, Aryeh Friedman wrote: > > I have two machines with 8.2.2263 and 8.2.5052 respectively with > > the following .vimrc (same NIS account/NFS home dir) and in the 2263 > > machine shows a transparent background (wh

Re: strange difference in UI for identical .vimrc

On 8/3/22 5:37 PM, Aryeh Friedman wrote: I have two machines with 8.2.2263 and 8.2.5052 respectively with the following .vimrc (same NIS account/NFS home dir) and in the 2263 machine shows a transparent background (which is what I want) and the 5052 shows and opaque one which is not what I want

strange difference in UI for identical .vimrc

I have two machines with 8.2.2263 and 8.2.5052 respectively with the following .vimrc (same NIS account/NFS home dir) and in the 2263 machine shows a transparent background (which is what I want) and the 5052 shows and opaque one which is not what I want (See screen shots). How do I make 5052 behav

Re: Import vim9 script as that and map that.func fails

Thank you Bram, - I added as described. - Can you just look at this gif that shows that I have to source $MYVIMRC to take account an import vim9script, then the function that blink the searched work is working. https://drive.google.com/file/d/1l4l_7M14eHjEG_cgwCpkm6NFX_QIWYCj/vie

Re: Import vim9 script as that and map that.func fails

Import is now successfull, what is now wrong is overloading mapping as intended by D.Conway https://www.youtube.com/watch?v=aHm36-na4-4#t6m36s as this : # Imported Functions {{{ import autoload 'nvhelper.vim' as that # nnoremap that.HLNext(80) # CALL SUCCESS *nnoremap n n:* that.HLNex

Re: Import vim9 script as that and map that.func fails

> Would import vim9 script as that. It seems to work when I directly call > that.foobar. > > But how to map the same call in a nnoremapping ? > Thank you > NV > > > # Imported Functions {{{ > import './vimfiles/autoload/nvhelper.vim' as that > nnoremap n n:call that.HLNext(80) > nnoremap N N:

Re: Import vim9 script as that and map that.func fails

import autoload 'nvhelper.vim' as that # nnoremap that.HLNext(80) # SUCCESS nnoremap n n: that.HLNext(80) # FAILS nnoremap N n: that.HLNext(80) Le mercredi 3 août 2022 à 10:57:25 UTC+2, N V a écrit : > # Imported Functions {{{ > import autoload 'nvhelper.vim' as that

Re: Import vim9 script as that and map that.func fails

# Imported Functions {{{ import autoload 'nvhelper.vim' as that SUCEED call that.HLNext(80) SUCEED map foo :call that.HLNext(80) FAILS var FooFunc = that.HLNext map foo :call FooFunc(80)

Import vim9 script as that and map that.func fails

Hi, Would import vim9 script as that. It seems to work when I directly call that.foobar. But how to map the same call in a nnoremapping ? Thank you NV # Imported Functions {{{ import './vimfiles/autoload/nvhelper.vim' as that nnoremap n n:call that.HLNext(80) nnoremap N N:call that.HLNext(80)

Re: Jump tag definition does not work with CTRL-] but works with CTRL-leftmouseclick

myiskeyword=!-~,^*,^|,^",192-255 it seems that affects mapping considering this https://stackoverflow.com/questions/34018825/jump-to-tag-ctrl-stopped-working. Any idea ? Thank you Le lundi 1 août 2022 à 21:52:36 UTC+2, N V a écrit : > Hi, > > As mentionned in this pull request, > http