From: Vincent Lefevre <vincent@vinc17.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 696026-forwarded@bugs.debian.org, 696026@bugs.debian.org,
rlb@defaultvalue.org, 13505@debbugs.gnu.org
Subject: bug#13505: Bug#696026: emacs24: file corruption on saving
Date: Sun, 20 Jan 2013 23:22:11 +0100 [thread overview]
Message-ID: <20130120222211.GH2695@xvii.vinc17.org> (raw)
In-Reply-To: <20130120221007.GG2695@xvii.vinc17.org>
On 2013-01-20 23:10:08 +0100, Vincent Lefevre wrote:
> But Emacs should clearly tell the user what to do after C-x C-s and
> clearly say when there can be data loss. Currently it says:
[...]
In fact, I fear that this may not be sufficient, because some data
loss silently occurs when visiting the file. If after the decoding, it
appears that there are no problematic characters (is this possible?),
the user would be able to save the file without any message from
Emacs.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2013-01-20 22:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121215223809.GA7549@xvii.vinc17.org>
2013-01-20 4:09 ` bug#13505: Bug#696026: emacs24: file corruption on saving Rob Browning
2013-01-20 16:49 ` Eli Zaretskii
2013-01-20 17:31 ` Rob Browning
2013-01-20 20:24 ` Glenn Morris
2013-01-20 21:25 ` Vincent Lefevre
2013-01-20 21:40 ` Eli Zaretskii
2013-01-20 22:10 ` Vincent Lefevre
2013-01-20 22:22 ` Vincent Lefevre [this message]
2013-01-21 3:49 ` Eli Zaretskii
2013-01-21 3:48 ` Eli Zaretskii
2013-01-21 4:14 ` Vincent Lefevre
2013-01-21 17:55 ` Eli Zaretskii
2013-01-22 2:35 ` Vincent Lefevre
2013-01-22 7:56 ` Eli Zaretskii
2013-01-20 23:01 ` Andreas Schwab
2013-01-20 23:27 ` bug#13505: Bug#696026: " Rob Browning
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=20130120222211.GH2695@xvii.vinc17.org \
--to=vincent@vinc17.net \
--cc=13505@debbugs.gnu.org \
--cc=696026-forwarded@bugs.debian.org \
--cc=696026@bugs.debian.org \
--cc=eliz@gnu.org \
--cc=rlb@defaultvalue.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 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.