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.

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.

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.

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

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

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.

Re: Segfault in vim-obsession

In the recent vim, session files were changed to be able to process vim9script related mappings.

Might be related or not.

On Thursday, June 11, 2026 at 6:15:44 PM UTC+10 Manas wrote:

Hi folks, I probably should have posted this on
[vim-obsession](https://github.com/tpope/vim-obsession) issue page, but I cannot
reproduce it fully. I wanted to know if someone has seen this too.

I have seen vim crash with a segfault twice now, after I installed and started
using vim-obsession. Their issue page is empty about any segfaults. But I am
quite positive that segfault crash only started occuring after vim-obsession
managed my `Session.vim`. Previously, I was manually saving `Session.vim` and
never saw any segfault.

One more observation may involve tmux. I recall moving across tmux panes and
sessions, and when I came back to the vim pane, I saw it crashed.

Unfortunately, I don't know how to reproduce it.

Thanks
--
Manas

--
--
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/ed651fa0-c8e2-4430-b9b3-ff65aa8fa0dbn%40googlegroups.com.

Re: Segfault in vim-obsession

Hi folks, I probably should have posted this on [vim-obsession](https://github.com/tpope/vim-obsession) issue page, but I cannot reproduce it fully. I wanted to know if someone has seen this too. I have seen vim crash with a segfault twice now, after I installed and started using vim-obsession. Their issue page is empty about any segfaults. But I am quite positive that segfault crash only started occuring after vim-obsession managed my `Session.vim`. Previously, I was manually saving `Session.vim` and never saw any segfault. One more observation may involve tmux. I recall moving across tmux panes and sessions, and when I came back to the vim pane, I saw it crashed. Unfortunately, I don't know how to reproduce it. Thanks -- Manas -- -- 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/aiptfoQt8ano8tsd%40fedora.

Re: Loading filetype scripts when editing a file on VimEnter

Thank you 🙏 

On Tuesday, June 2, 2026 at 3:18:27 PM UTC+1 John Jackson wrote:

On 6/2/2026 9:22 AM, 黄岚军 wrote:
> Try adding `:filetype detect` to the line after `edit`.

This fixed it. Thank you!

John

--
--
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/3e9998b0-1391-4284-b4c0-9df1cd756cd5n%40googlegroups.com.

Re: Loading filetype scripts when editing a file on VimEnter

On 6/2/2026 9:22 AM, 黄岚军 wrote: > Try adding `:filetype detect` to the line after `edit`. This fixed it. Thank you! John -- -- 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/6cc9b491-8afd-41da-8fa1-6ada5100dfc5%40johnridesa.bike.

Re: Loading filetype scripts when editing a file on VimEnter

Try adding `:filetype detect` to the line after `edit`.

在2026年6月2日星期二 UTC+8 00:23:18<John Jackson> 写道：

Hello Vim users,

I want an installation of gVim to auto-edit a "notes" file when opened
with no arguments. I'm using this script in my Vim configuration:

vim9script
def LoadNotes()
  if argc() == 0
    edit path\to\notes.md
    echomsg "Auto-opened notes.md."
  endif
enddef
autocmd VimEnter * ++once LoadNotes()

This edits the file as expected. However, Vim does not apply syntax
highlighting to the file. When I run :scriptnames, none of the Markdown
ftplugin or syntax scripts are listed. (Although many other ftplugin
script names are listed.)

If I manually run :edit after startup, then the syntax highlighting
works, and Vim's ftplugin\markdown.vim and its associated scripts are
now all listed in :scriptnames.

Is there a way to guarantee that Vim will load all of the needed
filetype scripts during the VimEnter event? Or is there a more
appropriate event for this use case? I'm happy to provide more details
if they're helpful.

:version
VIM - Vi IMproved 9.2 (2026 Feb 14, compiled Feb 14 2026 12:17:29)
MS-Windows 64-bit GUI/console version with OLE support

John

--
--
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/3745a3e2-f3c3-4505-ad29-a78c004a3f8fn%40googlegroups.com.

Loading filetype scripts when editing a file on VimEnter

Hello Vim users, I want an installation of gVim to auto-edit a "notes" file when opened with no arguments. I'm using this script in my Vim configuration: vim9script def LoadNotes()   if argc() == 0     edit path\to\notes.md     echomsg "Auto-opened notes.md."   endif enddef autocmd VimEnter * ++once LoadNotes() This edits the file as expected. However, Vim does not apply syntax highlighting to the file. When I run :scriptnames, none of the Markdown ftplugin or syntax scripts are listed. (Although many other ftplugin script names are listed.) If I manually run :edit after startup, then the syntax highlighting works, and Vim's ftplugin\markdown.vim and its associated scripts are now all listed in :scriptnames. Is there a way to guarantee that Vim will load all of the needed filetype scripts during the VimEnter event? Or is there a more appropriate event for this use case? I'm happy to provide more details if they're helpful. :version VIM - Vi IMproved 9.2 (2026 Feb 14, compiled Feb 14 2026 12:17:29) MS-Windows 64-bit GUI/console version with OLE support John -- -- 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/0fde278a-c7b1-4e57-8016-03a673adaf1f%40icloud.com.

Is it possible to map ?

Hi,

Is it possible to map <M-Space> to something ?
If I use:

map <Esc><Space> ...

then I would get a delay on each single <Esc>, right ?

I don't want to lower timeouts or else over ssh I might get some spurious chars, etc.
I have tried keyprotocol=kitty and mok2 but doesn't seem to help.
I have tried
exec set <F22>=^[   (there is a space after the esc char)
exec map <F22> <F22>
Then use <F22> for lhs but this causes some real disaster with rgb terminal esc codes.

thx,

-m

--
--
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/8bd25a86-79bd-4ac7-8bf5-83aa1121a580n%40googlegroups.com.

Bug in popup maxwidth?

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/CANuxnEfeoDYktZ3Ku5iZ8G_H_4hs0iWcdMB_8_ikTKp4cQSZsQ%40mail.gmail.com.

Bug in popup with opacity?

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/CANuxnEc0_fDYBB99jYM_YV1axRUZ324VhDKzV%3DK7Cvs7QBj_1w%40mail.gmail.com.

Re: AW: Find a value , and insert it at the begining of line

 

------ Original Message ------
From: janis_papanagnou@hotmail.com
To: vim_use@googlegroups.com
Sent: Tuesday, May 26th 2026, 17:54
Subject: AW: Find a value , and insert it at the begining of line
A little shorter would probably be :%s/\(.*\)\(18\d\d\)\(.*\)/\2&/ (But since you haven't provided input samples and corresponding expected output I'm not sure and you will have to confirm it.) Janis ________________________________________ Von: 'c.willis111 ' via vim_use Gesendet: Dienstag, 26. Mai 2026 18:06 An: vim_use@googlegroups.com Betreff: Find a value , and insert it at the begining of line Hi this works. Is there a niftier way? (ie without capturing the context). :%s/\(.*\)\(18\d\d\)\(.*\)/\2\1\2\3/ It seems that the nested capture which wd have been a tad shorter, doesn't work. 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/483eb624.1c088.19e6509f0f5.Webtop.140%40btinternet.com

 

Thanks Janis, and particularly Tim. I keep forgetting about &.

 

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/DU0PR02MB104223044573EC3CE5325CB5FF30B2%40DU0PR02MB10422.eurprd02.prod.outlook.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/288d3ac2.1c3eb.19e654dd762.Webtop.140%40btinternet.com.

AW: Find a value , and insert it at the begining of line

A little shorter would probably be :%s/\(.*\)\(18\d\d\)\(.*\)/\2&/ (But since you haven't provided input samples and corresponding expected output I'm not sure and you will have to confirm it.) Janis ________________________________________ Von: 'c.willis111 ' via vim_use <vim_use@googlegroups.com> Gesendet: Dienstag, 26. Mai 2026 18:06 An: vim_use@googlegroups.com Betreff: Find a value , and insert it at the begining of line Hi this works. Is there a niftier way? (ie without capturing the context). :%s/\(.*\)\(18\d\d\)\(.*\)/\2\1\2\3/ It seems that the nested capture which wd have been a tad shorter, doesn't work. 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<mailto:vim_use+unsubscribe@googlegroups.com>. To view this discussion visit https://groups.google.com/d/msgid/vim_use/483eb624.1c088.19e6509f0f5.Webtop.140%40btinternet.com<https://groups.google.com/d/msgid/vim_use/483eb624.1c088.19e6509f0f5.Webtop.140%40btinternet.com?utm_medium=email&utm_source=footer>. -- -- 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/DU0PR02MB104223044573EC3CE5325CB5FF30B2%40DU0PR02MB10422.eurprd02.prod.outlook.com.

Re: Find a value , and insert it at the begining of line

On 2026-05-26 17:06, Vim Users wrote: > this works. Is there a niftier way? (ie without capturing the > context). > > :%s/\(.*\)\(18\d\d\)\(.*\)/\2\1\2\3/ You could do something like :%s/.*\(18\d\d\)/\1& if you wanted to simplify it. -tkc -- -- -- 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/ahXNPk6-t1Q2Ko0W%40thechases.com.

Find a value , and insert it at the begining of line

Hi

 

this works. Is there a niftier way? (ie without capturing the context).

 

:%s/\(.*\)\(18\d\d\)\(.*\)/\2\1\2\3/

 

It seems that the nested capture which wd have been a tad shorter, doesn't work.

 

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/483eb624.1c088.19e6509f0f5.Webtop.140%40btinternet.com.

Re: xterm_clipboard missing in Fedora 44

hi, On Tue, 26 May 2026 at 11:10, Manas <manas18244@iiitd.ac.in> wrote: > Hi folks, I upgraded my system from F42 to F44, and I guess something has > broken. I was using vim-enhanced and had also installed vim-X11, which as Fedora > says should contain +xterm_clipboard. "+y/p commands were working fine. But now > I see -xterm_clipboard: > > +clipboard +keymap +profile +vertsplit > +clipboard_provider +lambda -python +vim9script > +cscope +lua/dyn +signs +wayland_clipboard > +extra_search -mouse_sysmouse +tag_binary -xterm_clipboard > > I have checked that xsel/xclip are installed and they are working fine. > How can I solve this? one option would be to build/compile vim with your own configuration. -- regards, jr. You have the right to free speech, as long as you're not dumb enough to actually try it. (The Clash 'Know Your Rights') this email is intended only for the addressee(s) and may contain confidential information. if you are not the intended recipient, you are hereby notified that any use of this email, its dissemination, distribution, and/or copying without prior written consent is prohibited. -- -- 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/CAM-dBgq6XOa8qtgfJQJ-qYfA1%2B9wnPtuwvB%3D8Ti18NKAZH05fg%40mail.gmail.com.

Re: xterm_clipboard missing in Fedora 44

Hi folks, I upgraded my system from F42 to F44, and I guess something has broken. I was using vim-enhanced and had also installed vim-X11, which as Fedora says should contain +xterm_clipboard. "+y/p commands were working fine. But now I see -xterm_clipboard: +clipboard +keymap +profile +vertsplit +clipboard_provider +lambda -python +vim9script +cscope +lua/dyn +signs +wayland_clipboard +extra_search -mouse_sysmouse +tag_binary -xterm_clipboard I have checked that xsel/xclip are installed and they are working fine. How can I solve this? I am on Xorg/F44. Thanks -- Manas -- -- 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/ahVwavhheMXWnwnH%40fedora.

timer_start to refresh rulerformat

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 
$

Re: Can't get new o flag complete option working to add omnnicomplete results

Thanks Romain.

Ill try with the omnifunc for pythin that comes with vim, probably is just a problem with the jedi omnicompletion function

Thanks

El mar, 19 may 2026 a las 8:41, Romain Lafourcade (<romainlafourcade@gmail.com>) escribió:

The feature works as expected in 9.2.321 in JavaScript files (using the stock javascriptcomplete#CompleteJS) and Python files (using the stock python3complete#Complete). Thank you for pointing it out to me by the way.

Note that the completion list is prioritized by "kind", so items from omnifunc may be way down the menu if "o" is at the end of "omnifunc".

You should try it in a buffer for which the "omnifunc" is not set by a plugin, or simply with "$ vim --clean", in order to rule out a Vim bug:

$ vim --clean +set\ complete=o filename.py

If "omnifunc" is set and you get language-aware completion, then it means that the feature works and that the problem is somewhere else. You should probably talk about this with the Jedi maintainers.

If not, then you may have found a regression introduced between 321 and 449, in which case you should head to Vim's issue tracker.

On Saturday, May 16, 2026 at 6:42:21 PM UTC+2 Pablo Giménez wrote:

Hello.

Looking at the new features in Vim9.2, great release BTW, there is one that caught my attention, something I have been waiting for a long time.

The ability to get the results from several complete commands into one simple complete query.

Plugins like MuComplete where close, allowing to switch to different complete command, but the newly added o flag for the complete option looks like the proper solution.

Basically I want to press Ctrl-N and get results not only for keyword but also for omnicomplete, semantic aware results, I have been testing it with python where I use vim-jedi to

get omnicompletion working using the jedi#completions function.

Adding the o flag  doesn't seem to have any effect in the complete options offered when I press Ctrl-N, if I press Ctrl-X-O I got the expected results from omnicompletion, but those

results doesn't appear when I press Ctrrl-N.

These are the flags I use for complete:

set complete=.,w,b,k,o

Am I missing something? Are there some limitations with certain omnifuncs or jedi#completions needs tweaks to get it working?

I tried also using F and set complefunc to the same as omnifunc, but same result.

Using Vim 9.2.449

Thanks

--

Un saludo
Best Regards
Pablo Giménez

--
--
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/4ca31e1e-8ddf-46e6-b656-8d72871f0addn%40googlegroups.com.

--

Un saludo
Best Regards
Pablo Giménez

--
--
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/CAKt3ggKbMmvyXOowLkmMy06wfb1t4jpWuObubKDo%3DKNj_1jyCQ%40mail.gmail.com.

Re: Can't get new o flag complete option working to add omnnicomplete results

The feature works as expected in 9.2.321 in JavaScript files (using the stock javascriptcomplete#CompleteJS) and Python files (using the stock python3complete#Complete). Thank you for pointing it out to me by the way.

Note that the completion list is prioritized by "kind", so items from omnifunc may be way down the menu if "o" is at the end of "omnifunc".

You should try it in a buffer for which the "omnifunc" is not set by a plugin, or simply with "$ vim --clean", in order to rule out a Vim bug:

$ vim --clean +set\ complete=o filename.py

If "omnifunc" is set and you get language-aware completion, then it means that the feature works and that the problem is somewhere else. You should probably talk about this with the Jedi maintainers.

If not, then you may have found a regression introduced between 321 and 449, in which case you should head to Vim's issue tracker.

On Saturday, May 16, 2026 at 6:42:21 PM UTC+2 Pablo Giménez wrote:

Hello.

Looking at the new features in Vim9.2, great release BTW, there is one that caught my attention, something I have been waiting for a long time.

The ability to get the results from several complete commands into one simple complete query.

Plugins like MuComplete where close, allowing to switch to different complete command, but the newly added o flag for the complete option looks like the proper solution.

Basically I want to press Ctrl-N and get results not only for keyword but also for omnicomplete, semantic aware results, I have been testing it with python where I use vim-jedi to

get omnicompletion working using the jedi#completions function.

Adding the o flag  doesn't seem to have any effect in the complete options offered when I press Ctrl-N, if I press Ctrl-X-O I got the expected results from omnicompletion, but those

results doesn't appear when I press Ctrrl-N.

These are the flags I use for complete:

set complete=.,w,b,k,o

Am I missing something? Are there some limitations with certain omnifuncs or jedi#completions needs tweaks to get it working?

I tried also using F and set complefunc to the same as omnifunc, but same result.

Using Vim 9.2.449

Thanks

--

Un saludo
Best Regards
Pablo Giménez

--
--
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/4ca31e1e-8ddf-46e6-b656-8d72871f0addn%40googlegroups.com.

Can't get new o flag complete option working to add omnnicomplete results

Hello.

Looking at the new features in Vim9.2, great release BTW, there is one that caught my attention, something I have been waiting for a long time.

The ability to get the results from several complete commands into one simple complete query.

Plugins like MuComplete where close, allowing to switch to different complete command, but the newly added o flag for the complete option looks like the proper solution.

Basically I want to press Ctrl-N and get results not only for keyword but also for omnicomplete, semantic aware results, I have been testing it with python where I use vim-jedi to

get omnicompletion working using the jedi#completions function.

Adding the o flag  doesn't seem to have any effect in the complete options offered when I press Ctrl-N, if I press Ctrl-X-O I got the expected results from omnicompletion, but those

results doesn't appear when I press Ctrrl-N.

These are the flags I use for complete:

set complete=.,w,b,k,o

Am I missing something? Are there some limitations with certain omnifuncs or jedi#completions needs tweaks to get it working?

I tried also using F and set complefunc to the same as omnifunc, but same result.

Using Vim 9.2.449

Thanks

--

Un saludo
Best Regards
Pablo Giménez

--
--
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/CAKt3ggLfriqi%2Bjgc2RKqNUkARPtjMoNZm-9vNWfCxm_1srns2g%40mail.gmail.com.

Format not preserved when pasting from Google's AI-Generated output to Vim.

Please advice, when I paste text from AI-text generated output from the browser to Vim the format is not preserved as the pasted text shows all in one sentence, and it is not structured a it appears in the source text in the browser.

This only happens with text generated from Google's AI since other pasted text like text from a web search is pasted properly as it shows in the browser, or any other source like Word formatted text. I think I have tried most pasting commands and tried also the ":set paste" and ":set no paste" with no success. Please refer to the following example:

Original text from the browser Google's AI Output:

"Why Use Vim for Prose

• Modal Editing: Allows for quick maneuvering and editing (Normal mode) versus typing (Insert mode).
• Keyboard-Centric: Keeps hands on the home row, increasing efficiency by eliminating mouse usage.
• Plain Text Focus: Encourages writing in Markdown or simple text, which is lightweight, non-proprietary, and future-proof."

And this is how the pasted text shows in Vim:

"Why Use Vim for ProseModal Editing: Allows for quick maneuvering and editing (Normal mode) versus typing (Insert mode).Keyboard-Centric: Keeps hands on the home row, increasing efficiency by eliminating mouse usage.Plain Text Focus: Encourages writing in Markdown or simple text, which is lightweight, non-proprietary, and future-proof."

Regards.

--
--
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/11130928-145d-468f-b547-f160151f9363n%40googlegroups.com.