unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Unstable Horse <stable.master@unstable.horse>
To: Alexis Simon <alexis.simon@runbox.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix + fish shell help
Date: Mon, 23 Oct 2023 11:47:02 +0200	[thread overview]
Message-ID: <d9a581d157b47170f6ec8a079f88fd62b7a7e9fd.camel@unstable.horse> (raw)
In-Reply-To: <9a496edb-8277-4b68-83c4-59f790458592@runbox.com>

On Sun, 2023-10-22 at 19:51 -0700, Alexis Simon wrote:

> If people could let me know how they've managed to set up fish
> properly 
> with guix this would be great.

I use fish as my login shell on GuixSD and this is my config.fish:

--8<---------------cut here---------------start------------->8---
if status is-login
  eval "$(guix package --search-paths \
    -p ~/.config/guix/current \
    -p ~/.guix-profile \
    -p /run/current-system/profile)"

  fish_add_path -P -p ~/.local/bin
  fish_add_path -P -p /run/setuid-programs
end
--8<---------------cut here---------------end--------------->8---

guix package --search-paths takes care of all the environment variables
needed for your profile, including PATH. Keep in mind that it overrides
these variables, it doesn't append. So if fish is not your login shell,
then you will need to re-apply you custom paths.

Also, if it isn't your login shell, then the is-login check should
probably be removed.


  reply	other threads:[~2023-10-26 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  2:51 guix + fish shell help Alexis Simon
2023-10-23  9:47 ` Unstable Horse [this message]
2023-10-23 17:32   ` Alexis Simon

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=d9a581d157b47170f6ec8a079f88fd62b7a7e9fd.camel@unstable.horse \
    --to=stable.master@unstable.horse \
    --cc=alexis.simon@runbox.com \
    --cc=help-guix@gnu.org \
    /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).