From: Julien Lepiller <julien@lepiller.eu>
To: yasu@yasuaki.com
Cc: help-guix@gnu.org
Subject: Re: How do I install neovim plugins?
Date: Sat, 19 Sep 2020 19:41:19 -0400 [thread overview]
Message-ID: <E5B057F5-D6DF-4901-915B-51044AFEF5BB@lepiller.eu> (raw)
In-Reply-To: <3cd347998081391e3d1666ad12889e9a@yasuaki.com>
Le 19 septembre 2020 19:18:14 GMT-04:00, yasu@yasuaki.com a écrit :
>Hi Julien,
>
>Thank you for the pointer, here is what I did to make it work:
>
> set runtimepath+=/home/yasu/.guix-profile/share/vim/vimfiles
>
>The plugin and neovim were installed as below:
>
>guix package --install=vim-airline
>guix package --install=nvim
Great! Glad I could help :)
>
>But this seems rather "imperative" and is not what I expected to do,
>after spending many weeks trying home-manager from NixOS :-)
>
>excerpt from .config/nixpkgs/home.nix
>...
> programs.neovim = {
> enable = true;
> plugins = [
> pkgs.vimPlugins.vim-airline
> pkgs.vimPlugins.vim-nix
> ];
>...
>
>In the Nix world, I think people were not seeing much point of:
>
> nix-env -i
>
>which seems to be their equivalent of:
>
> guix package --install=
>
>As an alternative, 'home-manger' seemed popular.
>
>Would you say the same for Guix as well?
I agree, this is very imperative, but since we don't have an equivalent of the home manager (except for my channel which is not very popular because I don't recommend it for everyday use), this the kind of thing we usually do.
Actually, the most popular in guix is rather to set some *PATH environment variable, sometimes even patching the software to honor them. But we don't have any for neovim.
The equivalent of your home.nix example would be:
(user-home
neovim-home-type
(neovim-confiquration
(plugins (list neovim-airline neovim-nix))))
(Assuming we actually have these packages)
The guix home manager follows the spirit of functionnal management closer than the nix home manager, because itqmakes your entire home a symlink to a store path, whereas nix home only overwrites some files that can later be modified imperatively (by you or a software). That makes it harder to use and breaks many software, but is much more satisfying :)
>
>-Yasu
>
>
>
>On 19.09.2020 23:40, Julien Lepiller wrote:
>> If you install plugins in your profile, you can add:
>>
>> set runpath+=/home/user/.guix-profile/share/nvim/site
>>
>> In your .config/nvem/init.vim
>>
>> I also have a guix-home-manager at
>> https://framagit.org/tyreunom/guix-home-manager but it's more
>> involved.
>>
>> Le 19 septembre 2020 10:04:45 GMT-04:00, Yasuaki Kudo
>> <yasu@yasuaki.com> a écrit :
>>
>>> I see some vim plugin packages for guix but I have no idea how I
>>> enable them in the neovim (nvim) that I installed in Guix.
>>>
>>> In NixOS I just used "home manager" and modified some existing
>>> template I found to add more plugins.
next prev parent reply other threads:[~2020-09-19 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 14:04 How do I install neovim plugins? Yasuaki Kudo
2020-09-19 14:40 ` Julien Lepiller
2020-09-19 23:18 ` yasu
2020-09-19 23:41 ` Julien Lepiller [this message]
2020-09-20 0:17 ` John Soo
2020-09-20 0:33 ` Yasuaki Kudo
2020-09-20 0:19 ` Yasuaki Kudo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E5B057F5-D6DF-4901-915B-51044AFEF5BB@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=yasu@yasuaki.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).