From: William Case <billlinux@rogers.com>
To: Robert Thorpe <rthorpe@realworldtech.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Another 'best' practices question ??
Date: Fri, 04 May 2007 15:58:58 -0400 [thread overview]
Message-ID: <1178308738.17374.68.camel@CASE> (raw)
In-Reply-To: <1178296587.165223.59960@y80g2000hsf.googlegroups.com>
Thanks Robert;
This exactly the kind of thing I was looking for.
On Fri, 2007-05-04 at 09:36 -0700, Robert Thorpe wrote:
[snip]
> The normal procedures is to keep the regular Emacs separate from your
> customizations of it. So, usually you put modes that you have
> downloaded from elsewhere somewhere out of the way of the normal Emacs
> tree. This allows you to upgrade Emacs more simply. The normal place
> to put these modes is in "site-lisp". There are two "site-lisp"
> directories, one in /usr/share/emacs/site-lisp is intended for things
> that can work on many versions of emacs. The one in /usr/share/emacs/
> 22.0.95/site-lisp is intended for things that are there for the
> benefit of that particular version of Emacs.
>
> A simple mode consisting of a single .el file I would put straight
> into the site-lisp directory. If the mode consists of many files that
> would make reading the directory confusing then I'd make a new
> directory just to put the mode in. Then add that dir to the load-path
> in .emacs. Or, add a line into .emacs to load the main file of the
> mode directly rather than relying on the load-path.
>
> There are no hard-and-fast rules.
I gather.
However, this question and your answer are seldom mentioned in
documentation. They are normally the kind of thing that one picks up
from colleagues. But when you are retired, working at home, there are
no colleagues to ask. So your explanation is doubly appreciated.
I recently went through the SVN manual. One of the things that made it
a real learner was the authors took the time to write a "best practises"
paragraph or two at the conclusion of major sections. It's a nice way
to summarize what has been taught previously and to relieve any concern
that a new user might have about looking like an idiot greenhorn the
first time they use a program publicly.
--
Regards Bill
next prev parent reply other threads:[~2007-05-04 19:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.183.1178214842.32220.help-gnu-emacs@gnu.org>
2007-05-04 16:36 ` Another 'best' practices question ?? Robert Thorpe
2007-05-04 18:24 ` Sebastian Tennant
2007-05-04 19:58 ` William Case [this message]
[not found] ` <mailman.256.1178309153.32220.help-gnu-emacs@gnu.org>
2007-05-08 13:40 ` Robert Thorpe
2007-05-03 17:47 William Case
2007-05-03 17:59 ` Lennart Borgman (gmail)
2007-05-03 19:35 ` William Case
2007-05-03 20:27 ` Lennart Borgman (gmail)
2007-05-04 6:12 ` Christian Herenz
2007-05-04 14:18 ` Tom Tromey
2007-05-04 15:23 ` Sebastian Tennant
2007-05-04 17:04 ` Tom Tromey
2007-05-04 17:21 ` Tom Tromey
2007-05-04 18:46 ` Sebastian Tennant
2007-05-04 18:41 ` Tom Tromey
2007-05-04 19:34 ` Sebastian Tennant
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=1178308738.17374.68.camel@CASE \
--to=billlinux@rogers.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rthorpe@realworldtech.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.
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).