From: ludo@gnu.org (Ludovic Courtès)
To: 27206@debbugs.gnu.org
Subject: bug#27206: Fish: figure out a solution for the vendor path extension to fish
Date: Thu, 03 Aug 2017 00:11:45 +0200 [thread overview]
Message-ID: <871sotsjq6.fsf@gnu.org> (raw)
In-Reply-To: <20170603105132.birbtxvakprht5wx@abyayala> (ng0@pragmatique.xyz's message of "Sat, 3 Jun 2017 10:51:32 +0000")
ng0 <ng0@pragmatique.xyz> skribis:
> ng0 transcribed 0.4K bytes:
>> A feature-bug I forgot to report a while ago.
>> It has been described on the mailinglist (or was
>> it in my blog or some release announcement I made?)
>>
>> Fish doesn't pick up stuff like 'fish-guix' from store
>> without modifications to the path where fish searches
>> for vendor or sysadmin installed systemwide 'things'
>> for fish.
>
> I have many more fish packages in a branch which
> I want to get into guix, but they are stuck because
> of this. Help welcome, otherwise I'll promise to
> fix it one day.
>
> Currently the only workaround is to symlink individual files from your
> ~/.guix-profile/whereever/things/went/ to ~/.config/fish/{approriate subdirs}
Does Fish have an environment variable that can be used to specify the
search path for extensions, similar to BASH_LOADABLES_PATH? If it does,
we could use that.
Otherwise, perhaps we can consider it an upstream issue in a way?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-08-02 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 10:41 bug#27206: Fish: figure out a solution for the vendor path extension to fish ng0
2017-06-03 10:51 ` ng0
2017-08-02 22:11 ` Ludovic Courtès [this message]
2017-08-02 22:42 ` ng0
2018-01-14 18:42 ` ng0
2019-01-07 3:45 ` Meiyo Peng
2019-02-02 7:02 ` Meiyo Peng
2019-02-04 22:13 ` 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=871sotsjq6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27206@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).