[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Saving when the coding system can't code all buffer characters
From: |
Kenichi Handa |
Subject: |
Re: Saving when the coding system can't code all buffer characters |
Date: |
Tue, 09 Jan 2007 16:23:57 +0900 |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.92 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) |
In article <address@hidden>, Sascha Wilde <address@hidden> writes:
> > 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:
Sorry for the late response and thank you for a good
suggestion. I've just installed this slightly modified
version.
diff -u -r1.307 -r1.308
--- mule-cmds.el 30 Dec 2006 06:27:30 -0000 1.307
+++ mule-cmds.el 9 Jan 2007 07:22:11 -0000 1.308
@@ -788,10 +788,10 @@
(car coding)))))
(setq i (1+ i))))
(insert "\n"))
- (insert "\
+ (insert (substitute-command-keys "\
-Click on a character to jump to the place it appears,\n"
- (substitute-command-keys "\
+Click on a character (or switch to this window by `\\[other-window]'\n\
+and select the characters by RET) to jump to the place it appears,\n\
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\
---
Kenichi Handa
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Saving when the coding system can't code all buffer characters,
Kenichi Handa <=