« File transfer
Java woes »

eselect

Works:

eselect bashcomp enable --global ri

Silently fails:

eselect bashcomp enable ri --global

Reason: (/usr/share/eselect/modules/bashcomp.eselect)

do_enable() {
	#...snip...
	if [[ ${1} == "--global" ]] ; then
		bcdir="${ROOT}/etc/bash_completion.d"
		shift
	fi
	#...snip...
	# ignore any unrecognized options
	[[ ${bc} == --* ]] && continue

Always looks for --global as the first parameter, apparently. Bug? Not sure. This would be the second eselect-related bug I've noticed in the past two days, if so.

Tags: ,
This entry was posted on Wednesday, August 1st, 2007 at 9:36 pm. You can follow any responses to this entry through the RSS 2.0 feed. Or subscribe to comments below to receive email notifications. This post is open for commenting. Pinging is currently not allowed.

3 Responses to “eselect”

  1. August 2nd, 2007 at 4:29 am
    Quoth Ciaran McCreesh:

    That's no more a bug in eselect than a bug in a C program is a bug in GCC.

  2. August 2nd, 2007 at 4:55 am
    Quoth Brian:

    Nothing to do with eselect itself, I know. Just a module. Loose usage of terminology on my part.

  3. August 2nd, 2007 at 3:30 pm
    Quoth Steven Oliver:

    Bug or not, the second method, which doesn't work, seems more natural to me anyway. Perhaps it should accept both.

Leave a Reply

You can use these tags in comments (Note: HTML is automatically escaped inside <pre> tags, nowhere else, so if you post source code, put it in <pre>):

<pre lang="some_programming_language"> 
<em>
<strong>
<a href="url">

NOTE: Comments are automatically spam-filtered. If your comment fails to appear, it was likely munched by the filter. Try not to link-spam or post anything that looks like it was typed by a robot.