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.