* [Marcus Brinkmann] > So I am considering to write a "filter" program that has two threads > and takes a filename as an argument. One thread reads on stdin and > writes to the opened file, the other thread reads from the file and > writes to stdout. This should work rather well, and can be used like > this: > > cat text | filter /tmp/foo > /tmp/text-foo-ed
It's cheating, but wouldn't the following in most cases do the same as filter? #!/bin/bash `showtrans $1 | cut -d \ -f 2-` Generally, filtering input through a translator that runs a program seems to me a bit more cumbersome than just piping directly through the program :) Users will probably ask for this later anyway, and it's useful if the program needs special access (root or another system user could own the node), so it would still be worth having. (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 >) Oystein -- This message was brought to you by the letter ß and the number e. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
