Wednesday, August 10, 2022

Re: New version of vim unsolicitedly sourcing defaults.vim?

On Wed, Aug 10, 2022 at 11:07:55AM +0100, Bram Moolenaar wrote:
>Tim Chase wrote:
>> Yep, as Yegappan found, this bug is tracking the issue at hand:
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251420
>>
>> I've got a FreeBSD Bugzilla account and will follow up there.
[snip]
> An alternative would be to check if ~/.vimrc exists, and only load
> defaults.vim then. Then it's closer to what Vim normally does (but then
> the overrides may still confuse the user).

That's one of the solutions I proposed in that bug-tracking URL,
though it's complicated because it's not just a .vimrc but according
to docs, but it sounds like ~/.vim/vimrc or ~/_vimrc or ~/.exrc or
~/_exrc or $MYVIMRC or $VIMINIT or $VIM or $EXINIT might also prevent
defaults.vim from loading. And I'm not 100% certain that list is
complete.

So it sounds like it would require a big chained if-statement testing
filereadable() on all of those sources and only sourcing defaults.vim
if *none* of them exist.

-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 on the web visit https://groups.google.com/d/msgid/vim_use/YvOw4yi%2BvaJQutWn%40thechases.com.

No comments: