Re: piping messages to external scripts

[Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday, March 19 at 05:08 PM, quoth Kyle Wheeler:
> Eh? The new process remains in control of the terminal as long as it 
> wants (i.e. it can't give up control at any point). Here's the thing, 
> though: when you pipe a message to a script, you're filling the 
> standard input with the *message*. If you use typical shell prompting 
> mechanisms, they'll all try to pull from standard input, which will 
> either be the message or will be *closed* because you already slurped 
> it up with something. So, you can't use standard input.

What I meant to add here, but forgot, is that if you DO use standard 
input, it will appear as though your script ran very quickly and then 
lost control of the terminal.

~Kyle
- -- 
Necessity is the plea for every infringement of human freedom. It is 
the argument of tyrants; it is the creed of slaves.
                                            -- William Pitt the Younger
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iEYEARECAAYFAkfhkiQACgkQBkIOoMqOI1538wCaAk4uFWmws+Rgr2Up5xCAWeU8
WGYAnjdb/evOeIY7Xz8NOWXnuU9ojpPz
=Tmjv
-----END PGP SIGNATURE-----