From: "René Berber" <rene.berber@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Vim gives error message since 8.2.3755-1
Date: Sun, 24 Jul 2022 21:52:10 -0500 [thread overview]
Message-ID: <d8734a8b-7570-9551-e973-2027c0ba9900@gmail.com> (raw)
In-Reply-To: <982613274.886853.1658711514654@mail.yahoo.com>
On 7/24/2022 8:11 PM, Thomas DiModica via Cygwin wrote:
> Since 8.2.3755-1, Vim has given me an error message about being
> unable to open the defaults.vim file whenever I open a file with vi.
> I do not see this message with 8.2.0486-1. Notably, vi --version for
> the last two updates tell me that the user vimrc file is
> "/home/Marco/.virc", rather than "$HOME/.virc". [snip]
Depends on what you are really using, my vim is the alias of vi, and the
"user vimrc file: "$HOME/.vimrc", not .virc
$ which vi
/usr/bin/vi
$ type vi
vi is aliased to `vim'
$ vi --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb 13 2022 22:15:51)
...
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
...
My guess is that one of those files have changed things up.
Also I think vim detects that it was called with an alias, and may
behave differently.
--
R.B.
WARNING: multiple messages have this Message-ID
From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Vim gives error message since 8.2.3755-1
Date: Sun, 24 Jul 2022 21:52:10 -0500 [thread overview]
Message-ID: <d8734a8b-7570-9551-e973-2027c0ba9900@gmail.com> (raw)
Message-ID: <20220725025210.hMppmm6jmS3ycgKbYEe-xEf-5a3pbRTC4XMaTnXqJXA@z> (raw)
In-Reply-To: <982613274.886853.1658711514654@mail.yahoo.com>
On 7/24/2022 8:11 PM, Thomas DiModica via Cygwin wrote:
> Since 8.2.3755-1, Vim has given me an error message about being
> unable to open the defaults.vim file whenever I open a file with vi.
> I do not see this message with 8.2.0486-1. Notably, vi --version for
> the last two updates tell me that the user vimrc file is
> "/home/Marco/.virc", rather than "$HOME/.virc". [snip]
Depends on what you are really using, my vim is the alias of vi, and the
"user vimrc file: "$HOME/.vimrc", not .virc
$ which vi
/usr/bin/vi
$ type vi
vi is aliased to `vim'
$ vi --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb 13 2022 22:15:51)
...
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
...
My guess is that one of those files have changed things up.
Also I think vim detects that it was called with an alias, and may
behave differently.
--
R.B.
next prev parent reply other threads:[~2022-07-25 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <982613274.886853.1658711514654.ref@mail.yahoo.com>
2022-07-25 1:11 ` Thomas DiModica
2022-07-25 2:52 ` René Berber [this message]
2022-07-25 2:52 ` René Berber
2022-07-25 9:37 ` marco atzeri
2022-07-25 17:41 ` John Ruckstuhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8734a8b-7570-9551-e973-2027c0ba9900@gmail.com \
--to=rene.berber@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).