[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: stderr usage instead of /dev/tty
From: |
Paul Jarc |
Subject: |
Re: stderr usage instead of /dev/tty |
Date: |
Fri, 10 Aug 2001 14:08:41 -0400 |
User-agent: |
Gnus/5.090004 (Oort Gnus v0.04) Emacs/20.7 |
Please observe Mail-Copies-To or Mail-Followup-To, depending on
whether you're reading via mail or news.
Padraig Brady <Padraig@linux.ie> writes:
> Paul Jarc wrote:
>> What would definitely be more flexible is if bash let you use
>> normal redirection for interactive stuff independently.
>
> Yes, it would be more flexible, but is there any reason you would
> every need to redirect the prompt/readline() stuff. This is only human
> parseable?
It seems that way. But if everyone who thought that was always right,
we wouldn't need Expect.
>> You could do something like:
>> $ bash-set-interpreter 'eval "$BASH_COMMAND" 2> somewhere'
>> bash-set-interpreter would be a new builtin.
BTW, a while ago, someone else asked for something like
$PROMPT_COMMAND which would be run after the user entered a command,
and before executing the command. (He didn't say what he wanted to
use it for.) This feature would also satisfy that request.
paul
Re: stderr usage instead of /dev/tty, Padraig Brady, 2001/08/09