From: Zach Forrest <zach@disinformation.ca>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] latest and greatest gentoo.completion
Date: Wed, 13 Mar 2002 10:30:43 -0800 [thread overview]
Message-ID: <3C8F9AD3.8060705@disinformation.ca> (raw)
In-Reply-To: 20020313070557.76AFA2004E02@chiba.3jane.net
It is what you think it is. You simply have to place the file in /etc
(or anywhere else really, but /etc is the best place) and add the
following to your .bashrc script. You will most likely want to add it to
the root user's .bashrc script as well. The test for the $PS1
environment variable makes sure that we're running interactively and the
second test makes sure the file exists.
if [ "$PS1" ] && [ -e /etc/gentoo.completion ]; then
# Source completion code
. /etc/gentoo.completion
fi
You could also add the following to /etc/profile instead of the .bashrc
scripts to make it available to all users (it's really a matter of
preference). The test for $BASH_VERSION makes sure that the completion
code is only sourced for users using the bash shell (i.e. if they are
using csh the code won't work and errors will be generated).
if [ "$BASH_VERSION" ] && [ "$PS1" ] && [ -e /etc/gentoo.completion ]
then
# Source completion code
. /etc/gentoo.completion
fi
Hope this helps.
Zach
Thilo Bangert wrote:
> On Wednesday, 13. March 2002 02:05, you wrote:
>
>>I've made some significant changes incorporating the latest available
>>options and making the completion more intelligent. Enjoy!
>>
>>Zach
>
>
> is this what i think it is and for bash? or is it for some weird shell
> ;-)
>
> how does a newbie like me get that to work?
>
next prev parent reply other threads:[~2002-03-13 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 1:05 [gentoo-dev] latest and greatest gentoo.completion Zach Forrest
2002-03-13 6:48 ` Thilo Bangert
2002-03-13 18:30 ` Zach Forrest [this message]
2002-03-13 18:56 ` Thilo Bangert
2002-03-14 22:38 ` jboyens
2002-03-16 17:56 ` Ian Smith
2002-03-16 18:05 ` Gerald Schneider
2002-03-16 18:27 ` Ian Smith
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=3C8F9AD3.8060705@disinformation.ca \
--to=zach@disinformation.ca \
--cc=gentoo-dev@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