From: jgart <jgart@dismail.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Tobias Geerinckx-Rice" <me@tobias.gr>,
guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Guix Devel" <guix-devel@gnu.org>
Subject: Re: repl macro (metacommand?) for guix CLI (sub)commands
Date: Tue, 5 Jul 2022 17:27:43 -0500 [thread overview]
Message-ID: <20220705172743.GB3448@gac> (raw)
In-Reply-To: <86tu7wxzpw.fsf@gmail.com>
On Tue, 05 Jul 2022 00:47:07 +0200 zimoun <zimon.toutoune@gmail.com> wrote:
> All that said, maybe it could be nice to extend the current
> meta-commands of the REPL. What would be the need between the current
> CLI and the current Scheme API?
Hi,
That's a good question! Maybe we should make a feature table and analyze
what we currently have exposed to decide what we might want in the near
future that we don't currently have.
> Maybe all the ’leave’ and ’exit’ could be wrapped using an hypothetical
> ’maybe-exit’ catching if it is called from REPL or not.
I'll have to read more code. I was just imagining something like that could work.
> Is it possible to detect if an interactive call? I was thinking to add
> a global parameter in ’(guix scripts repl) and then this new
> ’maybe-exit’ could check it; but I guess Guile provides a better
> mechanism for checking interactiveness.
Do you know if guile provides a way of checking that? Should we ask on the guile mailing
list or should we read more code first to see what's currently provided?
all best,
jgart
next prev parent reply other threads:[~2022-07-05 22:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 18:11 repl macro (metacommand?) for guix CLI (sub)commands jgart
2022-07-04 8:29 ` zimoun
2022-07-04 13:22 ` Ludovic Courtès
2022-07-04 18:21 ` jgart
2022-07-04 20:28 ` Tobias Geerinckx-Rice
2022-07-04 22:47 ` zimoun
2022-07-05 22:27 ` jgart [this message]
2022-07-06 6:44 ` zimoun
2022-07-06 12:13 ` bokr
2022-07-06 12:58 ` zimoun
2022-07-16 19:08 ` Bengt Richter
2022-07-07 7:31 ` Ludovic Courtès
2022-07-07 7:58 ` bokr
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=20220705172743.GB3448@gac \
--to=jgart@dismail.de \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--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 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).