Re: CSS syntax suddenly produces lots of errors

[Maxim Kim]

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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/79a69ae1-5f7f-45ec-bdda-468145b2857dn%40googlegroups.com.

Re: CSS syntax suddenly produces lots of errors

[Maxim Kim]

>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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ae9119e1-7315-4b99-8c34-75d086e3834fn%40googlegroups.com.

Re: CSS syntax suddenly produces lots of errors

[Maxim Kim]

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 2024-04-10 17-22-04.png]
> On Wednesday, April 10, 2024 at 4:44:42 PM UTC+10 Christian Brabandt wrote:
>
>>
>> On Mi, 10 Apr 2024, 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 patchlevel 9.1.296 or earlier. I didn't see it a few days 
>> > ago but I'm not sure at which changeset it appeared. 
>> > 
>> > I'm copying below what I saw while opening one HTLM file : 
>> > 
>> > "pub/public/nb_au/nbau.contents.html" 
>> > 
>> > "pub/public/nb_au/nbau.contents.html" 26L, 799B 
>> > Error detected while processing BufRead Autocommands for 
>> > "*.html"..function dist#ft#FThtml[13]..FileType Autocommands for 
>> > "*"..Syntax Autocommands for "*"..function 11_SynSet[25]..script 
>> > 
>> /usr/local/share/vim/vim91/syntax/html.vim[308]../usr/local/share/vim/vim91/syntax/css.vim:
>>  
>>
>> > line 129: 
>> > E409: Unknown group name: 
>> > cssValue.*,cssFunction,cssColor,cssStringQ,cssStringQQ oneline 
>> > E475: Invalid argument: cssMathGroup contained 
>> > matchgroup=cssMathParens start="(" end=")" 
>> > containedin=cssFunction,cssMathGroup 
>> > 
>> contains=cssCustomProp,cssValue.*,cssFunction,cssColor,cssStringQ,cssStringQQ
>>  
>>
>> > oneline 
>> > line 130: 
>> > E409: Unknown group name: 
>> > cssValue.*,cssFunction,cssURL,cssColor,cssStringQ,cssStringQQ oneline 
>> > E475: Invalid argument: cssFunction contained 
>> > matchgroup=cssFunctionName start="\<\(var\|calc\)\s*(" end=")" 
>> > 
>> contains=cssCustomProp,cssValue.*,cssFunction,cssURL,cssColor,cssStringQ,cssStringQQ
>>  
>>
>> > oneline 
>> > line 453: 
>> > E409: Unknown group name: 
>> > 
>> css.*Prop,cssComment,cssValue.*,cssColor,cssURL,cssImportant,cssCustomProp,cssError,cssStringQ,cssStringQQ,cssFunction,cssUnicodeEscape,cssVendor,cssDefinition,cssHacks,cssNoise
>>  
>>
>> > fold 
>> > E475: Invalid argument: cssDefinition transparent matchgroup=cssBraces 
>> > start='{' end='}' 
>> > 
>> contains=cssTagName,cssAttributeSelector,cssClassName,cssIdentifier,cssAtRule,cssAttrRegion,css.*Prop,cssComment,cssValue.*,cssColor,cssURL,cssImportant,cssCustomProp,cssError,cssStringQ,cssStringQQ,cssFunction,cssUnicodeEscape,cssVendor,cssDefinition,cssHacks,cssNoise
>>  
>>
>> > fold 
>> > line 498: 
>> > E409: Unknown group name: 
>> > 
>> css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
>>  
>>
>> > E475: Invalid argument: cssAttrRegion start=/:/ 
>> > end=/\ze\(;\|)\|}\|{\)/ contained 
>> > 
>> contains=cssPseudoClassId,css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
>>  
>>
>> > line 502: 
>> > E409: Unknown group name: 
>> > 
>> css.*Prop,css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
>>  
>>
>> > E475: Invalid argument: cssAttrRegion start=/transition\s*:/ 
>> > end=/\ze\(;\|)\|}\)/ contained 
>> > 
>> contains=css.*Prop,css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
>>  
>>
>> > line 527: 
>> > E409: Unknown group name: 
>> > css.*Prop,cssValue.*,cssVendor,cssAtKeyword,cssComment 
>> > nextgroup=cssDefinition 
>> > E475: Invalid argument: cssAtRule start=/@supports\>/ end=/\ze{/ 
>> > skipwhite skipnl 
>> > 
>> contains=cssAtRuleLogical,cssAttrRegion,css.*Prop,cssValue.*,cssVendor,cssAtKeyword,cssComment
>>  
>>
>> > nextgroup=cssDefinition 
>> > Error detected while processing BufRead Autocommands for 
>> > "*.html"..function dist#ft#FThtml[13]..FileType Autocommands for 
>> > "*"..Syntax Autocomm

Re: CSS syntax suddenly produces lots of errors

[Maxim Kim]

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 patchlevel 9.1.296 or earlier. I didn't see it a few days
> ago but I'm not sure at which changeset it appeared.
>
> I'm copying below what I saw while opening one HTLM file :
>
> "pub/public/nb_au/nbau.contents.html"
>
> "pub/public/nb_au/nbau.contents.html" 26L, 799B
> Error detected while processing BufRead Autocommands for
> "*.html"..function dist#ft#FThtml[13]..FileType Autocommands for
> "*"..Syntax Autocommands for "*"..function 11_SynSet[25]..script
>
> /usr/local/share/vim/vim91/syntax/html.vim[308]../usr/local/share/vim/vim91/syntax/css.vim:
> line 129:
> E409: Unknown group name:
> cssValue.*,cssFunction,cssColor,cssStringQ,cssStringQQ oneline
> E475: Invalid argument: cssMathGroup contained
> matchgroup=cssMathParens start="(" end=")"
> containedin=cssFunction,cssMathGroup
>
> contains=cssCustomProp,cssValue.*,cssFunction,cssColor,cssStringQ,cssStringQQ
> oneline
> line 130:
> E409: Unknown group name:
> cssValue.*,cssFunction,cssURL,cssColor,cssStringQ,cssStringQQ oneline
> E475: Invalid argument: cssFunction contained
> matchgroup=cssFunctionName start="\<\(var\|calc\)\s*(" end=")"
>
> contains=cssCustomProp,cssValue.*,cssFunction,cssURL,cssColor,cssStringQ,cssStringQQ
> oneline
> line 453:
> E409: Unknown group name:
>
> css.*Prop,cssComment,cssValue.*,cssColor,cssURL,cssImportant,cssCustomProp,cssError,cssStringQ,cssStringQQ,cssFunction,cssUnicodeEscape,cssVendor,cssDefinition,cssHacks,cssNoise
> fold
> E475: Invalid argument: cssDefinition transparent matchgroup=cssBraces
> start='{' end='}'
>
> contains=cssTagName,cssAttributeSelector,cssClassName,cssIdentifier,cssAtRule,cssAttrRegion,css.*Prop,cssComment,cssValue.*,cssColor,cssURL,cssImportant,cssCustomProp,cssError,cssStringQ,cssStringQQ,cssFunction,cssUnicodeEscape,cssVendor,cssDefinition,cssHacks,cssNoise
> fold
> line 498:
> E409: Unknown group name:
>
> css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
> E475: Invalid argument: cssAttrRegion start=/:/
> end=/\ze\(;\|)\|}\|{\)/ contained
>
> contains=cssPseudoClassId,css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
> line 502:
> E409: Unknown group name:
>
> css.*Prop,css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
> E475: Invalid argument: cssAttrRegion start=/transition\s*:/
> end=/\ze\(;\|)\|}\)/ contained
>
> contains=css.*Prop,css.*Attr,cssColor,cssImportant,cssValue.*,cssFunction,cssString.*,cssURL,cssComment,cssUnicodeEscape,cssVendor,cssError,cssAttrComma,cssNoise
> line 527:
> E409: Unknown group name:
> css.*Prop,cssValue.*,cssVendor,cssAtKeyword,cssComment
> nextgroup=cssDefinition
> E475: Invalid argument: cssAtRule start=/@supports\>/ end=/\ze{/
> skipwhite skipnl
>
> contains=cssAtRuleLogical,cssAttrRegion,css.*Prop,cssValue.*,cssVendor,cssAtKeyword,cssComment
> nextgroup=cssDefinition
> Error detected while processing BufRead Autocommands for
> "*.html"..function dist#ft#FThtml[13]..FileType Autocommands for
> "*"..Syntax Autocommands for "*"..function 11_SynSet[25]..script
> /usr/local/share/vim/vim91/syntax/html.vim:
> line 312:
> E409: Unknown group name:
>
> css.*Attr,css.*Prop,cssComment,cssLength,cssColor,cssURL,cssImportant,cssError,cssString,@htmlPreproc
> E475: Invalid argument: htmlCssDefinition matchgroup=htmlArg
> start='style="' keepend matchgroup=htmlString end='"'
>
> contains=css.*Attr,css.*Prop,cssComment,cssLength,cssColor,cssURL,cssImportant,cssError,cssString,@htmlPreproc
>
>
> Best regards,
> Tony.
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/4374ce40-631a-487c-a06d-3c339fac4f65n%40googlegroups.com.

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

[Maxim Kim]

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 apply 
> all the above fixes. The default tar tool on Windows may still be limited 
> though and not support all the expected archive types.
>
> —
> Reply to this email directly, view it on GitHub 
> .
>
> You are receiving this because you are subscribed to this thread.Message 
> ID: 
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5c163939-080a-4809-8557-3d9e1723e0f4n%40googlegroups.com.

Re: Vim 9.1 has been released

[Maxim Kim]

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 9.1 release.  Thanks Christian for your hard work in 
> making
> this release happen.
>
> Regards,
> Yegappan
>
> On Tue, Jan 2, 2024 at 9:46 AM Christian Brabandt  wrote:
>
>> Dear Vim users,
>>
>> The Vim project is happy to announce that Vim 9.1 has finally been 
>> released. This release is dedicated to Bram Moolenaar, Vim's lead 
>> developer for more than 30 years, who suddenly passed away in August 
>> 2023.
>>
>> The most notable changes are support for Vim9 classes and objects, 
>> smooth scrolling support and virtual text support. And as usual, runtime 
>> files have been updated, many bugs have been fixed and potential 
>> security relevant fixes have been included. You can find the full 
>> announcement https://www.vim.org/vim-9.1-released.php
>>
>> I would like to thank everybody who contributed to the project through 
>> patches, translations, bug reporters and everybody else who helped 
>> making this release! We are very grateful for any support. 
>>
>> If you like Vim, you are encouraged to make a donation for needy 
>> children in Uganda. Please visit the ICCF web site for more information: 
>> https://iccf-holland.org
>>
>> Thanks and Happy New Year 2024!
>> Christian
>>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6f06caf2-d169-4824-8a23-97fdf242eca4n%40googlegroups.com.

Re: Where is Bram?

[Maxim Kim]

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 haven't seen any emails from Bram to the mailing list for more than a 
>> month.
>> Is he on vacation?  Has anyone had any contact with him in the last month?
>>
>> Regards,
>> Yegappan
>>
>> -- 
>> -- 
>> 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 
>> "vim_dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to vim_dev+u...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3De52bn9Hfip8VAs2N%3DNTEhNTjHkSkyzp0TKfpuiiPz4Q%40mail.gmail.com
>> .
>>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5a13bf47-b642-4224-b40b-41a454cff433n%40googlegroups.com.

Re: vim9 autoloaded functions in expression register

[Maxim Kim]

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 a good way to make this work. Being able to access 
"misc", which is script-local in one specific script, from any other 
context, means script-local isn't really "local" any more. 


I see. I guess it would probably require some trickery/hacks which will 
make it less robust. 
 

The best I can think of is to add a script-local function and use that: 

vim9script 
import autoload 'misc.vim' 

def Eatchar(arg: string): string 
return misc.Eatchar(arg) 
enddef 

iab  p! println!()=Eatchar('\s') 


This would defeat the purpose of putting function into autoloaded dir. 
I think the misc#Eatchar() is better from user experience perspective.

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/e21317f6-3c85-46f4-bf12-b5d27c981560n%40googlegroups.com.

vim9 autoloaded functions in expression register

[Maxim Kim]

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: misc

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6c4c7da5-d703-4f3c-bb4a-e488478d7534n%40googlegroups.com.

Re: edit buffer using a builtin function

[Maxim Kim]

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}"

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6fb57b3e-1b3c-4379-b0e9-341ba69e30f0n%40googlegroups.com.

Re: Choices for Vim9 class implementation

[Maxim Kim]

понедельник, 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 with "this." to avoid a name collision, while other object 
> members are used without "this.". I find that very confusing. Example: 
>
> SomeObject(String name) 
> { 
> this.name = name; 
> gender = Gender.unknown; 
> } 
>
>  
I would go with this.name and this.gender while accessing the variables.
 

>
> One thing I'm not yet sure about is the declaration. Currently it works 
> like this: 
>
> this.name: string 
> this.gender: Gender 
>
> and 

var name: string
var gender: Gender

to declare them. 

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5e7c4f18-1652-45b8-9f24-bf5bba8df051n%40googlegroups.com.

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

[Maxim Kim]

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. 
> > 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 am not sure how formatexpr should look like
>
> суббота, 5 ноября 2022 г. в 20:35:19 UTC+5, Bram Moolenaar: 
>
>>
>> > Oh, `formatexpr` can't speak vim9script! 
>> > 
>> > ``` 
>> > setl formatexpr=json#FormatExpr() 
>> > ``` 
>> > 
>> > Works! 
>> > 
>> > @brammool I can create a PR if needed. 
>>
>> It would be good to review, have others make comments. 
>> A PR should work for that. 
>>
>> I suppose including the script under autoload/dist works, then those who 
>> want to use it can set 'formatexpr' as you mentioned, with a filetype 
>> autocmd. If it works really well we could do it in the json filetype 
>> plugin. I suppose we would somehow need to vote about that. 
>>
>> -- 
>> Anyone who is capable of getting themselves made President should on no 
>> account be allowed to do the job. 
>> -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" 
>>
>> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net 
>> \\\ 
>> /// \\\ 
>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// 
>> \\\ help me help AIDS victims -- http://ICCF-Holland.org /// 
>>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/800a8994-b9ee-4f5f-9d28-84cf199cceb1n%40googlegroups.com.

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

[Maxim Kim]

> 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 am not sure how formatexpr should look like

суббота, 5 ноября 2022 г. в 20:35:19 UTC+5, Bram Moolenaar: 

>
> > Oh, `formatexpr` can't speak vim9script!
> > 
> > ```
> > setl formatexpr=json#FormatExpr()
> > ```
> > 
> > Works!
> > 
> > @brammool I can create a PR if needed.
>
> It would be good to review, have others make comments.
> A PR should work for that.
>
> I suppose including the script under autoload/dist works, then those who
> want to use it can set 'formatexpr' as you mentioned, with a filetype
> autocmd. If it works really well we could do it in the json filetype
> plugin. I suppose we would somehow need to vote about that.
>
> -- 
> Anyone who is capable of getting themselves made President should on no
> account be allowed to do the job.
> -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
>
> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\
> /// \\\
> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/56f60f85-53f8-4378-8308-6947cb349e8cn%40googlegroups.com.

Re: Health update

[Maxim Kim]

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 need to be
> done, which will take time. I won't be able to do much Vim stuff for a
> few days.
>
> I am in La Laguna medical hospital in Tenerife, they say the best in the
> area. It is very busy, need to wait for tests, which can be more than a
> day. They take fairly good care of me and I have friends helping out.
> I hope I have a diagnosis in a couple of days, then we'll see.
>
> Please hang in there, if my head is clear I'll try to go through a few
> PR (pick out the simple things :-). If only to keep me from going
> bored.
>
> -- 
> CART DRIVER: Bring out your dead!
> There are legs stick out of windows and doors. Two MEN are fighting in the
> mud - covered from head to foot in it. Another MAN is on his hands in
> knees shovelling mud into his mouth. We just catch sight of a MAN falling
> into a well.
> "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
>
> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\
> /// \\\
> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/0a9b3d0d-831b-4a60-a1a8-db1d3926419fn%40googlegroups.com.

Re: need to back out updates

[Maxim Kim]

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 my source level to 
9.0.0469 so i can have an editor that works?




git checkout v9.0.0469

sudo make install



thx in advance
--
--
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 "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CALfSX1xmE8t-nob10OczezbLq0bnE3RU6JvDYra12wD26GovmA%40mail.gmail.com 
.


--
--
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 "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/80bd258e-fed5-0ef0-3d52-a75e7a74aabc%40gmail.com.

Re: At patch level 9.0.471: Segmentation fault at startup

[Maxim Kim]

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 changed" and "other" modules? (I'm on openSUSE
Tumbleweed, a rather "volatile" OS.)

Best regards,
Tony.

On Thu, Sep 15, 2022 at 8:48 PM Tony Mechelynck
  wrote:

• I only tested the Big version.
• This happens in both vim and gvim.
• With my usual handcoded Session file, it happens immediately in both
vim and gvim.
• With only my usual vimrc, it happens immediately in gvim; in vim the
:info splash screen is displayed, then hitting Space a couple of times
gives SEGV.
• With --clean, it happens immediately in gvim; in vim the splash
screen appears then hitting Space does nothing, but :h followed by the
Enter key gives SEGV instead of displaying the help.

The following script is sourced in bash before compiling the concerned
executable:

export CONF_OPT_GUI='--enable-gui=gtk3'
export CONF_OPT_MULTIBYTE='--enable-multibyte'
export CONF_OPT_AUTOSERVE='--enable-autoservername'
export CONF_OPT_FEAT='--with-features=big'
export CONF_OPT_COMPBY='"--with-compiledby=antoine.mechely...@gmail.com"'

Best regards,
Tony.


--
--
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 "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/1ac58bef-cc58-1873-4c03-e2f74ce88cbc%40gmail.com.

Re: how to get old versions of vim

[Maxim Kim]

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 bisect to find the 
problematic patch. I realize that I'd have to learn more git. So, how 
to get vim 9.0, vim 8.0?




If you're ok with compiling vim then: (if you're sure v9.0. has no 
issues, if it has, choose older version tag)


1. git clone g...@github.com:vim/vim.git
2. git bisect start
3. git bisect bad
4. git bisect good v9.0.

build vim, check your plugin if it is bad: `git bisect bad`, if it is 
good: `git bisect good`


continue until commit that breaks your plugin is found.

--
--
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 "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/7f38b29d-ff87-e75d-0b9b-fc8a6d205fad%40gmail.com.

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

[Maxim Kim]

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 because you are subscribed to the Google Groups "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/e7b4cb8d-662f-f57a-a837-6b6311147209%40gmail.com.

Re: List of features to vote on

[Maxim Kim]

 > 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 9.0 has been released I thought it would be a good moment
> to update the list of features:
> https://www.vim.org/sponsor/vote_results.php
>
> Although it would be nice to reduce the length of the list, I find it
> difficult to decide what items to drop. Perhaps items that won't
> happen, such as improving the Athena support?
>
> What I was thinking of adding:
> - Multiple cursors, edit in several locations at the same time
> - built-in LSP support
> - virtual text (e.g. to display type information)
> - may hide part of the first line, scroll per screen line
>
> Anything else? I prefer not to add too many items, only things worth
> voting on, to avoid the list getting even longer.
>
> Note that this is not an invitation for everybody to call out their
> favorite feature!
>
> - Bram
>
> -- 
> It was recently discovered that research causes cancer in rats.
>
> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\
> /// \\\
> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/3f3c18b3-f6aa-41c5-8b8a-88fd680cb904n%40googlegroups.com.

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

[Maxim Kim]

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 Kim wrote:
>
>> *Is your feature request about something that is currently impossible or 
>> hard to do? Please describe the problem.*
>>
>> It would be nice if there were a way to have current line number aligned 
>> right when set number relativenumber is active:
>>
>> [image: image] 
>> <https://user-images.githubusercontent.com/234774/155730941-ddd69c3c-25c9-47eb-b998-3a501c28e507.png>
>>
>> *Describe the solution you'd like*
>> A setting, like set relativenumberopt=right that aligns current 
>> relativenumber line right.
>>
>> —
>> Reply to this email directly, view it on GitHub 
>> <https://github.com/vim/vim/issues/9847>.
>> Triage notifications on the go with GitHub Mobile for iOS 
>> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email=8=524675>
>>  
>> or Android 
>> <https://play.google.com/store/apps/details?id=com.github.android=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>>  
>>
>> You are receiving this because you are subscribed to this thread.Message 
>> ID: 
>>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/a4a1eadc-c013-47a9-ab41-a03067b48d1bn%40googlegroups.com.

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

[Maxim Kim]

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.
> >
> > Is there a reason not to support file/directory names?
> >
>
> The call stack to get/expand a list of file/directory names is nested 
> deeply. In
> this function stack, the search pattern gets mangled (to add wildcard 
> characters
> and escape other special characters). So a lot of code changes are needed 
> to
> add fuzzy completion for file name/directory names. I may look at this 
> after
> adding fuzzy completion for tag names.
>
> Regards,
> Yegappan
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/47dcc040-719f-4d70-b6e2-294d64f4bb8cn%40googlegroups.com.

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

[Maxim Kim]

> 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, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/bd7ef6bf-a82b-4a5e-97ce-e3db26528b39n%40googlegroups.com.

def! in legacy vimscript

[Maxim Kim]

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 Hello is 
globally defined and one can :call Hello() and get echoed "hello world".

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/a4ebf292-a736-429c-bf3f-6794cb94983dn%40googlegroups.com.

Re: vim/colorschemes: Request For Comments

[Maxim Kim]

суббота, 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 issue for the same purpose (to 
get more feedback)? It would probably have more visibility.
On the other hand, if you include them now, we will definitely get real 
feedback on the matter.

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/8f36646b-276c-42ae-b6d6-3c1e6c31dfe0n%40googlegroups.com.

Re: vim9 vimCommentString

[Maxim Kim]

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_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 received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/9f943ddc-da03-4454-bff3-504c9f90bd8bn%40googlegroups.com.

vim9 vimCommentString

[Maxim Kim]

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 received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/c89108af-b9ac-4a8d-92d7-12d2a8d6b549n%40googlegroups.com.

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

[Maxim Kim]

понедельник, 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. 
>
>
How would you create a colorscheme like peachpuff without defining Normal 
hl group? Or blue, darkblue, etc? 

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6cbd4c9a-216e-459e-9f5b-998d43196311n%40googlegroups.com.

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

[Maxim Kim]

Basically, the issue is fairly simple to reproduce (cmd.exe, windows):

1. `vim -Nu NONE`
2. `set tgc`
3. `set cursorline`
4. `set ft=vim`
5. `syntax on`
6. `iecho "hello world"`

 we can see syntax under cursorline

7. ` colo industry`

^^^ no syntax highlighting


And it 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:43 UTC+3, Maxim Kim: 

>
> 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 января 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 
>>> <https://github.com/vim/vim/issues/9617#issuecomment-1019859913>.
>>> Triage notifications on the go with GitHub Mobile for iOS 
>>> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email=8=524675>
>>>  
>>> or Android 
>>> <https://play.google.com/store/apps/details?id=com.github.android=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>>>  
>>>
>>>
>>> You are receiving this because you are subscribed to this thread.Message 
>>> ID: 
>>>
>>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/8980587d-c87f-4359-a163-6d13764896b3n%40googlegroups.com.

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

[Maxim Kim]

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 января 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 
>> <https://github.com/vim/vim/issues/9617#issuecomment-1019859913>.
>> Triage notifications on the go with GitHub Mobile for iOS 
>> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email=8=524675>
>>  
>> or Android 
>> <https://play.google.com/store/apps/details?id=com.github.android=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>>  
>>
>>
>> You are receiving this because you are subscribed to this thread.Message 
>> ID: 
>>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/a90e701b-368a-4683-855c-5e7f060b8241n%40googlegroups.com.

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

[Maxim Kim]

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 
> .
> Triage notifications on the go with GitHub Mobile for iOS 
> 
>  
> or Android 
> .
>  
>
>
> You are receiving this because you are subscribed to this thread.Message 
> ID: 
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/c9b81fc0-e821-460e-9619-344f1a4eddf3n%40googlegroups.com.

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

[Maxim Kim]

 = 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
endfor



And there is also buffer local options, are you about to have 2 
dictionaries?

понедельник, 24 января 2022 г. в 09:38:27 UTC+3, yegapp...@gmail.com: 

> Hi all,
>
> Currently Vim options can be accessed from a Vim script by prefixing the
> option name with a '&':
>
> let  = 2
> let oldval = 
>
> The Python Vim interface supports a dictionary for accessing the Vim 
> options
> https://vimhelp.org/if_pyth.txt.html#python-options
>
> The Lua Vim interface in Neovim support this:
> https://github.com/neovim/neovim/blob/master/runtime/doc/lua.txt#L1022
>
> But this is currently not supported by Vim script.
>
> What do you think about adding support for a v:vim.opt dictionary to
> read/modify Vim options:
>
> let v:vim.opt.shiftwidth = 2
> let oldval = v:vim.opt.shiftwidth
> echo has_key(v:vim.opt, 'newopt')
> echo keys(v:vim.opt)
> echo items(v:vim.opt)
>
> The changes to support this are available at:
>
> https://github.com/yegappan/vim/commit/52beff56044e93c7bb982243ff593b461cd649c2
>
> Regards,
> Yegappan
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/54bce5d3-beeb-44ed-9125-e5db49587c1an%40googlegroups.com.

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

[Maxim Kim]

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 at 04:10:23PM +0100, Christian Brabandt <
> cbl...@256bit.org> wrote:
> > On Di, 11 Jan 2022, Thomas Köhler wrote:
> > 
> > > Actually, please let me know if any changes are required for
> > > koehler.vim or let me have a look at the new version if you
> > > already made those changes. I would take the opportunity to have
> > > a look into those changes (plus into any additional highlight
> > > groups that might exist and that I would then fully support).
> > 
> > Improving the existing Colorschemes are worked on in the 
> > vim/colorschemes repository. For koehler, you can have a look at:
> > https://github.com/vim/colorschemes/blob/master/colors/koehler.vim
>
> Thanks.
> I just tested a bit and found an issue:
> When I run vim in an xterm and then decide to switch to the gui
> via ":gui", the colorscheme doesn't fully apply.
> The reason for this is that the code that defines everything for
> the gui is enclosed in code like this:
>
> if (has('termguicolors') && ) || has('gui_running')
> let g:terminal_ansi_colors = ['#00', '#cd', '#00cd00', '#cdcd00', 
> '#ee', '#cd00cd', '#00cdcd', '#e5e5e5', '#7f7f7f', '#ff', 
> '#00ff00', '#00', '#5c5cff', '#ff00ff', '#00', '#ff']
> hi ColorColumn guifg=NONE guibg=#8b gui=NONE cterm=NONE
> [...]
> unlet s:t_Co
> finish
> endif
>
> So in other words, if you start vim in xterm, termguicolors may
> not be available and gui_running obviously is not the case, which
> leads to g:terminal_ansi_colors not being set and and the "hi"
> commands that would setup highlightning for the gui correctly are
> not executed. If you then decide to run ":gui", the colorscheme
> isn't loaded again, skipping this part completely. I ended up
> with gvim and white background even though my colorscheme has
> been developed for a black background.
>
> I could fix this by adding the following lines near the beginning
> of the file:
>
> augroup COLORSCHEME
> au! GuiEnter * colorscheme koehler
> augroup END
>
> However, I'm not sure if this is actually a safe way to address
> the issue (just using an autocommand didn't work in my case as my
> .vimrc contains another "au! GuiEnter ..." which overwrites all
> autocommands for the GuiEnter event; that's why I tried the
> augroup in the first place). Someone might create a COLORSCHEME
> augroup in his .vimrc which might then collide with the one
> defined here.
>
> Maybe one of the people working on the colorschemes has a better
> idea how to resolve this?
>
> > Best,
> > Christian
>
> Bye,
> Thomas
>
> -- 
> Thomas Köhler Email: jean...@picard.franken.de
> <>< WWW: http://gott-gehabt.de
> IRC: tkoehler Freenode: thkoehler
> PGP public key available from Homepage!
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/e7b6d964-0e0b-4b6b-b430-c5b9bd59861en%40googlegroups.com.

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

[Maxim Kim]

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 the same escape codes? And what are they?
>
> For me, using xfce4-terminal-0.8.7.4 on xubuntu-18.04.6 (so a bit ancient),
> double underline works in the terminal as illustrated in the screenshot 
> below.
> But dotted and dashed underline shows nothing.
>
> [image: double-underline-et-with-xfce4-terminal-0 8 7 4] 
> 
>
> —
> Reply to this email directly, view it on GitHub 
> .
> Triage notifications on the go with GitHub Mobile for iOS 
> 
>  
> or Android 
> .
>  
>
>
> You are receiving this because you are subscribed to this thread.Message 
> ID: 
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/2b2d18b8-9f59-46fc-aad9-cec68aef203fn%40googlegroups.com.

vim9script lambda syntax highlight

[Maxim Kim]

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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/63d34cf6-e176-4a0e-8c65-a4b6d76a5e03n%40googlegroups.com.

Re: Patch 8.2.4059

[Maxim Kim]

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, src/map.c, src/proto/map.pro,
> src/testdir/test_vim9_import.vim
>
>
> *** ../vim-8.2.4058/src/getchar.c 2022-01-04 18:01:17.889123524 +
> --- src/getchar.c 2022-01-11 11:28:26.060819006 +
> ***
> *** 2785,2791 
> int save_m_noremap;
> int save_m_silent;
> char_u *save_m_keys;
> - char_u *save_m_str;
> #else
> # define save_m_noremap mp->m_noremap
> # define save_m_silent mp->m_silent
> --- 2785,2790 
> ***
> *** 2834,2840 
> save_m_noremap = mp->m_noremap;
> save_m_silent = mp->m_silent;
> save_m_keys = NULL; // only saved when needed
> - save_m_str = NULL; // only saved when needed
>
> /*
> * Handle ":map ": evaluate the {rhs} as an expression. Also
> --- 2833,2838 
> ***
> *** 2851,2858 
> may_garbage_collect = FALSE;
>
> save_m_keys = vim_strsave(mp->m_keys);
> ! save_m_str = vim_strsave(mp->m_str);
> ! map_str = eval_map_expr(save_m_str, NUL);
>
> // The mapping may do anything, but we expect it to take care of
> // redrawing. Do put the cursor back where it was.
> --- 2849,2855 
> may_garbage_collect = FALSE;
>
> save_m_keys = vim_strsave(mp->m_keys);
> ! map_str = eval_map_expr(mp, NUL);
>
> // The mapping may do anything, but we expect it to take care of
> // redrawing. Do put the cursor back where it was.
> ***
> *** 2900,2906 
> }
> #ifdef FEAT_EVAL
> vim_free(save_m_keys);
> - vim_free(save_m_str);
> #endif
> *keylenp = keylen;
> if (i == FAIL)
> --- 2897,2902 
> *** ../vim-8.2.4058/src/map.c 2022-01-02 20:20:41.377033186 +
> --- src/map.c 2022-01-11 11:40:09.263727756 +
> ***
> *** 260,265 
> --- 260,266 
> {
> mp->m_script_ctx.sc_sid = sid;
> mp->m_script_ctx.sc_lnum = lnum;
> + mp->m_script_ctx.sc_version = in_vim9script() ? SCRIPT_VERSION_VIM9 : 0;
> }
> else
> {
> ***
> *** 1565,1571 
> }
> #ifdef FEAT_EVAL
> if (mp->m_expr)
> ! s = eval_map_expr(mp->m_str, c);
> else
> #endif
> s = mp->m_str;
> --- 1566,1572 
> }
> #ifdef FEAT_EVAL
> if (mp->m_expr)
> ! s = eval_map_expr(mp, c);
> else
> #endif
> s = mp->m_str;
> ***
> *** 1600,1606 
> */
> char_u *
> eval_map_expr(
> ! char_u *str,
> int c) // NUL or typed character for abbreviation
> {
> char_u *res;
> --- 1601,1607 
> */
> char_u *
> eval_map_expr(
> ! mapblock_T *mp,
> int c) // NUL or typed character for abbreviation
> {
> char_u *res;
> ***
> *** 1609,1618 
> pos_T save_cursor;
> int save_msg_col;
> int save_msg_row;
>
> // Remove escaping of CSI, because "str" is in a format to be used as
> // typeahead.
> ! expr = vim_strsave(str);
> if (expr == NULL)
> return NULL;
> vim_unescape_csi(expr);
> --- 1610,1621 
> pos_T save_cursor;
> int save_msg_col;
> int save_msg_row;
> + scid_T save_sctx_sid = current_sctx.sc_sid;
> + int save_sctx_version = current_sctx.sc_version;
>
> // Remove escaping of CSI, because "str" is in a format to be used as
> // typeahead.
> ! expr = vim_strsave(mp->m_str);
> if (expr == NULL)
> return NULL;
> vim_unescape_csi(expr);
> ***
> *** 1625,1636 
> --- 1628,1649 
> save_cursor = curwin->w_cursor;
> save_msg_col = msg_col;
> save_msg_row = msg_row;
> + if (mp->m_script_ctx.sc_version == SCRIPT_VERSION_VIM9)
> + {
> + current_sctx.sc_sid = mp->m_script_ctx.sc_sid;
> + current_sctx.sc_version = SCRIPT_VERSION_VIM9;
> + }
> + 
> + // Note: the evaluation may make "mp" invalid.
> p = eval_to_string(expr, FALSE);
> + 
> --textwinlock;
> --ex_normal_lock;
> curwin->w_cursor = save_cursor;
> msg_col = save_msg_col;
> msg_row = save_msg_row;
> + current_sctx.sc_sid = save_sctx_sid;
> + current_sctx.sc_version = save_sctx_version;
>
> vim_free(expr);
>
> *** ../vim-8.2.4058/src/proto/map.pro 2021-07-30 20:32:41.448722501 +0100
> --- src/proto/map.pro 2022-01-11 11:28:31.184817355 +
> ***
> *** 10,16 
> char_u *set_context_in_map_cmd(expand_T *xp, char_u *cmd, char_u *arg, int 
> forceit, int isabbrev, int isunmap, cmdidx_T cmdidx);
> int ExpandMappings(regmatch_T *regmatch, int *num_file, char_u ***file);
> int check_abbr(int c, char_u *ptr, int col, in

vim9 readiness + legacy colorscheme remakes

[Maxim Kim]

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 to resolve

* incsearch visibility (there is already a PR to address it)
* diff visibility issues with error highlighting.

Remakes would definitely be a "breaking change" as they:
* try to use 256 color palette where possible with fallback to 16 colors 
and no colors depending on t_Co
* some colorschemes were using completely different colors in gui and tui 
-- we did pick one and made it consistent too.

It means that, for example, peachpuff now is light even in tui -- and there 
for sure people who use peachpuff with dark background relying on terminal 
0-15 colors who probably would not be very happy with this change.

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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/10a9be01-99d7-469b-b75b-8e9271c85186n%40googlegroups.com.

Re: Patch 8.2.4050

[Maxim Kim]

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() .. '_'
>
> Now works (as of 8.2.4058)
> понедельник, 10 января 2022 г. в 15:17:40 UTC+3, Bram Moolenaar: 
>
>>
>> Maxim Kim wrote: 
>>
>> > 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 comment.Toggle() 
>> > # xnoremap   gc comment.Toggle() 
>> > # nnoremap   gcc comment.Toggle() .. '_' 
>> > export def Toggle(...args: list): string 
>> > ... 
>> > 
>> > And in my ~/vimfiles/vimrc: 
>> > 
>> > import autoload 'comment.vim' 
>> > nnoremap   gc comment.Toggle() 
>> > xnoremap   gc comment.Toggle() 
>> > nnoremap   gcc comment.Toggle() .. '_' 
>> > # nnoremap   gc comment#toggle() 
>> > # xnoremap   gc comment#toggle() 
>> > # nnoremap   gcc comment#toggle() .. '_' 
>> > 
>> > After pressing gcc I get error: 
>> > 
>> > E121: Undefined variable: comment 
>>
>> This isn't fully implemented yet. It turns out it's more complicated. 
>>
>> Thanks for the example, I'll try it out after some more changes. 
>>
>> -- 
>> GALAHAD: Camelot ... 
>> LAUNCELOT: Camelot ... 
>> GAWAIN: It's only a model. 
>> "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD 
>>
>> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net 
>> \\\ 
>> /// \\\ 
>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// 
>> \\\ help me help AIDS victims -- http://ICCF-Holland.org /// 
>>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/150ae53a-06c2-41ad-9e1c-2f45a62a3452n%40googlegroups.com.

Re: Patch 8.2.4050

[Maxim Kim]

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 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 comment.Toggle()
> > # xnoremap   gc comment.Toggle()
> > # nnoremap   gcc comment.Toggle() .. '_'
> > export def Toggle(...args: list): string
> > ...
> > 
> > And in my ~/vimfiles/vimrc:
> > 
> > import autoload 'comment.vim'
> > nnoremap   gc comment.Toggle()
> > xnoremap   gc comment.Toggle()
> > nnoremap   gcc comment.Toggle() .. '_'
> > # nnoremap   gc comment#toggle()
> > # xnoremap   gc comment#toggle()
> > # nnoremap   gcc comment#toggle() .. '_'
> > 
> > After pressing gcc I get error:
> > 
> > E121: Undefined variable: comment
>
> This isn't fully implemented yet. It turns out it's more complicated.
>
> Thanks for the example, I'll try it out after some more changes.
>
> -- 
> GALAHAD: Camelot ...
> LAUNCELOT: Camelot ...
> GAWAIN: It's only a model.
> "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
>
> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\
> /// \\\
> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/19140862-7752-4965-9147-b16e1c4a96adn%40googlegroups.com.

Re: Patch 8.2.4050

[Maxim Kim]

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 comment.Toggle()
#  xnoremap   gc comment.Toggle()
#  nnoremap   gcc comment.Toggle() .. '_'
export def Toggle(...args: list): string
...

And in my ~/vimfiles/vimrc:

import autoload 'comment.vim'
nnoremap   gc comment.Toggle()
xnoremap   gc comment.Toggle()
nnoremap   gcc comment.Toggle() .. '_'
# nnoremap   gc comment#toggle()
# xnoremap   gc comment#toggle()
# nnoremap   gcc comment#toggle() .. '_'

After pressing gcc I get error:

E121: Undefined variable: comment

[image: 2022-01-10_10-17-06.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 subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/d211cce6-38c2-49fa-8458-2f7b2a513c35n%40googlegroups.com.

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

[Maxim Kim]

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: ‘GTimeVal’ is 
> deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
> > 73 | GTimeVal last_popdown;
> > | ^~~~
> > 
> > 
> > Not sure if it is important and/or should be fixed.
> > 
> > My build commands are:
> > 
> > sudo make distclean
> > ./configure --with-features=huge --enable-python3interp --enable-gui
> > sudo make install
>
> Yes, see https://github.com/vim/vim/issues/4987
>
> I don't think there is much that we can do here. You may try the 
> mentioned "patch" there. Or start using the GTK3 gui, since gtk2 is 
> end-of-life already. Or use -Wno-deprecated-declarations as CFLAG
>
>
> Best,
> Christian
> -- 
> Die gefährlichsten Menschen auf der Welt sind die enttäuschten
> Individualisten.
> -- Halldór Kiljan Laxness
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5dbbe022-e618-4d8e-b734-0407a2af6755n%40googlegroups.com.

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

[Maxim Kim]

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 build commands are:

sudo make distclean
./configure --with-features=huge --enable-python3interp --enable-gui
sudo make install

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/35423b48-2ad1-4407-a236-2918b880948an%40googlegroups.com.

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

[Maxim Kim]

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 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 can try using the following site: 
> https://axelf.nu/vim-helptag-versions/
>
> - Yegappan
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/dfa4fac4-1b78-4056-a19c-777bc3c20aaen%40googlegroups.com.

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

[Maxim Kim]

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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/04e4901f-a875-46e6-9982-b4c47ab89d14n%40googlegroups.com.

Proper way to find when a function appeared in vim

[Maxim Kim]

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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/4e09e058-14b9-41c1-aae1-1e1f3c8b9889n%40googlegroups.com.

Re: vi stackexchange "verification"

[Maxim Kim]

>
>
> 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 replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/b2925756-6163-4ae8-ae0f-f3226cd4d6d6n%40googlegroups.com.

vi stackexchange "verification"

[Maxim Kim]

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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/1e64c487-2c89-40a1-a197-c8351b2a2f15n%40googlegroups.com.

Re: duplicate exists() tag

[Maxim Kim]

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 GUI version with OLE support
> Included patches: 1-3318
>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/eeec9653-70ab-4954-bbfc-7771cbf7be96n%40googlegroups.com.

duplicate exists() tag

[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 GUI version with OLE support
Included patches: 1-3318

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/2d40e239-8e93-479b-b9b8-f7bbc1e46087n%40googlegroups.com.

Re: Patch 8.2.3255

[Maxim Kim]

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< 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, src/textobject.c
>>
>
> Nice, thank you!
>
> Although it works a bit different to ci".
>
>   here is the cursor where we press cib to jump
>   to the next line (and here would be the cursor) 
>
> I wonder if ci" could work this way 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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f5e07165-5547-4df6-a69e-756010080b24n%40googlegroups.com.

Re: Patch 8.2.3255

[Maxim Kim]

суббота, 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, src/textobject.c
>

Nice, thank you!

Although it works a bit different to ci".

  here is the cursor where we press cib to jump
  to the next line (and here would be the cursor) 

I wonder if ci" could work this way 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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f297fb03-db88-4864-a68e-f879f5d1a274n%40googlegroups.com.

Re: Patch 8.2.2912

[Maxim Kim]

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: runtime/doc/options.txt, src/mbyte.c, src/option.c, src/option.h,
> > src/testdir/test_writefile.vim
>
> I still wonder if there are users who have a problem with this change.
> If you do, please let us know. If too many people complain we can
> revert this.
>
> -- 
> Save the plankton - eat a whale.
>
> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\
> /// \\\
> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/9baa6292-b32c-42eb-b616-86340bd64eb6n%40googlegroups.com.

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

[Maxim Kim]

>
>
> 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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/d32b90be-c01e-4ec5-9941-e777a2fbaf67n%40googlegroups.com.

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

[Maxim Kim]

суббота, 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" 
> > > set -ag terminal-overrides ",xterm-256color:Tc" 
> > > 
> > > Let me know if something needs to be changed. 
> > > 
> > > 
> > > 
> > This works for me too (on debian): 
> > 
> > set -g default-terminal "tmux-256color" 
> > set -ag terminal-overrides ',*:RGB' 
>
> OK, so which one of the two should we recommend? 
>
>  
I guess it depends on what terminfo is more common to be installed by 
default:

https://unix.stackexchange.com/questions/1045/getting-256-colors-to-work-in-tmux
 

quote>

> The newest version of ncurses ships with a *tmux-256color* terminfo entry 
(the FAQ 
<https://github.com/tmux/tmux/wiki/FAQ#why-do-you-use-the-screen-terminal-description-inside-tmux>
 does 
mention this). 
> As an example, a benefit of using *tmux-256color* over *screen-256color* is 
that italics is properly rendered (screen doesn't support italics).

> So if you are using tmux 2.6 or above, and have the latest ncurses 
package, the following will work as well:
> set -g default-terminal "tmux-256color"

Also for terminal overrides 
https://gist.github.com/bbqtd/a4ac060d6f6b9ea6fe3aabe735aa9d95#rgb-colors

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/68fd9879-7eae-41d1-9174-c3614f16f604n%40googlegroups.com.

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

[Maxim Kim]

пятница, 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.
>
>
>
This works for me too (on debian):

set -g default-terminal "tmux-256color"
set -ag terminal-overrides ',*:RGB'

 

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/3eb801b5-e2fd-4bd1-9cb8-230b3a286304n%40googlegroups.com.

Re: Insert non-rectangular selection

[Maxim Kim]

пятница, 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. I think that's better than 
>> having "zp" drop spaces that were yanked. 
>>
>>
> What about "zd" then? 
>

I mean I know it deletes a fold and it is kind of gets out of the row of 
"zp", "zy" and "zd" 

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/b9eb2eac-16c7-4396-abd9-240694aa8376n%40googlegroups.com.

Re: Insert non-rectangular selection

[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. I think that's better than 
> having "zp" drop spaces that were yanked. 
>
>
What about "zd" then? 

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5de914b9-05b7-4acc-a096-6a7ef1b3c8ccn%40googlegroups.com.

Re: Insert non-rectangular selection

[Maxim Kim]

>
>
> 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 information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/44ad88f7-181b-47e5-8f31-7208ec296346n%40googlegroups.com.

Re: Patch 8.2.2759

[Maxim Kim]

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 vim.h:2165,
 from evalvars.c:14:
proto/vim9script.pro:15:6: note: declared here
 void update_vim9_script_var(int create, dictitem_T *di, int flags, 
typval_T *tv, type_T **type, int do_member);
  ^~
evalvars.c:3356:6: error: too few arguments to function 
‘update_vim9_script_var’
  update_vim9_script_var(TRUE, di, flags, tv, );
  ^~
In file included from proto.h:236,
 from vim.h:2165,
 from evalvars.c:14:
proto/vim9script.pro:15:6: note: declared here
 void update_vim9_script_var(int create, dictitem_T *di, int flags, 
typval_T *tv, type_T **type, int do_member);
  ^~


вторник, 13 апреля 2021 г. в 22:08:25 UTC+3, basi...@internode.on.net: 

>
> On 14-Apr-2021 04:54, Bram Moolenaar wrote:
> > Patch 8.2.2759
> > Problem: Vim9: for loop infers type of loop variable.
> > Solution: Do not get the member type. (closes #8102)
> > Files: src/vim9type.c, src/proto/vim9type.pro, src/list.c,
> > src/vim9script.c, src/proto/vim9script.pro, src/vim.h,
> > src/testdir/test_vim9_script.vim
> >
> >
> After this patch mingw64 (gcc 10.3.0) spits out this error:
> 
> gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 
> -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -D__USE_MINGW_ANSI_STDIO 
> -pipe -march=native -Wall -O3 -fomit-frame-pointer -freg-struct-return 
> -fpie -fPIE  evalvars.c -o objnative/evalvars.o
> evalvars.c: In function 'set_var_const':
> evalvars.c:3258:3: error: too few arguments to function 
> 'update_vim9_script_var'
>  3258 |   update_vim9_script_var(FALSE, di, flags, tv, );
>   |   ^~
> In file included from proto.h:236,
>  from vim.h:2165,
>  from evalvars.c:14:
> proto/vim9script.pro:15:6: note: declared here
>15 | void update_vim9_script_var(int create, dictitem_T *di, int 
> flags, typval_T *tv, type_T **type, int do_member);
>   |  ^~
> evalvars.c:3356:6: error: too few arguments to function 
> 'update_vim9_script_var'
>  3356 |  update_vim9_script_var(TRUE, di, flags, tv, );
>   |  ^~
> In file included from proto.h:236,
>  from vim.h:2165,
>  from evalvars.c:14:
> proto/vim9script.pro:15:6: note: declared here
>15 | void update_vim9_script_var(int create, dictitem_T *di, int 
> flags, typval_T *tv, type_T **type, int do_member);
>   |  ^~
> make: *** [Make_cyg_ming.mak:1145: objnative/evalvars.o] Error 1
> 
>
> Cheers
> John
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/e129afb4-1708-4d44-8ee4-31932e6a4efan%40googlegroups.com.

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

[Maxim Kim]

четверг, 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 it wouldn't disable it cause ftplugin checks for var existense:

if has("folding") && exists("g:markdown_folding")
...


> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub 
> , or 
> unsubscribe 
> 
> .
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/db778eff-aea7-4307-895b-a9212baf5ee8n%40googlegroups.com.

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

[Maxim Kim]

понедельник, 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 
> stay open as long as the popup menu is open. Not longer. Since we can only 
> have 1 popup menu at a time, we would only have 1 focusable popup window.
>
That is exactly the case, thx!
 

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ea90d85f-961d-46d5-b459-d985bffa2fb3n%40googlegroups.com.

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

[Maxim Kim]

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 
Diff(Text|Change|Add).

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/0c8e7436-ce26-40ec-b9ae-72e51dcfad14n%40googlegroups.com.

Re: How to create a syntax keyword at runtime?

[Maxim Kim]

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 properties with external text analyzer might be a good fit 
for it.

понедельник, 14 декабря 2020 г. в 08:04:27 UTC+3, Ron Aaron: 

> I explained exactly what I mean in the original post.
>
> Yes, of course I'm talking about a specific file type, but the specific 
> type is unimportant since it's something I'm creating and not something in 
> the vim syntax files.
>
> What I intend is simply that if the user types in (the file being created) 
> something like:
>
> *: foo bar ;*
>
> Then "*foo*" becomes a syntax keyword. The criteria for becoming a 
> keyword in this context is that it is preceded by a colon, and delimited by 
> white-space. Thus 'bar' is not a keyword, nor is ": foo".  Think of the 
> leading colon-space as a function declarator.
>
> What I can't figure out is how to trap "foo" without trapping the leading 
> colon-space.
>
> On Sunday, December 13, 2020 at 5:28:28 PM UTC+2 Charles Campbell wrote:
>
>> Ron Aaron wrote: 
>> > Is this possible w/ vim's syntax highlighting? 
>> > 
>> > On Wednesday, December 9, 2020 at 10:56:35 AM UTC+2 Ron Aaron wrote: 
>> > 
>> > Hi all - 
>> > 
>> > I want to have a keyword (user-defined function) highlighted by my 
>> > syntax file. 
>> > 
>> > The code looks like this: 
>> > 
>> > :  foo  blah blah ; 
>> > 
>> > In this case I want "foo" to be scooped up. What I'm doing now is 
>> > this: 
>> > 
>> >  syn match colonDef "^\s*:\s\+\zs\S\+" 
>> > 
>> > That highlights the correct thing (e.g. 'foo') where it's defined, 
>> > but I can't figure out how to get it to be highlighted elsewhere 
>> > in the code (e.g. when simply 'foo' appears without a leading colon). 
>> > 
>> > How can I accomplish this? 
>> > 
>> > 
>> What do you mean by "vim's syntax highlighting"? Assuming no filetype, 
>> say in a file called "joe.coffee", you could type 
>>
>> syn keyword colonDef foo 
>> hi link colonDef Statement 
>>
>> and foo would be highlighted as Statement in your file. 
>>
>> Somehow I don't think you're really meaning "vim's syntax highlighting", 
>> but rather "vim's syntax highlighting for the XYZ filetype". Naturally, 
>> that missing information greatly affects things.  Syntax highlighting 
>> involves groups, containment, matches, regions, etc. My guess is that 
>> you want your modified "colonDef" highlighting to occur in some region 
>> defined by the filetype's syntax highlighting, but you've defined a 
>> match that is not contained in that region. To find out what that region 
>> is named, you could try my plugin: 
>> http://www.drchip.org/astronaut/vim/index.html#HILINKS and use :HLT!, 
>> move the cursor about, and you'll see a trace explaining what syntax and 
>> highlighting regions/etc are involved. Additionally, there's issues of 
>> priority involved, but often you can use "containedin=..." to get what 
>> you want. 
>>
>> Once you've done that, you could place a file in your 
>> .vim/after/syntax/XYZ.vim file the extra directions giving the 
>> additional highlighting you want. 
>>
>> Regards, 
>> Chip Campbell 
>>
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/bcde1c7b-1b39-4de8-aba5-7ed26cb2c795n%40googlegroups.com.

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

[Maxim Kim]

> 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, ftplugin, 
syntax) https://github.com/habamax/.vim/tree/master/pack/habamax/start/vim-toml

This change wouldn't break it, right?


-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/81e8d971-6531-4251-adbe-6ad8ca7d6f35n%40googlegroups.com.

Re: Patch 8.2.2015

[Maxim Kim]

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 much more common than using an expression, and
> considering that JavaScript uses this syntax, using the {} form for 
dictionary
> literals was considered a much more useful syntax. In Vim9 script the {} 
form
> uses literal keys: >
> let dict = {key: value}


What is correct? `Literally`, `literaly`? Or should it be just `literal` as 
in
dictionary literal values 
https://www.linuxtopia.org/online_books/programming_books/python_programming/python_ch15s02.html?

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5979c6d9-d251-41bb-8134-22b61acd1cd3n%40googlegroups.com.

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

[Maxim Kim]

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.
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/a6d722e1-d441-45b2-9943-a00dcd2e4401n%40googlegroups.com.

Re: Patch 8.2.1978

[Maxim Kim]

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 subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/7d98d5c5-e4e6-42df-9b87-24cbd0b8f4a8n%40googlegroups.com.

Re: Patch 8.2.1978

[Maxim Kim]

 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)
> Files: runtime/doc/autocmd.txt, runtime/doc/eval.txt,
> runtime/doc/map.txt, src/edit.c, src/errors.h, src/ex_docmd.c,
> src/ex_getln.c, src/getchar.c, src/insexpand.c, src/keymap.h,
> src/map.c, src/misc2.c, src/normal.c, src/ops.c,
> src/proto/getchar.pro, src/screen.c, src/terminal.c,
> src/testdir/test_mapping.vim
>
>
> *** ../vim-8.2.1977/runtime/doc/autocmd.txt 2020-10-21 12:19:50.080854732 
> +0200
> --- runtime/doc/autocmd.txt 2020-11-12 13:28:53.302992440 +0100
> ***
> *** 551,562 
> *CmdlineEnter*
> CmdlineEnter After moving the cursor to the command line,
> where the user can type a command or search
> ! string.
>  is set to a single character,
> indicating the type of command-line.
> |cmdwin-char|
> *CmdlineLeave*
> ! CmdlineLeave Before leaving the command line.
> Also when abandoning the command line, after
> typing CTRL-C or .
> When the commands result in an error the
> --- 551,565 
> *CmdlineEnter*
> CmdlineEnter After moving the cursor to the command line,
> where the user can type a command or search
> ! string; including non-interactive use of ":"
> ! in a mapping, but not when using ||.
>  is set to a single character,
> indicating the type of command-line.
> |cmdwin-char|
> *CmdlineLeave*
> ! CmdlineLeave Before leaving the command line; including
> ! non-interactive use of ":" in a mapping, but
> ! not when using ||.
> Also when abandoning the command line, after
> typing CTRL-C or .
> When the commands result in an error the
> *** ../vim-8.2.1977/runtime/doc/eval.txt 2020-11-09 18:31:30.544791868 
> +0100
> --- runtime/doc/eval.txt 2020-11-12 13:23:14.947599257 +0100
> ***
> *** 8592,8597 
> --- 8662,8668 
> the following mappings: >
> nnoremap  GG ":echom ".screencol()."\n"
> nnoremap  GG :echom screencol()
> + nnoremap GG echom screencol()
> <
> screenpos({winid}, {lnum}, {col}) *screenpos()*
> The result is a Dict with the screen position of the text
> *** ../vim-8.2.1977/runtime/doc/map.txt 2020-10-07 17:28:47.473370302 +0200
> --- runtime/doc/map.txt 2020-11-12 13:56:22.455089311 +0100
> ***
> *** 254,260 
> - The |:normal| command.
> - Moving the cursor is allowed, but it is restored afterwards.
> If you want the mapping to do any of these let the returned characters do
> ! that.
>
> You can use getchar(), it consumes typeahead if there is any. E.g., if you
> have these mappings: >
> --- 271,277 
> - The |:normal| command.
> - Moving the cursor is allowed, but it is restored afterwards.
> If you want the mapping to do any of these let the returned characters do
> ! that, or use a || mapping instead.
>
> You can use getchar(), it consumes typeahead if there is any. E.g., if you
> have these mappings: >
> ***
> *** 283,297 
> CTRL-L inserts the next number, CTRL-R resets the count. CTRL-R returns an
> empty string, so that nothing is inserted.
>
> ! Note that there are some tricks to make special keys work and escape CSI 
> bytes
> ! in the text. The |:map| command also does this, thus you must avoid that 
> it
> ! is done twice. This does not work: >
> ! :imap   ""
> ! Because the  then
> ! again for using . This does work: >
> ! :imap   "\u611B"
> ! Using 0x80 as a single byte before other text does not work, it will be 
> seen
> ! as a special key.
>
>
> 1.3 MAPPING AND MODES *:map-modes*
> --- 300,341 
> CTRL-L inserts the next number, CTRL-R resets the count. CTRL-R returns an
> empty string, so that nothing is inserted.
>
> ! Note that using 0x80 as a single byte before other text does not work, 
> it will
> ! be seen as a special key.
> ! 
> ! ** *:map-cmd*
> ! The special text  begins a "command mapping", it executes the 
> command
> ! directly without changing modes. Where you might use ":..." in the
> ! {rhs} of a mapping, you can instead use "...".
> ! Example: >
> ! noremap x echo mode(1)
> ! <
> ! This is more flexible than `:` in Visual and Operator-pending mode, 
> or
> ! `:` in Insert mode, because the commands are executed directly in 
> the
> ! current mode, instead of always going to Normal mode. Visual mode is
> ! preserved, so tricks with |gv| are not needed. Commands can be invoked
> ! directly in Command-line mode (which would otherwise require timer 
> hacks).
> ! Example of using  halfway Insert mode: >
> ! nnoremap  aText echo mode(1) Added
> ! 
> ! Unlike  mappings, there are no special restrictions on the 
> ! command: it is executed as if an (unrestricted) |autocmd| was invoked.
> ! 
> ! Note:
> ! - Because  avoids mode-changes it does not trigger |CmdlineEnter| 
> and
> ! |CmdlineLeave| events, because no user interaction is expected.
> ! - For the same reason, |keycodes| like  

Fuzzy scoring of beginning of line vs length

[Maxim Kim]

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 personally would expect that 'hello world with a longer line' would be 
scored higher.

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f1171f00-c7de-4df1-be7a-2defe7919261n%40googlegroups.com.

Re: Fuzzy matching scoring of / against _

[Maxim Kim]

>
>
> 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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f5b5201e-9820-4694-b63a-602864b3afe0n%40googlegroups.com.

Fuzzy matching scoring of / against _

[Maxim Kim]

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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/a016317f-d68b-4491-bec4-0c0ff3897797n%40googlegroups.com.

Re: Fuzzy matching for command-line completion

[Maxim Kim]

>
> 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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/6494544c-286d-46b7-b5dd-1b2ff593c216n%40googlegroups.com.

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

[Maxim Kim]

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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/55cf0fb2-83a7-4543-9be5-7133520f2b3dn%40googlegroups.com.

Re: matchfuzzy scoring

[Maxim Kim]

пятница, 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 sense: 
>
>
Another example: https://i.imgur.com/TyN1FEv.png

let g:tdata = ['autoload/select.vim','autoload/vital/WindowSelector']
echo g:tdata->matchfuzzy('autoselect')


-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/2b59c6cb-1035-4ea6-ac4c-3780ec701d77n%40googlegroups.com.

Re: matchfuzzy scoring

[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 sense:

let g:tdata = ['hello/world','hellopworld', 'helloworld']
echo g:tdata->matchfuzzy('llwod')

current result:

['helloworld', 'hello/world', 'hellopworld']

better result would probably be

['hello/world', 'helloworld', 'hellopworld']


--
--
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 "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5fe819d1-a880-8623-ad22-68e2d33c10a4%40gmail.com.

Re: matchfuzzy scoring

[Maxim Kim]

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:
>
> 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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/8536d78a-e0fd-476b-a95d-5b2a80b31096n%40googlegroups.com.

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

[Maxim Kim]

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 been able to 
> reproduce the issue.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub 
> , or 
> unsubscribe 
> 
> .
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f5d6420c-99d3-45bd-8743-66d6a8df0d18n%40googlegroups.com.

matchfuzzy scoring

[Maxim Kim]

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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ffec138a-33f0-4d4d-9a91-f1f5408b3526n%40googlegroups.com.

Re: matchfuzzypos sort is "unstable"

[Maxim Kim]

 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 received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5f6aa94f-6627-49b2-a4fa-b756ecb965b7n%40googlegroups.com.

matchfuzzypos sort is "unstable"

[Maxim Kim]

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 --no-ignore-vcs --hidden --glob !.git` in a job
2. On out_cb handler I update the buffer with the files
3. You can see ordering of the same files is constantly changed -- I 
believe it shouldn't be like this, but not 100% sure.

So should the order or sort of the matchfuzzypos result be the same on the 
second, third etc run? The data matchfuzzypos operates on is constantly 
increasing but the output (top) is the same only sorted a bit differently.

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/aca4a79e-550b-42aa-b1e6-10ea880d1f99n%40googlegroups.com.

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

[Maxim Kim]

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 
> matchfuzypos. It is written in vimscript 8 so should work in older 
> version as well as graceful fallback if matchfuzzy doesn't exist and if 
> prop_add doesn't exist such as in neovim.
>
> https://github.com/prabirshrestha/quickpick.vim
>
> Demos for it can be found at:
>
>- golang lsp workspace symbols with vim-lsp and quickpick.vim 
> golang lsp server is a bit slow so 
>you can see the busy spinner indicator 
>- rust lsp workspace symbols search with quickpick.vim 
>. same as above but is fast so you 
>might not see the spinner. 
>- quickpick.vim colorscheme chooser . 
>live changes of colorscheme as you select different items 
>
> Sources used:
>
>- https://github.com/prabirshrestha/quickpick-colorschemes.vim 
>- https://github.com/prabirshrestha/quickpick-lsp.vim 
>
> quickpick is a generic picker ui so can be used as a replacement for 
> ctrlp. quickpick-colorscheme uses as example of matchfuzzy with list of 
> strings while quickpick-lsp uses matchfuzzy with list of dict.
>
> Here is the image for quickpick-lsp that uses list of dict as well as 
> highlights with matchfuzzypos.
>
> [image: image] 
> 
>
> Currently it uses two buffer/windows. Blocked on 
> https://groups.google.com/g/vim_dev/c/42DjcXhuVAE/m/8yzxkBysAQAJ in order 
> to use popups as I don't want to use fake cursors to mock the input.
>
> —
> You are receiving this because you commented.
>
>
> Reply to this email directly, view it on GitHub 
> , or 
> unsubscribe 
> 
> .
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/21af371b-7fcb-43da-beb6-4a5ae8c46613n%40googlegroups.com.

Unnecessary "syntax reset"

[Maxim Kim]

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 still necessary? ":hi clear" already achieves this as far as
I can tell.

":hi clear" causes syncolor.vim to be sourced, which, if syntax is on,
follows this path (condition true):

|if !exists("syntax_cmd") || syntax_cmd == "on" |

This causes the standard syntax links to be defined with "hi link"
rather than the "hi! link" of "syn reset", but since all groups have
already had their colours cleared, this has the same effect.

E.g.

|hi Function ctermfg=1 hi! link Function Error hi clear |

"hi clear" removes the colour and resets the link to Identifier
(tested with Vim 8.2.869).

It looks like delek is the only standard colorscheme that doesn't do an
explicit "syn reset". The others cause syncolor.vim to be sourced twice.


--
--
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 "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/7330a914-9146-c07c-fe80-412d626b046f%40gmail.com.

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

[Maxim Kim]

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 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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/4e4d61d4-69a7-43ba-ad65-bcde6d436964n%40googlegroups.com.

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

[Maxim Kim]

среда, 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
> > > colorscheme may choose to give htmlTagName specific colours. This sort
> > > of thing happens frequently.
> > >
> > > If you then switch from one of these fancy colorschemes to one that 
> uses
> > > only the standard groups, htmlTagName won't be highlighted with
> > > Statement colours as you might expect, because the link has gone. It
> > > looks like the second colorscheme is broken.
> > >
> > > The idea was that if default links as well as default colours are
> > > restored on ":hi clear", then colorschemes will be working with a more
> > > consistent initial state, and produce the colours that the user expects
> > > to see.
> >
> > Can you make a new pull request, so we can see the difference with the
> > already included solution? The test would also need updating.
>
>
the patch:

>From 25796fd833e3d39418b7de3b58f1a5252347332d Mon Sep 17 00:00:00 2001
From: Maxim Kim 
Date: Wed, 16 Sep 2020 16:35:11 +0300
Subject: [PATCH] feat: save and restore default links

This approach is from Antony Scriven @adscriven:

* default hi-links are saved on `hi def`
* and restored in `hi clear`

Having this user doesn't have to do neither `syntax on` nor `syntax
enable` to be able to apply default links on a cleared highlight groups.

Thus there will be no need to update old colorschemes to make it work.
---
runtime/doc/syntax.txt | 3 ++-
src/highlight.c | 9 +++--
src/testdir/test_highlight.vim | 19 +--
3 files changed, 14 insertions(+), 17 deletions(-)

diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 9c5656719..f7de54a55 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -4808,7 +4808,8 @@ in their own color.
:hi[ghlight] clear Reset all highlighting to the defaults. Removes all
highlighting for groups added by the user!
Uses the current value of 'background' to decide which
- default colors to use.
+ default colors to use. Default highlight links are
+ restored. |:hi-link|

:hi[ghlight] clear {group-name}
:hi[ghlight] {group-name} NONE
diff --git a/src/highlight.c b/src/highlight.c
index fe22da0f8..7e325afde 100644
--- a/src/highlight.c
+++ b/src/highlight.c
@@ -73,6 +73,7 @@ typedef struct
char_u *sg_gui_sp_name;// GUI special color name
#endif
int sg_link; // link to this highlight group ID
+ int sg_deflink; // default link; restored in highlight_clear()
int sg_set; // combination of SG_* flags
#ifdef FEAT_EVAL
sctx_T sg_script_ctx; // script in which the group was last set
@@ -739,6 +740,9 @@ do_highlight(
else
to_id = syn_check_group(to_start, (int)(to_end - to_start));

+ if (dodefault && (forceit || HL_TABLE()[from_id - 1].sg_deflink == 0))
+ HL_TABLE()[from_id - 1].sg_deflink = to_id;
+
if (from_id > 0 && (!init || HL_TABLE()[from_id - 1].sg_set == 0))
{
/*
@@ -1683,6 +1686,8 @@ highlight_clear(int idx)
HL_TABLE()[idx].sg_gui_attr = 0;
#endif
#ifdef FEAT_EVAL
+ // Restore default link
+ HL_TABLE()[idx].sg_link = HL_TABLE()[idx].sg_deflink;
// Clear the script ID only when there is no link, since that is not
// cleared.
if (HL_TABLE()[idx].sg_link == 0)
diff --git a/src/testdir/test_highlight.vim b/src/testdir/test_highlight.vim
index b8fdf17a8..be96efe79 100644
--- a/src/testdir/test_highlight.vim
+++ b/src/testdir/test_highlight.vim
@@ -796,14 +796,12 @@ func Test_highlight_term_attr()
hi clear
endfunc

-" Test default highlighting is restored
-func Test_highlight_restore_defaults()
+" Test default highlighting links are restored
+func Test_highlight_restore_default_links()

- hi! link TestLink Identifier
- hi! TestHi ctermbg=red
+ hi def link TestLink Identifier

let hlTestLinkPre = HighlightArgs('TestLink')
- let hlTestHiPre = HighlightArgs('TestHi')

" Test colorscheme
hi clear
@@ -811,21 +809,14 @@ func Test_highlight_restore_defaults()
syntax reset
endif
let g:colors_name = 'test'
- hi! link TestLink ErrorMsg
- hi! TestHi ctermbg=green
+ hi link TestLink ErrorMsg

- " Restore default highlighting
+ " Default links should be restored
colorscheme default
- syntax on
- " 'default' should work no matter if highlight group was cleared
- hi def link TestLink Identifier
- hi def TestHi ctermbg=red

let hlTestLinkPost = HighlightArgs('TestLink')
- let hlTestHiPost = HighlightArgs('TestHi')

call assert_equal(hlTestLinkPre, hlTestLinkPost)
- call assert_equal(hlTestHiPre, hlTestHiPost)
hi clear
endfunc

-- 
2.20.1



-- 
-- 
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, vi

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

[Maxim Kim]

среда, 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 only mentioning this alternative because it doesn't 
>> require that syntax is reloaded. This seems to be welcome behaviour but 
>> I can't decide whether this is an intrusive change or not. --Antony 
>>
>
> It actually doesn't work without syntax on or syntax enable for me.
>
> Could you double check on your side with the example given in the issue 
> description?
>

I was wrong, indeed, with your patch it works better, no need to syntax on.

Let me push your variant for Bram to decide.

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5f562c0f-a32e-47f2-a8b5-3be0eb32035an%40googlegroups.com.

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

[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 only mentioning this alternative because it doesn't 
> require that syntax is reloaded. This seems to be welcome behaviour but 
> I can't decide whether this is an intrusive change or not. --Antony 
>

It actually doesn't work without syntax on or syntax enable for me.

Could you double check on your side with the example given in the issue 
description?

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/f82ca98b-7d64-40ca-871b-94a5a51c7f69n%40googlegroups.com.

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

[Maxim Kim]

вторник, 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, view it on GitHub 
> , or 
> unsubscribe 
> 
> .
>

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5162f6e3-2ef4-402d-9be5-a306f8ec2895n%40googlegroups.com.

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

[Maxim Kim]

среда, 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 highlighting issues since trying it out (altering links
>> and then changing colorschemes), but I'm not a heavy user of syntax
>> highlighting and I'm not sure what the implications would be.
>>
>> --Antony
>>
>
Yes, result is the same and it also passes the test I have added. 

I think that proper check for cleared in  'hl_has_settings' is simpler 
though.

-- 
-- 
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 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/a2c26600-b1e1-4762-989e-bb3e07b3d39en%40googlegroups.com.

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

[Maxim Kim]

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 matched chars, 
like fzf, ctrlp, vim-clap or leaderf plugins do:


https://i.imgur.com/FogkBBH.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 subscribed to the Google Groups "vim_dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/47bacbaa-66a6-ba94-2338-0b88919e2de8%40gmail.com.

menu.vim bug

[Maxim Kim]

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 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

Fwd: VisualBasic 'elseif' indent error

[Maxim Kim]

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
To: vim_dev


Hi,

I have just found thatvbindentation has error:

if isBlablabla() then
    blablabla
    elseif isTada() then
        Tada
    end if

It should be:

if isBlablabla() then
    blablabla
elseif isTada() then
    Tada
end if

The fix is fairly easy. In theindent/vb.vim change line 66 from
    elseif this_line =~? '^\s*\\(end\|else\|until\|loop\|next\|wend\)
\'
to
    elseif this_line =~? '^\s*\\(end\|else\|elseif\|until\|loop\|next
\|wend\)\'

I am not sure of the way fixes of that kind are included into vim
runtime.

Maxim.

-- 
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: Fwd: VisualBasic 'elseif' indent error

[Maxim Kim]

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: 20 авг 2009, 10:58
 Subject: VisualBasic 'elseif' indent error
 To: vim_dev

 Hi,

 I have just found thatvbindentation has error:

 if isBlablabla() then
     blablabla
     elseif isTada() then
         Tada
     end if

 It should be:

 if isBlablabla() then
     blablabla
 elseif isTada() then
     Tada
 end if

There is also one minor issue with 'if' block -- if there are spaces
after 'then' keyword then indentation is wrong.
The problem lies in line 50:
if previous_line =~? '^\s*\\(begin\|\%(\%(private\|public\|friend
\)\s\+\)\=\%(function\|sub\|property\)\|select\|case\|default\|if\.\
{-}\then\\s*$\|else\|elseif\|do\|for\|while\|enum\|with\)\'

See '\|if\.\{-}\then\\s*$' part -- looks like it should handle
spaces at the end of 'then' but it is not.
I would remove '\.\{-}\then\\s*$' as 'elseif' doesn't have that.
(Both of them should have the same indent behaviour)

updated line 50:
if previous_line =~? '^\s*\\%(begin\|\%(\%(private\|public\|friend
\)\s\+\)\=\%(function\|sub\|property\)\|select\|case\|default\|if\|else
\|elseif\|do\|for\|while\|enum\|with\)\'

Maxim.

-- 
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: vim73a help -- bug of feature?

[Maxim Kim]

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.  When your cursor moves off of the line, the ||
 are concealed, which completely removes them from display.

 See :help new-conceal for more information.

But as I pointed in PS block there is no 'shrink and widen' behaviour
if I run vim with -u NORC.
And I do not move cursor out of that line -- I do move it left and
right.

-- 
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: vim73a help -- bug of feature?

[Maxim Kim]

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 the highlighting
 engine.

3. :syntax on



 Moving the cursor back and forth over the concealed text to cause it
 to appear is the original behavior of the conceal feature in the
 development branch of Vim, but it has been changed to having the
 cursor anywhere within the line causes all concealed text to be shown
 within that line.  This was to solve a problem with another new
 feature.

It would look alright if concealed characters become visible as soon
as I am on consealed text.
But in my example they do not appear when cursor is on strchars(). But
when I move cursor left to 'and' word which is not concealed.

-- 
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: vim73a help -- bug of feature?

[Maxim Kim]

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()
 5. navigate to strchars() function
 6. press h several times to reach strwidth() function and l to go
 back.

 The line widens and shrinks.

 PS
 If I run gvim with -u NORC and do all above with set nocp first --
 everything is ok.

Here are 2 screenshots:


http://picasaweb.google.com/lh/photo/g7T_toVidI7hbIYJtLl4Uw?feat=directlink

after I do one right keypress
http://picasaweb.google.com/lh/photo/9mzV-plHx54rcCRoRp0xdA?feat=directlink

-- 
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: vim73a help -- bug of feature?

[Maxim Kim]

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
  2. :filetype plugin on
  3. :syntax on
  4. :h strdisplaywidth()
  5. navigate to strchars() function
  6. press h several times to reach strwidth() function and l to go
  back.

  The line widens and shrinks.

  PS
  If I run gvim with -u NORC and do all above with set nocp first --
  everything is ok.

 Here are 2 screenshots:

 http://picasaweb.google.com/lh/photo/g7T_toVidI7hbIYJtLl4Uw?feat=dire...

 after I do one right keypress

:s/right/left

-- 
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: vim73a help -- bug of feature?

[Maxim Kim]

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 strdisplaywidth()
 5. navigate to strchars() function
 6. press h several times to reach strwidth() function and l to go
 back.

 The line widens and shrinks.

 PS
 If I run gvim with -u NORC and do all above with set nocp first --
 everything is ok.

 I can't reproduce it.  There were a few recent changes in this area. Do
 you still see the problem if you build from the current Mercurial
 version?

I have just compiled vim -- there is no such problem in the current
Mercurial version.

Maxim.

-- 
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

vim73a help -- bug of feature?

[Maxim Kim]

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 to reach strwidth() function and l to go
back.

The line widens and shrinks.

PS
If I run gvim with -u NORC and do all above with set nocp first --
everything is ok.

-- 
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: flexwiki ftplugin causing problems ('bomb')

[Maxim Kim]

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 in extra characters at the front of my utf8 files -- this
 has caused problems with other software which reads those files (I
 never have 'bomb' set).

 Scanning the ftplugins, it seems 'flexwiki' is the only one which sets
 'bomb'.  Is it an ok thing for it to do?  Also, why is flexwiki the
 handler, when wikipedia is probably the most widely used wiki?  But
 that's a quibble.

I had the very same problem with it.

Check 
http://groups.google.com/group/vim_use/browse_thread/thread/23f33912b2c0d292/90ba2a0b3a80a1fc?lnk=gstq=flexwiki#90ba2a0b3a80a1fc

In my plugin I just do

augroup filetypedetect
   clear FlexWiki's stuff
  au! * *.wiki
augroup end

-- 
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: flexwiki ftplugin causing problems ('bomb')

[Maxim Kim]

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 a script
 something/ftplugin/flexwiki.vim with something being an entry which
 comes after $VIMRUNTIME in the 'runtimepath' option (i.e.
 $VIM/vimfiles/after on any platform, or also $HOME/vimfiles/after on
 Windows, $HOME/.vim/after on Unix), with the following contents (create
 the file and/or directories if they don't yet exist; append to the file
 if it does exist):

         setlocal nobomb
In my case the problem with this solution was in changed state of the
buffer after switching bomb/nobomb.

-- 
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

www.vim.org: Change my plugin type

[Maxim Kim]

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 http://www.vim.org/maillist.php