all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
	67489@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	Ricardo Wurmus <rekado@elephly.net>,
	Christopher Baines <guix@cbaines.net>
Subject: [bug#67489] [PATCH] monad-repl: Add REPL commands to inspect package arguments.
Date: Tue, 28 Nov 2023 17:39:23 +0100	[thread overview]
Message-ID: <CAJ3okZ2dryn0ZyxJAB9719kesOizUODnYnnWuFiUcqA8bkPdDQ@mail.gmail.com> (raw)
In-Reply-To: <871qc9svc5.fsf@gnu.org>

Re,

On Tue, 28 Nov 2023 at 17:20, Ludovic Courtès <ludo@gnu.org> wrote:

> > Without drifting, why not the meta-command ,arguments?
>
> One can already do “,pp (package-arguments package)”, so I wanted to
> have something short and to-the-point that would improve on that.
>
> In particular, we know by convention that certain arguments can be
> interpreted as code (gexps or sexps) so we can process them do display
> them in a nice way (lowering gexps, applying the pretty printer).  We
> cannot necessarily do that for other arguments where there’s no
> established convention.

Unrelated to this patch series, maybe an opportunity for establishing
some of these conventions, no?

BTW, because this potential meta ,arguments targets package developer,
I would find nice to apply what it is done with ,phases to
'package-arguments'.  As I showed in my previous message, “,pp
(package-arguments package)” is not really practical.  Well, anyway...
let as a exercise for the curious reader. ;-)

Cheers,
simon




  reply	other threads:[~2023-11-28 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 17:19 [bug#67489] [PATCH] monad-repl: Add REPL commands to inspect package arguments Ludovic Courtès
2023-11-28 10:49 ` Simon Tournier
2023-11-28 16:20   ` Ludovic Courtès
2023-11-28 16:39     ` Simon Tournier [this message]
2023-12-04 21:51   ` bug#67489: " 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=CAJ3okZ2dryn0ZyxJAB9719kesOizUODnYnnWuFiUcqA8bkPdDQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=67489@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=guix@cbaines.net \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.org \
    --cc=rekado@elephly.net \
    /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.