Bugs item #311401, was opened at 30/01/2009 10:10 Status: Open Priority: 2 Submitted By: David Paleino (hanska-guest) Assigned to: Nobody (None) Summary: DBTS 100743: inconsistent handling of filename completion wrt colons Distribution: None Originally reported in: Debian BTS Original bug number: 100743
Initial Comment: From: Yann Dirson <[email protected]> To: Debian Bug Tracking System <[email protected]> Subject: bash: inconsistent handling of filename completion wrt colons Date: Wed, 13 Jun 2001 22:25:56 +0200 Package: bash Version: 2.05-4 Severity: normal `complete-filename' is appently taking `:' as a non-filename-component. `possible-completions' OTOH accepts it as a filename-component char. -> this appears to be inconsistent -> I know that `:' is the separator for *PATH variables, but in those variables only components stating with /, or being just ".", do make sense. I don't see any reason for not activating filename completion when we're not in one of those cases. Not having file completion with colon chars not only causes problems with names of X sockets, but also with the pathnames used by SFS (www.fs.net, and packages sfs-*), which are usually cut'n'pasted and contain colons. Anyway, `:' is definitely not a special char for the shell, despite what I read as argument in one bugreport. It is interpreted specially by a number of programs and library functions, that's all. This is why I'd be in favor of using a new function, named `complete-filename-in-path' or so, and bind it for example to ESC-:, and have complete-filename do what it's name suggests it does. ---------------------------------------------------------------------- You can respond by visiting: http://alioth.debian.org/tracker/?func=detail&atid=413095&aid=311401&group_id=100114 _______________________________________________ Bash-completion-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
