all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: steve.tolkin@fmr.com (Steven Tolkin)
Subject: How to find "bad" characters that cannot be saved using some encoding
Date: 7 Nov 2004 16:00:19 -0800	[thread overview]
Message-ID: <107e75b8.0411071600.76156474@posting.google.com> (raw)

Sometimes emacs tells me it cannot save a buffer because there
are characters that cannot use the current coding system. 
How can I have it show me the offending character or characters?  

Suppose I chose raw-text and save the buffer.
Then later when I read the file, it seems to have all ordinary characters,
and after a trivial change such as adding a blank it now can be saved.
Was some "bad" character replaced with a different character?
I am using emacs version 21.2.1 on Windows XP.

According to this old message fixing this was on some TODO list.
Was this ever done?
<quote>
From: Eli Zaretskii 
Subject: Re: what file was it that caused a coding system warning 
Newsgroups: gnu.emacs.bug
Date: 2002-01-17 03:33:12 PST 

> 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.
</quote>

Thanks,
Steve
-- 
Steven Tolkin    Steve . Tolkin at Fmr . Com   617-563-0516 
Fidelity Investments   82 Devonshire St. V13C    Boston MA 02109
There is nothing so practical as a good theory.  Comments are by me, 
not Fidelity Investments, its subsidiaries or affiliates.

             reply	other threads:[~2004-11-08  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  0:00 Steven Tolkin [this message]
2004-11-08  8:19 ` How to find "bad" characters that cannot be saved using some encoding Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=107e75b8.0411071600.76156474@posting.google.com \
    --to=steve.tolkin@fmr.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.