host: elwood
path: /users/database/faq/mbedit
file: terminal.htm

M.Braun - MHE 1 - 28.02.01


Frequently asked Questions: mbedit
----------------------------------

Q: I can't invoke mbedit from the command line:

A: Ensure, that the search PATH is setup correctly, for example:
      unix: PATH=$PATH:/usr/local/bin:.
      os-9: setenv PATH $(PATH)/dd/XCMDS:



Q: After starting up mbedit, I see only a whole lot of strange characters on
   the screen:


   
   Click for Full Size
   mbedit started in an hpterm 


A: You are probably using the wrong terminal emulation (hpterm instead of
   xterm). mbedit assumes to run in a vt100 compatible terminal window.

   If you are inside an hpterm, this doesn't interprete the escape sequences
   correctly and thus produces a lot of unreadable characters.

   Solution: Start an xterm by typing "xterm &" and start mbedit again in
   the new xterm, which is vt100 compatible.


   
   Click for Full Size
   mbedit started in an xterm (empty file) 



Q: It's not possible to open an xterm. I get an error message instead:
   "Error: Can't open display: hostname:0.0
    Error: Couldn't find per display information".

A: Make sure, that the environment variable DISPLAY ist set correctly,
   for example:
      DISPLAY=xterm16:0.0
      export DISPLAY

   Set the access rights by typing "xhost +" in a new window.
   The system must response with:
   "access control disabled, clients can connect from any host".