-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.nvimrc instead of .neovimrc #235
Comments
+1 for this. I think it was decided to use On Sat, Mar 1, 2014 at 4:13 AM, justinmk notifications@github.com wrote:
|
+1 |
I think that neovim should follow XDG base directory specification and name it |
.config/nvim/rc.vim
|
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 😁 !) |
In #149, however, several people prefer that the executable be named 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
Several applications have switched to it now, and I think that it is a nice idea if neovim join this movement as well. |
@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. |
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. |
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? |
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. |
+1 |
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. |
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. |
My 2 cents:
|
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
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 |
Hey guys. I tried implementing this. Now all we have to do is decide and double check I got all the needed changes. |
@wilbertom +1 👍 |
+1 to use nvimrc |
I have to vote for either |
👍 nvimrc |
@trusktr thank you. |
closed by #330 |
Since the binary is
nvim
, shouldn't the rc files be.nvimrc
,.nviminfo
, etc.?#44 added support for
.neovimrc
, then #113 changed the binary tonvim
, 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.The text was updated successfully, but these errors were encountered: