Package: bash-completion
Version: 1:2.8-5
Severity: normal

Dear Maintainer,

lets consider this session with bash and unrar:

user@debian:~/Downloads/n$ ls -1
somethingelse.txt
'Notes of Obsession 1.0.0.7 x64.rar'
user@debian:~/Downloads/n$ unrar <TAB>
e   l   lb  lt  p   t   v   vb  vt  x   
user@debian:~/Downloads/n$ unrar -<TAB>
-ad    -av-   -cfg-  -cu    -ep    -idp   -inul  -o+    -ow    -p-    -ta    
-tn    -u     -ver   -x     -y     
-ap    -c-    -cl    -dh    -f     -ierr  -kb    -o-    -p     -r     -tb    
-to    -v     -vp    -x@    
user@debian:~/Downloads/n$ unrar x <TAB>Notes\ of\ Obsession\ 1.0.0.7\ x64.rar 

However, unrar with .rar file and no 'x' works perfectly too, and is my 
prefered way of using it 99% of the time, but it is not suggested in 
completions:

I.e.

user@debian:~/Downloads/n$ unrar <TAB>  (no .rar file suggested)

but:

user@debian:~/Downloads/n$ unrar Notes\ of\ Obsession\ 1.0.0.7\ x64.rar 


unrar 0.0.1  Copyright (C) 2004  Ben Asselstine, Jeroen Dekkers
Extracting from /home/user/Downloads/n/Notes of Obsession 1.0.0.7 x64.rar

Extracting  Notes of Obsession.exe                                    OK        
Extracting  Engine/Binaries/ThirdParty/ICU/icu4c-53_1/Win64/VS2015/icudt53.dll 
OK        
Extracting  Engine/Binaries/ThirdParty/ICU/icu4c-53_1/Win64/VS2015/icudtd53.dll 
OK        
...
All OK
user@debian:~/Downloads/n$ cd ..


So I think unrar completion should be updated.

unzip completion works in more intuitive way, where it completes immedietly 
.zip files, directories, and few other file types (i.e. *.exe files, that could 
be self extracting), without any options.

Thanks.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Reply via email to