From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Bug] Issues with format.el: coding system, byte/char confusi on
Date: Wed, 09 Apr 2003 01:39:24 -0400 [thread overview]
Message-ID: <E1938Iu-0000HG-00@fencepost.gnu.org> (raw)
In-Reply-To: <67B8CED503F3D511BB9F0008C75DAD6605485571@dewdfx17> (christoph.wedler@sap.com)
> That would be true, if there is anything in
> after-insert-file-functions other than
> after-insert-file-set-buffer-file-coding-system. Normally I believe
> there isn't anything else.
What does this mean? Is `after-insert-file-functions' obsolete without
being declared as such?
It is not obsolete. What I am saying is that normally the only
element of after-insert-file-functions is
after-insert-file-set-buffer-file-coding-system.
If you add other elements, you can choose where to put them.
> Not necessarily. That would depend on what those other functions are.
> Normally there aren't any others. I suppose if you add other functions
> to this hook that you should put them in the proper order.
As I said, the coding system is determined not only after some functions
in this hook, but also after the format-decode functions.
I think I am totally lost now.
next prev parent reply other threads:[~2003-04-09 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 18:01 [Bug] Issues with format.el: coding system, byte/char confusi on Wedler, Christoph
2003-04-09 5:37 ` Kenichi Handa
2003-04-09 5:39 ` Richard Stallman [this message]
2003-04-15 2:06 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 18:26 Wedler, Christoph
2003-04-10 6:23 ` Richard Stallman
2003-04-10 12:05 ` Kenichi Handa
2003-04-11 8:51 ` Richard Stallman
2003-04-11 11:04 ` Kenichi Handa
2003-05-02 14:11 Wedler, Christoph
2003-05-03 15:03 ` Richard Stallman
2003-05-13 17:18 Wedler, Christoph
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=E1938Iu-0000HG-00@fencepost.gnu.org \
--to=rms@gnu.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).