From: "Ludovic Courtès" <ludo@gnu.org>
To: "Collin J. Doering" <collin@rekahsoft.ca>
Cc: 37364@debbugs.gnu.org
Subject: [bug#37364] [PATCH 1/1] gnu: Add z for zsh
Date: Wed, 11 Sep 2019 14:23:17 +0200 [thread overview]
Message-ID: <87d0g7vx6y.fsf@gnu.org> (raw)
In-Reply-To: <87v9u03m3m.fsf@rekahsoft.ca> (Collin J. Doering's message of "Mon, 09 Sep 2019 22:45:49 -0400")
Hello Collin,
"Collin J. Doering" <collin@rekahsoft.ca> skribis:
> * gnu/packages/shellutils.scm (z): New variable.
>
> Signed-off-by: Collin J. Doering <collin@rekahsoft.ca>
[...]
> +(define-public z
> + (package
> + (name "z")
So far there’s only one package with a one-letter name. I’d be tempted
to rename “z” to “sh-z” (because it works with both Zsh and Bash) or
something similar, WDYT?
> + (mkdir-p man-path)
> + (invoke "gzip" "z.1")
> + (copy-file "z.1.gz" (string-append man-path "/z.1.gz"))
You can omit the “gzip” invocation because the ‘compress-documentation’
phase takes care of that, and passes the ‘-n’ flag, which is important
for bitwise reproducibility.
Also, you can remove the ‘mkdir-p’ call and replace the ‘copy-file’ call
with:
(install-file "z.1" man)
Last: please remove ‘-path’ from variable names—in GNU the convention is
touse the term “path” only for search paths ($PATH, etc.)
> + (synopsis "Jump about directories")
> + (description
> + "Tracks your most used directories, based on freecency. After a short
> +learning phase, z will take you to the most frecent directory that matches
> +ALL of the regexes given on the command line in order.")
It’s suggest writing “``frecency''” (with quotes) to make it clear that
it’s not a typo. :-)
Could you send an updated patch?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-09-11 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 2:40 [bug#37364] [PATCH 0/1] Add z for zsh Collin J. Doering
2019-09-10 2:45 ` [bug#37364] [PATCH 1/1] gnu: " Collin J. Doering
2019-09-11 12:23 ` Ludovic Courtès [this message]
2019-09-12 3:13 ` Collin J. Doering
2019-09-13 8:47 ` Ludovic Courtès
2019-09-10 14:41 ` [bug#37364] [PATCH] - Amended: Add copyright line and gpg sign email Collin J. Doering
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=87d0g7vx6y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37364@debbugs.gnu.org \
--cc=collin@rekahsoft.ca \
/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).