[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: run.c translator

From: Oystein Viggen
Subject: Re: run.c translator
Date: Wed, 20 Mar 2002 21:25:21 +0100
User-agent: Gnus/5.090005 (Oort Gnus v0.05) XEmacs/21.1 (Capitol Reef, i386-debian-linux)

* [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

`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 >)

This message was brought to you by the letter ß and the number e.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]