2004-10-14 06:53:25 +00:00
|
|
|
# btdownloadheadless(1) completion by Guillaume Rousse <rousse@ccr.jussieu.fr>
|
2009-01-14 22:24:51 +02:00
|
|
|
|
2009-06-08 21:22:43 +03:00
|
|
|
have btdownloadheadless.py || have btdownloadcurses.py || \
|
|
|
|
have btdownloadgui.py &&
|
2004-10-14 06:53:25 +00:00
|
|
|
_btdownload()
|
|
|
|
{
|
|
|
|
local cur prev
|
|
|
|
|
|
|
|
COMPREPLY=()
|
2008-05-10 18:04:06 +02:00
|
|
|
cur=`_get_cword`
|
2004-10-14 06:53:25 +00:00
|
|
|
prev=${COMP_WORDS[COMP_CWORD-1]}
|
|
|
|
|
|
|
|
case "$prev" in
|
|
|
|
--@(responsefile|saveas))
|
|
|
|
_filedir
|
|
|
|
return 0
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
|
|
|
|
if [[ "$cur" == -* ]]; then
|
|
|
|
COMPREPLY=( $( compgen -W '--max_uploads --keepalive_interval \
|
|
|
|
--download_slice_size --request_backlog \
|
|
|
|
--max_message_length --ip --minport --maxport \
|
|
|
|
--responsefile --url --saveas --timeout \
|
|
|
|
--timeout_check_interval --max_slice_length \
|
|
|
|
--max_rate_period --bind --upload_rate_fudge \
|
|
|
|
--display_interval --rerequest_interval \
|
|
|
|
--min_peers --http_timeout --max_initiate \
|
|
|
|
--max_allow_in --check_hashes \
|
|
|
|
--max_upload_rate --snub_time --spew \
|
|
|
|
--rarest_first_cutoff --min_uploads \
|
Quote unquoted $cur to prevent globbing.
Closes Alioth #311614
Globbing might occur if $cur contains one of these globbing characters: * ? [ ]
The bug becomes apparent:
On Cygwin if the glob-string contains backslashes as well, causing a warning (Cygwin >= 1.7):
MS-DOS style path detected: ...
Preferred POSIX equivalent is: ...
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
On Linux, using strace, you can see bash-completion doing an unnecessary `open' system call.
Steps to reproduce on Linux using `strace':
Environment: Linux, bash-completion-1.0
1. Start bash with bash-completion loaded and find out PID ($$):
$ echo $$
MYPID
2. In a second bash shell, `strace' the above PID:
$ strace -e trace=open -f -o strace.log -p MYPID
3. Within the first bash shell, type:
$ cur="?"; _kernel_versions
4. In the second bash shell, type ^C to quick `strace'.
5. Check `strace.log', here you can see bash accessing
something it shouldn't:
...
open(".", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
...
6. The above call to `open' disappears if $cur in _kernel_versions gets
quoted, and you repeat the steps above:
_kernel_versions()
{
COMPREPLY=( $( compgen -W '$( command ls /lib/modules )' -- "$cur" ) )
}
2009-09-25 09:36:29 +02:00
|
|
|
--report_hash_failures' -- "$cur" ) )
|
2004-10-14 06:53:25 +00:00
|
|
|
else
|
|
|
|
_filedir
|
|
|
|
fi
|
2009-06-08 21:22:43 +03:00
|
|
|
} &&
|
2004-10-14 06:53:25 +00:00
|
|
|
complete -F _btdownload btdownloadheadless.py btdownloadcurses.py btdownloadgui.py
|
2009-10-01 20:54:51 +03:00
|
|
|
|
|
|
|
# Local variables:
|
|
|
|
# mode: shell-script
|
|
|
|
# sh-basic-offset: 8
|
|
|
|
# sh-indent-comment: t
|
|
|
|
# indent-tabs-mode: t
|
|
|
|
# End:
|
|
|
|
# ex: ts=8 sw=8 noet filetype=sh
|