🚀 go-pugleaf

jonathan@cats.ucsc.edu (Jonathan Cano) and Gary Murphy writes:
 
 
>I'm using xemacs v18.58 on a sun4 architecture.
 
>When I run emacs like this:
>  % xemacs -font 8x13 -geometry 81x60+200+5 &
 
>emacs uses the font and geometry that I specify but it also
>creates buffers called -font, 8x13, -geometry and 81x60+200+5 !
>This is not what I want!! Is this a bug or am I doing something wrong?
 
>Also, emacs seems to ignore the resource that I specify in my .Xdefaults
>file e.g.
>Xemacs*geometry (or Xemacs*Geometry)
 
Gee jonathan, I've experienced the same problem and I can't help you.
I'm replying to your message so you won't think the messages that
you post to this news group are invisible ... :^)
 
--Jonathan

The first problem you mentioned looks like a bug but the second is a 
problem in your definition.  The rules for classes in the .Xdefaults
dictates that if the first character begins with an X the second letter
must be capitalized also, ie XEmacs, but in this case the class isn't
xemacs but rather Emacs.

Here are the emacs entries from my .Xdefaults file.

Emacs*font:     9x15
emacs*Background:       LightBlue
emacs*Foreground:       black
Emacs*bitmapIcon:       on
Emacs*Cursor:   red
Emacs*Geometry: 80x48-10-30
emacs*Mouse:    green
emacs*iconName: tec

Note that you can freely mix class entries and command name entries.
The class entries apply to all things emacs while the command (lower
case) entries only apply to the command called emacs.  If emacs is renamed
they wouldn't be found.  These work on my sun.





--
    _      _     Dale DePriest  		San Jose, California
   /`) _  //     daled@Cadence.COM		voice: (408) 428-5249
 o/_/ (_(_X_(`