Bugs item #313328, was changed at 2011-09-04 11:30 by Ville Skyttä You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313328&group_id=100114
>Status: Closed Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Regression: "sh filename" completion works only if filename ends in .sh Distribution: --Distribution-Agnostic-- Originally reported in: None Milestone: None >Status: Won't Fix Original bug number: Initial Comment: In bash-completion 1.3, after the "sh" command, only folders and files ending with .sh are completed. But often there are scripts with no extension, so it would be desirable to suggest all files as possible expansions. This worked in a previous version of bash-completion (but I'm not sure which one, maybe 1.2). This bug has been reported here: http://bugzilla.novell.com/show_bug.cgi?id=715865 Steps to reproduce: cat <<EOF >my_script #!/bin/sh echo Hello world EOF chmod +x my_script sh my_<<TAB>> Expected behaviour: "my_" is completed to "my_script" Current behaviour: Nothing happens. ---------------------------------------------------------------------- >Comment By: Ville Skyttä (scop-guest) Date: 2011-09-04 23:33 Message: As far as I'm concerned, this is intentional and consistent with other completions. Users can always force bash's default filename completion with Alt+/ if they do not like bash-completion's behavior. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313328&group_id=100114 _______________________________________________ Bash-completion-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel
