From: "Florian Gamböck" <ml@floga.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Purpose of bashcomp_alias in bash-completion-r1.eclass?
Date: Sun, 30 Nov 2014 16:07:37 +0100 [thread overview]
Message-ID: <547B32B9.30507@floga.de> (raw)
Good day!
Before reporting a bug I wanted to hear other opinions on that: In
bash-completion-r1.eclass, what is the true purpose of bashcomp_alias?
For now I only see error messages when trying to "eselect bashcomp
enable" two aliases of the same script because of the same linkname.
What benefit could one gain in aliasing their completion script to
differnet names?
In fact I find this confusing and highly contradicting, because you
obviously can enable only one alias at the same time, but actually with
enabling one you automatically enable all the others, since they are
symlinks. Then why even bothering with those aliases? (Actual example:
app-text/calibre-1.48-r1, which installs 14 or so aliases to the exact
same completion script.)
--
Flo
next reply other threads:[~2014-11-30 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 15:07 Florian Gamböck [this message]
2014-11-30 15:27 ` [gentoo-user] Re: Purpose of bashcomp_alias in bash-completion-r1.eclass? James
2014-11-30 15:57 ` Florian Gamböck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547B32B9.30507@floga.de \
--to=ml@floga.de \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox