Makes sense, that explains it. Thanks!
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Pierre Neidhardt writes:
>> In practice only a subset of these grafts are applied because, for
>> instance, Fish doesn’t depend (directly or indirectly) on Ghostscript at
>> run time whereas it does depend on Perl:
>>
>> --8<---cut here---start->8---
>> $ gui
Pierre Neidhardt skribis:
>> A package will be grafted when any
>> of its inputs (direct or transitive) have been replaced.
>
> I understand why that would happen when _updating_ fish, but why does it
> happen
> when (re-)building it from scratch, for instance when the graft source is gone
> fro
Pierre Neidhardt skribis:
> - Is the issue here that grafting does not support wide string literals?
> Shouldn't we fix the Guix code to support wide strings as well?
I’m not too keen on doing that: the scanner in (guix build grafts) would
have to be quite different if it were to catch /gnu/st
> A package will be grafted when any
> of its inputs (direct or transitive) have been replaced.
I understand why that would happen when _updating_ fish, but why does it happen
when (re-)building it from scratch, for instance when the graft source is gone
from the store?
--
Pierre Neidhardt
http
Pierre Neidhardt writes:
> I'm not so well versed in grafting, so let me ask a few questions:
>
> - Why is fish grafted in the first place?
Almost any package can be grafted. A package will be grafted when any
of its inputs (direct or transitive) have been replaced. The goal of
grafting is t
Hi Pierre,
Pierre Neidhardt skribis:
> I think Ricardo got a hunch of what's happening, except that it's not
> about cache files in the user home's directory. Instead, Fish seems to
> record the path to the graft source. A grep in the fish folder does not
> seem to reveal anything, nor does `s
On Sat, 27 Jan 2018, l...@gnu.org (Ludovic Courtès) wrote:
> Hi ng0 and Meiyo,
>
> n...@n0.is skribis:
>
>> On Sat, 27 Jan 2018, Meiyo Peng wrote:
>>> Hi,
>>>
>>> I am using GuixSD 0.14. After upgrading fish shell to latest
>>> version(v2.7.1) and
>>> running `guix gc`, fish shell does not work w
Hi ng0 and Meiyo,
n...@n0.is skribis:
> On Sat, 27 Jan 2018, Meiyo Peng wrote:
>> Hi,
>>
>> I am using GuixSD 0.14. After upgrading fish shell to latest version(v2.7.1)
>> and
>> running `guix gc`, fish shell does not work well.
>
> Can you explain a bit more about your setup? I assume you use
ng0 wrote:
> Can you explain a bit more about your setup? I assume you use
> fish as you user shell and not just as a shell you switch into
> from a Bash enabled user, correct?
My GuixSD is a fresh setup. I did no customization to fish and did not
set fish as login shell.
The bug I reported is r
Ricardo Wurmus writes:
> Where are these environment variables defined?
According to `share/fish/config.fish`, they are defined in fish.cpp.
#+BEGIN_SRC fish
# __fish_datadir, __fish_sysconfdir, __fish_help_dir, __fish_bin_dir
# are expected to have been set up by read_init from fish.cpp
#+EN
Hi Meiyo,
thanks for the report.
> I am using GuixSD 0.14. After upgrading fish shell to latest version(v2.7.1)
> and
> running `guix gc`, fish shell does not work well.
[…]
> Fish shell is installed in:
> #+BEGIN_EXAMPLE
> /gnu/store/ajbbi9cgj9j0my7v5habp0lcysaf2a51-fish-2.7.1/
> #+END_EXAMP
Hi Meiyo,
thanks for your report. Indeed, Fish has some problems in Guix.
On Sat, 27 Jan 2018, Meiyo Peng wrote:
> Hi,
>
> I am using GuixSD 0.14. After upgrading fish shell to latest version(v2.7.1)
> and
> running `guix gc`, fish shell does not work well.
Can you explain a bit more about you
Hi,
I am using GuixSD 0.14. After upgrading fish shell to latest version(v2.7.1) and
running `guix gc`, fish shell does not work well.
#+BEGIN_EXAMPLE
meiyo@guix ~$ fish
fish:
echo $_ " "; __fish_pwd
^
in command substitution
called on standard input
fish:
__f
14 matches
Mail list logo
