unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: jgart via Guix-patches via <guix-patches@gnu.org>
To: mail@nicolasgoaziou.fr, 60212@debbugs.gnu.org
Cc: 60212-done@debbugs.gnu.org
Subject: [bug#60212] [PATCH] gnu: Add emacs-fzf.
Date: Wed, 21 Dec 2022 00:54:11 +0000	[thread overview]
Message-ID: <6dc428a54acf3ee157fd1a2784aa76b0@dismail.de> (raw)
In-Reply-To: <87ili6cqx5.fsf@nicolasgoaziou.fr>

I keep forgetting re @command

I'll stop doing that. It has become a habit.

Thanks for the review!

It's much appreciated,

jgart

https://whereis.みんな/

December 20, 2022 4:26 AM, "Nicolas Goaziou" <mail@nicolasgoaziou.fr> wrote:

> Hello,
> 
> jgart via Guix-patches via <guix-patches@gnu.org> writes:
> 
>> * gnu/packages/emacs-xyz.scm (emacs-fzf): New variable.
> 
> Thank you.
> 
>> + #~(modify-phases %standard-phases
>> + (add-after 'unpack 'patch-fzf-executable
>> + (lambda* (#:key inputs #:allow-other-keys)
>> + (make-file-writable "fzf.el")
> 
> Nitpick: The expression above is usually not necessary, even though some
> package definitions use it.
> 
>> + (emacs-substitute-variables "fzf.el"
>> + ("fzf/executable" (search-input-file inputs "/bin/fzf"))))))))
>> + (inputs (list fzf))
>> + (home-page "https://github.com/bling/fzf.el")
>> + (synopsis "Front-end for fzf")
> 
> I expounded it a bit.
> 
>> + (description "An @command{emacs} front-end for @command{fzf}.")
> 
> Please write full sentences in descriptions, even if upstream does not.
> 
> Also, "@command{emacs}" conveys no more information than "Emacs". So
> does "@command{fzf}" vs "Fzf". The simpler the better, IMO.
> 
> Applied!
> 
> Regards,
> --
> Nicolas Goaziou




      parent reply	other threads:[~2022-12-21  0:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20  3:29 [bug#60212] [PATCH] gnu: Add emacs-fzf jgart via Guix-patches via
2022-12-20 10:25 ` bug#60212: " Nicolas Goaziou
2022-12-21  0:54 ` jgart via Guix-patches via [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=6dc428a54acf3ee157fd1a2784aa76b0@dismail.de \
    --to=guix-patches@gnu.org \
    --cc=60212-done@debbugs.gnu.org \
    --cc=60212@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=mail@nicolasgoaziou.fr \
    /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).