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.

Re: New Line Criteria ?

On 2026-04-13 14:28, 'Paul' via vim_use wrote: > On Mon, Mar 30, 2026 at 01:43:23PM -0700, Christopher wrote: >> How do I get vim to show a file to display for example where there is >> */bin:* place it on a new line but revert back to how it was before the >> file was loaded into vim ? > > Put all "/bin:"s on a new line: :%s/\/bin:/\r&/g > Revert (if simply undoing (u) isn't enough): :e! Or, if you don't intend to do any other edits that you'll want to save: :q! That quits Vim without saving your edited version of the file. Stan Brown Tehachapi, CA, USA https://BrownMath.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/bd43b933-22f6-4701-8959-a0888d8dcd4a%40fastmail.fm.

Re: New Line Criteria ?

On Mon, Mar 30, 2026 at 01:43:23PM -0700, Christopher wrote: > How do I get vim to show a file to display for example where there is >*/bin:* place it on a new line but revert back to how it was before the >file was loaded into vim ? Put all "/bin:"s on a new line: :%s/\/bin:/\r&/g Revert (if simply undoing (u) isn't enough): :e! -- -- 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/ad1gCX-UJQpFNQQa%40kitt.

How hard would it be to have :term windows operate with "nowrap" ?

I find the ability to have a vim window operate as a terminal really useful (the :terminal command).  

The one thing I really find annoying about it is the fact that it wraps lines that are longer than the window width with a hard carriage return, so that if you go back and select text from the terminal, it contains carriage returns that were not actually present in the program output.  As far as I can tell, there are no settings to change that.  How hard would it be to add that capability?

--
--
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/CAJjaVfVHJd%2BbRY5BpuYfL0QgdUo34ShTufWuvVf5py0i51tcew%40mail.gmail.com.

Re: autocmds general usage

On Wednesday, April 1, 2026 at 10:43:09 AM UTC-4 Christopher wrote:

I have a general question about autocmd, how can I use it without always having invoke it by using ":" then loading the appropriate commands then finally the file to which I want it to apply or must I script it ?

I don't understand the question (what do you mean "use it" without "using ':'", etc.?), but:

The typical practice for autocommands is to put them in your vimrc (~/.vim/vimrc, etc.) or a local plugin (~/.vim/plugin/<name>.vim) so they are established during startup.

Some customizations don't required autocommands, though: if you're customizing the behavior of a particular filetype, then use an ftplugin, indent, or syntax script. (Or your filetype may already have knobs to tweak; see `:help :syn-file-remarks`, `:help ftplugin-docs`, `:help local-additions`, etc. Completing with `:help ft-<filetype><Ctrl-d>` is usually good too.)

--
--
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/75d80253-9b2f-414c-af30-6b8909714b86n%40googlegroups.com.

autocmds general usage

I have a general question about autocmd, how can I use it without always having invoke it by using ":" then loading the appropriate commands then finally the file to which I want it to apply or must I script it ?

--
--
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/8c22618b-c796-4dd8-ae79-e674df044fe6n%40googlegroups.com.

New Line Criteria ?

How do I get vim to show a file to display for example where there is /bin: place it on a new line but revert back to how it was before the file was loaded into vim ?  

--
--
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/b8d1d80d-e21d-41f8-b7d6-0e24c31df5d3n%40googlegroups.com.

Re: $VIMRC over .vimrc ?

On Friday, March 20, 2026 at 10:58:21 AM UTC-4 D. Ben Knoble wrote:

On Fri, Mar 20, 2026 at 9:58 AM Christopher <crestchr...@gmail.com> wrote:
>
>
>
> On Thursday, March 19, 2026 at 8:44:22 PM UTC-4 Marvin Renich wrote:
>
> * Christopher <crestchr...@gmail.com> [260319 19:14]:
> > On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mr...@renich.org> wrote:
> > > The user's vimrc file _must_ be one of the files listed above, unless
> > > you specify the -u option. The only way to specify the vimrc file in an
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> > > before (or while) starting vim.
> >
> > You mention, the only way to specify a vimrc in a environment variable; I
> > assume as in $MYVIMRC is to export VIMNT which is the source of your vimrc
> > file. If my vimrc file was located in the system path then that would be;
> > VIMINT=`/etc/vimrc and that would create the environment variable $MYVIMRC
> > ?
>
> You need to read carefully and for exact syntax and content:
>
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Remember that VIMINIT specifies an ex command to execute, not a file
> name. If you want to source a file using VIMINIT, you must specify the
> source command itself, not just the file name.
>
> Also, when testing this, know that :scriptnames is your friend.
>
> Also note that if your vimrc file is the system vimrc file (/etc/vimrc
> on some distributions, /etc/vim/vimrc on Debian), it is sufficient to
> use:
>
> VIMINIT=':' vim
>
> or
>
> export VIMINIT=':'
> vim
>
> as the system vimrc is sourced even if you specify a VIMINIT. Setting
> VIMINIT=':' simply disables reading of the user vimrc file, but not the
> system vimrc file. (':' is an empty ex command.)
>
> Finally, if you specify VIMINIT, MYVIMRC is _not_ set by vim.
>
> ...Marvin
>
>
> What do you mean by :scriptnames ?

":scriptnames" is an Ex command supported by Vim that announces what
scripts have been executed in the current session. (":help
:scriptnames").

> Within vim I run the command; VIMIT=: (colon) and that takes my system vimrc assigns it the variable $MYVIMRC or that has to be done after ?

I get the sense you may not be reading very carefully, but let me try
to clear up some confusion:

- "VIMINIT=: vim" is an example shell command that would disable
initializations from vimrc files other than the system vimrc.
(Notably, this does _not_ disable user-local plugins.)
- Vim will assign MYVIMRC if and when it finds and executes a user
vimrc. It never (AFAIK) assigns MYVIMRC to the path of the system
vimrc.
- The above point is moot if you set VIMINIT; then nothing sets MYVIMRC
- MYVIMRC is never _read_ by Vim to take any action (unless a plugin
or script uses it)

I wanted to clarify that it's now clear. In order to use the environment variable $MYVIMRC you must have a user; .vimrc file created, typically at the $HOME path for the installed nix version.

--
--
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/0ab878b1-afba-4524-913b-5ffe79587c76n%40googlegroups.com.

Re: pattern syntax for match()

tim / christian

thank you.  both forms work as expected:  single and double quoted forms.  in all of my quoting permutations, i had been escaping the bar, also.

works fine, now.  many thanks.

On March 25, 2026 12:41:15 PM PDT, Christian Brabandt <cblists@256bit.org> wrote:

On Mi, 25 Mär 2026, Tim Chase wrote:

On 2026-03-25 12:01, S. Cowles wrote:
i would like to do the following operation:
	let m = match( "foo" , "foo\|beep" )
however, i get no match.  (m is (-1).)
what is the correct pattern syntax to enable this match?

Because they're strings, do you need to escape the "\", making it

  let m = match( "foo" , "foo\\|beep" )

Or a bit more readable, use single quotes instead.

Thanks,
Christian

--
scowles@sonic.net
+1 510 380 8661

Re: pattern syntax for match()

On Mi, 25 Mär 2026, Tim Chase wrote:

> On 2026-03-25 12:01, S. Cowles wrote:
> > i would like to do the following operation:
> > let m = match( "foo" , "foo\|beep" )
> > however, i get no match. (m is (-1).)
> > what is the correct pattern syntax to enable this match?
>
> Because they're strings, do you need to escape the "\", making it
>
> let m = match( "foo" , "foo\\|beep" )

Or a bit more readable, use single quotes instead.

Thanks,
Christian
--
Are we not men?

--
--
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/acQ6W0dcgdWjG1p2%40256bit.org.

Re: pattern syntax for match()

On 2026-03-25 12:01, S. Cowles wrote:
> i would like to do the following operation:
> let m = match( "foo" , "foo\|beep" )
> however, i get no match. (m is (-1).)
> what is the correct pattern syntax to enable this match?

Because they're strings, do you need to escape the "\", making it

let m = match( "foo" , "foo\\|beep" )

-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/acQ5bWo0u3TymbWb%40thechases.com.

pattern syntax for match()

i would like to do the following operation:
let m = match( "foo" , "foo\|beep" )
however, i get no match. (m is (-1).)
what is the correct pattern syntax to enable this match?
i am running vim:
VIM - Vi IMproved 9.2 (2026 Feb 14, compiled Mar 25 2026 09:59:45)
Included patches: 1-240
Huge version with GTK3 GUI.

thanks.

--
s. cowles
scowles at sonic dot net
Key fingerprint = 6DEC FF05 6952 3967 BE66 1BBD 588D 8B40 EFB8 4AA2


--
--
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/ca2d97a1-0097-72ab-6646-92670559e880%40sonic.net.

Re: issues posting to the dev list

On Mo, 23 Mär 2026, Eli the Bearded wrote:

> Someone in comp.editors is reporting that attempts to post to Vim Dev
> list (<vim_dev@googlegroups.com> and <vim-dev@vim.org>) are bouncing
> with Google errors:
>
> "We're writing to let you know that the group you tried to
> contact (vim_dev) may not exist, or you may not have permission
> to post messages to the group. A few more details on why you
> weren't able to post:
> * You might have spelled or formatted the group name incorrectly.
> * The owner of the group may have removed this group.
> * You may need to join the group before receiving permission to post.
> * This group may not be open to posting.
> If you have questions related to this or any other Google Group,
> visit the Help Center at https://groups.google.com/support/."
>
> Subscribing to the list works, but doesn't fix the problem.
>
> Anyone running that list and able to read/post to Usenet still?
>
> From: Janis Papanagnou <janis_papanagnou+ng@hotmail.com>
> Newsgroups: comp.editors
> Subject: Vim mailing list
> Date: Sun, 22 Mar 2026 03:38:27 +0100
> Message-ID: <10pnkn3$2utmg$1@dont-email.me>
>
> I suggested the google version of the list address and don't have
> any other concrete suggestions.

I cannot see a member with that name or E-Mail address in either the
vim_use or vim_dev list. You can direct him to me, but my possibilities
are limited. Google groups is a free service but also has no real
support unfortunately.

Thanks,
Christian
--
Contestants have been briefed on some questions before the show.

--
--
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/acGsKh6BOvvUbClB%40256bit.org.

issues posting to the dev list

Someone in comp.editors is reporting that attempts to post to Vim Dev
list (<vim_dev@googlegroups.com> and <vim-dev@vim.org>) are bouncing
with Google errors:

"We're writing to let you know that the group you tried to
contact (vim_dev) may not exist, or you may not have permission
to post messages to the group. A few more details on why you
weren't able to post:
* You might have spelled or formatted the group name incorrectly.
* The owner of the group may have removed this group.
* You may need to join the group before receiving permission to post.
* This group may not be open to posting.
If you have questions related to this or any other Google Group,
visit the Help Center at https://groups.google.com/support/."

Subscribing to the list works, but doesn't fix the problem.

Anyone running that list and able to read/post to Usenet still?

From: Janis Papanagnou <janis_papanagnou+ng@hotmail.com>
Newsgroups: comp.editors
Subject: Vim mailing list
Date: Sun, 22 Mar 2026 03:38:27 +0100
Message-ID: <10pnkn3$2utmg$1@dont-email.me>

I suggested the google version of the list address and don't have
any other concrete suggestions.

Elijah

--
--
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/4ffkVk4CDPzfYm%40panix5.panix.com.

Re: Ctrl+PageUp in 9.2.0204

On 2026-03-20, Christian Brabandt wrote:
> On Fr, 20 M�r 2026, jazztickets wrote:
>
> > For me the issue is still happening in 9.2.209 on the terminals I've
> > tried: xterm, xfce, gnome console, gnome terminal. It is working
> > however on Konsole, which also worked in 9.2.204.
>
> Thanks, let me ping the author

Patch 9.2.0229 seems to have fixed it. Thanks!

Regards,
Gary

--
--
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/20260322222903.GG10946%40phoenix.

Re: Ctrl+PageUp in 9.2.0204

On Fr, 20 Mär 2026, jazztickets wrote:

> For me the issue is still happening in 9.2.209 on the terminals I've
> tried: xterm, xfce, gnome console, gnome terminal. It is working
> however on Konsole, which also worked in 9.2.204.

Thanks, let me ping the author

Thanks,
Christian
--
Term, holidays, term, holidays, till we leave school, and then work, work,
work till we die.
-- C. S. Lewis

--
--
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/ab3Ifyp3iTWBoIhQ%40256bit.org.

Re: Ctrl+PageUp in 9.2.0204

On Fri, Mar 20, 2026 at 3:33 PM Christian Brabandt <cblists@256bit.org> wrote:
>
>
> On Fr, 20 Mär 2026, Gary Johnson wrote:
>
> > On 2026-03-20, Gary Johnson wrote:
> > > On 2026-03-20, jazztickets wrote:
> > > > I'm using ctrl+PageUp/ctrl+PageDown to switch between tabs but after upgrading
> > > > to vim 9.2.0204 in Arch Linux, ctrl+PageUp no longer goes to the previous tab.
> > > > Instead it's sending ctrl+e and scrolling one line down. Tested with
> > > > xfce4-terminal and gnome's terminal. Do I need to change something in the
> > > > terminal?
> > >
> > > I can verify this on Ubuntu 24.04.4. I did a git bisect and found
> > > the difference (bug?) to have been introduced at patch 9.2.0192.
> > > This behavior is not affected by "k" in 'cpoptions'. I haven't
> > > looked into it further.
> >
> > I forgot to mention that the terminal I used was xterm version 403
> > and the desktop environment was GNOME 46.0.
> >
> > However, I discovered that the issue is not present in the latest
> > Vim, 9.2.209, when using GNOME Terminal version 3.52.0.
>
> Thanks for reporting, but it's not clear to me is this issue only
> present in xterm? Or is it resolved with latest master?

For me the issue is still happening in 9.2.209 on the terminals I've
tried: xterm,
xfce, gnome console, gnome terminal. It is working however on Konsole, which
also worked in 9.2.204.

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

Re: Ctrl+PageUp in 9.2.0204

On Fr, 20 Mär 2026, Gary Johnson wrote:

> On 2026-03-20, Gary Johnson wrote:
> > On 2026-03-20, jazztickets wrote:
> > > I'm using ctrl+PageUp/ctrl+PageDown to switch between tabs but after upgrading
> > > to vim 9.2.0204 in Arch Linux, ctrl+PageUp no longer goes to the previous tab.
> > > Instead it's sending ctrl+e and scrolling one line down. Tested with
> > > xfce4-terminal and gnome's terminal. Do I need to change something in the
> > > terminal?
> >
> > I can verify this on Ubuntu 24.04.4. I did a git bisect and found
> > the difference (bug?) to have been introduced at patch 9.2.0192.
> > This behavior is not affected by "k" in 'cpoptions'. I haven't
> > looked into it further.
>
> I forgot to mention that the terminal I used was xterm version 403
> and the desktop environment was GNOME 46.0.
>
> However, I discovered that the issue is not present in the latest
> Vim, 9.2.209, when using GNOME Terminal version 3.52.0.

Thanks for reporting, but it's not clear to me is this issue only
present in xterm? Or is it resolved with latest master?

Thanks,
Christian
--
Flugg's Law:
When you need to knock on wood is when you realize
that the world is composed of vinyl, naugahyde and aluminum.

--
--
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/ab28rhNqM957aQsd%40256bit.org.

Re: Ctrl+PageUp in 9.2.0204

On 2026-03-20, Gary Johnson wrote:
> On 2026-03-20, jazztickets wrote:
> > I'm using ctrl+PageUp/ctrl+PageDown to switch between tabs but after upgrading
> > to vim 9.2.0204 in Arch Linux, ctrl+PageUp no longer goes to the previous tab.
> > Instead it's sending ctrl+e and scrolling one line down. Tested with
> > xfce4-terminal and gnome's terminal. Do I need to change something in the
> > terminal?
>
> I can verify this on Ubuntu 24.04.4. I did a git bisect and found
> the difference (bug?) to have been introduced at patch 9.2.0192.
> This behavior is not affected by "k" in 'cpoptions'. I haven't
> looked into it further.

I forgot to mention that the terminal I used was xterm version 403
and the desktop environment was GNOME 46.0.

However, I discovered that the issue is not present in the latest
Vim, 9.2.209, when using GNOME Terminal version 3.52.0.

Regards,
Gary

--
--
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/20260320203046.GF10946%40phoenix.

Re: Ctrl+PageUp in 9.2.0204

On 2026-03-20, jazztickets wrote:
> I'm using ctrl+PageUp/ctrl+PageDown to switch between tabs but after upgrading
> to vim 9.2.0204 in Arch Linux, ctrl+PageUp no longer goes to the previous tab.
> Instead it's sending ctrl+e and scrolling one line down. Tested with
> xfce4-terminal and gnome's terminal. Do I need to change something in the
> terminal?

I can verify this on Ubuntu 24.04.4. I did a git bisect and found
the difference (bug?) to have been introduced at patch 9.2.0192.
This behavior is not affected by "k" in 'cpoptions'. I haven't
looked into it further.

--------------------------------------------------------------------
c4d212257d61f5c2a9cd919486288c747aaaa05d is the first bad commit
commit c4d212257d61f5c2a9cd919486288c747aaaa05d
Author: AstroSnail <astrosnail@protonmail.com>
Date: Tue Mar 17 21:24:43 2026 +0000

patch 9.2.0192: not correctly recognizing raw key codes

Problem: When "k" is excluded from cpoptions, vim should be able to
recognize raw key codes in mappings and replace them with
builtin codes (e.g. ^[OA is replaced with <Up>) so that
changing the builtin code also changes the mapping to match.
Currently, this only works properly if the builtin code does
not contain modifiers (e.g. @;*).
Solution: Teach find_term_bykeys how to recognize keys with modifiers
(AstroSnail).

fixes: #19182
closes: #19643

Signed-off-by: AstroSnail <astrosnail@protonmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>

src/term.c | 93 +++++++++++++++++++++++++++++++++++++-----
src/testdir/test_termcodes.vim | 20 +++++++++
src/version.c | 2 +
3 files changed, 104 insertions(+), 11 deletions(-)
--------------------------------------------------------------------

Regards,
Gary

--
--
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/20260320194659.GE10946%40phoenix.

Ctrl+PageUp in 9.2.0204

I'm using ctrl+PageUp/ctrl+PageDown to switch between tabs but after upgrading to vim 9.2.0204 in Arch Linux, ctrl+PageUp no longer goes to the previous tab. Instead it's sending ctrl+e and scrolling one line down. Tested with xfce4-terminal and gnome's terminal. Do I need to change something in the terminal?

--
--
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/a0d10bae-cc9b-4d7d-85ab-8da124ab1e3an%40googlegroups.com.

Re: $VIMRC over .vimrc ?

On Fri, Mar 20, 2026 at 9:58 AM Christopher <crestchristopher@gmail.com> wrote:
>
>
>
> On Thursday, March 19, 2026 at 8:44:22 PM UTC-4 Marvin Renich wrote:
>
> * Christopher <crestchr...@gmail.com> [260319 19:14]:
> > On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mr...@renich.org> wrote:
> > > The user's vimrc file _must_ be one of the files listed above, unless
> > > you specify the -u option. The only way to specify the vimrc file in an
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> > > before (or while) starting vim.
> >
> > You mention, the only way to specify a vimrc in a environment variable; I
> > assume as in $MYVIMRC is to export VIMNT which is the source of your vimrc
> > file. If my vimrc file was located in the system path then that would be;
> > VIMINT=`/etc/vimrc and that would create the environment variable $MYVIMRC
> > ?
>
> You need to read carefully and for exact syntax and content:
>
> > > environment variable is to export VIMINT="source /path/to/your/vimrc"
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Remember that VIMINIT specifies an ex command to execute, not a file
> name. If you want to source a file using VIMINIT, you must specify the
> source command itself, not just the file name.
>
> Also, when testing this, know that :scriptnames is your friend.
>
> Also note that if your vimrc file is the system vimrc file (/etc/vimrc
> on some distributions, /etc/vim/vimrc on Debian), it is sufficient to
> use:
>
> VIMINIT=':' vim
>
> or
>
> export VIMINIT=':'
> vim
>
> as the system vimrc is sourced even if you specify a VIMINIT. Setting
> VIMINIT=':' simply disables reading of the user vimrc file, but not the
> system vimrc file. (':' is an empty ex command.)
>
> Finally, if you specify VIMINIT, MYVIMRC is _not_ set by vim.
>
> ...Marvin
>
>
> What do you mean by :scriptnames ?

":scriptnames" is an Ex command supported by Vim that announces what
scripts have been executed in the current session. (":help
:scriptnames").

> Within vim I run the command; VIMIT=: (colon) and that takes my system vimrc assigns it the variable $MYVIMRC or that has to be done after ?

I get the sense you may not be reading very carefully, but let me try
to clear up some confusion:

- "VIMINIT=: vim" is an example shell command that would disable
initializations from vimrc files other than the system vimrc.
(Notably, this does _not_ disable user-local plugins.)
- Vim will assign MYVIMRC if and when it finds and executes a user
vimrc. It never (AFAIK) assigns MYVIMRC to the path of the system
vimrc.
- The above point is moot if you set VIMINIT; then nothing sets MYVIMRC
- MYVIMRC is never _read_ by Vim to take any action (unless a plugin
or script uses it)

--
--
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/CALnO6CC33KPvhAc06k-WzcMcgvsff9mCyxjb7c4EsDKqDRr%3DOw%40mail.gmail.com.

Re: $VIMRC over .vimrc ?

On Thursday, March 19, 2026 at 8:44:22 PM UTC-4 Marvin Renich wrote:

* Christopher <crestchr...@gmail.com> [260319 19:14]:
> On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mr...@renich.org> wrote:
> > The user's vimrc file _must_ be one of the files listed above, unless
> > you specify the -u option. The only way to specify the vimrc file in an
> > environment variable is to export VIMINT="source /path/to/your/vimrc"
> > before (or while) starting vim.
>
> You mention, the only way to specify a vimrc in a environment variable; I
> assume as in $MYVIMRC is to export VIMNT which is the source of your vimrc
> file. If my vimrc file was located in the system path then that would be;
> VIMINT=`/etc/vimrc and that would create the environment variable $MYVIMRC
> ?

You need to read carefully and for exact syntax and content:

> > environment variable is to export VIMINT="source /path/to/your/vimrc"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Remember that VIMINIT specifies an ex command to execute, not a file
name. If you want to source a file using VIMINIT, you must specify the
source command itself, not just the file name.

Also, when testing this, know that :scriptnames is your friend.

Also note that if your vimrc file is the system vimrc file (/etc/vimrc
on some distributions, /etc/vim/vimrc on Debian), it is sufficient to
use:

VIMINIT=':' vim

or

export VIMINIT=':'
vim

as the system vimrc is sourced even if you specify a VIMINIT. Setting
VIMINIT=':' simply disables reading of the user vimrc file, but not the
system vimrc file. (':' is an empty ex command.)

Finally, if you specify VIMINIT, MYVIMRC is _not_ set by vim.

...Marvin

What do you mean by :scriptnames ?

Within vim I run the command; VIMIT=: (colon) and that takes my system vimrc assigns it the variable $MYVIMRC or that has to be done after ? 

 

--
--
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/93a47316-1060-4434-b330-d8b8b72e6595n%40googlegroups.com.

Re: $VIMRC over .vimrc ?

* Christopher <crestchristopher@gmail.com> [260319 19:14]:
> On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mr...@renich.org> wrote:
> > The user's vimrc file _must_ be one of the files listed above, unless
> > you specify the -u option. The only way to specify the vimrc file in an
> > environment variable is to export VIMINT="source /path/to/your/vimrc"
> > before (or while) starting vim.
>
> You mention, the only way to specify a vimrc in a environment variable; I
> assume as in $MYVIMRC is to export VIMNT which is the source of your vimrc
> file. If my vimrc file was located in the system path then that would be;
> VIMINT=`/etc/vimrc and that would create the environment variable $MYVIMRC
> ?

You need to read carefully and for exact syntax and content:

> > environment variable is to export VIMINT="source /path/to/your/vimrc"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Remember that VIMINIT specifies an ex command to execute, not a file
name. If you want to source a file using VIMINIT, you must specify the
source command itself, not just the file name.

Also, when testing this, know that :scriptnames is your friend.

Also note that if your vimrc file is the system vimrc file (/etc/vimrc
on some distributions, /etc/vim/vimrc on Debian), it is sufficient to
use:

VIMINIT=':' vim

or

export VIMINIT=':'
vim

as the system vimrc is sourced even if you specify a VIMINIT. Setting
VIMINIT=':' simply disables reading of the user vimrc file, but not the
system vimrc file. (':' is an empty ex command.)

Finally, if you specify VIMINIT, MYVIMRC is _not_ set by vim.

...Marvin

--
--
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/abyYWCKoex7z/GPU%40basil.wdw.

Re: $VIMRC over .vimrc ?

On Thursday, March 19, 2026 at 12:29:46 PM UTC-4 D. Ben Knoble wrote:

On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mr...@renich.org> wrote:
>
> * Christopher <crestchr...@gmail.com> [260319 03:56]:
> > On Wednesday, March 18, 2026 at 3:48:41 PM UTC-4 Ben Knoble wrote:
> > I'm afraid your question isn't clear to me, but let's look at `:help
> > myvimrc`:
> >
> > c. Five places are searched for initializations. The first that exists
> > is used, the others are ignored. The `$MYVIMRC` environment variable is
> > set to the file that was first found, unless `$MYVIMRC` was already set
>
> and
>
> > when using VIMINIT. The `$MYVIMDIR` environment variable is
> > set to the personal 'rtp' directory, however it is not verified
> > that the directory actually exists.
> > I The environment variable VIMINIT (see also |compatible-default|) (*)
> > The value of $VIMINIT is used as an Ex command line.
> > II The user vimrc file(s):
> > "$HOME/.vimrc" (for Unix) (*)
> > "$HOME/.vim/vimrc" (for Unix) (*)
> > "$XDG_CONFIG_HOME/vim/vimrc" (for Unix) (*)
> > "s:.vimrc" (for Amiga) (*)
> > "home:.vimrc" (for Amiga) (*)
> > "home:vimfiles:vimrc" (for Amiga) (*)
> > "$VIM/.vimrc" (for Amiga) (*)
> > "$HOME/_vimrc" (for Win32) (*)
> > "$HOME/vimfiles/vimrc" (for Win32) (*)
> > "$VIM/_vimrc" (for Win32) (*)
> > "$HOME/config/settings/vim/vimrc" (for Haiku) (*)
>
> This quote is missing an important word, as shown above.
>
> Perhaps that word should be "or" rather than "and", but either way the
> meaning should be clear:
>
> If VIMINIT is set, it contains ex commands, vim does not search for or
> read any rc file, and MYVIMRC is not set.
>
> If VIMINIT is not set, vim searches for a file in the places listed
> above, and sets MYVIMRC to the file that was found and read.
>
> So, MYVIMRC is not an input to vim, it is how vim communicates to the
> user which file was found and read. If MYVIMRC is exported before
> invoking vim, it is ignored completely; it is neither read nor set.
>
> The user's vimrc file _must_ be one of the files listed above, unless
> you specify the -u option. The only way to specify the vimrc file in an
> environment variable is to export VIMINT="source /path/to/your/vimrc"
> before (or while) starting vim.
>
> The strongly recommended way is to _not_ use VIMINT, and to place your
> vimrc file at ~/.vim/vimrc. VIMINIT is a compatibility holdover.
>
> ...Marvin

Indeed. This is what I meant to convey, and I apologize if my initial
reply was not clear on this point:

Vim sets MYVIMRC for the user, not the other way around!

--
D. Ben Knoble

> The user's vimrc file _must_ be one of the files listed above, unless
> you specify the -u option. The only way to specify the vimrc file in an
> environment variable is to export VIMINT="source /path/to/your/vimrc"
> before (or while) starting vim.  

You mention, the only way to specify a vimrc in a environment variable; I assume as in $MYVIMRC is to export VIMNT which is the source of your vimrc file. If my vimrc file was located in the system path then that would be;

VIMINT=`/etc/vimrc and that would create the environment variable $MYVIMRC ? 

--
--
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/b3efd6e9-4d4f-4752-af97-2d5666abfd6en%40googlegroups.com.

Re: $VIMRC over .vimrc ?

* D. Ben Knoble <ben.knoble@gmail.com> [260319 12:29]:
> Indeed. This is what I meant to convey, and I apologize if my initial
> reply was not clear on this point:
>
> Vim sets MYVIMRC for the user, not the other way around!

What you were saying was clear to me, but it seemed like the OP was
still confused, so I tried to say it a different way.

...Marvin

--
--
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/abxJd/2VxlFsH%2BX8%40basil.wdw.

Re: $VIMRC over .vimrc ?

On Thu, Mar 19, 2026 at 9:45 AM Marvin Renich <mrvn@renich.org> wrote:
>
> * Christopher <crestchristopher@gmail.com> [260319 03:56]:
> > On Wednesday, March 18, 2026 at 3:48:41 PM UTC-4 Ben Knoble wrote:
> > I'm afraid your question isn't clear to me, but let's look at `:help
> > myvimrc`:
> >
> > c. Five places are searched for initializations. The first that exists
> > is used, the others are ignored. The `$MYVIMRC` environment variable is
> > set to the file that was first found, unless `$MYVIMRC` was already set
>
> and
>
> > when using VIMINIT. The `$MYVIMDIR` environment variable is
> > set to the personal 'rtp' directory, however it is not verified
> > that the directory actually exists.
> > I The environment variable VIMINIT (see also |compatible-default|) (*)
> > The value of $VIMINIT is used as an Ex command line.
> > II The user vimrc file(s):
> > "$HOME/.vimrc" (for Unix) (*)
> > "$HOME/.vim/vimrc" (for Unix) (*)
> > "$XDG_CONFIG_HOME/vim/vimrc" (for Unix) (*)
> > "s:.vimrc" (for Amiga) (*)
> > "home:.vimrc" (for Amiga) (*)
> > "home:vimfiles:vimrc" (for Amiga) (*)
> > "$VIM/.vimrc" (for Amiga) (*)
> > "$HOME/_vimrc" (for Win32) (*)
> > "$HOME/vimfiles/vimrc" (for Win32) (*)
> > "$VIM/_vimrc" (for Win32) (*)
> > "$HOME/config/settings/vim/vimrc" (for Haiku) (*)
>
> This quote is missing an important word, as shown above.
>
> Perhaps that word should be "or" rather than "and", but either way the
> meaning should be clear:
>
> If VIMINIT is set, it contains ex commands, vim does not search for or
> read any rc file, and MYVIMRC is not set.
>
> If VIMINIT is not set, vim searches for a file in the places listed
> above, and sets MYVIMRC to the file that was found and read.
>
> So, MYVIMRC is not an input to vim, it is how vim communicates to the
> user which file was found and read. If MYVIMRC is exported before
> invoking vim, it is ignored completely; it is neither read nor set.
>
> The user's vimrc file _must_ be one of the files listed above, unless
> you specify the -u option. The only way to specify the vimrc file in an
> environment variable is to export VIMINT="source /path/to/your/vimrc"
> before (or while) starting vim.
>
> The strongly recommended way is to _not_ use VIMINT, and to place your
> vimrc file at ~/.vim/vimrc. VIMINIT is a compatibility holdover.
>
> ...Marvin

Indeed. This is what I meant to convey, and I apologize if my initial
reply was not clear on this point:

Vim sets MYVIMRC for the user, not the other way around!

--
D. Ben Knoble

--
--
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/CALnO6CB5mct8F%3DD%3DSsnUWeEtWyjJNuCtHY-Kk9-od76qoH_V_w%40mail.gmail.com.