unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: Re: with-output-to-temp-buffer [Re: reverting CJK input methods]
Date: Mon, 10 May 2004 21:13:00 +0900 (JST)	[thread overview]
Message-ID: <200405101213.VAA04125@etlken.m17n.org> (raw)
In-Reply-To: <E1BMGVn-0000xh-3r@fencepost.gnu.org> (message from Richard Stallman on Fri, 07 May 2004 21:20:19 -0400)

In article <E1BMGVn-0000xh-3r@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:

>     I fully agree with that general principle.  But, for the
>     current case, I'm not sure it is the right thing that
>     erase-buffer signals such an error considering that it
>     removes even the narrowing restriction.

> I think I partly misunderstood the problem.  Is the problem that
> erase-buffer gets an error when there is read-only text in the buffer?

Yes.

> Maybe you're right that it should not get an error for that.

> However, consider the case of a Customize buffer.  That has lots of
> read-only text, the idea being that the user should not be able to
> edit it.  Should erase-buffer in a Customize buffer leave it empty?
> The result would be an undesirable confusion.  We could respond to
> that by saying, "So don't do erase-buffer in a Customize buffer."
> Maybe that's right, but I am not sure.

I think "So don't do ..." is sufficient.

> So it seems to me that there are some cases where we want erase-buffer
> to get rid of read-only text silently, but not all cases.  It seems
> better to change the callers, not change erase-buffer.

>     If we eval this once,

>     (display-message-or-buffer (propertize "abc\n\n" 'read-only t))

> That is clearly a bug, but I think the right fix is to change the
> caller here too.

Ok, I've just installed these changes in addition to fix of
describe-char.

2004-05-10  Kenichi Handa  <handa@m17n.org>

	* print.c (temp_output_buffer_setup): Bind inhibit-read-only and
	inhibit-modification-hooks to t temporarily before calling
	Ferase_buffer.

	* xfns.c (x_create_tip_frame): Bind inhibit-read-only and
	inhibit-modification-hooks to t temporarily before calling
	Ferase_buffer.

	* w32fns.c (x_create_tip_frame): Bind inhibit-read-only and
	inhibit-modification-hooks to t temporarily before calling
	Ferase_buffer.

But I still believe it is better to change erase-buffer
itself (perhaps it should delete all overlays too).  Let's
discuss it after the next release.

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2004-05-10 12:13 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 13:03 reverting CJK input methods Werner LEMBERG
2004-04-30  1:42 ` Kenichi Handa
2004-04-30  2:03   ` Miles Bader
2004-04-30  2:59     ` Miles Bader
2004-04-30 11:27       ` Juri Linkov
2004-04-30 13:26         ` Kenichi Handa
2004-05-01  8:22           ` Juri Linkov
2004-05-02  1:57             ` Kenichi Handa
2004-05-06  5:05               ` with-output-to-temp-buffer [Re: reverting CJK input methods] Kenichi Handa
2004-05-06 11:48                 ` Richard Stallman
2004-05-06 13:10                   ` Kenichi Handa
2004-05-06 14:27                     ` Stefan Monnier
2004-05-06 15:49                       ` Kevin Rodgers
2004-05-06 16:50                         ` Stefan Monnier
2004-05-06 20:57                           ` Kevin Rodgers
2004-05-07  1:53                       ` Kenichi Handa
2004-05-08  1:20                     ` Richard Stallman
2004-05-10 12:13                       ` Kenichi Handa [this message]
2004-05-10 14:28                         ` Stefan Monnier
2004-05-11  7:04                           ` Richard Stallman
2004-05-11  7:49                             ` David Kastrup
2004-05-12  7:51                               ` Richard Stallman
2004-05-11 13:39                             ` erase-buffer (was: with-output-to-temp-buffer) Stefan Monnier
2004-05-11 14:44                               ` erase-buffer Juri Linkov
2004-05-11 16:17                                 ` erase-buffer Juri Linkov
2004-05-11 15:32                               ` erase-buffer (was: with-output-to-temp-buffer) David Kastrup
2004-05-11 16:22                                 ` Kevin Rodgers
2004-05-11 19:30                                   ` Stefan Monnier
2004-05-12 21:10                                     ` Kevin Rodgers
2004-05-11 19:37                                   ` Juanma Barranquero
2004-05-11 18:14                                 ` Juanma Barranquero
2004-05-11 23:06                               ` Kenichi Handa
2004-05-11 23:26                                 ` Miles Bader
2004-05-12 19:42                                   ` Richard Stallman
2004-05-12 22:34                                     ` Miles Bader
2004-05-14  9:21                                       ` Richard Stallman
2004-05-11 23:34                                 ` Stefan Monnier
2004-05-11 23:47                                   ` Kenichi Handa
2004-05-12 19:40                               ` Richard Stallman
2004-05-11  1:45                         ` with-output-to-temp-buffer [Re: reverting CJK input methods] Luc Teirlinck
2004-05-11  2:34                           ` Kenichi Handa
2004-05-11  7:01                             ` David Kastrup
2004-05-11  6:55                               ` Kim F. Storm
2004-05-11  8:00                               ` Kenichi Handa
2004-05-12  7:51                               ` Richard Stallman
2004-04-30  5:06     ` reverting CJK input methods Kenichi Handa
2004-04-30 16:50       ` Werner LEMBERG
2004-05-01  9:07         ` Miles Bader
2004-05-01 17:18           ` Werner LEMBERG
2004-05-08  2:56         ` Kenichi Handa
2004-05-08 16:38           ` Werner LEMBERG
2004-05-10  4:40             ` Kenichi Handa
2004-05-12  2:42               ` Kenichi Handa
2004-05-12  8:32                 ` Werner LEMBERG
2004-05-12 11:10                   ` Kenichi Handa
2004-05-01 17:21       ` Werner LEMBERG

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=200405101213.VAA04125@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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).