vimr no longer reads ~/.config/nvim/init.vim

[telemachus]

OS X: 10.12.1
vimr: Version 0.11.0-SNAPSHOT-20161111.2237 (124)

On start, vimr no longer seems to read (or respect) the settings I have in ~/.config/nvim/init.vim (for example, my colorscheme is not chosen, line numbers are not set, etc.). In addition, if I try to manually load the colorscheme I want with :colorscheme github, I get the error, "E185: Cannot find the color scheme 'github'". (I don't have these problems when using neovim in the terminal.)

[qvacua]

Does it also happen with https://github.com/qvacua/vimr/releases/tag/snapshot%2Fv0.11.0-SNAPSHOT-20161111.1436-123 ?

[telemachus]

Yes, that pre-release has the same problem. I must have missed that upgrade. I checked a few earlier upgrades as well:

• v0.10.1-122 is fine.
• v0.11.0-SNAPSHOT-20161109.2136-121 is the most recent snapshot that is also ok.

[qvacua]

Hm, that's very strange, I'll look into it.

[wookayin]

For me, I am using v0.11.0-SNAPSHOT-20161111.2237 and init.vim is read and applied well. Possibly an environment issue?

[qvacua]

Well, from 121/122 to 123 I added LANG="en_US.UTF-8" to the environment when launching the Neovim subprocess via $SHELL. (And something when doing Cmd-V which most probably does not interfere with init.vim.) @wookayin which macOS version are you using? I'm using 10.11.6 and init.vim is read fine. Maybe it's a 10.12-thing?

[telemachus]

For what it's worth, LANG is already set to `en_US.UTF-8" in my environment. I can't quite see how setting it again would hurt anything, but I obviously might be missing something.

(That said, do you really want to set all users' environment to en_US? Won't that affect, e.g. money or date handling in ways that British or German users might not want?)

[qvacua]

Yes, I also don't know how setting it (again) can do some harm.

Hm... I haven't considered it that far... I just wanted that non-ASCII characters are Cmd-Ced correctly. Does Neovim get affected by the LANG setting? 😶

[telemachus]

Does Neovim get affected by the LANG setting? 😶

I'm not entirely sure. I would have guessed yes, but maybe not. However, even if Neovim itself is not affected, what about commands run using !, e.g. :r !date?

I don't know enough about LANG settings to know how to do it, but it sounds like what you want is (i) to make sure that UTF-8 is set while (ii) leaving the user's actual language setting (if present) alone.

[qvacua]

I built a version based on 125 without the LANG-setting. @telemachus could you try it? http://taewon.de/vimr-test.tar.bz2

[timhatch]

-122 is the last one that works for me. I'm on OSX 10.11.6 also.
I'll re-download the other recent releases and check which also exhibit this problem on my machine.

[telemachus]

@qvacua That test version works for me. I'll use that for now until you sort out what the larger issue is. Thanks!

[qvacua]

Hm... So it really is that LANG-setting... Very strange...

[timhatch]

The test version picks up the settings in init.vim for me also
-125 was also creating a folder named "~" in the folder containing whichever file I was opening on launch. Hadn't noted that behaviour on any earlier version

[qvacua]

I could reproduce the behavior on a different machine running 10.12. I'm going to experiment a bit and if I cannot fix it today, I'll build a snapshot without the LANG-setting.

[qvacua]

Try https://github.com/qvacua/vimr/releases/tag/snapshot%2Fv0.11.0-SNAPSHOT-20161113.1502-126. I don't know why exactly, but setting LANG a bit later and somewhere else worked at least on my 10.12 machine...

[timhatch]

Yes, seems fine.

• Picking up my init.vim setting.
• No new folder created in the working directory

Common plugins working, so no obvious side-effects

[telemachus]

Yes, this works well for me too. Thanks.

I'll leave this open in case you want to check anything else, but as far as I'm concerned, you can close this report whenever you like.

[qvacua]

Closing, reopen if the problem pops up again.

[diedummydie]

This issue has returned with macOS Mojave 10.14 Beta and Snapshot 293.

If I issue the :source ~/.config/nvim/init.vim command manually, then it loads. In Terminal.app, nvim loads the config correctly. I also tried the old "v0.11.0-SNAPSHOT-20161113.1502-126" here, and that does work correctly; that old snapshot does load my init.vim.

[udp]

I also have the problem of VimR not finding init.vim.

:healthcheck shows:

but the file is definitely there and can be loaded manually with :source.

LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL=

Strangely, it works if I run VimR as root. The permissions seem fine however

-rwxrwxrwx  1 james  staff   111B Mar 29 10:24 /Users/james/.config/nvim/init.vim

[iamcco]

latest version have the same issue

[hcoona]

reproduce it as well

[wookayin]

I am using the latest version (v0.28.0-328) and have no issues. What does the $HOME variable point to?

[hcoona]

I am using the latest version (v0.28.0-328) and have no issues. What does the $HOME variable point to?

$HOME = /Users/shuaiz

[Furkanzmc]

This was closed but I can still reproduce this on macOS 10.4 and VimR Version 0.32.0 (344).
If I run VimR with sudo, the init.vim file is sourced but otherwise it's not. And I get the same result as James does.

[naktinis]

Setting HOME variable and running VimR with --cur-env seems to have helped me. Of course, this still seems like something that could be fixed on VimR side, because nvim runs without problems or extra arguments.