From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>,
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 52347@debbugs.gnu.org, cayetano.santos@inventati.org
Subject: bug#52347: Shell: error when -m manifest is removed
Date: Tue, 07 Dec 2021 17:23:38 +0100 [thread overview]
Message-ID: <ac62d1852dd3c3d13dd80e1a52cec1db0a3bccd4.camel@gmail.com> (raw)
In-Reply-To: <CAJ3okZ0=MEowKqttsYZazSm6V14RFJZj7DmR93Wq1872x8-KHg@mail.gmail.com>
Am Dienstag, den 07.12.2021, 15:27 +0100 schrieb zimoun:
> Hi,
>
> On Tue, 7 Dec 2021 at 14:48, Liliana Marie Prikler
> <liliana.prikler@ist.tugraz.at> wrote:
>
> > I am pretty sure all files are owned by the same user in my
> > case. Can
> > stat:uid really return 0 then?
>
> Maybe I am doing wrong but I just 'pk' in find-file-in-parent-
> directories. :-)
You are doing wrong:
(if (or (not interactive?) ; true if giving -- COMMAND
disallow-implicit-load?
(options-contain-payload? opts))
So the pk in find-file-in-parent-directories should not even fire. I'm
pretty sure the interactive constraint has a reasoning that was
explained back then, so we should investigate carefully whether we want
to overthrow that. Warning, that noninteractive use of `guix shell'
requires an explicit manifest is also an option imo.
By the way, if we do search for a file, but find none, the warning
(warning (G_ "no packages specified; creating an empty environment~%"))
is displayed twice; once by auto-detect-manifest and once by guix-
environment*. We should probably change that string to something that
indicates that we've attempted to auto-load a manifest.
Cheers
next prev parent reply other threads:[~2021-12-07 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 8:33 bug#52347: Shell: error when -m manifest is removed Cayetano Santos via Bug reports for GNU Guix
2021-12-07 9:26 ` zimoun
2021-12-07 10:07 ` Cayetano Santos via Bug reports for GNU Guix
2021-12-07 10:18 ` zimoun
2021-12-07 10:23 ` Cayetano Santos via Bug reports for GNU Guix
2021-12-07 10:35 ` zimoun
2021-12-07 10:42 ` Cayetano Santos via Bug reports for GNU Guix
2021-12-07 13:12 ` zimoun
2021-12-07 13:33 ` Liliana Marie Prikler
2021-12-07 13:41 ` zimoun
2021-12-07 13:48 ` Liliana Marie Prikler
2021-12-07 14:27 ` zimoun
2021-12-07 16:23 ` Liliana Marie Prikler [this message]
2021-12-07 17:11 ` zimoun
2021-12-07 12:02 ` Maxime Devos
2021-12-07 18:11 ` Cayetano Santos via Bug reports for GNU Guix
2021-12-07 19:06 ` Maxime Devos
2021-12-22 22:42 ` Ludovic Courtès
2021-12-22 22:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac62d1852dd3c3d13dd80e1a52cec1db0a3bccd4.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=52347@debbugs.gnu.org \
--cc=cayetano.santos@inventati.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=zimon.toutoune@gmail.com \
/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.