From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Unrecoverable data loss
Date: Sun, 18 May 2008 20:21:02 +0200 [thread overview]
Message-ID: <87zlqnqxrl.fsf@escher.local.home> (raw)
1. emacs -Q
2. Type text in a buffer in accordance with normal Emacs usage (plain
text, code in some suitable mode, email in e.g. Gnus, etc.). I'll call
this buffer A.
3. Type (in any buffer) C-u C-x =, which pops up a *Help* buffer.
4. Return to buffer A, if you're not still there, and type `M-x
insert-buffer RET *Help*', thereby inserting the output of the command
in step 3 into buffer A.
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.
Note that if, instead of using insert-buffer, you copy the content of
the *Help* buffer either with M-w or with the mouse and then yank it
into buffer A, then the yanked text does not have clickable links.
In GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+ Version 2.12.0) of
2008-05-15 on escher
Steve Berman
next reply other threads:[~2008-05-18 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 18:21 Stephen Berman [this message]
2008-05-18 21:25 ` Unrecoverable data loss martin rudalics
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=87zlqnqxrl.fsf@escher.local.home \
--to=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).