SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For everyone that uses the bash-completion package from /extra, please have a look at http://connie.slackware.com/~rworkman/bash-completion/ and consider testing the 2.0 prerelease (1.90 at the moment). Be sure to read over the README in there.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Thanks for the feedback, guys - it's much appreciated.
Re the /var/log/packages/ tab completion (added space), I too have noticed that, but I also work around it by using the completion as intended. I guess it's arguable whether that's even a bug...
This should be fixed now in the master branch of bash-completion with this commit. If there is a slash somewhere in argument to removepkg, completion assumes that user tries to enter a filename.
> I guess it's arguable whether that's even a bug...
Completing filenames is not very useful, but sometimes it can be more desirable. For example, this way you can remove kde with one command
$ removepkg /srv/ftp/slackware/{kde,kdei}/*.txz
Found a bug, just not sure if it happens only after package rebuild or it was there right from the start (I'll try to rebuild without the last patch). Here's how to reproduce:
Code:
$ touch foo\(bar\).txt
$ mv fo<TAB> fo<TAB>
The second attempt to complete does nothing. Happens only with files which have parentheses in their names.
Nope, still the same without the last patch. Also it seems that it's the escaping that's causing this, not the parens themselves (the bug occurs with escaped space characters etc).
This is a known issue. Completion fails if there are sequential duplicate items in a list of arguments. It is unlikely that this bug will be fixed before release of bash-completion-2.0
Audrius, your issue is fixed now in the master branch. There is also one new slackware related improvement: completion for upgradepkg now supports "oldpkg%newpkg" notation
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.