From: mike@rohleder.de
To: 39963@debbugs.gnu.org
Subject: [bug#39963] [PATCH] fd bash_completion typo
Date: Sat, 07 Mar 2020 01:03:02 +0100 [thread overview]
Message-ID: <87v9nh116x.fsf@rohleder.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 89 bytes --]
Hey guix!
* The "fd" package installs its bash_completion file in the wrong directory.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: Type: text/x-patch, Size: 1130 bytes --]
diff --git a/gnu/packages/rust-apps.scm b/gnu/packages/rust-apps.scm
index 72c982f23c..ce50562228 100644
--- a/gnu/packages/rust-apps.scm
+++ b/gnu/packages/rust-apps.scm
@@ -184,11 +184,11 @@ also knows about symlinks, extended attributes, and Git.")
;; Manpages
(install-file "doc/fd.1" (string-append out "/share/man/man1"))
;; Completions
- (install-completion "^fd.bash$" "/etc/bash-completion.d")
+ (install-completion "^fd.bash$" "/etc/bash_completion.d")
(install-completion "^fd.fish$" "/share/fish/vendor_completions.d")
(install-completion "^_fd$" "/share/zsh/site-functions")
- (rename-file (string-append out "/etc/bash-completion.d/fd.bash")
- (string-append out "/etc/bash-completion.d/fd"))
+ (rename-file (string-append out "/etc/bash_completion.d/fd.bash")
+ (string-append out "/etc/bash_completion.d/fd"))
#t))))))
(inputs `(("jemalloc" ,jemalloc)))
(home-page "https://github.com/sharkdp/fd")
[-- Attachment #1.3: Type: text/plain, Size: 114 bytes --]
--
APL is a write-only language. I can write programs in APL, but I can't
read any of them.
-- Roy Keir
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2020-03-07 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 0:03 mike [this message]
2020-03-07 18:05 ` bug#39963: [PATCH] fd bash_completion typo Jakub Kądziołka
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=87v9nh116x.fsf@rohleder.de \
--to=mike@rohleder.de \
--cc=39963@debbugs.gnu.org \
/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).