.nvimrc instead of .neovimrc

[justinmk]

Since the binary is nvim, shouldn't the rc files be .nvimrc, .nviminfo, etc.?

#44 added support for .neovimrc, then #113 changed the binary to nvim, so maybe this got overlooked.

It's possible that .nvimrc may collide with some existing utility, but a quick web search doesn't suggest any problems.

[felipecrv]

+1 for this. I think it was decided to use .neovimrc before the
executable name decision.

On Sat, Mar 1, 2014 at 4:13 AM, justinmk notifications@github.com wrote:

Since the binary is nvim, shouldn't the rc files be .nvimrc, .nviminfo,
etc.?

#44 #44 added support for .neovimrc,
then #113 #113 changed the binary
to nvim, so maybe this got overlooked.

It's possible that .nvimrc may collide with some existing utility, but a
quick web search doesn't suggest any problems.

Reply to this email directly or view it on GitHubhttps://github.com//issues/235
.

[notpratheek]

+1

[ZyX-I]

I think that neovim should follow XDG base directory specification and name it rc.vim. .config/neovim/rc.vim to be specific (see #78).

[felipecrv]

.config/nvim/rc.vim
On Mar 1, 2014 12:15 PM, "ZyX-I" notifications@github.com wrote:

I think that neovim should follow XDG base directory specification and
name it rc.vim. .config/neovim/rc.vim to be specific (see #78#78
).

Reply to this email directly or view it on GitHubhttps://github.com//issues/235#issuecomment-36427046
.

[notpratheek]

@ZyX-I

Any specific/important reason to follow XDG base directory specification ? What's wrong with having the way vim stores stuff, in the home directory as a hidden folder ? (I want to mention that this is not a rhetorical question, but a serious one 😁 !)

[dtinth]

In #149, however, several people prefer that the executable be named neovim instead of nvim, and then it makes perfect sense to use .neovimrc.

Do we need voting again (this time on the executable and rc filename/path)?

---

@Pychimp based on what I search about XDG Base Directory Specification, people said that following it would

• make home directory cleaner and clearly separate configuration, cache, and user data,
• which allows for efficient backup, and
• makes it easier to clear preferences/cache without losing user data, and gives us more flexibility due to path not being hardcoded.

Several applications have switched to it now, and I think that it is a nice idea if neovim join this movement as well.

[justinmk]

@dtinth the binary name was already decided. It's just that that didn't happen until after the support for .neovimrc was added. Avoid another vote, I hope.

[ZyX-I]

Any specific/important reason to follow XDG base directory specification ? What's wrong with having the way vim stores stuff, in the home directory as a hidden folder ? (I want to mention that this is not a rhetorical question, but a serious one !)

XDG base directory specification was introduced because home directory turns into a garbage without it: it is main my reason. @dtinth has shown other reasons as well.

[notpratheek]

@dtinth @ZyX-I

Thanks for the explanation ! 😄

[scott-linder]

This inconsistency has been brought up a couple times now without a clear decision: the config file names and binary names were decided separately by separate "votes" in their respective issues and then merged; we should probably have a more formal vote and stick with it?

[mahkoh]

Since the configuration file is read only, the XDG question seems to be irrelevant. Simply source both paths and let the user choose which one he likes better.

[JackMc]

+1

[vonbirdie]

I don't think XDG or not is irrelevant. We have a chance to do things right without giving much regard to previous implementations and choosing a mix feels worse than picking either one.

I'd prefer XDG to try and unclutter the home folder and to make things more consistent.

I think someone needs to decide whether we should use nvim or neovim though and after that we should use that everywhere. I know there's been a lot of talk about it and votes here and there but not sure how formal or whom has taken what decision so someone should probably clear that up.

[mahkoh]

I strongly prefer configuration files in ~. This has nothing to do with giving regard to previous implementations.

XDG is hardly standard and even those programs that use .config don't follow it. Claims that .config is easier to back up are dubious.

The code needed to source both files is negligible compared to the code needed to build the XDG path.

[trusktr]

My 2 cents:

1. I feel the config file name is better if it resembles the command name.
2. I also feel the naming of the project would be nicer if it matched the command name.

[ZyX-I]

1. I feel the config file name is better if it resembles the command name.

It makes sense when it is located in home folder. If it is located in ~/.config/neovim then ~/.config/neovim/neovimrc is a tautology. It is then better that config name resemble config purpose. So no neovimrc. rc.vim is not the best thing as well, even though it was suggested by me. init.vim or startup.vim would be better. // Updated #78 to replace rc.vim with startup.vim.

1. I also feel the naming of the project would be nicer if it matched the command name.

I generally agree on this case. But for programs that I am going to launch frequently it is best to use shorter name. I can, of course, use shell aliases, but if I aliase neovim to e.g. nv I will still have to write neovim when speaking in public places (e.g. IRC, github issues, mailings lists and so on). So for neovim I would prefer to use shorter command name while keeping project name long. It is not an uncommon practice: all popular VCS except git use this (hg/mercurial, svn/subversion, bzr/bazaar), 7z/7-zip. That’s all though: cannot remember anything else except for the fact that nearly any other name is an abbreviation of something.

[wilbertom]

Hey guys. I tried implementing this. Now all we have to do is decide and double check I got all the needed changes.

[trusktr]

@wilbertom +1 👍

[fastcppcoder]

+1 to use nvimrc

[simendsjo]

I have to vote for either .neovimrc or .nvimrc. I don't care which one of these though.
Naming it just rc.vim or similar is pretty awful if you symlink files. I like the filename to state what it does rather than its location.
Vim defaults to ~/.vimrc, so I think we also should put it in the home folder.

[tarruda]

👍 nvimrc

[wilbertom]

@trusktr thank you.

[tarruda]

closed by #330