Re: [Nix-dev] YouCompleteMe in 16.09

2017-03-19 Thread Tilo Schwarz
Thank you all for your replies, now I have to digest it ... (I think what most "normal" users would expect: After plugin installation, vim "just finds" the new plugin after restart.) Tilo On Sun, Mar 19, 2017 at 1:10 PM ben...@gmail.com wrote: > AFAIK it currently does not.

Re: [Nix-dev] YouCompleteMe in 16.09

2017-03-19 Thread ben...@gmail.com
AFAIK it currently does not. And I agree, it would be a better user experience if that were the case. On Sun, Mar 19, 2017 at 4:06 PM, Bjørn Forsman wrote: > On 19 March 2017 at 20:50, ben...@gmail.com wrote: >> That results in just a `vim` executable

Re: [Nix-dev] YouCompleteMe in 16.09

2017-03-19 Thread Bjørn Forsman
On 19 March 2017 at 20:50, ben...@gmail.com wrote: > That results in just a `vim` executable that does not load any user > .vimrc at startup, and none of the other binaries like > gvim/xxd/vimdiff. What I'm after (and what I suspect most new users > expect to find) is something

Re: [Nix-dev] YouCompleteMe in 16.09

2017-03-19 Thread Vladimír Čunát
On 03/19/2017 08:33 PM, ben...@gmail.com wrote: > I keep wanting vim_configurable to produce a "normal" vim package > (including executables for gvim, xxd, vimdiff, etc) that has no > special behaviors other than having various plugins installed, but > there does not seem to be an easy way to

Re: [Nix-dev] YouCompleteMe in 16.09

2017-03-19 Thread ben...@gmail.com
Ha, you beat me to the post by like ten seconds! I see you use the same trick with sourcing ~/.vimrc in vim_configurable - now I am wondering, does anybody out there use it the way it appears it's intended to be used? I keep wanting vim_configurable to produce a "normal" vim package (including

Re: [Nix-dev] YouCompleteMe in 16.09

2017-03-19 Thread Vladimír Čunát
On 03/19/2017 08:15 PM, Tilo Schwarz wrote: > I try to get YouCompleteMe running. [...] > > What would be the "nixos-correct" way to proceed? I'm using a wrapper that includes my settings, plugins, etc. The code is something like this: # defined as `vim` alias within a set in