Mailinglist Archive: opensuse-bugs (5061 mails)
| < Previous | Next > |
[Bug 751014] New: bash completion chokes on ~
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 7 Mar 2012 15:46:27 +0000
- Message-id: <bug-751014-21960@http.bugzilla.novell.com/>
https://bugzilla.novell.com/show_bug.cgi?id=751014
https://bugzilla.novell.com/show_bug.cgi?id=751014#c0
Summary: bash completion chokes on ~
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.1
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Basesystem
AssignedTo: ro@xxxxxxxx
ReportedBy: jdelvare@xxxxxxxx
QAContact: qa@xxxxxxx
Found By: Community User
Blocker: ---
For many commands, I noticed that bash completion chokes on ~. For example, if
I type:
$ vi ~/Docu<TAB>
bash will complete that to:
$ vi ~/Documents
Notice the lack of trailing /, which prevents me from typing the beginning of
the next file name component directly. As long as I don't type / myself, bash
completion is stuck and won't go further.
After noticing that not all commands are affected, I tracked it down to the
_exp_ function which is defined in /etc/profile.d/complete.bash. If I remove
the -F _exp_ from vi's "complete" definition, the problem disappears. So the
problem is that this _exp_ function misbehaves if the object of the completion
starts with ~.
This is a minor thing for sure, but pretty annoying for daily work, so a fix
would be welcome.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |