Re: Ash wildcard usability bug

2016-10-27 Thread Lauri Kasanen
On Thu, Oct 27, 2016, at 09:14, Kang-Che Sung wrote: > If you are arguing about usability, you should assume a case that you > are in an _interactive_ shell. Non-interactive environment is for > shell scripts, and for that portability and robustness will be more > important than what you called "us

Re: Ash wildcard usability bug

2016-10-26 Thread Kang-Che Sung
On Wed, Oct 26, 2016 at 5:28 PM, Lauri Kasanen wrote: > On Wed, Oct 26, 2016, at 05:44, Kang-Che Sung wrote: >> I wonder why you can't implement an easy workaround using ls or >> something. >> >> filename="`ls *zip | head -n 1`" >> nc 10.0.0.1 12345 < "$filename" >> do_something_else <

Re: Ash wildcard usability bug

2016-10-26 Thread Lauri Kasanen
On Wed, Oct 26, 2016, at 05:44, Kang-Che Sung wrote: > I wonder why you can't implement an easy workaround using ls or > something. > > filename="`ls *zip | head -n 1`" > nc 10.0.0.1 12345 < "$filename" > do_something_else < "$filename" > > Yeah. Just avoid the glob on the redirection

Re: Ash wildcard usability bug

2016-10-26 Thread Bastian Bittorf
* Kang-Che Sung [26.10.2016 10:00]: > filename="`ls *zip | head -n 1`" > nc 10.0.0.1 12345 < "$filename" > do_something_else < "$filename" > > Yeah. Just avoid the glob on the redirection and instead get the > filename before that. Any difficulty? better do (without pipes and cheatin

AW: Ash wildcard usability bug

2016-10-25 Thread dietmar.schindler
> Von: Lauri Kasanen [mailto:cur...@operamail.com] > Gesendet: Dienstag, 25. Oktober 2016 19:25 > > > > On Mon, Oct 24, 2016, at 20:09, Denys Vlasenko wrote: > > > > Note that they allow to consistently never do globbing on the > > > > redirect word. > > > > > > > > To me it looks like the best cou

Re: Ash wildcard usability bug

2016-10-25 Thread Kang-Che Sung
On Wed, Oct 26, 2016 at 1:24 AM, Lauri Kasanen wrote: > > Well, I did try to use tab completion: cat < *zip[TAB] > > Of course it doesn't work. In my case, I had many files sharing a > prefix, but only one ending in *zip, so typing that was several > times faster than letter- tab, oh more letters,

Re: Ash wildcard usability bug

2016-10-25 Thread Lauri Kasanen
> > On Mon, Oct 24, 2016, at 20:09, Denys Vlasenko wrote: > > > Note that they allow to consistently never do globbing on the > > > redirect word. > > > > > > To me it looks like the best course of action. > > > > Surely we all agree that it's terrible usability to not expand it? > > It may be terr

AW: Ash wildcard usability bug

2016-10-25 Thread dietmar.schindler
> Von: Lauri Kasanen [mailto:cur...@operamail.com] > Gesendet: Dienstag, 25. Oktober 2016 10:49 > > On Mon, Oct 24, 2016, at 20:09, Denys Vlasenko wrote: > > Note that they allow to consistently never do globbing > > on the redirect word. > > > > To me it looks like the best course of action. > > S

Re: Ash wildcard usability bug

2016-10-25 Thread Lauri Kasanen
On Mon, Oct 24, 2016, at 20:09, Denys Vlasenko wrote: > Note that they allow to consistently never do globbing > on the redirect word. > > To me it looks like the best course of action. Surely we all agree that it's terrible usability to not expand it? - Lauri -- http://www.fastmail.com - IMAP

Re: Ash wildcard usability bug

2016-10-24 Thread Denys Vlasenko
On Mon, Oct 24, 2016 at 8:20 AM, wrote: >> Von: Denys Vlasenko >> Gesendet: Montag, 24. Oktober 2016 01:31 >> ... >> >> On Tue, Oct 18, 2016 at 4:31 PM, Lauri Kasanen wrote: >> > The following fails in ash 1.24.1, probably also in git. Works in bash. >> >> but not in non-interactive bash called

AW: Ash wildcard usability bug

2016-10-23 Thread dietmar.schindler
> Von: Denys Vlasenko > Gesendet: Montag, 24. Oktober 2016 01:31 > ... > > On Tue, Oct 18, 2016 at 4:31 PM, Lauri Kasanen wrote: > > The following fails in ash 1.24.1, probably also in git. Works in bash. > > but not in non-interactive bash called as sh! > > Interactive bash: works > Interactive b

Re: Ash wildcard usability bug

2016-10-23 Thread Denys Vlasenko
On Tue, Oct 18, 2016 at 4:31 PM, Lauri Kasanen wrote: > The following fails in ash 1.24.1, probably also in git. Works in bash. but not in non-interactive bash called as sh! Interactive bash: works Interactive bash called as sh: works bash -c 'cat http://lists.busybox.net/mailman/listinfo/busybo

Re: Ash wildcard usability bug

2016-10-18 Thread Ron Yorston
Lauri Kasanen wrote: >The following fails in ash 1.24.1, probably also in git. Works in bash. > >nc 10.0.0.1 1234 < *zip > >"sh: can't open *zip: no such file" > >Also applies to cat, etc. With only one matching file in the directory. Confirmed that it fails with latest git master. It also fails

Ash wildcard usability bug

2016-10-18 Thread Lauri Kasanen
Hi, The following fails in ash 1.24.1, probably also in git. Works in bash. nc 10.0.0.1 1234 < *zip "sh: can't open *zip: no such file" Also applies to cat, etc. With only one matching file in the directory. - Lauri -- http://www.fastmail.com - The way an email service should be ___