From: Richard Stallman <rms@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: insert-file-contents and format-decode
Date: Sat, 30 Jun 2007 20:30:29 -0400 [thread overview]
Message-ID: <E1I4nKf-0002m7-JR@fencepost.gnu.org> (raw)
In-Reply-To: <46863F67.20208@gmx.at> (message from martin rudalics on Sat, 30 Jun 2007 13:32:55 +0200)
> We have a plan for dealing with functions called by `format-decode'. We
> do not have a plan yet for dealing with `after-insert-file-functions'.
> Shall we treat functions there the same way we treat functions called by
> `format-decode'?
>
> If it's good for one, it's probably good for the other. Consistency
> between the two features is also good.
>
> Do you see any reason NOT to do so?
We could introduce one: Keep `format-decode' for practical use and
`after-insert-file-functions' for applications that want to fine-tune
every single step of the decoding process.
Incoherence is a minus, not a plus. If there is no specific reason
to treat them differentlky, let's treat them the same!
I already changed my mind: I now think instead that `format-decode' and
`after-insert-file-functions' _should_ be able to detect whether the
insertion is done at the beginning of the current buffer or any other
position (simply by comparing the `begin' argument with `point-min'
wthout any need to widen the buffer).
If you think that's useful, then let's not insert a save-restriction.
So the only remaining change to be done is to inhibit execution of
certain hooks in `format-decode' and around the calls to
`after-insert-file-functions'.
Would you like to implement this?
next prev parent reply other threads:[~2007-07-01 0:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 14:06 insert-file-contents and format-decode martin rudalics
2007-06-08 7:12 ` Richard Stallman
2007-06-17 13:34 ` martin rudalics
2007-06-18 21:31 ` Richard Stallman
2007-06-19 7:50 ` martin rudalics
2007-06-23 18:26 ` Richard Stallman
2007-06-23 18:26 ` Richard Stallman
2007-06-24 10:30 ` martin rudalics
2007-06-25 13:19 ` Richard Stallman
2007-06-26 6:54 ` martin rudalics
2007-06-26 22:48 ` Richard Stallman
2007-06-27 6:33 ` martin rudalics
2007-06-27 19:50 ` Richard Stallman
2007-06-30 11:11 ` martin rudalics
2007-07-01 0:30 ` Richard Stallman
2007-07-02 8:14 ` martin rudalics
2007-07-03 4:24 ` Richard Stallman
2007-07-03 6:47 ` martin rudalics
2007-07-04 3:43 ` Richard Stallman
2007-06-26 22:48 ` Richard Stallman
2007-06-27 6:34 ` martin rudalics
2007-06-27 23:43 ` Richard Stallman
2007-06-30 11:32 ` martin rudalics
2007-07-01 0:30 ` Richard Stallman [this message]
2007-07-02 8:27 ` martin rudalics
2007-07-03 4:24 ` Richard Stallman
2007-07-03 6:43 ` martin rudalics
2007-08-06 14:22 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1I4nKf-0002m7-JR@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.