Dan Norris <d-norri_at_uiuc.edu> writes:
> Thanks for all the help. The problem was passing the -Aa to gcc. All's well
> now I just have to spend the next few months customizing :)
>
> 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 :)
You should always check the FAQ if you want others to spend their
valuable time helping you. At least lie about it and say "I checked
the FAQ and I couldn't find it".
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:
Key # A A Nop
(Any line containing "Key #" would be suspect.)
Since a "#" sign is probably a shifted 3 on your keyboard, you might
also look for a line like:
Key 3 S A Nop
> Thanks,
> Dan
> --
> Dan Norris Computer Science
> d-norri_at_uiuc.edu University of Illinois
> http://www.uiuc.edu/ph/www/d-norri/
--
Dan Espen Phone: (908) 699-5570
dane_at_bae.bellcore.com
444 Hoes Lane Room RRC 1C-214
Piscataway, NJ 08854
--
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 Thu May 30 1996 - 13:42:01 BST