READ_CHAR

     Stores in a string variable the next character entered from the
     keyboard.  This character is not echoed on the screen; therefore, the
     cursor position does not move.

  Note:  Using READ_CHAR is NOT recommended, because it does not process
         escape sequences.  If you enter escape sequences or other non-text
         characters, use READ_KEY.

         In the DECwindows version of TPU, the READ_CHAR built-in cannot
         read a keypad key or a function key.  If a TPU procedure uses
         READ_CHAR and the user presses a keypad or function key, READ_CHAR
         returns a null string and signals the warning TPU$_NOCHARREAD.

     Syntax

     string := READ_CHAR

  Examples

     1.  new_char := READ_CHAR

         Stores in the variable NEW_CHAR the next character entered from the
         keyboard.

     2.  The following procedure puts into the current buffer the next
         character entered from the keyboard.  If a key that sends an escape
         sequence is pressed, the entire escape sequence is put into the
         buffer, as if it were regular text.

         PROCEDURE user_quote_character
            COPY_TEXT (READ_CHAR);
         ENDPROCEDURE;

  Related topics

     ASCII   COPY_TEXT   READ_KEY   READ_LINE