unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: William Case <billlinux@rogers.com>
To: EMACS List <help-gnu-emacs@gnu.org>
Subject: Another 'best' practices question ??
Date: Thu, 03 May 2007 13:47:23 -0400	[thread overview]
Message-ID: <1178214443.3172.18.camel@CASE> (raw)

Hi;

I have downloaded nxhtml-1.00.070501.zip.  I now have to put it
somewhere and then add it to my loadpath.  Is that correct?

If so, where should I put it?  I am looking for a best practises answer
that would be applicable to other downloaded or created *.el files.

I have a half answer from the emacswiki, but that leaves me with
choosing the location and as a relative newbie it is not clear what
would be the best choice.

I have emacs 22, on a Fedora core 6 machine.  My existing loadpath is:

("/usr/share/emacs/22.0.95/site-lisp" 
"/usr/share/emacs/site-lisp" 
"/usr/share/emacs/site-lisp/site-start.d" 
"/usr/share/emacs/22.0.95/lisp" 
"/usr/share/emacs/22.0.95/lisp/url" 
"/usr/share/emacs/22.0.95/lisp/textmodes" 
"/usr/share/emacs/22.0.95/lisp/progmodes" 
"/usr/share/emacs/22.0.95/lisp/play" 
"/usr/share/emacs/22.0.95/lisp/obsolete" 
"/usr/share/emacs/22.0.95/lisp/net" 
"/usr/share/emacs/22.0.95/lisp/mh-e" 
"/usr/share/emacs/22.0.95/lisp/mail" 
"/usr/share/emacs/22.0.95/lisp/language" 
"/usr/share/emacs/22.0.95/lisp/international" 
"/usr/share/emacs/22.0.95/lisp/gnus" 
"/usr/share/emacs/22.0.95/lisp/eshell" 
"/usr/share/emacs/22.0.95/lisp/erc" 
"/usr/share/emacs/22.0.95/lisp/emulation" 
"/usr/share/emacs/22.0.95/lisp/emacs-lisp" 
"/usr/share/emacs/22.0.95/lisp/calendar" 
"/usr/share/emacs/22.0.95/lisp/calc" 
"/usr/share/emacs/22.0.95/leim")

Should I create a new directory in "/usr/share/emacs/22.0.95/lisp" or
add the file to an existing directory?  I tried to include it with the
XHTML-mode but I could find specific XHTML, HTML or PHP mode files or
directories to include it with.  Is that a good idea or not?

-- 
Regards Bill

             reply	other threads:[~2007-05-03 17:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 17:47 William Case [this message]
2007-05-03 17:59 ` Another 'best' practices question ?? 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
2007-10-29 12:29                   ` ELPA package listings [formerly: Another 'best' practices question ??] Sebastian Tennant
2007-10-29 12:36                     ` Sebastian Tennant
     [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
     [not found]   ` <mailman.256.1178309153.32220.help-gnu-emacs@gnu.org>
2007-05-08 13:40     ` Robert Thorpe

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=1178214443.3172.18.camel@CASE \
    --to=billlinux@rogers.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).