[vim/vim] gvim --help does not show important information about configuration files (Issue #10999)

[Chris Drake]

gvim on windows 11 does not appear to be reading my .vimrc or _vimrc or vimfiles\vimrc file (I tried all 3).
:help vimrc also doesn't seem to be clear about what's going on.

the gvim --help command should display to us exactly what the code is actually looking for, so we don't have to guess.

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10999@github.com>

[Tony Mechelynck]

1. Start Vim or gvim.
2. ":help startup" is the chapter about what Vim does at startup.
   It is a rather long chapter, you may have to scroll to read it all. As it says at the end of § 3.d., "(*)" means "if this file is found, Vim will start in 'nocompatible' mode".

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10999/1229455814@github.com>

[Bram Moolenaar]

What "gvim --help" does tell you is the "-V" option: gvim -V9 might reveal what is going on.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10999/1229512589@github.com>

[Christian Brabandt]

you can also check :version output:

You can then use :e $HOME/vimfiles/vimrc to open/edit the vimrc file.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10999/1229842897@github.com>

[Tony Mechelynck]

On Mon, Aug 29, 2022 at 8:39 AM Christian Brabandt <vim-dev...@256bit.org> wrote:

you can also check :version output:

You can then use :e $HOME/vimfiles/vimrc to open/edit the vimrc file.

—

The attached is the same but in English and on Linux:

Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10999/1229842897@github.com>

--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/10999/1229842897%40github.com.

[vim-dev ML]

On Mon, Aug 29, 2022 at 8:39 AM Christian Brabandt <
***@***.***> wrote:

> you can also check :version output:
> [image: image]

> <https://user-images.githubusercontent.com/244927/187138462-1944adb6-5990-422c-87bf-b15590c7a496.png>

> You can then use :e $HOME/vimfiles/vimrc to open/edit the vimrc file.
>
> —
>
The attached is the same but in English and on Linux:

Reply to this email directly, view it on GitHub

> <https://github.com/vim/vim/issues/10999#issuecomment-1229842897>.
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>

>
> --
> --
> You received this message from the "vim_dev" 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_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to ***@***.***

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/10999/1229842897%40github.com

> <https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/10999/1229842897%40github.com?utm_medium=email&utm_source=footer>
> .
>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10999/1230988854@github.com>