all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: indieterminacy <indieterminacy@libre.brussels>
To: Christopher Howard <christopher@librehacker.com>
Cc: Luis Felipe <sirgazil@zoho.com>,
	Ricardo Wurmus <rekado@elephly.net>,
	guix-devel@gnu.org
Subject: Re: Unhelpful "--help" output
Date: Tue, 12 Nov 2024 16:31:56 +0000	[thread overview]
Message-ID: <f185f021ebc224f1fcdf398ef8fad053@libre.brussels> (raw)
In-Reply-To: <87o72kqv40.fsf@librehacker.com>

Hello Christopher,

On 2024-11-12 16:23, Christopher Howard wrote:
> Hi, if planning to make changes to --help output, could you please try 
> to preserve the output formatting as much as possible? 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.

Sounds interesting.

I guess you are being implicit regarding the spacing order?
It may be more resilient to consider counting the number of opening 
spaces/tabs and then compare the results.

In any case Id like to look at the uri to see how Transient is operating 
off your PEGs.

Thanks for working on this!

Kind regards,


Jonathan


  reply	other threads:[~2024-11-12 17:13 UTC|newest]

Thread overview: 10+ 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 [this message]
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
  -- 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
2024-12-10 16:44 ` Simon Tournier

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=f185f021ebc224f1fcdf398ef8fad053@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=christopher@librehacker.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    --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.