Xterm and .Xresources

[Jerry A Clabaugh]

Actually, since I'm starting this xterm from the fvwm2
config file, the -fn option is not an impediment at all,
and solves my problem.  

It seems that specifying xterm*geometry or xterm*font
in a .Xresources or .Xdefaults file causes the xterm
popup menus to break.  I'll assume it's a bug in xterm.
Thanks to both -

Jerry

On Wed, 1 Sep 1999, Derek Martin wrote:

> On Wed, 1 Sep 1999, John Chambers,,,781-647-1813 wrote:
> 
> > 	DON'T DO THAT! 
> > 
> > Whever not?  Isn't this how .Xresources is supposed to be used?  Just
> > shouting  at  someone  to NOT DO something isn't very helpful, unless
> > you give some explanation as to what you're shouting to not  do.   Do
> > you mean to not use .Xresources? How about .Xdefaults? Or do you mean
> > to not use xterm* entries?  Or perhaps you're  shouting  to  not  use
> > *font entries?  Or maybe you know of something broken specifically in
> > xterm*font?
> 
> Well, you are right of course, but I was and still am short on time.
> Ordinarily I would not do that, and I didn't really mean to leave it at
> that but I was distracted by the task at hand. I don't remember exactly
> what the deal is but I think that sets ALL the xterm fonts to the same
> thing, causing the popup menus to all use the same font.
> 
> 
> -- 
> Derek D. Martin   |  UNIX System Administrator
> derek at netria.com  |  dmartin at lancity.com
> 
> -
> Subcription/unsubscription/info requests: send e-mail with
> "subscribe", "unsubscribe", or "info" on the first line of the
> message body to discuss-request at blu.org (Subject line is ignored).
> 

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).