unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: 46823-done@debbugs.gnu.org, 46823@debbugs.gnu.org
Subject: [bug#46823] [PATCH 1/3] gnu: Add python-readability.
Date: Sat, 06 Mar 2021 11:13:52 +0100	[thread overview]
Message-ID: <8735x8egin.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <37b77e5fee4340e717ef8a1105e2dd6d6ac2aa26.camel@zaclys.net> ("Léo Le Bouter"'s message of "Sat, 06 Mar 2021 00:19:46 +0100")

Hello,

Léo Le Bouter <lle-bout@zaclys.net> writes:

> On Fri, 2021-03-05 at 17:32 +0100, Nicolas Goaziou wrote:

>> Note that (native-)inputs should be sorted alphabetically, and
>> descriptions ought to be full sentences.
>
> I did the descriptions but did not sort all *inputs because it is quite
> troublesome to do so editing commit history etc.. I don't like doing it
> manually and don't have any tooling, also don't think it is very
> worthwhile use of my time, nor do I think it adds much value to GNU
> Guix.

I obviously cannot tell what is worth of your time. 

However, sorting inputs alphabetically has some value. For example, it
makes it easier to add more inputs later, as it becomes less tedious to
check for duplicates.

> If you have any tooling to suggest to do it easily in Emacs then
> I'll happily do that in every of my contributions by default.

What about a basic M-x sort-lines ? Note that you need to be cautious
about the first and last inputs, as opening and closing parens should be
sent to another line there.

If you don't want to special-casing first and last inputs, there's the
more "advanced"

  M-x sort-regexp-fields RET (".+?".*?) RET \& RET

while selecting the full input field (with C-M-SPC).

HTH,
-- 
Nicolas Goaziou




  reply	other threads:[~2021-03-06 10:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 22:34 [bug#46823] [PATCH 1/3] gnu: Add python-readability Léo Le Bouter via Guix-patches via
2021-02-27 22:36 ` [bug#46823] [PATCH 2/3] gnu: Add python-listparser Léo Le Bouter via Guix-patches via
2021-02-27 22:36   ` [bug#46823] [PATCH 3/3] gnu: Add gfeeds Léo Le Bouter via Guix-patches via
2021-02-27 22:42 ` [bug#46823] [PATCH 1/3] gnu: Add python-readability Léo Le Bouter via Guix-patches via
2021-03-05 16:32   ` Nicolas Goaziou
2021-03-05 23:19     ` Léo Le Bouter via Guix-patches via
2021-03-06 10:13       ` Nicolas Goaziou [this message]
2021-03-06 17:44         ` Léo Le Bouter via Guix-patches via
2021-03-08  9:16           ` zimoun

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=8735x8egin.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=46823-done@debbugs.gnu.org \
    --cc=46823@debbugs.gnu.org \
    --cc=lle-bout@zaclys.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 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).