From: zimoun <zimon.toutoune@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
52347@debbugs.gnu.org, cayetano.santos@inventati.org
Subject: bug#52347: Shell: error when -m manifest is removed
Date: Tue, 7 Dec 2021 18:11:44 +0100 [thread overview]
Message-ID: <CAJ3okZ03sOCb5ZzSKxAaWeGYx+MEbFk3hYYvJLLfhEsxcN81oQ@mail.gmail.com> (raw)
In-Reply-To: <ac62d1852dd3c3d13dd80e1a52cec1db0a3bccd4.camel@gmail.com>
Hi,
On Tue, 7 Dec 2021 at 17:23, Liliana Marie Prikler
<liliana.prikler@gmail.com> wrote:
> > 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
Yes, indeed. I simply grepped "manifest" and looked at
'find-file-in-parent-directories', because if it is not called, the
"manifest" file cannot be loaded. :-) Then I incorrectly used the
wrong command line invokation. Bad day with a lot of inattentive
today. :-/
> 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.
I am in favour to keep it explicit. (Personally, I already find that
"guix shell" is wrong ;-))
> 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.
I agree.
Cheers,
simon
next prev parent reply other threads:[~2021-12-07 17:14 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
2021-12-07 17:11 ` zimoun [this message]
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=CAJ3okZ03sOCb5ZzSKxAaWeGYx+MEbFk3hYYvJLLfhEsxcN81oQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=52347@debbugs.gnu.org \
--cc=cayetano.santos@inventati.org \
--cc=liliana.prikler@gmail.com \
--cc=liliana.prikler@ist.tugraz.at \
/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.