Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): udisks-1.0.1-2.el6.x86_64 How reproducible: Steps to Reproduce: 1. run terminal 2. type command: typeset -f 3. Actual results: function __udisks () { $lot_of_if's; } is printed Expected results: no function should be there unless defined in shell profile or rc file Additional info: * RHEL 6 nightly * function is defined in /etc/profile.d/udisks-bash-completion.sh
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
(In reply to comment #0) > Description of problem: > > > Version-Release number of selected component (if applicable): > udisks-1.0.1-2.el6.x86_64 > > How reproducible: > > > Steps to Reproduce: > 1. run terminal > 2. type command: > typeset -f > 3. > > Actual results: > function __udisks () { $lot_of_if's; } is printed > > Expected results: > no function should be there unless defined in shell profile or rc file I don't agree with this. Why do you think this is so? > Additional info: > * RHEL 6 nightly > * function is defined in /etc/profile.d/udisks-bash-completion.sh That file is there so completion on the udisks(1) command works out of the box.
I should have noted that the bash-completion is not even installed on the system in question. Looking at the contents of bash-completion package, it seems that program-specific functions are stored either in /etc/bash-completion.d/ or in /usr/share/bash-completion/ .
It doesn't matter if bash-completion (which is just a collection of random completion snippets) is installed; the intent is for the udisks(1) bash completion to work regardless (just like it does for files and other things). Don't worry, it's a common mistake to assume this. I'm closing this as NOTABUG.