On Wed, Mar 20, 2002 at 09:25:21PM +0100, Oystein Viggen wrote: > It's cheating, but wouldn't the following in most cases do the same as > filter? > > #!/bin/bash > `showtrans $1 | cut -d \ -f 2-`
Sure, that's a neat trick, too (you might need to strip more options from it that are specific to the translator, though, when they appear). > Generally, filtering input through a translator that runs a program > seems to me a bit more cumbersome than just piping directly through the > program :) Yes, maybe this can be combined with some muxing translator in some interesting way, etc... I never claimed to have inventing anything, but I think there is potential. It also allows to easily demonstrate what translators do and how they work. It's just another variant of the chaining commands idea. > (Oh, and you _can_ do this using just the shell and clever redirects, no > filter program involved. Lookie here: > <URL: http://mail.gnu.org/pipermail/bug-hurd/2002-January/006342.html >) Ah, that's a nice trick, I drop my filter idea. If it's not necessary, it doesn't make sense to write it. Thanks, Marcus _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
