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)

github.com/sponsors/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.

Learn more about our updated Terms of Service

rebbe.malachi.mailfeed@blogger.com  Every couple of years, we update our Terms of Service. We wanted to let you know ahead of time that the next update will be on July 30, 2026. These changes won’t affect the way you use our services, but they should help make it easier for you to understand what to expect from Google — and what we expect from you — as you use our services. You can review the new terms here. If you’re based in the European Economic Area (EEA) or Switzerland, we’ve also provided a summary of the key changes to the EEA version of our terms. At a glance, here’s what this update means for you: In general: We added a section to help you better understand why our services may access the internet when not actively engaged, to encourage you to check your Internet service plan and your device and network settings, as each of those may affect your costs. We updated and clarified our Settling disputes, governing law, and courts section. We make it clearer how various sections in our terms relate to each other. If you’re based in the EEA: In addition to the changes in the In general section, we updated various sections to reflect the latest EEA laws and regulations that apply to our services, including: Google’s obligation to make legally-required updates to our digital content, services, and goods. A new, online “withdrawal button” in the EEA instructions on withdrawal section. We also removed the Handling requests for your data section, because we’re centralizing our data disclosure language on our main data disclosure policy page. If you’re based outside the EEA:  In addition to the changes in the In general section, we added new disclosures and disclaimers, including ones about AI outputs. If you’re based in India, we also added new reporting language about our obligations if you violate applicable law. If you’re a parent or guardian, and you allow your child to use the services, please review the updates to our terms with your child and help them decide whether they need to make any changes to their account. Please remember that these terms apply to you and you’re responsible for your child’s activity on the services. If you don’t agree to the new terms, you should remove your content and stop using the services. You can also end your relationship with us at any time, without penalty, by closing your Google Account. Thank you for using Google services!  © 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043  You have received this email to update you about important changes to Google’s Terms of Service.