On Fri, Sep 07, 2012 at 06:50:48AM +0200, Harald Becker wrote: > Hi Rich ! > > On 07-09-2012 00:13 Rich Felker <[email protected]> wrote: > > >">file" is valid by itself as a command; it truncates file to 0 bytes, > >creating it if it does not exist. It's even more useful with noclobber > >mode, e.g. > > > >set -C;bg_command&>lockfile||exit 1 > > I don't want to jump into the discussion (due to lack of time), so just > some question to satisfy my interesst: > > What magic thing are you trying to do here? > > set -C;>lockfile||exit 1 > > looks ok ... create lockfile or abort if not possible > > .... why throwing in that background command at this place? > > .... why not generally adding a space after &? It's so easy to fix the > script with a single sed call, if it does not contain tons of ugly > constructs (like strings containing "&>"). > > Sorry if it sound provocative, I'm just interested/wondering what/why > are you doing here. Nothing more.
I'm not doing it. I'm just uncomfortable with having a shell that will misinterpret conforming, albeit obfuscatd, shell scripts from third parties, and was giving one such example. I suspect the main place such code might come from a is a script that obfuscates and/or removes all unnecessary whitespace from a given shell script. Rich _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
