From: Kenichi Handa <handa@m17n.org>
Cc: lennart.borgman@gmail.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Saving when the coding system can't code all buffer characters
Date: Thu, 28 Dec 2006 11:09:51 +0900 [thread overview]
Message-ID: <E1GzkiN-0006tt-3C@etlken.m17n.org> (raw)
In-Reply-To: <uhcvh1naz.fsf@gnu.org> (message from Eli Zaretskii on Wed, 27 Dec 2006 15:27:32 +0200)
In article <uhcvh1naz.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> I fixed the wording some more.
Thank you.
> I really like how this works now; my only minor gripe is that clicking
> on the problematic characters causes one to get out of the minibuffer
> without deactivating it, so C-g will not gonna do what a naive user
> expects, unless she returns to the minibuffer first.
I agree. So, it is better to guide a user to type C-g
before clicking.
How about moving "Click a character ..." under "or cancel ..."
as this?
Select one of the safe coding systems listed below,
or cancel the writing with C-g and fix the problematic characters
(click a problematic character above to jump to the place it appears,
where `C-u C-x =' will give information about it),
or specify any other coding system (and risk losing
the problematic characters).
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-12-28 2:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 22:40 Saving when the coding system can't code all buffer characters Lennart Borgman
2006-12-22 10:50 ` Eli Zaretskii
2006-12-22 21:03 ` Richard Stallman
2006-12-23 12:09 ` Kenichi Handa
2006-12-24 1:35 ` Richard Stallman
2006-12-25 6:00 ` Kenichi Handa
2006-12-26 2:25 ` Richard Stallman
2006-12-27 1:39 ` Kenichi Handa
2006-12-27 2:59 ` Lennart Borgman (gmail)
2006-12-27 5:13 ` Kenichi Handa
2006-12-27 13:27 ` Eli Zaretskii
2006-12-27 21:16 ` Richard Stallman
2006-12-28 2:09 ` Kenichi Handa [this message]
2006-12-27 8:28 ` Eli Zaretskii
2006-12-27 11:06 ` Kenichi Handa
2006-12-27 12:20 ` Eli Zaretskii
2006-12-27 12:37 ` Lennart Borgman (gmail)
2006-12-27 14:17 ` Eli Zaretskii
2006-12-28 0:31 ` Kenichi Handa
2006-12-27 21:16 ` Richard Stallman
2006-12-28 1:32 ` Kenichi Handa
2006-12-28 4:20 ` Eli Zaretskii
2006-12-29 15:44 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 11:15 LENNART BORGMAN
2006-12-22 11:50 ` Eli Zaretskii
2006-12-22 15:48 ` David Kastrup
2006-12-22 16:23 ` Lennart Borgman
2006-12-23 7:31 ` David Kastrup
2006-12-31 14:36 ` Sascha Wilde
2006-12-31 16:04 ` Lennart Borgman
2006-12-31 19:27 ` Aidan Kehoe
2007-01-09 7:23 ` Kenichi Handa
2006-12-22 17:35 ` Lennart Borgman
2006-12-23 20:14 ` Richard Stallman
2006-12-23 20:41 ` Lennart Borgman
2006-12-24 17:09 ` 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
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=E1GzkiN-0006tt-3C@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=rms@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).