all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Plan for fish shell in Guix.
Date: Mon, 7 Jan 2019 12:45:46 +0100	[thread overview]
Message-ID: <CAE4v=pi8+Apq5VJskwh6a+4_g9c3jJ+cbCRM7jy7+g-OFUzeeA@mail.gmail.com> (raw)
In-Reply-To: <87k1jgr97e.fsf@elephly.net>

Hello,

this seems to be one of the problem points that comes around again and again.

Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2019. jan. 7., H, 12:37):
>
>
> Hi,
>
> > I plan to make Guix more friendly for fish shell, so that users can set
> > fish shell as their login shell.
>
> Thank you for taking the initiative.

Yes, thank you.

There is also a problem that often manifest on Debian and derivatives,
where /bin/sh is dash, as
some parts of the current generated script, and also some of our hints
imply bash.

Another problem on Debian like systems, is that the startup scripts
are ran in a distribution specific manner,
so for example the XDG_DATA_DIR environment should be set up in
.xsessionrc, as that is the only startup
script running on GUI session initialization... I guess there might be
other distro specific problems.

It might be worthy to have a look at other shells too, have a list
which ones are supported, or how could support be improved.

Best regards,
g_bor

  reply	other threads:[~2019-01-07 11:46 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 [this message]
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
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='CAE4v=pi8+Apq5VJskwh6a+4_g9c3jJ+cbCRM7jy7+g-OFUzeeA@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.