From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: utf-7 coding system autoload
Date: Mon, 24 Oct 2005 20:36:16 +0900 [thread overview]
Message-ID: <E1EU0ci-0004f7-00@etlken> (raw)
In-Reply-To: <87ll0lf1sj.fsf@zip.com.au> (message from Kevin Ryde on Sun, 23 Oct 2005 11:41:00 +1000)
In article <87ll0lf1sj.fsf@zip.com.au>, Kevin Ryde <user42@zip.com.au> writes:
> Is the utf-7 coding system a candidate for autoload-coding-system?
I agree that it's a good change. I've just installed the
attached change.
---
Kenichi Handa
handa@m17n.org
*** utf-7.el 07 Jul 2005 11:07:50 +0900 1.4
--- utf-7.el 24 Oct 2005 20:33:47 +0900
***************
*** 36,41 ****
--- 36,42 ----
;;; Code:
+ ;;;###autoload(autoload-coding-system 'utf-7 '(require 'utf-7))
(make-coding-system
'utf-7 0 ?U
"UTF-7 encoding of Unicode (RFC 2152)"
prev parent reply other threads:[~2005-10-24 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 1:41 utf-7 coding system autoload Kevin Ryde
2005-10-24 11:36 ` Kenichi Handa [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=E1EU0ci-0004f7-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@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.
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).