From: Richard Stallman <rms@gnu.org>
To: "paul r" <paul.r.ml@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Feature Request : autoload-form
Date: Mon, 31 Mar 2008 12:24:45 -0400 [thread overview]
Message-ID: <E1JgMoP-00024x-7G@fencepost.gnu.org> (raw)
In-Reply-To: <e30f0f320803300424s6215e966v859f8822d054853f@mail.gmail.com> (paul.r.ml@gmail.com)
- I got rid of the monolithic .emacs, so that bits of configuration
go into dedicated "modules". There is a module for C-mode, one for
Muse-mode etc. One module resides in one file. Modules are shared in
your network of friends/colleagues ... anybody syncing with you, so
they are "network-specific" but not "user-specific".
I think I understand what these do. I'm not completely sure why you
want them, though. What job do these do, which you couldn't do by
installing some Lisp libraries in the usual way?
- To allow fine-tuning, a user can use "module configuration file",
which is an other file, with personal tweaking in it. Those conf files
are not shared and are usually optional. They are user specific, and
private. Exemple : the ERC module does a lot of configuration, but it
can not set up username, password etc because this information is
user-specific.
Why not put this stuff directly in .emacs?
I could put, at beginning of *every* modules, a (load-file
"thisModuleConfigurationFile" t).
I don't see why you want to do that, rather than putting the
"module configuration" expressions directly in .emacs.
What do you gain?
This is what I did before, but I do
not find that elegant, nor fully satisfactory in many ways for the
needs, so it now is to the TidyConfig system to carry proper loading
of modules.
I am confused. Are you talking about making a module load its module
configuration expressions, or are you talking about how to load the
module itself when it is needed? Those are two different issues, right?
Some of your words seem to imply one, and some seem to imply the other.
Here we are. I currently have no option to do so, except putting the
form I want to eval in a dummy file and registering this file with
autoload.
I have lost you completely here.
next prev parent reply other threads:[~2008-03-31 16:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 20:05 Feature Request : autoload-form paul r
2008-03-29 4:20 ` Stefan Monnier
2008-03-29 9:49 ` paul r
2008-03-29 19:40 ` Stefan Monnier
2008-03-30 5:49 ` Richard Stallman
2008-03-30 11:24 ` paul r
2008-03-30 15:03 ` Stefan Monnier
2008-03-30 22:28 ` paul r
2008-03-31 7:58 ` Levin Du
2008-03-30 19:55 ` Richard Stallman
2008-03-30 21:35 ` Mike Mattie
2008-03-31 16:24 ` Richard Stallman [this message]
2008-03-31 17:36 ` paul r
2008-03-31 21:31 ` Mike Mattie
2008-04-02 2:53 ` Richard Stallman
2008-04-02 12:44 ` paul r
2008-04-02 17:34 ` Richard Stallman
2008-04-02 19:06 ` paul r
2008-04-02 21:07 ` Don Armstrong
2008-04-03 4:30 ` Stephen J. Turnbull
2008-04-03 5:01 ` Don Armstrong
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=E1JgMoP-00024x-7G@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=paul.r.ml@gmail.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).