Sorry about the indentation, supercite gets seriously confused....
>>>> "-BP" == William M Perry
<wmperry(a)aventail.com> writes:
-BP> Hrvoje Niksic <hniksic(a)srce.hr> writes:
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp>
writes:
> Hrvoje> I don't know if it ever worked. The funny thing is that I
> Hrvoje> don't even know if it's *supposed* to work. It doesn't
> Hrvoje> work in FSFmacs, for instance. It works for xterm,
> Hrvoje> though. `xterm -name foo' effectively makes xterm ignore
> Hrvoje> all of my resources.
>
> Presumably all your resources are specified with "xterm*...", not
> "XTerm*..."?
Yup. Should I rename my resources to `xemacs*'?
Short answer: yes. Of course, as Bill points out:
-BP> But then you by default get a personal-resource-less xemacs
-BP> when you run 'xemacs-21.0-b39', etc. Which I find
-BP> annoying. :)
I guess it's adding insult to injury, but the "solution" to that is of
course `xemacs-21.0-b39 -name xemacs'.
An alternative solution is one I mentioned earlier: replicating
XEmacs.ad with the name for all resources set to "vanilla".
In fact, this might be a good thing to provide in general. Then
xemacs -vanilla could be taught to set the application name to
"vanilla", too. This would rid of us of confusion via user's
resource settings as well as the .emacs, etc. in debugging, all in one
shot.
The only problem I can see is that there may be resources that are not
mentioned in XEmacs.ad. Of course, XEmacs.ad doubles in length....
Agh! Code bloat! :-)
And, of course, the maintainers need to specify exactly what would be
most useful as a vanilla XEmacs. This is mostly done, of course, but
with something as weird as X resources it's probably worth pausing for
thought. And what's already in XEmacs.ad may not be best. (Allowing
for the possibility that "best" != "any constant baseline will do".)