From: ng0 <ng0@pragmatique.xyz>
To: 26792@debbugs.gnu.org
Subject: bug#26792: Acknowledgement (Fix output of --help in package fish)
Date: Sat, 6 May 2017 11:36:33 +0000 [thread overview]
Message-ID: <20170506113633.elg5jvkhl7myfkkr@abyayala> (raw)
In-Reply-To: <20170506110353.zn67kryidtvmfhud@abyayala>
ng0 transcribed 0.9K bytes:
> ng0 transcribed 1.0K bytes:
> > I just created a new user which uses fish as the login shell and
> > I need to update this patch. There is more to be embeded for fish.
>
> This is similar to the "mc" situation.
>
> In a plain fish profile with no bash whatsoever, your default $PATH is:
>
> echo $PATH
> /usr /usr/bin
A correction: $PATH = /bin /usr/bin
> the major issue when logging in is:
>
> 1. grep is not found.
> 2. hostname is not found.
>
> The question to think about is, how do we provide access to the basic
> applications (grep, awk, hostname, etc) fish needs? Substituting a minimal
> set of files where necessary seems like the best working solution for a
> system which does not assume any other shell and therefore does initially
> export no $PATH other than /usr and /usr/bin.
>
> The very least I want people to experience is no error immediately after
> first login. This happens at the moment.
> --
> https://pragmatique.xyz
> PGP: https://people.pragmatique.xyz/ng0/
>
>
>
--
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/
next prev parent reply other threads:[~2017-05-06 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 0:56 bug#26792: Fix output of --help in package fish ng0
[not found] ` <handler.26792.B.149403223818956.ack@debbugs.gnu.org>
2017-05-06 10:44 ` bug#26792: Acknowledgement (Fix output of --help in package fish) ng0
2017-05-06 11:03 ` ng0
2017-05-06 11:36 ` ng0 [this message]
2017-05-06 13:53 ` bug#26792: Fix output of --help in package fish Ludovic Courtès
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=20170506113633.elg5jvkhl7myfkkr@abyayala \
--to=ng0@pragmatique.xyz \
--cc=26792@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).