Bug#919833: 90% of shell scripts probably don't have a .sh extension

2019-03-13 Thread Gabriel F. T. Gomes
On Wed, Mar 13 2019, 積丹尼 Dan Jacobson wrote: > > OK, maybe even less, > $ file /usr/bin/*|grep -c shell\ script > 194 > $ ls /usr/bin/*.sh > /usr/bin/gettext.sh This only means that a very tiny fraction of shell scripts *inside* /usr/bin have .sh extension. Anyhow, thanks for the clarification.

Bug#919833: 90% of shell scripts probably don't have a .sh extension

2019-03-13 Thread 積丹尼 Dan Jacobson
> "GFTG" == Gabriel F T Gomes writes: GFTG> You could be right (specially since bash completes any filename), GFTG> however, where did you get this statistic from? OK, maybe even less, $ file /usr/bin/*|grep -c shell\ script 194 $ ls /usr/bin/*.sh /usr/bin/gettext.sh But that's just my

Bug#919833: 90% of shell scripts probably don't have a .sh extension

2019-03-10 Thread Gabriel F. T. Gomes
On Sun, Jan 20 2019, 積丹尼 Dan Jacobson wrote: > Package: bash-completion > Version: 1:2.8-5 > Severity: wishlist > File: /usr/share/bash-completion/completions/sh > > I think 90% of shell scripts don't have a .sh extension. > Therefore > $ sh anyf > should still complete to > $ sh anyfile You

Bug#919833: 90% of shell scripts probably don't have a .sh extension

2019-01-19 Thread 積丹尼 Dan Jacobson
Package: bash-completion Version: 1:2.8-5 Severity: wishlist File: /usr/share/bash-completion/completions/sh I think 90% of shell scripts don't have a .sh extension. Therefore $ sh anyf should still complete to $ sh anyfile Thanks.