unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: William Case <billlinux@rogers.com>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>,
	EMACS List <help-gnu-emacs@gnu.org>
Subject: Re: Another 'best' practices question ??
Date: Thu, 03 May 2007 15:35:20 -0400	[thread overview]
Message-ID: <1178220921.3172.31.camel@CASE> (raw)
In-Reply-To: <463A22EF.7060707@gmail.com>

Hi Lennart;

I appreciate your personal response.

On Thu, 2007-05-03 at 19:59 +0200, Lennart Borgman (gmail) wrote:
> William Case wrote:
> > 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?
> 
> Unpack it and follow the instructions in readme.txt. You do not have to 
> put it in your load-path. If you follow the instructions some 
> directories will instead be added to your load-path.
> 
> > If so, where should I put it?
> 
> Anywhere, see above.
> 
> When you open your first .html file you will get some more instructions.
> 
> > 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?
> 
> I am not sure what you mean, but nXhtml includes a new mode for XHTML 
> called nxhtml-mode. You can also use the mode that comes with Emacs 22, 
> html-mode, but then you will miss completion for XHTML.
> 
> nXhtml also includes a php-mode. Please use that one, not some other 
> version, since I have made some corrections to it.
> 

I can see that my above questions, might have been particularly
newbie-dumb, but I am not the only dumb newbie out there. Might not it
have been useful to other users to see your response.

Particularly, since I have followed your instructions and have the new
nXhtml-mode working, I would now like to congratulate you on your work.
I think that those kudos from me and others should be on the public
list.

I am really impressed with what you have done and what you have shown
can be done with Lisp in emacs. 

-- 
Regards Bill

  reply	other threads:[~2007-05-03 19:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 17:47 Another 'best' practices question ?? William Case
2007-05-03 17:59 ` Lennart Borgman (gmail)
2007-05-03 19:35   ` William Case [this message]
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=1178220921.3172.31.camel@CASE \
    --to=billlinux@rogers.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lennart.borgman@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.
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).