Hey,
I was toying with the idea of automatically detecting discrepancies in
environment variables, so I tried the attached patch, which would check
/proc/PID/environ compared to the profile’s search path variables.
Unfortunately, that doesn’t work because Bash for instance does not
change its
Ludovic Courtès writes:
> Hi!
>
> Danny O'Brien skribis:
>
>> Brendan Tildesley writes:
>>
>>> Doom Emacs has a tool `doom doctor' for diagnosing common
>>> errors. Perhaps there
>>> could be a `guix doctor' that would check for such things. `guix
>>> offload test'
>>> is already somewhat
Hi!
Danny O'Brien skribis:
> Brendan Tildesley writes:
>
>> Doom Emacs has a tool `doom doctor' for diagnosing common
>> errors. Perhaps there
>> could be a `guix doctor' that would check for such things. `guix
>> offload test'
>> is already somewhat like that but for offloading, althought it
Doom Emacs has a tool `doom doctor' for diagnosing common errors.
Perhaps there could be a `guix doctor' that would check for such things.
`guix offload test' is already somewhat like that but for offloading,
althought it could improve. Any bug report from a user where the
solution is to tell
Hello Guix!
One thing that often trips up newcomers, especially on other distros, is
the interaction of ‘guix environment’ and ‘.bashrc’ etc. when it comes
to setting environment variables. Often the first experience is “why
doesn’t ‘guix environment’ set environment variables correctly?”.
The
