[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: Sat, 23 Dec 2006 21:09:07 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.91 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

In article <address@hidden>, Richard Stallman <address@hidden> writes:

> Handa-san, would you please join in this?
>     The first problematic character is at point in the displayed buffer,
>     and C-u C-x = will give information about it.

>     At the prompt "Select coding system (default mule-utf-8):" this just 
>     gives information about the minibuffer.

> That is true.  So you have to switch windows in order to use the command
> C-u C-x = to get that information.

>      And when using C-g to quit the 
>     problematic character disappears from screen.

> Of course, that is what C-g is supposed to do.

But, *Warning* buffer is still there, and thus you can
click a character by mouse shown under the line:
"However, each of them encountered these problematic characters:"
to jump to that character.

> I see two things we could do:

> * Change the message to say that you need to switch to that window
> before you give the command.

> * Make up some simpler command, and make it work without switching
>   windows.  What command could it be?  It has to be typable on a tty.

How about typing C-g prints:
Jump to the first problematic character? (y or n)
and when 'y' is typed, move point to that character?

Kenichi Handa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]