From: Zach Forrest <diatribe@shaw.ca>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-ebuild] Bash 2.05a with bash_completion
Date: Sun, 09 Dec 2001 14:03:06 -0800 [thread overview]
Message-ID: <3C13DF9A.2090909@shaw.ca> (raw)
In-Reply-To: 1103.24.38.252.76.1007931574.squirrel@thinktank.mediafarm.ch
1) The best way to get a better idea of what the patch does is to look
through the patch file, but basically it allows you to complete on
services in init.d followed by the scripts available commands. After
looking at bash_completion a little more closely, it seems that service
completion is a little RedHat specific at the moment, but I'll try to
come up with a more generic one.
More precisely, it adds bash_servicename_completion_function (text,
state) and related code to bashline.c/h.
Maybe I should just forget the patch and make a separate package.
2) This may have something to do with the following condition:
if [ -z "`use build`" ]
This is from Daniels Bash 2.04 ebuild. In make.conf, it says not to set
the 'build' USE flag and it looks like this flag is used to build the
docs in this particular ebuild. So, can't answer this very well. Any help?
You're right that bash does have example completion code and
bash_completion is based on this.
3) Again, this was the homepage defined in the previous ebuild. I did
check out the site you mentioned and it does seem to be the homepage. It
does say though, that it is a GNU project so I'm inclined to leave it as
is for now.
Finale) Yes, I've made a decision: I'm going to make a separate package
without the service completion patch. This seems to be the simple and
straight forward approach for now.
Zach
Tom von Schwerdtner wrote:
> Hey,
>
> A few questions:
>
> 1) What do these 'service completions' provide over the programmable
> copletions in the current bash in portage?
>
> 2) Why arent the example docs that come with the curren bash installed?
> There is some completion code in there...
>
> 3) The bash homepage isnt http://www.gnu.org/software/bash/bash.html, its
> http://cnswww.cns.cwru.edu/~chet/bash/bashtop.html
>
>
> -Tom
>
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
>
next prev parent reply other threads:[~2001-12-09 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200112092010.ACU39946@thor.inter.net.il>
2001-12-09 20:59 ` [gentoo-dev] Re: [gentoo-ebuild] Bash 2.05a with bash_completion Tom von Schwerdtner
2001-12-09 22:03 ` Zach Forrest [this message]
2001-12-09 20:51 ` Chad Huneycutt
2001-12-09 23:52 ` Zach Forrest
2001-12-09 22:48 ` Zach Forrest
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=3C13DF9A.2090909@shaw.ca \
--to=diatribe@shaw.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