From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 21780@debbugs.gnu.org
Subject: bug#21780: 25.0.50; Saving *Help* results in bad encoding because of curly quotes
Date: Fri, 30 Oct 2015 08:07:54 -0700 (PDT) [thread overview]
Message-ID: <17cf8a49-1cc4-4834-91ec-b7d092693ebf@default> (raw)
In-Reply-To: <<83k2q423x7.fsf@gnu.org>>
> > I think now that what I did earlier, when specified utf-8, I was
> > using my setup. When I try that again (with my setup), I see the
> > problem I reported.
>
> So the question now becomes what do you have in your setup that causes
> this. I'm guessing you do something that changes the defaults for
> encoding/decoding text.
I have tons of stuff in my setup. Let me know what I might search
for that might affect encoding/decoding.
> > Also, with my setup the *Warning* text is different. Instead of
> > providing lots of possible encoding choices and using
> > chinese-iso-8bit as the default (which is what I get with emacs
> > -Q - why is that, BTW?), it says:
> >
> > Select one of the safe coding systems listed below,
> > or cancel the writing with C-g and edit the buffer
> > to remove or modify the problematic characters,
> > or specify any other coding system (and risk losing
> > the problematic characters).
> >
> > raw-text no-conversion
>
> What its suggests depend on your customizations.
Such as? Again, could it be affected by the default font choice?
> > > UTF-8 should have worked. I wouldn't expect you to see octal escapes
> > > after saving in UTF-8.
> >
> > See above for, I think, the explanation of what I did and saw.
>
> It doesn't. You have something in your customizations that runs afoul
> of your expectations (which do work in "emacs -Q").
Please read again what I said about the crash. I think it
at least explains why I saw octal escapes when I visited
the last-saved file - it was saved with raw text. Only the
auto-save file was saved with utf-8. When I visited the file
in a new session, it showed the octal escapes because it was
saved as raw text.
Why that happened I'm not sure. Perhaps when I did `C-x C-w'
the *Help* buffer was first saved as raw text (?), then
autosaved as utf-8, then the crash interrupted finally
resaving the file itself as utf-8 (?).
You will need to give me an idea what to look for, if I am to
try hunting for something in my init file and all that it loads.
One thing I do is this, to get Unix-style line endings:
(setq-default buffer-file-coding-system 'undecided-unix)
And I do this:
(setq process-coding-system-alist
(cons '("bash" . (raw-text-dos . raw-text-unix))
process-coding-system-alist))
But I don't imagine that either of those is related to this.
next prev parent reply other threads:[~2015-10-30 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<536fdfb7-20dd-4d23-886c-8e842b6844fd@default>
[not found] ` <<83lhal1qtm.fsf@gnu.org>
2015-10-29 20:53 ` bug#21780: 25.0.50; Saving *Help* results in bad encoding because of curly quotes Drew Adams
2015-10-30 7:47 ` Eli Zaretskii
[not found] ` <<2c1ac781-86b8-4365-8466-52455afb79f6@default>
[not found] ` <<83k2q423x7.fsf@gnu.org>
2015-10-30 15:07 ` Drew Adams [this message]
2015-10-30 15:22 ` Eli Zaretskii
[not found] ` <<17cf8a49-1cc4-4834-91ec-b7d092693ebf@default>
[not found] ` <<83si4sz8i5.fsf@gnu.org>
2015-10-30 16:02 ` Drew Adams
2015-10-30 16:17 ` Drew Adams
2015-10-30 20:50 ` Eli Zaretskii
2015-10-30 20:57 ` Eli Zaretskii
2015-10-29 1:50 ` Drew Adams
2015-10-29 17:41 ` Eli Zaretskii
2015-10-30 23:06 ` Andy Moreton
2015-10-31 7:28 ` Eli Zaretskii
2015-10-31 18:10 ` Andy Moreton
[not found] <<48a87436-595a-4f65-9e3c-094f6d77ee96@default>
[not found] ` <<83eggcytam.fsf@gnu.org>
[not found] ` <<83d1vwyt02.fsf@gnu.org>
2015-10-30 21:27 ` Drew Adams
[not found] <<ab84db1b-77e3-4ef1-ac0e-e91264d78b8f@default>
[not found] ` <<83oafh1sj1.fsf@gnu.org>
2015-10-29 17:58 ` Drew Adams
2015-10-29 18:18 ` 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=17cf8a49-1cc4-4834-91ec-b7d092693ebf@default \
--to=drew.adams@oracle.com \
--cc=21780@debbugs.gnu.org \
--cc=eliz@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 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.