Dan Espen wrote,...
> Dan Norris <d-norri_at_uiuc.edu> writes:
> > I also ran into a problem with vi. When I was using mwm, vi seemed to be
> > fine. Now, after switching to fvwm, I can't seem to insert any "#" signs int
> > into anything. Is this something common? Maybe I should check the FAQ,
> > but I'm sure someone has the answer :)
>
> Fvwm has no specific interaction with vi. If you can't type a "#"
> sign in any window, it is possible that fvwm is intercepting the "#"
> before the application sees it. If you also can't type "#" in an
> xterm, look in your .fvwm2rc for a line like:
I assume that the tty modes of your xterms are set incorrectly: you
probably cannot insert a '_at_' anywhere either...
This d_at_#$mned default (erase_character=# kill_whole_line=@) goes back to
the olden teletype days (as does the name tty); wonder why at&t stuck
with it.
The cure might be something aling the line of ....
XTerm*TtyModes: erase ^h kill ^x dsusp ^y susp ^Z weras ^W eol ^j
...in your ~/.Xdefaults ~/.Xresources. It initializes your xterms to a
"sane" mode.
Martin
--
| S I E M E N S | Martin.Kraemer_at_mch.sni.de | Siemens Nixdorf
| ------------- | Voice: +49-89-636-46021 | Informationssysteme AG
| N I X D O R F | FAX: +49-89-636-44994 | 81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri May 31 1996 - 03:22:34 BST