From: "Arne Jørgensen" <arne@arnested.dk>
Subject: Re: [user42@zip.com.au: html-coding.el -- coding system from meta tag]
Date: Thu, 21 Jul 2005 00:36:30 +0200 [thread overview]
Message-ID: <87vf352jgx.fsf@seamus.arnested.dk> (raw)
In-Reply-To: E1DvMkA-0000VA-PS@fencepost.gnu.org
"Richard M. Stallman" <rms@gnu.org> writes:
> Could people who know more than I about HTML specifications please
> look at this, and tell me whether they think it is good to add to Emacs?
[...]
> From: Kevin Ryde <user42@zip.com.au>
[...]
> ;; This code is designed for Emacs 21. The Emacs cvs head (which will be
> ;; Emacs 22 or whatever) already has this feature (in
> ;; sgml-html-meta-auto-coding-function), so nothing is done there.
No need to add it to Emacs 22.
Kind regards,
--
Arne Jørgensen <http://arnested.dk/>
prev parent reply other threads:[~2005-07-20 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 22:08 [user42@zip.com.au: html-coding.el -- coding system from meta tag] Richard M. Stallman
2005-07-20 22:36 ` Arne Jørgensen [this message]
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=87vf352jgx.fsf@seamus.arnested.dk \
--to=arne@arnested.dk \
/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).