[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problems with INTERACTIVE-STREAM-P
Nathan Sidwell <firstname.lastname@example.org> writes:
> However, it is always saying *error-output* is interactive, even when I
> redirect to a file or pipe, ie,
> clisp -x '(interactive-stream-p *error-output*)' >& foo
> puts T into the output file. I get the same result when I use
> *standard-output* or *terminal-io* too.
You have redirected the output to a file, but the input part of *terminal-io*
is still referring to your terminal. This is why `interactive-stream-p'
You could redirect standard input from /dev/null, but unfortunately CLISP
does not know about /dev/null's special nature. (How do you tell that
a file descriptor is pointing to /dev/null when all you have is the file
Bruno Haible email: <email@example.com>
Software Engineer phone: +33-1-49083585