Bug 12321 - Auto-complete lists commands as well as documents
Summary: Auto-complete lists commands as well as documents
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 4rn
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-16 05:35 CET by Doug Laidlaw
Modified: 2014-01-16 22:38 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Doug Laidlaw 2014-01-16 05:35:16 CET
When I use the Tab key after a command, to complete the name of a document as argument to the command, I get a list that includes all possible commands starting with that string.

Love the new Bugzilla!
Comment 1 Doug Laidlaw 2014-01-16 05:37:59 CET
No, they aren't just commands.  For "urpmi goog" looking for google-earth, I got:

googlecl
google-croscore-arimo-fonts
google-croscore-cousine-fonts
google-croscore-fonts-common
google-croscore-symbolneu-fonts
google-croscore-tinos-fonts
google-crosextra-caladea-fonts
google-crosextra-carlito-fonts
google-droid-sans-fonts
google-droid-sans-mono-fonts
google-droid-serif-fonts
google-earth-stable_current_i386.rpm
google-earth-stable_current_x86_64.rpm
google-gson
google-gson-javadoc
google-guice
google-guice-javadoc
google-noto-sans-armenian-fonts
google-noto-sans-avestan-fonts
google-noto-sans-bengali-fonts
google-noto-sans-bengali-ui-fonts
google-noto-sans-brahmi-fonts
google-noto-sans-carian-fonts
google-noto-sans-cherokee-fonts
google-noto-sans-coptic-fonts
google-noto-sans-deseret-fonts
google-noto-sans-devanagari-fonts
google-noto-sans-devanagari-ui-fonts
google-noto-sans-egyptian-hieroglyphs-fonts
google-noto-sans-ethiopic-fonts
google-noto-sans-fonts
google-noto-sans-georgian-fonts
google-noto-sans-glagolitic-fonts
google-noto-sans-gujarati-fonts
google-noto-sans-gujarati-ui-fonts
google-noto-sans-hanunno-fonts
google-noto-sans-hebrew-fonts
google-noto-sans-imperial-aramaic-fonts
google-noto-sans-kaithi-fonts
google-noto-sans-kannada-fonts
google-noto-sans-kannada-ui-fonts
google-noto-sans-kayah-li-fonts
google-noto-sans-kharoshthi-fonts
google-noto-sans-khmer-fonts
google-noto-sans-khmer-ui-fonts
google-noto-sans-lao-fonts
google-noto-sans-lao-ui-fonts
google-noto-sans-lisu-fonts
google-noto-sans-lycian-fonts
google-noto-sans-lydian-fonts
google-noto-sans-malayalam-fonts
google-noto-sans-malayalam-ui-fonts
google-noto-sans-mandaic-fonts
google-noto-sans-meeteimayek-fonts
google-noto-sans-nko-fonts
google-noto-sans-old-south-arabian-fonts
google-noto-sans-old-turkic-fonts
google-noto-sans-osmanya-fonts
google-noto-sans-phoenician-fonts
google-noto-sans-shavian-fonts
google-noto-sans-symbols-fonts
google-noto-sans-tagalog-fonts
google-noto-sans-tai-tham-fonts
google-noto-sans-tai-viet-fonts
google-noto-sans-tamil-fonts
google-noto-sans-tamil-ui-fonts
google-noto-sans-telugu-fonts
google-noto-sans-telugu-ui-fonts
google-noto-sans-thai-fonts
google-noto-sans-thai-ui-fonts
google-noto-sans-ugaritic-fonts
google-noto-sans-ui-fonts
google-noto-sans-vai-fonts
google-noto-serif-armenian-fonts
google-noto-serif-fonts
google-noto-serif-georgian-fonts
google-noto-serif-khmer-fonts
google-noto-serif-lao-fonts
google-noto-serif-thai-fonts
Comment 2 Manuel Hiebel 2014-01-16 21:35:20 CET
Can you explain where is the bug (if there is one) or your request ? I fail to see
Comment 3 David Walser 2014-01-16 21:42:18 CET
Indeed, as described here, this is not a bug.  When bash-completion is installed, completions for "urpmi" will be the names of packages you could possibly install.  In Mageia 4, all of those google packages are fonts packages that are newly imported.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 4 Doug Laidlaw 2014-01-16 22:15:35 CET
OK, looks as though I misread the symptoms.

I have a directory RPMS_on_disk, containing RPMs that I can install with urpmi, but which are not in a repository.

In that directory I have two google-earth rpms, for i586 and 64-bit.

Normally, auto-complete completes only filenames found in the directory.  I have done this operation repeatedly, and auto-complete has given me only the two local RPMs.  This is the first time it has gone outside those two.  Perhaps in the past I have used a more limiting string.

Typing "google-e" would have excluded all the ones listed.

It is because of mistakkes like this that I don't want to join Claire's QA team.
Comment 5 Manuel Hiebel 2014-01-16 22:31:30 CET
Bash-completion is now suggested since Mageia 4, that mean that it will be likely automatically be installed, which was not the case in previous version.

For local rpm you can use ./myname.rpm or ./mynam*.rpm which will works fine.

Will add something to the release notes.


>It is because of mistakkes like this that I don't want to join Claire's QA team.
Well, there is no harm, you learn when trying ;)

Whiteboard: (none) => 4rn

Comment 6 Doug Laidlaw 2014-01-16 22:38:08 CET
Thanks Manuel. I had heard that it can cause problems.

I thought of using "./" after I had signed off a moment ago.

Another thing that misled me is a rule I learned in my beginner days.  All those items are package names.  I was told: use the complete rpm name when installing, use the package name when uninstalling.  Apparently that is not the case with urpmi.

I was going to add something else, but my mind has gone blank.

Note You need to log in before you can comment on or make changes to this bug.