{"action":"created","issue":{"url":"https://api.github.com/repos/neovim/neovim/issues/8871","repository_url":"https://api.github.com/repos/neovim/neovim","labels_url":"https://api.github.com/repos/neovim/neovim/issues/8871/labels{/name}","comments_url":"https://api.github.com/repos/neovim/neovim/issues/8871/comments","events_url":"https://api.github.com/repos/neovim/neovim/issues/8871/events","html_url":"https://github.com/neovim/neovim/issues/8871","id":351804049,"node_id":"MDU6SXNzdWUzNTE4MDQwNDk=","number":8871,"title":"[RFE] system-wide configuration file on Unix (with merging-in options)","user":{"login":"mcepl","id":198999,"node_id":"MDQ6VXNlcjE5ODk5OQ==","avatar_url":"https://avatars1.githubusercontent.com/u/198999?v=4","gravatar_id":"","url":"https://api.github.com/users/mcepl","html_url":"https://github.com/mcepl","followers_url":"https://api.github.com/users/mcepl/followers","following_url":"https://api.github.com/users/mcepl/following{/other_user}","gists_url":"https://api.github.com/users/mcepl/gists{/gist_id}","starred_url":"https://api.github.com/users/mcepl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcepl/subscriptions","organizations_url":"https://api.github.com/users/mcepl/orgs","repos_url":"https://api.github.com/users/mcepl/repos","events_url":"https://api.github.com/users/mcepl/events{/privacy}","received_events_url":"https://api.github.com/users/mcepl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-08-18T08:49:15Z","updated_at":"2018-08-18T14:28:01Z","closed_at":null,"author_association":"NONE","body":"- `nvim --version`:\r\n\r\n    NVIM v0.3.2-dev\r\n    Build type: RelWithDebInfo\r\n    Lua 5.3\r\n    Compilation: /usr/bin/cc -Wconversion -DMIN_LOG_LEVEL=3 -Og -g -Wall -Wextra -pedantic\r\n    -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla\r\n    -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds\r\n    -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE\r\n    -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM\r\n    -I/home/abuild/rpmbuild/BUILD/neovim-0.3.1+git.1534330940.b5cfac089/build/config\r\n    -I/home/abuild/rpmbuild/BUILD/neovim-0.3.1+git.1534330940.b5cfac089/src -I/usr/include\r\n    -I/home/abuild/rpmbuild/BUILD/neovim-0.3.1+git.1534330940.b5cfac089/build/src/nvim/auto\r\n    -I/home/abuild/rpmbuild/BUILD/neovim-0.3.1+git.1534330940.b5cfac089/build/include\r\n     \r\n     Features: +acl +iconv +jemalloc +tui \r\n     See \":help feature-compile\"\r\n     \r\n     systémový vimrc soubor: \"$VIM/sysinit.vim\"\r\n     implicitní hodnota $VIM:\"/usr/share/nvim\"\r\n    \r\n    Run :checkhealth for more info\r\n\r\n- Vim (version: ) behaves differently?\r\n\r\nNo, exactly the same problem.\r\n\r\n- Operating system/version:\r\n\r\nLinux, openSUSE Tumbleweed 20180812, but the issue is non-distro specific, applies to any Unix-like system (perhaps Windows as well)\r\n\r\n- Terminal name/version: gnome-terminal, but that's really unnecessary\r\n- `$TERM`: xterm-256color\r\n\r\n### Steps to reproduce using `nvim -u NORC`\r\n\r\nWell, that's exactly the point. Many Unix utilities (``mutt`` is one nice example) uses two-tier system of configuration files. To quote [MuttGuide](https://gitlab.com/muttmua/mutt/wikis/MuttGuide/Syntax):\r\n\r\n    Mutt reads its configuration by default 1st from a system-wide\r\n    config-file (\"/etc/Muttrc\"), which normally controls system settings and\r\n    provides viable default personal settings for all users, then it reads\r\n    the personal config file (\"~/.muttrc\" or \"~/.mutt/muttrc\"). This way the\r\n    personal settings override system settings as needed.\r\n\r\nI would love to see the same behaviour for neovim. Currently ``:he vimrc`` repeats couple of times something in style:\r\n\r\n    The files are searched in the order specified above and only the first\r\n    one that is found is read.\r\n\r\nWhich is true, but exactly the behaviour which I don't like. **ALL** configuration files (in the given order, and the list shouldn't be too long, configurable during the compile time preferably) should be read in the given order and their values incrementally merged.\r\n\r\n### Actual behaviour\r\n\r\nSee above, only one file is considered.\r\n\r\n### Expected behaviour\r\n\r\nAll files should be read, and values merged.\r\n\r\nI would think that the bug like this should have been already filed here, but I really couldn't find. There was a lot of discussion about location of files (XDG specification), but not about this merging values. Or at least I wasn't able to find one."},"comment":{"url":"https://api.github.com/repos/neovim/neovim/issues/comments/414061777","html_url":"https://github.com/neovim/neovim/issues/8871#issuecomment-414061777","issue_url":"https://api.github.com/repos/neovim/neovim/issues/8871","id":414061777,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNDA2MTc3Nw==","user":{"login":"jamessan","id":112971,"node_id":"MDQ6VXNlcjExMjk3MQ==","avatar_url":"https://avatars0.githubusercontent.com/u/112971?v=4","gravatar_id":"","url":"https://api.github.com/users/jamessan","html_url":"https://github.com/jamessan","followers_url":"https://api.github.com/users/jamessan/followers","following_url":"https://api.github.com/users/jamessan/following{/other_user}","gists_url":"https://api.github.com/users/jamessan/gists{/gist_id}","starred_url":"https://api.github.com/users/jamessan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamessan/subscriptions","organizations_url":"https://api.github.com/users/jamessan/orgs","repos_url":"https://api.github.com/users/jamessan/repos","events_url":"https://api.github.com/users/jamessan/events{/privacy}","received_events_url":"https://api.github.com/users/jamessan/received_events","type":"User","site_admin":false},"created_at":"2018-08-18T14:28:01Z","updated_at":"2018-08-18T14:28:01Z","author_association":"MEMBER","body":"> With the resolution of vim/vim#2042, this is a wontfix\r\n\r\nVim's problem is completely different.  The issue there is that _some_ of the defaults are provided by defaults.vim, rather than being builtin.  The \"defaults\" in defaults.vim are loaded after the system-wide config, since they are only loaded if the user doesn't have a vimrc.  In effect, this means that although Vim supports a system-wide configuration file, it is completely ignored in terms of how that interacts with the second-tier defaults.\r\n\r\nSince nvim's defaults are all builtin, this is a non-issue.  The correct precedence is still followed, where the system-wide configuration is overridden by the user's configuration (and plugins)."}}
{"actor":{"display_login":"jamessan"}}