From: Zach Forrest <diatribe@shaw.ca>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] updated emerge bash completion + question
Date: Fri, 14 Dec 2001 10:37:39 -0800 [thread overview]
Message-ID: <3C1A46F3.4020706@shaw.ca> (raw)
In-Reply-To: 1008324439.25078.0.camel@gentoo.theleaf.office
I think you may be right.
Geert Bevin wrote:
> Well this works, but it doesn't use the bash normal file completion
> command which imho is not implemented correctly. I don't think that
> --usepkg should limit itself to the binary packages directory, the
> completion that follows should be a standard bash file completion. If
> you see how file completion on other commands has been implemented, then
> you'll see that they suffer from the same problem (eg. chown chmod ....)
> I think that the compgen implementation of -f is flawed, it doesn't
> react any different than -d. I'll try to contact the bash author(s).
>
> On Thu, 2001-12-13 at 22:13, Zach Forrest wrote:
>
>>This seems to work (see attachment).
>>
>>[DISCLAIMER: I make no claims that this is pretty.]
>>
>>Geert,
>>
>>I think the problem with filename completion when '--usepkg' is
>>specified has to do with the suffix and glob flags when setting $setsma.
>>I made a few other changes and was having the same problem (i.e. after
>>the dirname was completed, it appended a "/" and added a space;
>>interestingly, though, was that when I backspaced, it then completed on
>>filenames properly). To get it working, I removed the '-S' flag and
>>changed the glob pattern to "*/" (only when '--usepkg' is specified, of
>>course).
>>
>>Maybe one of us should mail this addition to the bash_completion
>>maintainer so it can be included in the main package. (He might also be
>>able to clean it up a bit. If you'd like to send it in, feel free to
>>point the finger at me for the hacks. ;-) )
>>
>>Zach
>>
prev parent reply other threads:[~2001-12-14 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 12:34 [gentoo-dev] updated emerge bash completion + question Geert Bevin
2001-12-13 21:13 ` Zach Forrest
2001-12-14 10:07 ` Geert Bevin
2001-12-14 18:37 ` Zach Forrest [this message]
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=3C1A46F3.4020706@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