1\variable{MESSAGE_BUFFER}
2\synopsis{The Contents of the Message Buffer}
3\usage{String_Type MESSAGE_BUFFER}
4\description
5  The \var{MESSAGE_BUFFER} variable is a read-only string variable
6  whose value indicates the text to be displayed or is currently
7  displayed in the message buffer.
8\seealso{message, vmessage, error, verror}
9\done
10
11\function{beep}
12\synopsis{Beep (according to the value of \var{IGNORE_BEEP})}
13\usage{Void beep ();}
14\description
15  The \var{beep} function causes the terminal to beep according to the value
16  of the variable \var{IGNORE_BEEP}.
17\seealso{tt_send}
18\seealso{IGNORE_BEEP}
19\done
20
21\function{clear_message}
22\synopsis{Clear the message line of the display}
23\usage{Void clear_message ();}
24\description
25  This function may be used to clear the message line of the display.
26\seealso{message, update, error, flush}
27\done
28
29\function{flush}
30\synopsis{Immediately display "msg" as a message in the mini-buffer}
31\usage{Void flush (String msg);}
32\description
33  The \var{flush} function behaves like \var{message} except that it immediately
34  displays its argument \var{msg} as a message in the mini-buffer.  That is,
35  it is not necessary to call \var{update} to see the message appear.
36\seealso{message, error}
37\done
38
39\function{tt_send}
40\synopsis{Send "s" directly to the terminal}
41\usage{Void tt_send (String s);}
42\description
43  This function may be used to send a string specified by \var{s} directly
44  to the terminal with no interference by the editor.  One should
45  exercise caution when using this routine since it may interfere with
46  JED's screen management routines forcing one to redraw the screen.
47  Nevertheless, it can serve a useful purpose.  For example, when run in
48  an XTerm window, using
49#v+
50        tt_send ("\e[?9h");
51#v-
52  will enable sending mouse click information to JED encoded as
53  keypresses.
54\seealso{beep}
55\done
56
57