Re: CSS syntax suddenly produces lots of errors

oh 2 was probably auto selected for me when 0 was set :) On Wednesday, April 10, 2024 at 5:36:32 PM UTC+10 Maxim Kim wrote: > >You only get the error with :set re=1? But :set re=2 works? > > I have just tried `:set re=2` -- works too > -- -- You received this message fr

Re: CSS syntax suddenly produces lots of errors

>You only get the error with :set re=1? But :set re=2 works? I have just tried `:set re=2` -- works too -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php

Re: CSS syntax suddenly produces lots of errors

Tried the same in v9.1.0295 -- works both with `:set re=1` and `:set re=0` On Wednesday, April 10, 2024 at 5:22:39 PM UTC+10 Maxim Kim wrote: > > > And can you also check if `:set re=1` helps? > > I did `:set re=1` and got same error > > [image: Screenshot from 20

Re: CSS syntax suddenly produces lots of errors

Have same version, no issues opening html file with embedded css. On Wednesday, April 10, 2024 at 9:02:17 AM UTC+10 Tony Mechelynck wrote: > Suddenly when opening a CSS file in Vim (or when opening an HTML file, > because HTML syntax invokes CSS syntax), I see a huge lot of errors. > This is at

Re: [vim/vim] Fix GetLatestVimScript and get it working again, including on Windows (Issue #13898)

I think it would be better to either contact Charles E. Campbell or do it with PR against vim repo. On Tuesday, January 23, 2024 at 6:18:47 PM UTC+11 Timothy Madden wrote: > Uploaded a 'patch' type script to vim.org/scripts > , that can

Re: Vim 9.1 has been released

Congrats! > Many bugs have been fixed since the release of Vim 9.0, including varous fixes for unsafe memory access, memory leaks, buffer overflows and potential crashes. should be `various`? On Wednesday, January 3, 2024 at 5:39:32 AM UTC+11 Yegappan Lakshmanan wrote: > > Happy to see the

Re: Where is Bram?

https://groups.google.com/g/vim_announce/c/tWahca9zkt4 RIP Bram. On Saturday, August 5, 2023 at 8:18:33 PM UTC+10 tooth pik wrote: > i've been wondering the same thing -- my guess was he's in africa again > > On Sat, Aug 5, 2023 at 12:34 AM Yegappan Lakshmanan > wrote: > >> Hi all, >> >> I

Re: vim9 autoloaded functions in expression register

Your "old way" example most likely works because "misc#" finds the misc.vim script file in an autoload directory. The "import" line doesn't matter (I haven't tried this though). Indeed, import doesn't matter, it was just a leftover from previous try and not needed here. I can't think of

vim9 autoloaded functions in expression register

Is there a way to use vim9 autoloaded function in expression register? The old way works: vim9script import autoload 'misc.vim' iab p! println!()=misc#Eatchar('\s') the dotted call doesn't: vim9script import autoload 'misc.vim' iab p! println!()=misc.Eatchar('\s') E121: Undefined variable:

Re: edit buffer using a builtin function

Is there a builtin function to edit a buffer in the current window? There is no function as far as I know for this. I use execute string(bnr) .. 'buffer' Anything more script oriented? Pretty much this, with variations using string interpolation: :exe $"{bnr}buffer" :exe $"b {bnr}" --

Re: Choices for Vim9 class implementation

понедельник, 19 декабря 2022 г. в 00:33:24 UTC+11, Bram Moolenaar: > > > > > For object members most languages use the "this." prefix. But not > everywhere, which makes it inconsistent. A good example is a > constructor where object members that are also an argument need to be > prefixed

Re: [vim/vim] Add first class support for json format (Issue #11426)

Ok, for visual mode I had to redefine `gq` vim9script import autoload 'dist/json.vim' setl formatexpr=json.FormatExpr() xnoremap gq json.Format(line('v'), line('.')) суббота, 5 ноября 2022 г. в 21:49:54 UTC+5, Maxim Kim: > > It would be good to review, have others make comments. &g

Re: [vim/vim] Add first class support for json format (Issue #11426)

> It would be good to review, have others make comments. > A PR should work for that. https://github.com/vim/vim/pull/11506 Hopefully other people will try it and improve if needed. * It doesn't handle escapes of \" and I don't know if json allows it actually * {Visual}gq doesn't work and I

Re: Health update

Hi Bram, we are all glad to hear you are more or less OK. Please, have a rest, PRs will wait. четверг, 27 октября 2022 г. в 23:55:04 UTC+5, Bram Moolenaar: > > I am very sorry to report that I have a medical problem. I fainted and > have been taken to hospital to find out what is wrong. Tests

Re: need to back out updates

On 16/09/2022 01:44, tooth pik wrote: please -- i need a working editor the last version of vim i had that worked was Patch 9.0.0469 -- updates to 9.0.0475 leave me with a vim that bombs so bad it breaks the X11/KDE/bash shell it's running in can someone tell me the git commands to back

Re: At patch level 9.0.471: Segmentation fault at startup

Got the same with # make distclean ./configure --with-features=huge --enable-gui=gtk3 --enable-python3interp sudo make install Starts fine with vim -Nu NONE On 15/09/2022 22:37, Tony Mechelynck wrote: The problem disappears after "make reconfig". Library discrepancy between "recently

Re: how to get old versions of vim

On 27/08/2022 07:56, Charles Campbell wrote: So, I thought what I'd like to do is to get vim 9.0 back (with no patches) and see if that worked. Then, if the plugin continues to misbehave, then I'd like to get vim 8.0. Once I have a version of vim where the plugin works I'd like to use git

Re: Finding an item using a lambda function in a List using the index() function

Not sure what to call it, indexfunc() ? - indexof() - indexby() -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message

Re: List of features to vote on

> Anything else? What about popup windows improvement -- it would be really nice to have editable(focused?) popup windows. It would make all that plugins (fuzzy file finders and the rest) way better/simpler. воскресенье, 3 июля 2022 г. в 19:46:47 UTC+3, Bram Moolenaar: > > Now that Vim

Re: [vim/vim] Align right current line number when `set nu rnu` (Issue #9847)

Experimental one(s): https://github.com/habamax/.vim/tree/master/pack/local/start/vim-monk/colors воскресенье, 27 февраля 2022 г. в 14:45:31 UTC+3, imran...@gmail.com: > Unrelated. But what is the colorscheme you are using? > > On Friday, February 25, 2022 at 8:24:10 PM UTC+6 Maxim

Re: [vim/vim] Add support for fuzzy completion to command-line completion (PR #9803)

Thank you, will look forward for this too! воскресенье, 20 февраля 2022 г. в 18:08:02 UTC+3, yegapp...@gmail.com: > Hi, > > On Sun, Feb 20, 2022 at 1:03 AM Maxim Kim wrote: > > > > > It is not supported for file/directory names, tag names and color > scheme names

Re: [vim/vim] Add support for fuzzy completion to command-line completion (PR #9803)

> It is not supported for file/directory names, tag names and color scheme names. Is there a reason not to support file/directory names? -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information,

def! in legacy vimscript

Shouldn't def functions be prohibited in legacy vimscript? https://vi.stackexchange.com/questions/36829/how-can-i-define-vim9-functions-and-vim9-lambdas-in-a-vim9-script Basically if you add def! Hello() echo "hello world" enddef to a regular legacy vim file (.vimrc, for example), function

Re: vim/colorschemes: Request For Comments

суббота, 12 февраля 2022 г. в 15:25:27 UTC+3, Romain Lafourcade: > SUMMARY: All the remakes of the built-in color schemes we have been > working on at vim/colorschemes are ready to be tested/included into the > Vim distribution. Feedback welcome. > @Bram, @chrisbra should we create a github

Re: vim9 vimCommentString

Forgot to include the text: vim9script # if has( "gui_running" ) highlighted # if has("gui_running") not highlighted среда, 2 февраля 2022 г. в 13:09:51 UTC+3, Maxim Kim: > What is the reason of highlighting a string in vim9 comments? > > [image: 2022-02-02_1

vim9 vimCommentString

What is the reason of highlighting a string in vim9 comments? [image: 2022-02-02_13-09-12.png] -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You

Re: [vim/vim] `set cursorline` makes code syntax colors gone (Issue #9617)

понедельник, 24 января 2022 г. в 13:04:16 UTC+3, cbl...@256bit.org: > > > Yes I remember something like that. What I don't know, is that something > that should be fixed by vim core or should the colorscheme generally > define/not define the Normal highlighting group? > > Don't know. > >

Re: [vim/vim] `set cursorline` makes code syntax colors gone (Issue #9617)

boils down to whether colorscheme did define `Normal` group or not. For example, if you remove `:hi Normal` from `industry` -- it will "fix" the cursorline issue. @chrisbra, I remember we were discussing it on vi.se in comments, but couldn't find it. понедельник, 24 января 2022 г. в 12:22

Re: [vim/vim] `set cursorline` makes code syntax colors gone (Issue #9617)

https://vi.stackexchange.com/questions/31881/how-do-i-make-sure-terminal-vim-has-syntax-highlighting-with-cursorline-and-t понедельник, 24 января 2022 г. в 12:13:10 UTC+3, Maxim Kim: > It is a "known" issue with windows cmd and 'termguicolors'. > > > понедельник, 24 янв

Re: [vim/vim] `set cursorline` makes code syntax colors gone (Issue #9617)

It is a "known" issue with windows cmd and 'termguicolors'. понедельник, 24 января 2022 г. в 11:55:56 UTC+3, Christian Brabandt: > that sounds more like a problem with your colorscheme > > — > Reply to this email directly, view it on GitHub >

Re: RFC: Support for v:vim.opt dictionary to access vim options

= 1 var old_sw = echo exists('') echo getcompletion('', 'option') # this might be capped though, at least for other completions it is for opt in getcompletion('', 'option') echo opt endfor for opt in getcompletion('', 'option') if !empty(opt) exe "set " .. opt .. "?" endif

Re: Colorscheme remake problem (was: Re: vim9 readiness + legacy colorscheme remakes)

Yes, we know about it, see https://github.com/vim/colorschemes/issues/54 This is something we would like to address in some future with the help of colortemplate author, @lifepillar воскресенье, 23 января 2022 г. в 14:17:26 UTC+3, jean...@picard.franken.de: > Hi all, > > On Tue, Jan 11, 2022

Re: [vim/vim] Dotted/dashed underline support (Issue #9553)

On wsltty (windows) everything is rendered: [image: 2022-01-19_15-14-58.png] среда, 19 января 2022 г. в 15:10:42 UTC+3, Dominique Pellé: > @brammool wrote: > > The double underline looks like a thin underline, is that a display error? > > Do all the terminals use

vim9script lambda syntax highlight

none of the statement keywords are highlighted: [image: 2022-01-14_10-48-14.png] -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this

Re: Patch 8.2.4059

Thanks, works for me. вторник, 11 января 2022 г. в 14:59:43 UTC+3, Bram Moolenaar: > > Patch 8.2.4059 > Problem: Vim9: an expression of a map cannot access script-local items. > (Maxim Kim) > Solution: Use the script ID of where the map was defined. > Files: src/getchar.c, sr

vim9 readiness + legacy colorscheme remakes

Hi Bram, Could you share your thoughts on when you think vim9 would be released (as you're closing vim9script it looks like this year for me). We would like to be ready with legacy colorschemes remake before vim9 release happen. As of now all of them are remade with a couple 'major' issues

Re: Patch 8.2.4050

Oops, I take it back -- it doesn't work :) вторник, 11 января 2022 г. в 09:31:54 UTC+3, Maxim Kim: > Following: > > import autoload 'comment.vim' > nnoremap gc comment.Toggle() > xnoremap gc comment.Toggle() > nnoremap gcc comment.Toggle() .. '_' > > N

Re: Patch 8.2.4050

Following: import autoload 'comment.vim' nnoremap gc comment.Toggle() xnoremap gc comment.Toggle() nnoremap gcc comment.Toggle() .. '_' Now works (as of 8.2.4058) понедельник, 10 января 2022 г. в 15:17:40 UTC+3, Bram Moolenaar: > > Maxim Kim wrote: > > > I have tried new

Re: Patch 8.2.4050

I have tried new way of autoload and for me it didn't work (windows 8.2.4050) I have autoload/comment.vim: vim9script autoload # Toggle comments # Usage: # 1. Save in ~/.vim/autoload/comment.vim # 2. Add following mappings to vimrc: # import autoload 'comment.vim' # nnoremap gc

Re: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead

Thx, using --enable-gui=gtk3 is ok вторник, 14 сентября 2021 г. в 09:40:41 UTC+3, cbl...@256bit.org: > > On Mo, 13 Sep 2021, Maxim Kim wrote: > > > On debian 11 I have started getting this warnings: > > > > /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTim

warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead

On debian 11 I have started getting this warnings: /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 73 | GTimeVal last_popdown; | ^~~~ Not sure if it is important and/or should be fixed. My

Re: Proper way to find when a function appeared in vim

It was the first thing I did. Unfortunately it knows nothing about `setcharpos`, `setcursorcharpos`, `charcol` etc. понедельник, 13 сентября 2021 г. в 18:10:21 UTC+3, yegapp...@gmail.com: > Hi, > > On Sun, Sep 12, 2021 at 5:39 AM Maxim Kim wrote: > > > > I want to se

Re: Proper way to find when a function appeared in vim

Thanks Michael! -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups

Proper way to find when a function appeared in vim

I want to set minimal vim version for a plugin depending of func existence. Is there a "simple" way to find out when `strchars(` was added to vim (there are more to check, this is an example)? For now I am searching github for the patches/PRs which is quite inefficient :) -- -- You received

Re: vi stackexchange "verification"

> > > Maybe I'm impersonating myself? :-) > It's linked to my gmail account, not github. > Your email is not visible there so we were guessing. Thanks for clarifying! -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

vi stackexchange "verification"

Hi Bram, Just wondering if it is you or somebody else is impersonating you: https://vi.stackexchange.com/a/34402/9333 -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Re: duplicate exists() tag

probably fixed in 3322 (built in debian)? вторник, 10 августа 2021 г. в 09:49:23 UTC+3, Maxim Kim: > :helptags ALL reports duplicate error: > > > [image: 2021-08-10_09-47-40.png] > > VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 8 2021 22:02:50) > MS-Windows 64-bit

duplicate exists() tag

:helptags ALL reports duplicate error: [image: 2021-08-10_09-47-40.png] VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 8 2021 22:02:50) MS-Windows 64-bit GUI version with OLE support Included patches: 1-3318 -- -- You received this message from the "vim_dev" maillist. Do not top-post!

Re: Patch 8.2.3255

nevermind, I have just read your explanation on another thread. суббота, 31 июля 2021 г. в 17:59:51 UTC+3, Maxim Kim: > > суббота, 31 июля 2021 г. в 14:32:23 UTC+3, Bram Moolenaar: > >> >> Patch 8.2.3255 >> Problem: ci" finds following string but ci< a

Re: Patch 8.2.3255

суббота, 31 июля 2021 г. в 14:32:23 UTC+3, Bram Moolenaar: > > Patch 8.2.3255 > Problem: ci" finds following string but ci< and others don't. > Solution: When not inside an object find the start. (Connor Lane Smit, > closes #8670) > Files: src/search.c, src/testdir/test_textobjects.vim,

Re: Patch 8.2.2912

THANK YOU! THANKS Ken Takata! воскресенье, 30 мая 2021 г. в 19:09:36 UTC+3, Bram Moolenaar: > > I wrote: > > > Patch 8.2.2912 > > Problem: MS-Windows: most users expect using Unicode. > > Solution: Default 'encoding' to utf-8 on MS-Windows. (Ken Takata, > > closes #3907) > > Files:

Re: [vim/vim] using tmux breaks vim's colors and termguicolors (#3608)

> > > OK, so which one of the two should we recommend? > > And tmux faq: * https://github.com/tmux/tmux/wiki/FAQ#how-do-i-use-a-256-colour-terminal * https://github.com/tmux/tmux/wiki/FAQ#how-do-i-use-rgb-colour -- -- You received this message from the "vim_dev" maillist. Do not

Re: [vim/vim] using tmux breaks vim's colors and termguicolors (#3608)

суббота, 29 мая 2021 г. в 18:57:42 UTC+3, Bram Moolenaar: > > Maxim Kim wrote: > > > > *tmux* > > > When using tmux you may want to use this in the tmux config: > > > > # tmux colors > > > set -g default-terminal "xterm-256color&q

Re: [vim/vim] using tmux breaks vim's colors and termguicolors (#3608)

пятница, 28 мая 2021 г. в 23:23:51 UTC+3, Bram Moolenaar: > > *tmux* > When using tmux you may want to use this in the tmux config: > > # tmux colors > set -g default-terminal "xterm-256color" > set -ag terminal-overrides ",xterm-256color:Tc" > > Let me know if something needs to be changed. >

Re: Insert non-rectangular selection

пятница, 28 мая 2021 г. в 10:42:17 UTC+3, Maxim Kim: > >> Here you can only yank a block including the spaces, and they would also >> be inserted with "zp". Perhaps we should also have a "zy" command to >> exclude the trailing spaces when yanking.

Re: Insert non-rectangular selection

> > Here you can only yank a block including the spaces, and they would also > be inserted with "zp". Perhaps we should also have a "zy" command to > exclude the trailing spaces when yanking. I think that's better than > having "zp" drop spaces that were yanked. > > What about "zd" then?

Re: Insert non-rectangular selection

> > > like a `zp` command, that does not add any trailing spaces. > > Btw if you paste at the end of the `;text` no trailing spaces would be added. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more

Re: Patch 8.2.2759

Have the same error with debian: evalvars.c: In function ‘set_var_const’: evalvars.c:3258:3: error: too few arguments to function ‘update_vim9_script_var’ update_vim9_script_var(FALSE, di, flags, tv, ); ^~ In file included from proto.h:236, from

Re: [vim/vim] Please document the hidden g:markdown_folding option. (#7945)

четверг, 11 марта 2021 г. в 19:29:59 UTC+3, Bram Moolenaar: > I think something like this would be sufficient: > > MARKDOWN *ft-markdown-plugin* > > To enable folding use this: > > let g:markdown_folding = 1 > < > > It implies that to disable it one has to do: let g:markdown_folding = 0 But

Re: [vim/vim] add support for focusing in popup (#7555)

понедельник, 28 декабря 2020 г. в 11:40:02 UTC+3, lacygoill: > > What they need is not the ability to focus *any* popup. They need to > focus *one* extra popup window below or above a popup menu displaying the > needle(s). It would be 1 line high, and as wide as the popup menu. It would >

Re: [vim/vim] indistinguishable colors in vimdiff mode (#4071)

We try to address that issue with reimplementation of built-in colorschemes (desert, for example https://github.com/vim/colorschemes/pull/50), but `default` one is out of the scope as there is no default colorscheme. I think it would be nice to add `guifg` and `ctermfg` to

Re: How to create a syntax keyword at runtime?

If I get you right I don't think this is possible (or really cumbersome to do) with existing :syntax commands. : foo bar ; <-- foo is defined and highlighted as statement then anywhere else in the text: bla bla bla foo bla bla <-- foo should be highlighted as statement Although, text

Re: [vim/vim] TOML (#7432)

> For a temporary solution you better set the right filetype (probably > "toml"), and add a syntax file that loads the yaml syntax for now. > Then it's easier for a user to drop in another toml.vim in their own > .vim/syntax directory to overrule it. I have my own toml syntax (ftdetect,

Re: Patch 8.2.2015

Hi! > Later it became clear that using a simple key name is very common, thus > **literally** dictionaries were introduced in a backwards compatible way: > > let dict = #{key: value} > > However, this #{} syntax is unlike any existing language. As it appears that > using a **literaly** key is

Re: [vim/vim] More improvement (#7317)

I am not sure if this is related to the prev patch of @mattn or not, but console vim on windows has some issue with pmenu redraw: https://i.imgur.com/rVvoti3.gif This is YCM plugin with console vim 8.2.2000 (with set nolazyredraw) -- -- You received this message from the "vim_dev" maillist.

Re: Patch 8.2.1978

Sorry, pic was lost: https://i.imgur.com/UhwfRfc.png -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are

Re: Patch 8.2.1978

is not highlighted in vimscript: четверг, 12 ноября 2020 г. в 16:22:44 UTC+3, Bram Moolenaar: > > Patch 8.2.1978 > Problem: Making a mapping work in all modes is complicated. > Solution: Add the special key. (Yegappan Lakshmanan, closes #7282, > closes 4784, based on patch by Bjorn Linse) >

Fuzzy scoring of beginning of line vs length

Hi, looks like text matched in the beginning has lower score than a shorter line with text not in the beginning: https://i.imgur.com/CuBkw0S.gif min repro: echo ['hello world with a longer line', 'onceHello']->matchfuzzy('hello') result: ['onceHello', 'hello world with a longer line'] I

Re: Fuzzy matching scoring of / against _

> > > I have created PR #7225 to add an additional bonus for matches after a > path separator. > > Thank you! -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Fuzzy matching scoring of / against _

Hi, I am not sure that words after _ should have higher scoring than words after / or \: https://i.imgur.com/bjb45g3.png What do you think? Min repro: echo ["plugin/setup.vim", "plugin/color_setup.vim", "after/plugin/setup.vim"]->matchfuzzy("setup") -- -- You received this message from

Re: Fuzzy matching for command-line completion

> > What do you think about extending this to support fuzzy matching? > We can add a value to the 'wildoptions' option (e.g. 'fuzzymatch') to > enable fuzzy matching instead of regular expression matching > for builtin commands. > > Would love to have it. -- -- You received this message from

Re: [vim/vim] Support for matching multiple words (#7163)

Thx! Looks really good! -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups

Re: matchfuzzy scoring

пятница, 16 октября 2020 г. в 09:36:23 UTC+3, Maxim Kim: > > On 16.10.2020 9:14, Christian Brabandt wrote: > > On a related note, I wonder whether SEPARATOR_BONUS should also be added > > for path delimiters (`/` on unix `\` on windows). > > > I think it makes

Re: matchfuzzy scoring

On 16.10.2020 9:14, Christian Brabandt wrote: On a related note, I wonder whether SEPARATOR_BONUS should also be added for path delimiters (`/` on unix `\` on windows). I think it makes sense: let g:tdata = ['hello/world','hellopworld', 'helloworld'] echo g:tdata->matchfuzzy('llwod')

Re: matchfuzzy scoring

Minimal repro: let g:testfuzzy = ['vimrc', 'vimrc_colors'] echom g:testfuzzy->matchfuzzy('vimrc') result: ['vimrc_colors', 'vimrc'] четверг, 15 октября 2020 г. в 09:21:32 UTC+3, Maxim Kim: > Hi, I wonder why "better" candidate has lower score than the others: > &g

Re: [vim/vim] Vim freezes after python import command (#7083)

I had the same issue with YCM which uses python too: https://github.com/ycm-core/YouCompleteMe/issues/3772 Tried with 8.2.1840 -- no issues so far. четверг, 15 октября 2020 г. в 02:30:19 UTC+3, IanSmith21: > Yes. Sorry. 184->1840 > > I have been using *8.2.1840* for a few days and I have not

matchfuzzy scoring

Hi, I wonder why "better" candidate has lower score than the others: https://i.imgur.com/NPhKNsZ.png tried to search `vimrc` and `.vim/vimrc` has lower score than `.vim/vimrc_colors`. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text

Re: matchfuzzypos sort is "unstable"

Note that for the same set of files and input on wsl vim I get "stable" sorted output. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You

matchfuzzypos sort is "unstable"

The plugin I do https://github.com/habamax/vim-select uses ripgrep to feed files into fuzzymatchpos function. It looks good for me with one minor issue with sorting, have a look into the video I have recorded: https://youtu.be/RPM3GccvDGA What is happening there: 1. I ran `rg --files

Re: [vim/vim] Add the matchfuzzy() function (#6932)

And another similar to quickpick plugin using matchfuzzypos() https://github.com/habamax/vim-select Thank you for implementing fuzzy functions! понедельник, 12 октября 2020 г. в 01:41:52 UTC+3, Prabir Shrestha: > Here is another vim plugin which I rewrote using the new matchfuzzy and >

Unnecessary "syntax reset"

Hi, could someone with knowledge clarify if syntax reset is actually needed when authoring colorschemes? From the issue description: https://github.com/vim/colorschemes/issues/34 |" Load the syntax highlighting defaults, if it's enabled. if exists("syntax_on") syntax reset endif | Is this

Re: [vim/vim] feat: make it possible to restore default highlighting (#6956)

With the new patch user would not need to 'syntax on' to really apply a new colorscheme as the information about default links is kept and applied on highlight_clear(). PS, I believe previous patch (wrt treating cleared group as has no settings) is still good to have though. -- -- You

Re: [vim/vim] feat: make it possible to restore default highlighting (#6956)

среда, 16 сентября 2020 г. в 22:55:00 UTC+3, Maxim Kim: > It is in an old PR as a new commit, I can make it as a separate PR. > > > > ср, 16 сент. 2020 г., 22:50 Bram Moolenaar : > > > > E.g. syntax/html.vim links htmlTagName to Statement, but a fancy > >

Re: [vim/vim] feat: make it possible to restore default highlighting (#6956)

среда, 16 сентября 2020 г. в 15:05:55 UTC+3, Maxim Kim: > > > среда, 16 сентября 2020 г. в 14:29:04 UTC+3, Antony Scriven: > >> >> > I think that proper check for cleared in 'hl_has_settings' is simpler >> > though. >> >> Yeah I know. I'm onl

Re: [vim/vim] feat: make it possible to restore default highlighting (#6956)

среда, 16 сентября 2020 г. в 14:29:04 UTC+3, Antony Scriven: > > > I think that proper check for cleared in 'hl_has_settings' is simpler > > though. > > Yeah I know. I'm only mentioning this alternative because it doesn't > require that syntax is reloaded. This seems to be welcome behaviour

Re: [vim/vim] Add the matchfuzzy() function (#6932)

вторник, 15 сентября 2020 г. в 22:34:33 UTC+3, bfrg: > But matchfuzzy() returns only a list of byte indexes (column numbers). > > Does that mean we wouldn't be able to match unicode (cyrillic for example)? > — > You are receiving this because you commented. > Reply to this email directly,

Re: [vim/vim] feat: make it possible to restore default highlighting (#6956)

среда, 16 сентября 2020 г. в 03:38:37 UTC+3, Antony Scriven: > In case I wasn't clear before, I'm wondering if could you save sg_link >> in do_highlight() when doing ":hi def link", and then restore it in >> highlight_clear(). Or would there be unintended consequences? >> >> I've not had any

Re: [vim/vim] Add the matchfuzzy() function (#6932)

On 14.09.2020 17:38, Bram Moolenaar wrote: Sergey Vlasov wrote: ... ``` [ ["clay", ["c", 0, 0], ["ay", 2, 3] ] ] ``` That makes it a lot more complex. What is the practical use for the match positions? Something like this is needed if one wants to highlight

menu.vim bug

Hi, There is floating bug that I can see when I start gvim (7.3, winxp, binaries from vim.org): http://picasaweb.google.com/lh/photo/pEQo_1GDSrWgLMn9BWk_MA?feat=directlink It just happens once in a while so I can not find steps to reproduce it. Maxim. -- You received this message from the

Fwd: VisualBasic 'elseif' indent error

Hi, Could we have this fix in vim73? I did email original author of indent/vb.vim -- Johannes Zellner johannes at zellner.org but had no reply. Maxim. -- Forwarded message -- From: Maxim Kim haba...@gmail.com Date: 20 авг 2009, 10:58 Subject: VisualBasic 'elseif' indent error

Re: Fwd: VisualBasic 'elseif' indent error

On 28 июл, 10:36, Maxim Kim haba...@gmail.com wrote: Hi, Could we have this fix in vim73? I did email original author of indent/vb.vim -- Johannes Zellner johannes at zellner.org but had no reply. Maxim. -- Forwarded message -- From: Maxim Kim haba...@gmail.com Date

Re: vim73a help -- bug of feature?

On 21 июл, 09:58, James Vega james...@jamessan.com wrote: This is due to the new conceal feature.  The tags in Vim's help files are surrounded by ||.  When your cursor is on a line with tags, the || are displayed but highlighted using the Ignore group so they blend in with the background.  

Re: vim73a help -- bug of feature?

On 21 июл, 10:32, Christian J. Robinson hept...@gmail.com wrote: On Tue, 20 Jul 2010, Maxim Kim wrote: On 21 июл, 09:58, James Vega james...@jamessan.com wrote: Because you don't have syntax highlight enabled in your example, which turns off the conceal feature as well, since it uses

Re: vim73a help -- bug of feature?

On 21 июл, 09:41, Maxim Kim haba...@gmail.com wrote: With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h strdisplaywidth

Re: vim73a help -- bug of feature?

On 21 июл, 13:59, Maxim Kim haba...@gmail.com wrote: On 21 июл, 09:41, Maxim Kim haba...@gmail.com wrote: With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim

Re: vim73a help -- bug of feature?

2010/7/21 Bram Moolenaar b...@moolenaar.net: Maxim Kim wrote: With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h

vim73a help -- bug of feature?

With the following minimal .vimrc and only builtin plugins I have quite a strange behaviour with help on strdisplaywidth() topic. .vimrc: set nocompatible finish 1. run gvim 2. :filetype plugin on 3. :syntax on 4. :h strdisplaywidth() 5. navigate to strchars() function 6. press h several times

Re: flexwiki ftplugin causing problems ('bomb')

On 29 апр, 10:48, ron r...@ronware.org wrote: I have recently started editing files with a '.wiki' extension, and rather than getting the 'wikipedia' filetype, they pick up  the 'flexwiki' type.  That's not the problem. The problem is that the 'flexwiki' filetype handler sets bomb, resulting

Re: flexwiki ftplugin causing problems ('bomb')

On 30 апр, 06:35, Tony Mechelynck antoine.mechely...@gmail.com wrote: On 29/04/10 16:55, Maxim Kim wrote: I had the very same problem with it. In my plugin I just do augroup filetypedetect     clear FlexWiki's stuff    au! * *.wiki augroup end A simpler solution would be to create

www.vim.org: Change my plugin type

Hi, How can I change script type of my vim plugin? It is 'ftplugin' at the moment but I'd like it to be 'utility' http://www.vim.org/scripts/script.php?script_id=2226 Best wishes, Maxim. -- You received this message from the vim_dev maillist. For more information, visit

  1   2   >