unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: Noah Evans <clonex100@protonmail.com>
Cc: 46907-done@debbugs.gnu.org
Subject: bug#46907: [PATCH] Update zsh completion file for guix command.
Date: Sat, 28 Aug 2021 17:58:45 +0200	[thread overview]
Message-ID: <87wno5d0i2.fsf@waegenei.re> (raw)
In-Reply-To: <uGNqqNxhoGy50hEDoqYXdx91SRCaPh_txZSGn5ySeUu5FZk865tdZsb4Z8QI3V74DSc1JjUlk8idGP6wYZ06aNpKr_90kkCV28iLBc_xVRk=@protonmail.com> (Noah Evans's message of "Wed, 03 Mar 2021 22:44:41 +0000")

Hello Noah,

I managed to fix your submited patch, by saving it with in "gnus-article-mode"
in Emacs and having a single spave before each context lines.

When applied I checked the arguments of each commands, fixed some duplicated
or missing ones, added your copyright, updated the guix commands list and wrote
a commit message.

I've puhsed it as a8dd285d5a0670abf124a721e6ba94da045b24ba.

ATM we are still missing completions for transform options, each importer
options and the following commands:
- archive
- edit
- copy
- git
- deploy
- describe
- pack
- search
- show
- weather
- offload
- processes
- repl

I think the current pattern of copying bits from the “--help” shows it's limit
as it's difficult to stay in sync with the actual “guix” arguments.  It would be
better to get thoses string at run time as it's done in bash's completions.

Cheers,
- Brice




      parent reply	other threads:[~2021-08-28 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 22:44 [bug#46907] [PATCH] Update zsh completion file for guix command Noah Evans via Guix-patches via
2021-03-07  9:27 ` Brice Waegeneire
2021-03-19 21:02   ` Ludovic Courtès
2021-08-28 15:58 ` Brice Waegeneire [this message]

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=87wno5d0i2.fsf@waegenei.re \
    --to=brice@waegenei.re \
    --cc=46907-done@debbugs.gnu.org \
    --cc=clonex100@protonmail.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).