all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Meiyo Peng <meiyo@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: Plan for fish shell in Guix.
Date: Mon, 21 Jan 2019 16:30:50 -0800	[thread overview]
Message-ID: <7931354B-E366-433E-B3CA-D6A0B8A90A71@asu.edu> (raw)
In-Reply-To: <871s562yyc.fsf@disroot.org>

Hello,

I just have one issue with the patch so far:  I can’t seem to unset an abbreviation. An old configuration file seems to be “sticking” around for lack of better term. Otherwise, good stuff!

John

> On Jan 21, 2019, at 12:32 AM, Meiyo Peng <meiyo@disroot.org> wrote:
> 
> Hello everyone,
> 
> Thank you for your patience.
> 
> I investigated the problem and chose to parse /etc/profile from fish
> rather than generate separate configuration files for fish.  I think
> this will make the Guix project easier to maintain in the future.
> 
> I looked NixOS's solution.  They choose this approach too, but their
> patch is more complex.  I implemented my patch in a minimalistic manner.
> 
> The patch has been sent to guix-patches@gnu.org:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34153
> 
> I set fish as my login shell and every thing is working well.  Please
> try the patch and report bugs if you are interested.
> 
> Thanks.
> 
> 
> --
> Meiyo Peng
> https://www.pengmeiyu.com/
> 

  parent reply	other threads:[~2019-01-22  0:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07  9:25 Plan for fish shell in Guix Meiyo Peng
2019-01-07 11:36 ` Ricardo Wurmus
2019-01-07 11:45   ` Gábor Boskovits
2019-01-07 12:04     ` zimoun
2019-01-21  8:32 ` Meiyo Peng
2019-01-21 20:57   ` John Soo
2019-01-22  0:52     ` Meiyo Peng
2019-01-22  0:30   ` John Soo [this message]
2019-01-22  1:24     ` Meiyo Peng
2019-01-22  2:22       ` John Soo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7931354B-E366-433E-B3CA-D6A0B8A90A71@asu.edu \
    --to=jsoo1@asu.edu \
    --cc=guix-devel@gnu.org \
    --cc=meiyo@disroot.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.