May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Jan Vroonhof

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > site-start can be *anywhere* in the load-path, and it follows the > usual rules for vanilla Elisp files. init.el is (the way the current > proposals are going) getting hard-coded at ~/.xemacs or > ~/.xemacs/lisp. No. My proposal loads the file[1] with means that it can be anywhere as well. I just ~/.xemacs/lisp as an example. Jan [1] It uses locate-file first but that is just because we need to set the value of user-init-file.

1 participants
0 comments

Re: custom file .xemacs and all that jazz. 25 years, 11 months

Jan Vroonhof

[Sorry, I should never have bound lisp-complte-symbol to C-c c ] sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > Note also that early-package-load-path may be nil. Which means that "~/.xemacs" isn't there and XEmacs will therefore happily load .emacs. (If we locate the library with (locate-file "site" early-package-load-path ".elc:.el:") instead of using load-library). Note that for my part we could also refrain from using early-package-load-path and just use the full load-path by I wanted try to keep stat'ing to a minimum. Jan

1 participants
0 comments

Re: custom file .xemacs and all that jazz. 25 years, 11 months

Jan Vroonhof

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > Note also that early-package-load-path may be nil. Which means that "~/.xemacs" isn't there and XEmacs will therefore happily load .emacs. (If we locate the library with (locate-file "site" early-package-

1 participants
0 comments

Re: custom file .xemacs and all that jazz. 25 years, 11 months

Jan Vroonhof

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > Jan> To me 'init.el' and 'options.el' are just startup files that are > Jan> (load..)-ed. > > That's not the way the code handles them. They are in the new version of the code I proposed. The only trouble is that if they are not found we need to go off and load .eamcs. Therefore the advertised locations becomes ~/.xemacs/lisp/init.el but it could as well be in in ~/.xemacs/lisp/my-own-init/init.el or anywhere else. Any special location for early.el, init.el etc and friends goes away they are just normal Emacs libraries that get 'load'ed. Nice and clean. That is why putting them in ./xemacs (i.e. no lisp dir) is ugly because that still needs special casing. > This is a crucial difference, though, as it fixes the location of > options.el. Therefore I propose to autodetect where we loaded them from and by default write the customs back there. This will also work with customizations in .emacs if you want to be compatible with FSF Emacs. The only thing that is fixed is that BY DEFAULT a NEW options.el in ~/.xemacs/lisp/ is used when there were no previous customizations. I you want to change that, just set custom-file. Jan -- Jan Vroonhof http://www.math.ethz.ch/~vroonhof/ Mathematik, vroonhof(a)math.ethz.ch HG E16, ETH-Zentrum, Tel: +41-1-6325456/25154 Raemistrasse 101, CH-8092 Zuerich. Fax: +41-1-6321085

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Michael Sperber

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> SL Baur <steve(a)xemacs.org> writes: >> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> >> > `.xemacs/' was never used in a released XEmacs version. >> >> .xemacs/ is recognized as a user package directory if it exists in >> both 20.3 and 20.4. Hrvoje> ...which is fine. Hrvoje> I meant `.xemacs/' as a directory prefix for random initialization Hrvoje> files. Hrvoje's absolutely right. If you guys put random stuff in there, I promise something will break eventually. It does not belong there. Ever. Period. The only way to use ~/.xemacs for random init goop would be to put the default early package hierarchy somewhere else. Maybe ~/.xemacs-packages. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

3 participants
2 comments

Re: custom file .xemacs and all that jazz. 25 years, 11 months

Michael Sperber

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> I don't like this. early-package-load-path has a well-defined meaning >> and is orthogonal to custom-file location. Jan> But WHY? Could you please explain to me what is so special about the Jan> package hierarchy such that site-start can be put in it but init.el Jan> and options.el not. Note also that early-package-load-path may be nil. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: custom file .xemacs and all that jazz. 25 years, 11 months

Michael Sperber

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> I don't like this. early-package-load-path has a well-defined meaning >> and is orthogonal to custom-file location. Jan> But WHY? Could you please explain to me what is so special about the Jan> package hierarchy such that site-start can be put in it but init.el Jan> and options.el not. Jan> To me 'init.el' and 'options.el' are just startup files that are Jan> (load..)-ed. That's not the way the code handles them. Jan> The only special thing with options.el is is that it is Jan> autogenerate. This is a crucial difference, though, as it fixes the location of options.el. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Michael Sperber

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: >> If you guys put random stuff in there, I promise something will break >> eventually. It does not belong there. Ever. Period. The only way >> to use ~/.xemacs for random init goop would be to put the default >> early package hierarchy somewhere else. Maybe ~/.xemacs-packages. Jan> Why? If site-start can be in lib/xemacs/packages/lisp why can init.el Jan> not be in .xemacs/lisp? site-start can be *anywhere* in the load-path, and it follows the usual rules for vanilla Elisp files. init.el is (the way the current proposals are going) getting hard-coded at ~/.xemacs or ~/.xemacs/lisp. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: custom file .xemacs and all that jazz. 25 years, 11 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > I don't like this. early-package-load-path has a well-defined meaning > and is orthogonal to custom-file location. But WHY? Could you please explain to me what is so special about the package hierarchy such that site-start can be put in it but init.el and options.el not. To me 'init.el' and 'options.el' are just startup files that are (load..)-ed. The only special thing with options.el is is that it is autogenerate. Jan

1 participants
0 comments

Re: XEmacs 21.0 DND API Part 7 25 years, 11 months

Adrian Aichner

>>>>> "Oliver" == Oliver Graf <ograf(a)fga.de> writes: Oliver> This patch is against plain b41. Oliver> It gives the CDE code the same dragging functinality as Oliver> the OffiX code has (i.e. it now can also drag filenames). Oliver> It's tested, but perhaps some CDE users can try Oliver> tests/Dnd/droptest.el also Oliver> (hi Adrian!). Hi Oliver, I have performed droptest.el under emacs-version "21.0 \"San Clemente\" XEmacs Lucid (beta41)" without any patches (obtained via CVS). I DND'd every top-button onto each bottom-target. Are there any other side-effects other than the message-log messages? Schöne Grüße, Adrian Here is what the message log has to say: load droptest.el? (y or n) load droptest.el? (y or n) Yes Loading /export/home/tmp/CVSroot/xemacs-20/tests/Dnd/droptest.el... Loading /export/home/tmp/CVSroot/xemacs-20/tests/Dnd/droptest.el...done load: 1 file. Wrote /u/aichner/tmp/DNDmisc-userExtentTestBuffer Dropped on target 1 with :(dragdrop-MIME ((text/plain) 8bit That's a test)) Dropped on target 2 with :(dragdrop-MIME ((text/plain) 8bit That's a test)) Dropped on target 3 with :(dragdrop-MIME ((text/plain) 8bit That's a test)) Dropped on target 1 with :(dragdrop-URL file:/tmp/printcap) Dropped on target 2 with :(dragdrop-URL file:/tmp/printcap) Dropped on target 3 with :(dragdrop-URL file:/tmp/printcap) Dropped on target 1 with :(dragdrop-URL file:/tmp/printcap file:/tmp/droptest file:/tmp/dragtest) Dropped on target 2 with :(dragdrop-URL file:/tmp/printcap file:/tmp/droptest file:/tmp/dragtest) Dropped on target 3 with :(dragdrop-URL file:/tmp/printcap file:/tmp/droptest file:/tmp/dragtest) Dropped on target 1 with :(dragdrop-URL http://www.xemacs.org/) Dropped on target 2 with :(dragdrop-URL http://www.xemacs.org/) Dropped on target 3 with :(dragdrop-URL http://www.xemacs.org/) Here is how the DND Test Buffer looked initially: -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Straße 2 Fax +49/89/41861-217 D-81673 MÜNCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

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

XEmacs-Beta May 1998