From: Oleg Pykhalov <go.wigust@gmail.com>
To: swedebugia@riseup.net
Cc: 32020@debbugs.gnu.org
Subject: bug#32020: 3 bash-completion errors
Date: Sat, 30 Jun 2018 20:00:06 +0300 [thread overview]
Message-ID: <87a7rc5hwp.fsf@gmail.com> (raw)
In-Reply-To: <106ea85e25bddfc69c20b97270ae35e6@riseup.net> (swedebugia's message of "Sat, 30 Jun 2018 08:30:48 -0700")
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
Hello,
Thank you for the report.
swedebugia@riseup.net writes:
> When using -m after guix package
What version of Guix do you run?
It does for me on ‘guix --version’:
--8<---------------cut here---------------start------------->8---
guix (GNU Guix) 12a96d4d419330056d647817aa09f02f031cba6f
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
--8<---------------cut here---------------end--------------->8---
> weather -m
Added.
> build; bash tries to expand
‘guix build’ doesn't have ‘-m’ flag, unfortunately.
I want to have it, too. :-)
> on names of packages instead of files in the filesystem.
>
> After guix build --load-path= bash does not expand. It should expand in
> the local filesystem I think.
I don't know how to implement ‘--load-path=’, but ‘-L’ was added.
> (nitpicking)
> Also when expanding on "-" after guix weather; bash suggests: "--e"
> among valid completions but it is NOT.
I cannot reproduce it, sorry.
> Same happens after guix build. Havent tested the others.
Let us know if more completion is missing.
Thanks,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-30 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 15:30 bug#32020: 3 bash-completion errors swedebugia
2018-06-30 16:52 ` bug#32020: [PATCH 1/2] bash completion: Complete files names after 'guix build -L' Oleg Pykhalov
2018-06-30 16:52 ` bug#32020: [PATCH 2/2] bash completion: Complete files names after 'guix weather -m' Oleg Pykhalov
2018-07-02 10:21 ` bug#32020: [PATCH 1/2] bash completion: Complete files names after 'guix build -L' Ludovic Courtès
2018-07-03 4:06 ` Oleg Pykhalov
2018-06-30 17:00 ` Oleg Pykhalov [this message]
2018-06-30 18:24 ` bug#32020: 3 bash-completion errors swedebugia
2018-06-30 18:41 ` Ricardo Wurmus
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=87a7rc5hwp.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=32020@debbugs.gnu.org \
--cc=swedebugia@riseup.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).