all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Howard <christopher@librehacker.com>
Cc: Luis Felipe <sirgazil@zoho.com>,  guix-devel@gnu.org
Subject: Re: Unhelpful "--help" output
Date: Thu, 14 Nov 2024 11:37:15 +0100	[thread overview]
Message-ID: <874j4acd9g.fsf@elephly.net> (raw)
In-Reply-To: <87frnuwym8.fsf@librehacker.com> (Christopher Howard's message of "Wed, 13 Nov 2024 13:35:43 -0900")

Christopher Howard <christopher@librehacker.com> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> I'm trying to
>>> fix the bitrot in the emacs-guix "shell commands" code, which actually
>>> parses the --help output using regexs, and and generates magit-popup
>>> menus based on that. So little things like the number of spaces on the
>>> line before the command name actually matter.
>>
>> Perhaps emacs-guix could instead fetch the list of items as an
>> S-expression.
>
> You mean through guix guile API, or...?

Yes.  The (guix scripts *) modules all define %options, a list of
options.  They are not exported, but they could be.   (Alternatively, an
accessor could be exported that returns the options as plain data.)
This structural data could be used in emacs-guix instead of parsing
its textual representation for presentation in the shell.

-- 
Ricardo


  reply	other threads:[~2024-11-14 10:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 16:23 Unhelpful "--help" output Christopher Howard
2024-11-12 16:31 ` indieterminacy
2024-11-12 19:56   ` Christopher Howard
2024-11-13 18:17 ` Ricardo Wurmus
2024-11-13 22:35   ` Christopher Howard
2024-11-14 10:37     ` Ricardo Wurmus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-12 13:14 Ricardo Wurmus
2024-11-12 15:03 ` Suhail Singh
2024-11-12 15:06 ` Luis Felipe

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=874j4acd9g.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=christopher@librehacker.com \
    --cc=guix-devel@gnu.org \
    --cc=sirgazil@zoho.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.