public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Time to remove app-shells/bash-completion-config
Date: Tue, 17 Feb 2009 11:49:42 -0800	[thread overview]
Message-ID: <20090217194942.GB3649@comet> (raw)
In-Reply-To: <90b936c0902170955o5c300d7evc906ef02116097fc@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

On 11:55 Tue 17 Feb     , Jeremy Olexa wrote:
> We should only be using eselect now to enable bash-completion. I think
> bash-completion-config is broken now anyway
> (https://bugs.gentoo.org/show_bug.cgi?id=253878). So, after this
> change, I will p.mask b-c-c for removal.
> 
> Any concerns? The upgrade path in the future is going to be wierd as
> upstream is releasing v1.0 soon, but that is not concern for now.

http://bugs.gentoo.org/show_bug.cgi?id=218557

[Comment #0] mescalinum@gentoo.org : 2008-04-20 12:26:38 0000
-------------------------------------------------------------------------------
if I type:

 eselect bashcomp enable [TAB]

I get a 'Killed' string printed to terminal:

 eselect bashcomp enable Killed

and it messes up the bash shell (i.e. history doesn't work anymore)

[Comment #3] w.schwiedop@web.de : 2008-07-31 00:41:39 0000
-------------------------------------------------------------------------------
Created an attachment (id=161784)
Replacement for the current eselect completion script


-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-17 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 17:55 [gentoo-dev] Time to remove app-shells/bash-completion-config Jeremy Olexa
2009-02-17 19:49 ` Donnie Berkholz [this message]
2009-02-17 20:27   ` Jeremy Olexa
2009-02-17 20:35     ` Ciaran McCreesh
2009-02-20  6:18 ` [gentoo-dev] " Jeremy Olexa

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=20090217194942.GB3649@comet \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-dev@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