Re: what file was it that caused a coding system warning

[Eli Zaretskii]

On 17 Jan 2002, Dan Jacobson wrote:

> Let's say we are merrily saving files when all the sudden
> 
> |These default coding systems were tried:
> |  chinese-big5-unix
> |However, none of them safely encodes the target text.
> |
> |Select one of the following safe coding systems:
> |  raw-text emacs-mule no-conversion
> 
> I think it should say somewhere on the screen what file the problem
> occurred upon, lest we weren't paying attention.

IIRC, when that message pops up, the buffer to which it pertains should 
be displayed.  Isn't it?

> Of course it could
> also zero in on the problem spot in the file that caused the warning,
> so we would know what to fix.

Alas, it cannot do that, currently: it simply doesn't know where's that 
spot.  A feature to add the (non-trivial) code that will find that spot 
is on our TODO list.

Also, the reference to ``problem spot'' is not really correct, at least 
not in all cases: this message could (and does) pop when Emacs simply 
needs to know how you'd like the text to be encoded, for example, when 
you send an email message with non-ASCII characters.  It doesn't 
necessarily indicate a ``problem'' that should be ``fixed'', just that 
there's a multiple-choice issue which Emacs is unable to resolve by 
itself.