Thursday, August 13, 2026

Re: Vim installer for Windows is 3 weeks old

Looks like something wrong with Windows build again. It is few days old, but in vim/vim/ I see new commits.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/7d09d304-1446-4b74-b2be-377c86385457n%40googlegroups.com.

Tuesday, August 11, 2026

Algol 68 - was AW: AW: Synchronize syntax highlighting

I'll answer your question but suggest to continue this topic in Usenet (comp.lang.misc) if you're interested in more details. Von: vim_use@googlegroups.com <vim_use@googlegroups.com> im Auftrag von arocker@Vex.Net <arocker@Vex.Net> Gesendet: Dienstag, 11. August 2026 21:07 An: vim_use@googlegroups.com > I'm curious to know why anyone is editing Algol 68 code in 2026. Simply; I'm *editing* it because I am _writing programs_ in Algol 68. The question was probably meant as why one would write programs in an old (legacy) language like Algol 68. - The answer is not simple. In the past 50 years I've programmed in a lot of languages, Algol 68 was amongst the cleanest, yet very powerful, and safe! It was not my first and certainly not my last language, but other languages with all these properties were long rare, even non-existing. When I found a high-quality Algol 68 interpreter lately I was glad to refresh my old programming skills in a language that was by far more enjoyable to program in than, say, in "C" (or similar), or in one of the many more languages (that are sometimes even hyped, for reasons beyond me). > Are there even functioning compilers available any more? The "Genie" compiler "a68g" is the one that I found, and used since then. It's of very high quality (as I said), and effectively a "complete" implementation of that very large language. In addition it has quite some powerful extensions (for math, plotting, databases, functions and methods we know Unix systems, etc.). I think it was developed in the 1990's and made public (with source code) for free use in the late 1990's (IIRC). A 700-pages PDF documentation comes with it. It is still maintained by its original author, Marcel van der Veer, and releases are still published. In addition there's a much more recent GNU project to release an Algol 68 compiler, "ga68", as part of the GNU Compiler Collection. It's probably too fresh - maybe even incomplete, can't tell - to say anything about it. But its recent development is an indication that there seems to be still some interest in the Algol 68 language. The Vim syntax file is a small contribution to support that interest. Janis -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/AS2SPRMB0054D02866ECB10097A6AB8EF3DD2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

New privacy settings for Search services and Google Play

Urgent: Sign in to your Google Account if you want to keep it

Sign in to your Google Account
rebbe.malachi.mailfeed@blogger.com

Your Google Account has not been used within a 2-year period.

If you want to keep your Google Account, sign in to your Google Account before September 15, 2026.

To protect user privacy and account data, Google will delete Google Accounts that are not used. Learn more

Learn how to download your Google data.

You received this email to let you know about important changes to your Google Account and services.

Re: AW: Synchronize syntax highlighting

See:




W dniu wt., 11 sie 2026 o 21:07 <arocker@vex.net> napisał(a):

I'm curious to know why anyone is editing Algol 68 code in 2026. Are there
even functioning compilers available any more?

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/083783b13ffab75485ad6631a4033ad1.squirrel%40webmail.vybenetworks.com.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAEHV%2Btbs0hxnhNBoziqiv7HzuUqcHpvBWGPT4RUErANk8tJKTQ%40mail.gmail.com.

Re: AW: Synchronize syntax highlighting

I'm curious to know why anyone is editing Algol 68 code in 2026. Are there even functioning compilers available any more? -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/083783b13ffab75485ad6631a4033ad1.squirrel%40webmail.vybenetworks.com.

AW: Synchronize syntax highlighting

Hi Christian! > > I've tried various suggestions (minlines, synmaxcol, etc.), > > read the manual for information about possible tweaks > > searched the web, ... - to no avail! > > > > Trying with various numbers in configs like > > set smc=9000 > > syntax sync minlines=1000 maxlines=1000 > > > > I'm still getting no sync in a (even non-demanding) test case: > > opening a 476 line file, max. columns 84 => highlighting okay, > > searching for a text that appears in line 438 => NO SYNC here! > > (After scrolling 3 pages up the sync was okay again.) > > > > More testing... > > Opened a 80x25 terminal window. > > Same testcase as above. => highlighting okay!!! > > Resized the terminal window to 120x50. > > Opened the file again, same testcase => NO SYNC ! > > Resized the terminal window back to 80x25. > > Opened the file again, same testcase => highlighting okay > > > > This is strange!!! > > Highlighting depends on the terminal size, not on the actual text! > > does > :syn sync fromstart > > help? I've meanwhile extended my file and the effect wasn't seen then any more, but with an old version this trick indeed re-established the sync. - Thanks! > > This depends on the current syntax script and file being used, but it is > worth a try when this happens. I suppose this happens with algol68 > files? This has a hard-coded limit of 500 lines. While I had observed this effect in the past also with other languages or text data in this case it's indeed an Algol 68 source. After your hint I've meanwhile also noticed the hard-coded limit. Do these limits make sense? (They appear to be quite small anyway!) Would it hurt to remove those limits? (Or define higher values?) The parameters are defined as: syn sync minlines=250 maxlines=500 which I think means a context of +/- 250 lines considered for syncing? - That's not much given that the sync is obviously not done on language-specific syntax sync points. - I've now changed my local ~/.vim/syntax/algol68.vim and adjusted these values to 1000 each[*]; this solved the issue - at least locally, and for this specific source; let's see how far I get with those values. [*] Is that sensible or should 'maxvalue' be twice as large to to obtain the +/- 1000 context range? (The parameter names are a bit confusing to me; a "sync-lines-before" and "sync-lines-after" semantics might be clearer.) Though I'm wondering that a user-specific setting (in .vimrc) cannot override the system setting here. (But that may be an effect of this syntax file is in my system also locally below ~/.vim/syntax, and therefore it takes precedence?) And the dependency of the effect on the window size is still a mystery to me! (To me that smells like a bug or design problem in this specific case.) > It is not generally recommended to use syn sync fromstart in syntax > script, because it comes with a performance penalty, but in cases when > you notice syntax being off, it is worth a try. Yes, that's certainly useful and good to know! With Vim I've never had any performance problem editing program's text. (Only on *very* large textual data there's regularly a performance issue.) I'd think an increase of (hard-coded) sync values for program texts would generally not hurt. (Or are people really writing _monolithic code_ of tens of thousands line of code in one file without structuring it in files?) There's a couple questions raised in this post; can you tell me whether you think some of these needs attention to be changed? Thanks again! Regards, Janis -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/AS2SPRMB0054C3CAB8CDA9B45BF0E344F3DD2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

Monday, August 10, 2026

Re: Synchronize syntax highlighting

On Mo, 10 Aug 2026, Janis Papanagnou wrote: > I've tried various suggestions (minlines, synmaxcol, etc.), > read the manual for information about possible tweaks > searched the web, ... - to no avail! > > Trying with various numbers in configs like > set smc=9000 > syntax sync minlines=1000 maxlines=1000 > > I'm still getting no sync in a (even non-demanding) test case: > opening a 476 line file, max. columns 84 => highlighting okay, > searching for a text that appears in line 438 => NO SYNC here! > (After scrolling 3 pages up the sync was okay again.) > > More testing... > Opened a 80x25 terminal window. > Same testcase as above. => highlighting okay!!! > Resized the terminal window to 120x50. > Opened the file again, same testcase => NO SYNC ! > Resized the terminal window back to 80x25. > Opened the file again, same testcase => highlighting okay > > This is strange!!! > Highlighting depends on the terminal size, not on the actual text! does :syn sync fromstart help? This depends on the current syntax script and file being used, but it is worth a try when this happens. I suppose this happens with algol68 files? This has a hard-coded limit of 500 lines. It is not generally recommended to use syn sync fromstart in syntax script, because it comes with a performance penalty, but in cases when you notice syntax being off, it is worth a try. Best, Christian -- -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/anoekP02s6s1AliB%40256bit.org.

AW: Synchronize syntax highlighting

I've tried various suggestions (minlines, synmaxcol, etc.), read the manual for information about possible tweaks searched the web, ... - to no avail! Trying with various numbers in configs like set smc=9000 syntax sync minlines=1000 maxlines=1000 I'm still getting no sync in a (even non-demanding) test case: opening a 476 line file, max. columns 84 => highlighting okay, searching for a text that appears in line 438 => NO SYNC here! (After scrolling 3 pages up the sync was okay again.) More testing... Opened a 80x25 terminal window. Same testcase as above. => highlighting okay!!! Resized the terminal window to 120x50. Opened the file again, same testcase => NO SYNC ! Resized the terminal window back to 80x25. Opened the file again, same testcase => highlighting okay This is strange!!! Highlighting depends on the terminal size, not on the actual text! $ vi --version VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Jul 13 2026 17:17:48) Included patches: 1-16, 647, 678, 697 Modified by team+vim@tracker.debian.org If you have some more config options to try out I'd be keen to hear. Thanks! Janis ________________________________________ Von: vim_use@googlegroups.com <vim_use@googlegroups.com> im Auftrag von Christian Brabandt <cblists@256bit.org> Gesendet: Sonntag, 9. August 2026 17:17 An: vim_use@googlegroups.com Betreff: Re: Synchronize syntax highlighting On So, 09 Aug 2026, Janis Papanagnou wrote: > Sometimes, for some files, the sync of syntax-highlighting fails > (i.e. all text gets uniformly colored). > > In the past, to tackle that, I've adjusted some vim parameter, > increased a value from something like 3000 to 10000, or so. > On my new system that setting got lost, unfortunately, and I > cannot find it. > > Can someone point me to the name of that parameter, please, > so that I can re-establish a better highlighting-sync behavior. :h 'synmaxcol' Best, Christian -- QOTD: "I drive my car quietly, for it goes without saying." -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/aniZ/O7l6XfNFoal%40256bit.org. -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/AS2SPRMB00541D5B0B40A1B43A60A99CF3DE2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

Sunday, August 9, 2026

Re: Synchronize syntax highlighting

On So, 09 Aug 2026, Janis Papanagnou wrote: > Sometimes, for some files, the sync of syntax-highlighting fails > (i.e. all text gets uniformly colored). > > In the past, to tackle that, I've adjusted some vim parameter, > increased a value from something like 3000 to 10000, or so. > On my new system that setting got lost, unfortunately, and I > cannot find it. > > Can someone point me to the name of that parameter, please, > so that I can re-establish a better highlighting-sync behavior. :h 'synmaxcol' Best, Christian -- QOTD: "I drive my car quietly, for it goes without saying." -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/aniZ/O7l6XfNFoal%40256bit.org.

Re: Synchronize syntax highlighting

On 2026-08-09 10:48, Janis Papanagnou wrote: > Sometimes, for some files, the sync of syntax-highlighting fails > (i.e. all text gets uniformly colored). > > In the past, to tackle that, I've adjusted some vim parameter, > increased a value from something like 3000 to 10000, or so. > On my new system that setting got lost, unfortunately, and I > cannot find it. I think you're looking for the minlines= and maxlines= values described here: :help syn-sync-maxlines :help syn-sync-third -tim -- -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/aniHL3avVmnNL3nP%40thechases.com.

Synchronize syntax highlighting

Sometimes, for some files, the sync of syntax-highlighting fails (i.e. all text gets uniformly colored). In the past, to tackle that, I've adjusted some vim parameter, increased a value from something like 3000 to 10000, or so. On my new system that setting got lost, unfortunately, and I cannot find it. Can someone point me to the name of that parameter, please, so that I can re-establish a better highlighting-sync behavior. Thanks! Janis -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/AS2SPRMB0054888E7352B5254DA6384EF3DF2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

AW: Synchronize syntax highlighting

Sorry, John, somehow my mail-client sent my email to you instead of the mailing list. ________________________________________ Von: Janis Papanagnou <janis_papanagnou@hotmail.com> Gesendet: Sonntag, 9. August 2026 12:48 An: 'John Jackson' via vim_use Betreff: Synchronize syntax highlighting Sometimes, for some files, the sync of syntax-highlighting fails (i.e. all text gets uniformly colored). In the past, to tackle that, I've adjusted some vim parameter, increased a value from something like 3000 to 10000, or so. On my new system that setting got lost, unfortunately, and I cannot find it. Can someone point me to the name of that parameter, please, so that I can re-establish a better highlighting-sync behavior. Thanks! Janis -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/AS2SPRMB0054564FC119CABBF1BAC3EFF3DF2%40AS2SPRMB0054.eurprd05.prod.outlook.com.

Friday, August 7, 2026

Re: Re: Vim on Debian Mint Linux

 

------ Original Message ------
From: eajmarceau@gmail.com
To: vim_use@googlegroups.com
Sent: Friday, August 7th 2026, 18:15
Subject: Re: Vim on Debian Mint Linux
 

    "Does it do PDFs as on Windows?"

If you mean, edit the PDF as a text file, leaving the encoded elements as is, the response is yes.


 

For any Debian-based system, the method to install is to open a shell in a terminal and enter the command,

  • sudo apt-get install vim-gtk3 (vim-gui-common)

Or look for the vim-gtk3 package from within Synaptic, and install that way.


 

Eric


 

On 2026-08-07 11:53, 'c.willis111 ' via vim_use wrote:
 

Hi

 

how do I install vim on debian mint Linux?

 

Does it do PDFs as on Windows?

 

regards - Chris

 

 

-- 
-- 
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unsubscribe@googlegroups.com" class="moz-txt-link-freetext">vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/344fdc93.1e04.19fdcede606.Webtop.1%40btinternet.com.
 

 

-- 
-- 
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unsubscribe@googlegroups.com">vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/22082605-9693-43f2-a059-18f1ea3a408f%40gmail.com.
Hi

 

thanks both Eric and Marco

 

Eric, in Windows Vim on a PDF preprocesses the file using PdfTk,, and restores the compression afterwards, likewise. This shows the content streams as clear text. I suspect that PdfTk doesn't work on Linux?

 

The post processing sorts out the length attributes that the compression and edits have changed.

 

regards - Chris

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/79d0729e.72fff.19fde4ec6a2.Webtop.227%40btinternet.com.

Re: Vim on Debian Mint Linux

Am 07.08.26 um 17:53 schrieb 'c.willis111 ' via vim_use: > > how do I install vim on debian mint Linux? There is Debian and there is Linux Mint Debian edition. 2 different operating systems. You can install vim via sudo apt install vim -- Gruß Marco Junk-Mail bitte an trashcan@stinkedores.dorfdsl.de -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/5a8d7d4c-a360-4ba8-bf09-128998d26a98%40dorfdsl.de.

Re: Vim on Debian Mint Linux

    "Does it do PDFs as on Windows?"

If you mean, edit the PDF as a text file, leaving the encoded elements as is, the response is yes.


For any Debian-based system, the method to install is to open a shell in a terminal and enter the command,

  • sudo apt-get install vim-gtk3 (vim-gui-common)

Or look for the vim-gtk3 package from within Synaptic, and install that way.


Eric


On 2026-08-07 11:53, 'c.willis111 ' via vim_use wrote:

Hi

 

how do I install vim on debian mint Linux?

 

Does it do PDFs as on Windows?

 

regards - Chris

 

 

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/344fdc93.1e04.19fdcede606.Webtop.1%40btinternet.com.

Vim on Debian Mint Linux

Hi

 

how do I install vim on debian mint Linux?

 

Does it do PDFs as on Windows?

 

regards - Chris

 

 

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/344fdc93.1e04.19fdcede606.Webtop.1%40btinternet.com.

Thursday, July 30, 2026

Re: Bug in popup maxwidth?

Excellent! Thank you. 

Sorry I missed your last message asking for a sample. Something came up that took all my time. 

Salman

I, too, shall something make and glory in the making.


On Thu, 30 Jul 2026, 10:05 h_east, <h.east.727@gmail.com> wrote:
Hi,

Thanks, those numbers were enough to reproduce it here.

It happens when 'wrap' is off and the popup is so close to the right
edge that the space left of it is smaller than "maxwidth".  On a 120
column screen:

    call popup_create([repeat('x', 93)],
                \ #{line: 3, col: 80, maxwidth: 50, wrap: 0, border: []})

The popup is shifted left to fit the text on the screen, and that shift
raises the width limit itself.  Patch 9.2.0247 already guarded against
this, but only for 'wrap' being on.

Fix: https://github.com/vim/vim/pull/20883

--
Best regards,
Hirohito Higashi (h_east)

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/fa0b32e3-2b25-49da-87a2-ac2a431a1dc7n%40googlegroups.com.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CANuxnEfUZCvruqajRiZWsnyUYYJKnCNFz%3D%2BbmkarXNQC9%2B6vZA%40mail.gmail.com.

Re: Bug in popup maxwidth?

Hi,

Thanks, those numbers were enough to reproduce it here.

It happens when 'wrap' is off and the popup is so close to the right
edge that the space left of it is smaller than "maxwidth".  On a 120
column screen:

    call popup_create([repeat('x', 93)],
                \ #{line: 3, col: 80, maxwidth: 50, wrap: 0, border: []})

The popup is shifted left to fit the text on the screen, and that shift
raises the width limit itself.  Patch 9.2.0247 already guarded against
this, but only for 'wrap' being on.

Fix: https://github.com/vim/vim/pull/20883

--
Best regards,
Hirohito Higashi (h_east)

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/fa0b32e3-2b25-49da-87a2-ac2a431a1dc7n%40googlegroups.com.

Wednesday, July 29, 2026

Re: Bug in popup with opacity?

Confirming that this worked. Thank you!

 
Salman

I, too, shall something make and glory in the making.


On Wed, 29 Jul 2026, 07:23 h_east, <h.east.727@gmail.com> wrote:
Hi,

Yes, this is a bug. I have fixed it and submitted a pull request.

--
Best regards,
Hirohito Higashi (h_east)

2026年5月27日水曜日 22:46:56 UTC+9 Salman Halim:
Hello,

I am on GVim 9.2, patch 541, on Windows 11.

If I set opacity in a popup to anything but 100, my font settings aren't observed. For example, my 'InfoBorder' (used for borderhighlight) is set to:

InfoBorder     xxx guibg=#6f4246 font=Consolas:h9

If the opacity is either unspecified or explicitly set to 100, the font is observed. Any actual opacity and the font is ignored and goes to the regular font used throughout.

Thank you.

--
 
Salman

I, too, shall something make and glory in the making.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/a19eb99f-2f35-4b8e-8b00-abf3d0f03465n%40googlegroups.com.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CANuxnEcb3cW8OvarDAeRXdte5ZNQOYgSOZXRD%3DgCOv6jhRXyHg%40mail.gmail.com.

Re: Bug in popup maxwidth?

Hi, 

I get all that. The problem is that popup_getoptions says that maxwidth and minwidth are both 50 and popup_getpos says core_width is 93 and width is 99. I can confirm that the popup on-screen is, indeed, very wide. 

Hmm, I can't reproduce the issue.
Could you please paste the script you actually verified?

--
Best regards,
Hirohito Higashi (h_east)

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/1012b43a-7e52-478a-a5e0-803a3b4800efn%40googlegroups.com.

Re: Bug in popup maxwidth?


On Wed, 29 Jul 2026, 09:33 h_east, <h.east.727@gmail.com> wrote:
Hi,

"maxwidth" still limits the width, what changed is how the width is
computed.  Since patch 9.2.0419 it is the longest line in the whole
buffer, not the longest displayed line, so that the width does not change
while you scroll the popup with the mouse wheel.  The completion menu
works the same way.

So a buffer with one long line now sits at "maxwidth" all the time.  The
documentation still described the old rule, which is being corrected:
https://github.com/vim/vim/pull/20870

If that is too wide, lower "maxwidth".

--
Best regards,
Hirohito Higashi (h_east)

I get all that. The problem is that popup_getoptions says that maxwidth and minwidth are both 50 and popup_getpos says core_width is 93 and width is 99. I can confirm that the popup on-screen is, indeed, very wide. 

Padding (from the options) is [1, 2, 1, 2], in case you want that, also. 

Salman 

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CANuxnEcp8C29PXosyADcVKCJ506Hmt8Jui2xOd4R1DBTMGwucQ%40mail.gmail.com.

Re: Bug in popup maxwidth?

Hi,

"maxwidth" still limits the width, what changed is how the width is
computed.  Since patch 9.2.0419 it is the longest line in the whole
buffer, not the longest displayed line, so that the width does not change
while you scroll the popup with the mouse wheel.  The completion menu
works the same way.

So a buffer with one long line now sits at "maxwidth" all the time.  The
documentation still described the old rule, which is being corrected:
https://github.com/vim/vim/pull/20870

If that is too wide, lower "maxwidth".

--
Best regards,
Hirohito Higashi (h_east)

2026年5月27日水曜日 23:25:11 UTC+9 Salman Halim:
Hello,

GVim 9.2, patch 541, Windows 11.

My popups are as wide as the widest line, ignoring the maxwidth setting. This was working fine in 9.1, patch 2125, from where I upgraded yesterday.

The maxheight works fine.

--
 
Salman

I, too, shall something make and glory in the making.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/353a95ad-1519-4b32-82a7-64d8ca8a4618n%40googlegroups.com.

Re: Bug in popup with opacity?

Hi,

Yes, this is a bug. I have fixed it and submitted a pull request.
https://github.com/vim/vim/pull/20866

--
Best regards,
Hirohito Higashi (h_east)

2026年5月27日水曜日 22:46:56 UTC+9 Salman Halim:
Hello,

I am on GVim 9.2, patch 541, on Windows 11.

If I set opacity in a popup to anything but 100, my font settings aren't observed. For example, my 'InfoBorder' (used for borderhighlight) is set to:

InfoBorder     xxx guibg=#6f4246 font=Consolas:h9

If the opacity is either unspecified or explicitly set to 100, the font is observed. Any actual opacity and the font is ignored and goes to the regular font used throughout.

Thank you.

--
 
Salman

I, too, shall something make and glory in the making.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/a19eb99f-2f35-4b8e-8b00-abf3d0f03465n%40googlegroups.com.

Re: timer_start to refresh rulerformat

Hi,

See https://github.com/vim/vim/pull/20865

--
Best regards,
Hirohito Higashi (h_east)

2026年5月26日火曜日 10:22:06 UTC+9 watael rocketmail:

HI,

I saw here :  https://vim.fandom.com/wiki/Display_date-and-time_on_status_line
and there : https://vi.stackexchange.com/questions/17875/how-to-update-the-statusline-continuously-even-if-the-window-becomes-inactive
that `timer_start` could refresh statusline.

something might have happened, because I can't get it to work.

here's the simple code I use:

```
set ruler
set rulerformat=%55(%{strftime('%H:%M:%S')}\ %5l,%-6(%c%V%)\ %P%)
call timer_start(1000, {-> execute(':let &stl=&stl')}, {'repeat': -1})
```

and here's version:

$ LC_ALL=C vim --version
VIM - Vi IMproved 9.2 (2026 Feb 14, compiled May 22 2026 18:43:08)
Included patches: 1-511
Compiled by Arch Linux
Huge version without GUI.  Features included (+) or not (-):
+acl                +file_in_path       +mouse_xterm        -tag_any_white
+arabic             +find_in_path       +multi_byte         +tcl/dyn
+autocmd            +float              +multi_lang         +termguicolors
+autochdir          +folding            -mzscheme           +terminal
-autoservername     -footer             +netbeans_intg      +terminfo
-balloon_eval       +fork()             +num64              +termresponse
+balloon_eval_term  +gettext            +packages           +textobjects
-browse             -hangul_input       +path_extra         +textprop
++builtin_terms     +iconv              +perl/dyn           +timers
+byte_offset        +insert_expand      +persistent_undo    +title
+channel            +ipv6               +popupwin           -toolbar
+cindent            +job                +postscript         +user_commands
+clientserver       +jumplist           +printer            +vartabs
-clipboard          +keymap             +profile            +vertsplit
+clipboard_provider +lambda             -python             +vim9script
+cmdline_compl      +langmap            +python3/dyn        +viminfo
+cmdline_hist       +libcall            +quickfix           +virtualedit
+cmdline_info       +linebreak          +reltime            +visual
+comments           +lispindent         +rightleft          +visualextra
+conceal            +listcmds           +ruby/dyn           +vreplace
+cryptv             +localmap           +scrollbind         -wayland
+cscope             +lua/dyn            +signs              -wayland_clipboard
+cursorbind         +menu               +smartindent        +wildignore
+cursorshape        +mksession          +socketserver       +wildmenu
+dialog_con         +modify_fname       -sodium             +windows
+diff               +mouse              -sound              +writebackup
+digraphs           -mouseshape         +spell              -X11
-dnd                +mouse_dec          +startuptime        +xattr
-ebcdic             +mouse_gpm          +statusline         -xfontset
+emacs_tags         -mouse_jsbterm      -sun_workshop       -xim
+eval               +mouse_netterm      +syntax             -xpm
+ex_extra           +mouse_sgr          +tabpanel           -xsmp
+extra_search       -mouse_sysmouse     +tag_binary         -xterm_clipboard
-farsi              +mouse_urxvt        -tag_old_static     -xterm_save
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
 3rd user vimrc file: "~/.config/vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/build/vim/src=/usr/src/debug/vim -flto=auto -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 
Linking: gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.42/core_perl/CORE -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto -L/usr/local/lib -o vim -lm -ltinfo -lnsl -lacl -lattr -lgpm -L/usr/lib -ltclstub8.6 -ldl -lz -lpthread -lm 
$

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/94444cc7-a0da-4432-911b-00a567efe0a1n%40googlegroups.com.

Wednesday, July 8, 2026

Learn more about our updated Terms of Service