From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Jarek Czekalski <jarekczek@poczta.onet.pl>, emacs-devel@gnu.org
Subject: Re: run/load a lisp script before user init file
Date: Wed, 09 Oct 2013 10:56:36 +0900 [thread overview]
Message-ID: <87fvsbjjfv.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <874n8rhdqr.fsf@fleche.redhat.com>
Tom Tromey writes:
> FWIW a long term goal I had for package.el was to have it also manage
> site-lisp.
XEmacs has had an option to have no site-lisp for more than 10 years,
and it's become default several years ago.
The preferred alternative is to put your code in
.../site-packages/my-stuff/library.el, decorate entry points with
autoload cookies, add a simple Makefile and package-info.in (mostly
complete skeletons provided for easy cases), and run make; make
bindist.
> Distros could easily take advantage of this by ensuring that elisp
> installed into site-lisp follows the package.el installation rules.
> This is easy to do...
Social engineering-wise, we didn't find it so. That's why we changed
the name when we changed the interface.
next prev parent reply other threads:[~2013-10-09 1:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 15:24 run/load a lisp script before user init file Jarek Czekalski
2013-10-07 16:43 ` Eli Zaretskii
2013-10-07 18:42 ` Jarek Czekalski
2013-10-07 19:00 ` Eli Zaretskii
2013-10-07 19:37 ` Jarek Czekalski
2013-10-07 20:08 ` Eli Zaretskii
2013-10-07 22:52 ` Stefan Monnier
2013-10-08 5:52 ` Jarek Czekalski
2013-10-08 6:27 ` Stephen J. Turnbull
2013-10-08 6:40 ` Harald Hanche-Olsen
2013-10-08 13:09 ` Stephen J. Turnbull
2013-10-08 14:30 ` Jarek Czekalski
2013-10-08 14:36 ` Jarek Czekalski
2013-10-08 14:50 ` Jarek Czekalski
2013-10-08 16:01 ` Stephen J. Turnbull
2013-10-08 19:34 ` Josh
2013-10-08 6:46 ` Jarek Czekalski
2013-10-08 16:22 ` Glenn Morris
2013-10-08 17:30 ` Tom Tromey
2013-10-09 1:56 ` Stephen J. Turnbull [this message]
2013-10-08 21:47 ` Jarek Czekalski
2013-10-08 6:16 ` Kevin Rodgers
-- strict thread matches above, loose matches on Subject: below --
2013-10-10 13:52 Barry OReilly
2013-10-10 16:11 ` Josh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvsbjjfv.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=jarekczek@poczta.onet.pl \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).