unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: Unrecoverable data loss
Date: Sun, 18 May 2008 23:25:39 +0200	[thread overview]
Message-ID: <48309ED3.3020701@gmx.at> (raw)
In-Reply-To: <87zlqnqxrl.fsf@escher.local.home>

 > 5. The inserted text retains the properties in buffer A that it has in
 > the *Help* buffer, in particular clickable links.  Click on the link
 > displaying the value of the preferred charset, or, if there are text
 > properties in the description, you can click on one of these links.
 > (Clicking the link of the value of the code point, or the button
 > labelled "customize what to show" does not produce the problem.)
 >
 > 6. Now buffer A is in Help mode and contains only the Help text of the
 > clicked link; the text you had previously type is gone.  If you type
 > C-_, Emacs beeps and says "Buffer is read-only".  If you toggle the
 > read-only status and type C-_ again, Emacs beeps again and says "No undo
 > information in this buffer".  If you were typing in a buffer that does
 > not have auto-save, its contents prior to step 5 is AFAICT unrecoverably
 > lost.

`describe-character-set' uses

     (with-output-to-temp-buffer (help-buffer)

where `help-buffer' is defined as

(defun help-buffer ()
   (buffer-name				;for with-output-to-temp-buffer
    (if help-xref-following
        (current-buffer)
      (get-buffer-create "*Help*"))))

hence turning your current buffer into a help buffer thus clearing its
contents and undo-list, making it read-only, ...

Maybe `help-buffer' should refuse to return a buffer if it is not
read-only, `buffer-undo-list' is not t, ...





  reply	other threads:[~2008-05-18 21:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18 18:21 Unrecoverable data loss Stephen Berman
2008-05-18 21:25 ` martin rudalics [this message]
2008-05-20  1:33   ` Stefan Monnier
2008-05-19  6:40 ` Richard M Stallman
2008-05-19  8:34   ` Stephen Berman
2008-05-19 16:26     ` Drew Adams
2008-05-20  6:00 ` tomas

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=48309ED3.3020701@gmx.at \
    --to=rudalics@gmx.at \
    --cc=Stephen.Berman@gmx.net \
    --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).