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.
does anybody else experienced the new strange/screwed behavior of updated bash-completion ver. 1.3 ?
F.E. instead of completing directory name with slash at the end and be ready to continue to complete its contents it finishes with directory name completed only. So for example if you would like to display contents of a file placed in a subdir with the less program, you have to press backspace and add '/' character to continue and that really sucks.
Most of core utils, less, tar and other tools are affected.
Can anybody else confirm this behaviour ? Unfortunately I've no mood and time to explore and fix it by myself :-/
F.E. instead of completing directory name with slash at the end and be ready to continue to complete its contents it finishes with directory name completed only. So for example if you would like to display contents of a file placed in a subdir with the less program, you have to press backspace and add '/' character to continue and that really sucks.
Most of core utils, less, tar and other tools are affected.
Can anybody else confirm this behaviour ?
I've been through this too and "fixed" it by (re)moving /etc/bash_completion
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.