Re: .emacs vs .xemacs vs .xemacs.el vs...?

Tuesday, 26 May 1998

        Hrvoje Niksic <hniksic(a)srce.hr&gt; writes:

...
 Raymond Toy <toy(a)rtp.ericsson.se&gt; writes:

 > I regret not having followed the decision not to use .xemacs/
 > anymore.
 > 
 > However, since the decision has been made not to use .xemacs/, but
 > .emacs instead, I'm getting confused.  Are customizations going to be
 > stored in .emacs now?  What happened to the use of .xemacs (or was
 > that .xemacs.el) to hold XEmacs startup code?  Current behavior (b41)
 > shows that .xemacs/init.el is still read.  

 This is turning into an xemacs-beta FAQ.  No specific decision was
 ever made.  `.xemacs/' was never used in a released XEmacs version.
 Customizations aren't stored to `.emacs' "now", they've always
been
 stored to .emacs (and no, I don't like that).  I sense that, if I 
But for the last many betas, my customize options were stored in
.xemacs/xemacs-options  but perhaps that's a remnant that never got
changed in my ./xemacs/init.el.

...
 repeat it more, I think I'm gonna scream with frustration.  :-(

Sorry!

...

 Finally, this decision is not final.  It is only a strategic drawback
 before the impending release. 
It was judged not yet ready for prime time, and that's fine with me.
I do hope we revisit this, because I rather liked having everything in 
the .xemacs directory.  Less clutter.

So let me get this straight.  This is how the real 21.0 is supposed to 
work.

1.  customize (and "save options") saves its stuff in .emacs
2.  XEmacs loads only .emacs (./xemacs/init.el is gone, and .xemacs
    and .xemacs.el never existed.)
3.  There is no options.el

Ray

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998