Aidan Kehoe <kehoea(a)parhasard.net> writes:
Ar an fichiú lá de mí Márta, scríobh Adrian Aichner:
> IIRC, it was decided we should be compatible, so that Emacs users
> giving XEmacs a try should not change to make lots of changes to get a
> familiar look.
I~m not sure what you mean there.
For example, I just did a global regexp replace ^XEmacs -> Emacs in my
~/.Xdefaults, reloaded the X resources, and started a GNU Emacs from the
middle of February. The only resources I could see that it honoured--and
I~ve set most of them--were those for the Lucid menubar, and the geometry
settings. So people moving from GNU Emacs have to write new resources
anyway, if that~s how they prefer to customise the appearance of their
Emacs. The resources for the two programs are incompatible, and getting more
so as time goes on.
Ah, that is convincing enough for me.
> Will your patch change this?
>
> Also, the emotive environent variable name
> BRANDING_IS_FOR_THE_INSECURE, while funny at first, will be a curse
> for those who try to help others in comp.emacs*.
I~m proposing that this mechanism just be available for a major release or
some equally short period, and should only be used by people who have been
No, we cannot hand-pick our users :-)
using XEmacs for years, and don~t have the time right now to move
over their
X resources. Newbies should be directed to the sample .Xresources file.
In that context, anyone we~re advising to use it should be well able to cut
and paste into their shell initialisation files, or the Win32 environment
dialog box.
My point is that discussing BRANDING_IS_FOR_THE_INSECURE on #emacs,
#xemacs, comp.emacs, etc. will just trigger confrontation.
> I'd prefer a more "technical" name.
Could you suggest one? Nothing sprang to my mind as more
appropriate, and that one is at least a little memorable.
How about
XEMACS_USES_EMACS_FRAME_NAME
which even has 28 characters too :-)
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/