unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sascha Wilde <wilde@sha-bang.de>
Cc: Eli Zaretskii <eliz@gnu.org>, "Richard M. Stallman" <rms@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Saving when the coding system can't code all buffer characters
Date: Sun, 31 Dec 2006 15:36:24 +0100	[thread overview]
Message-ID: <m2ac14i13r.fsf@kenny.sha-bang.de> (raw)
In-Reply-To: <458C068F.5070508@student.lu.se> (Lennart Borgman's message of "Fri\, 22 Dec 2006 17\:23\:43 +0100")

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Lennart Borgman <lennart.borgman.073@student.lu.se> wrote:
> David Kastrup wrote:
>> Eli Zaretskii <eliz@gnu.org> writes:
[...]
>>> 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 =".
>>
>> I think that is far too much to suppose from an average user.  How
>> about putting a property on the character that will highlight it and
>> display the information on mouse-over in a tooltip?
>
> Probably. Anyway I did not think of using C-x o here. I had no idea it
> worked from the minibuffer.

As this seems to be the only information missing from the *warning*
buffer for pure tty use (or mousephobics like me), maybe we should
simply add a note on C-x o to the text?

Here is my first try on this:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1084 bytes --]

diff -r e0ab6280c837 lisp/international/mule-cmds.el
*** a/lisp/international/mule-cmds.el	Sun Dec 31 12:25:06 2006 +0100
--- b/lisp/international/mule-cmds.el	Sun Dec 31 15:31:40 2006 +0100
***************
*** 792,798 ****
  
  Click on a character to jump to the place it appears,\n"
  		      (substitute-command-keys "\
! where `\\[universal-argument] \\[what-cursor-position]' will give information about it.\n"))))
  	  (insert (substitute-command-keys "\nSelect \
  one of the safe coding systems listed below,\n\
  or cancel the writing with \\[keyboard-quit] and edit the buffer\n\
--- 792,800 ----
  
  Click on a character to jump to the place it appears,\n"
  		      (substitute-command-keys "\
! where `\\[universal-argument] \\[what-cursor-position]' will give information about it.\n\
! You can also use `\\[other-window]' to witch to this window \n\
! and select the characters using RET.\n"))))
  	  (insert (substitute-command-keys "\nSelect \
  one of the safe coding systems listed below,\n\
  or cancel the writing with \\[keyboard-quit] and edit the buffer\n\


[-- Attachment #3: Type: text/plain, Size: 336 bytes --]


cheers
sascha
-- 
>++++++[<+++++++++++>-]<+.>+++[<++++++>-]<.---.---------.++++++.++++.---------
-.+++++++++++.+++++.>+++++++[<-------->-]<-.>++++++[<+++++++>-]<+.--.+++..----
---.-.>++++++[<------>-]<.>++++[<+++++++++++++>-]<.------------.---.>++++++[<-
----->-]<-.>+++++[<+++++++>-]<.--.>+++[<++++++>-]<+.>++++++++[<--------->-]<--.

[-- Attachment #4: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  parent reply	other threads:[~2006-12-31 14:36 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
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 [this message]
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=m2ac14i13r.fsf@kenny.sha-bang.de \
    --to=wilde@sha-bang.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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).