From: Masatake Y. <je...@gy...> - 2002-10-21 18:34:04
|
Thank you for comments. > A couple of other thoughts. First, you can't assume $_tty is set. See > the ugly code in _bashdb_msg from bashdb-io.inc. You may be inside a > command file and not in an interactive shell in which case there is no > tty. If you can find a cleaner way to handle _bashdb_msg the same > would work here. If not you might have to create the read command and > eval it - ugly. I see. I've decided to use variables that hold -F options and output stream for the prompt. See new patch. > > I've added new option -F to fource print output to stderr. > > You mean to stdout, not stderr, right? Stderr. See read.def::read_builtin: if (prompt && edit == 0) { fprintf (stderr, "%s", prompt); fflush (stderr); } The prompt is written to stderr. > Lastly I suppose we should create a test (in tests) and update the > documentation in bashref.texi. However one might wait until after we > get comments. Before these works. I'd like to commit the code to CVS repository. Ok? Masatake |