From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Saving when the coding system can't code all buffer characters
Date: Fri, 22 Dec 2006 13:50:50 +0200 [thread overview]
Message-ID: <u3b78m9np.fsf@gnu.org> (raw)
In-Reply-To: <6f1c06d176.6d1766f1c0@net.lu.se> (message from LENNART BORGMAN on Fri, 22 Dec 2006 12:15:45 +0100)
> Date: Fri, 22 Dec 2006 12:15:45 +0100
> From: LENNART BORGMAN <lennart.borgman.073@student.lu.se>
> Cc: emacs-devel@gnu.org
>
> I meant that
>
> C-u C-x =
>
> at the prompt gives information about the current position in the minibuffer. Or am I wrong?
You are supposed to type "C-u C-x =" in the buffer you are trying to
save. To this end, you can type "C-x o" to get out of the minibuffer
and to the buffer being saved, and then type "C-u C-x =".
That is, if you don't understand what is wrong with the character in
the first place, since the (hollow) cursor is placed on it when you
are prompted for the encoding.
> > > Could it be made a bit easier to use please?
> >
> > Please suggest an easier way, given that just hitting RET will DTRT.
>
>
> It would IMHO be much more convenient if point in the buffer to save was left at the problematic character.
Maybe we should simply include the information displayed by "C-u C-x ="
in the same *Warning* buffer that explains the problem. That would
eliminate the need for telling about "C-u C-x =" and for an
arrangement to find the problematic characters after C-g.
next prev parent reply other threads:[~2006-12-22 11:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 11:15 Saving when the coding system can't code all buffer characters LENNART BORGMAN
2006-12-22 11:50 ` Eli Zaretskii [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-12-21 22:40 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
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
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=u3b78m9np.fsf@gnu.org \
--to=eliz@gnu.org \
--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).