From: Drew Adams <drew.adams@oracle.com>
To: 31807@debbugs.gnu.org
Subject: bug#31807: 27.0; `info-apropos' bad name or bad matching
Date: Tue, 12 Jun 2018 16:59:19 -0700 (PDT) [thread overview]
Message-ID: <eb245b09-a156-4585-8021-7a3e0e173dbc@default> (raw)
In-Reply-To: <08a478b6-1819-4bef-8165-2fb2c2e162eb@default>
> Ouch! Bitten by the crazy-quote monster. Couldn't even save
> the file I wrote it in - asked me about possibly saving with
> Chinese this or that (in Emacs 27).
This is the scary text I saw, FWIW:
These default coding systems were tried to encode text
in the buffer 'aaaaa.txt':
(undecided-unix (768 . 8216) (771 . 8217)) (iso-latin-1-unix (768
. 8216) (771 . 8217))
However, each of them encountered characters it couldn't encode:
undecided-unix cannot encode these: ' '
iso-latin-1-unix cannot encode these: ' '
Click on a character (or switch to this window by 'C-x o'
and select the characters by RET) to jump to the place it appears,
where 'C-u C-x =' will give information about it.
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).
gb2312 shift_jis iso-2022-jp big5 utf-8 euc-kr euc-jis-2004 euc-jp
euc-tw windows-1256 windows-1258 cp874 iso-2022-jp-2004 windows-1255
cp869 windows-1253 iso-8859-7 adobe-standard-encoding macintosh
windows-1257 windows-1254 windows-1252 windows-1250 windows-1251
koi8-t gb18030 gbk big5-hkscs hz-gb-2312 utf-7 utf-16
utf-16be-with-signature utf-16le-with-signature utf-16be utf-16le
iso-2022-7bit utf-8-auto utf-8-with-signature eucjp-ms utf-8-hfs
georgian-academy georgian-ps korean-cp949 japanese-shift-jis-2004
japanese-iso-7bit-1978-irv japanese-cp932 pt154
cyrillic-alternativnyj utf-7-imap utf-8-emacs prefer-utf-8
next prev parent reply other threads:[~2018-06-12 23:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 23:01 bug#31807: 27.0; `info-apropos' bad name or bad matching Drew Adams
2018-06-12 23:21 ` Drew Adams
2018-06-12 23:39 ` Drew Adams
2018-06-12 23:59 ` Drew Adams [this message]
2018-06-14 13:29 ` Eli Zaretskii
2018-06-13 0:04 ` Noam Postavsky
2018-06-13 0:16 ` Drew Adams
2018-06-13 18:24 ` Drew Adams
[not found] ` <<eb245b09-a156-4585-8021-7a3e0e173dbc@default>
[not found] ` <<83muvx33ab.fsf@gnu.org>
2018-06-14 14:16 ` Drew Adams
2018-06-17 7:44 ` Eli Zaretskii
[not found] ` <<<eb245b09-a156-4585-8021-7a3e0e173dbc@default>
[not found] ` <<<83muvx33ab.fsf@gnu.org>
[not found] ` <<f7814f7b-d9c0-48d5-83aa-b354b047db10@default>
[not found] ` <<83muvtuab9.fsf@gnu.org>
2018-06-17 14:26 ` Drew Adams
2018-06-14 13:27 ` Eli Zaretskii
2018-06-14 14:11 ` Drew Adams
2018-06-14 14:28 ` Eli Zaretskii
[not found] <<<78156de2-86c8-4593-92b5-59edf7a8996e@default>
[not found] ` <<<83o9gd33dj.fsf@gnu.org>
[not found] ` <<<a4bf1dd4-d411-4a74-b5dd-9b7abaef9250@default>
[not found] ` <<<83in6l30ir.fsf@gnu.org>
[not found] ` <<5fc07c84-b8d2-493c-a17b-774ad1c213bf@default>
[not found] ` <<83fu1p2ym7.fsf@gnu.org>
2018-06-14 15:33 ` Drew Adams
2018-06-14 15:50 ` Eli Zaretskii
[not found] <<<<78156de2-86c8-4593-92b5-59edf7a8996e@default>
[not found] ` <<<<83o9gd33dj.fsf@gnu.org>
[not found] ` <<<<a4bf1dd4-d411-4a74-b5dd-9b7abaef9250@default>
[not found] ` <<<<83in6l30ir.fsf@gnu.org>
[not found] ` <<<5fc07c84-b8d2-493c-a17b-774ad1c213bf@default>
[not found] ` <<<83fu1p2ym7.fsf@gnu.org>
[not found] ` <<73c2c21d-9fba-4ab5-a0b0-8b36e9a23bcf@default>
[not found] ` <<83efh92wr2.fsf@gnu.org>
2018-06-14 15:58 ` Drew Adams
[not found] <<78156de2-86c8-4593-92b5-59edf7a8996e@default>
[not found] ` <<83o9gd33dj.fsf@gnu.org>
[not found] ` <<a4bf1dd4-d411-4a74-b5dd-9b7abaef9250@default>
[not found] ` <<83in6l30ir.fsf@gnu.org>
2018-06-14 14:42 ` Drew Adams
2018-06-14 15:09 ` Eli Zaretskii
2018-06-14 20:45 ` Drew Adams
2022-04-21 15:05 ` Lars Ingebrigtsen
2022-04-21 20:04 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eb245b09-a156-4585-8021-7a3e0e173dbc@default \
--to=drew.adams@oracle.com \
--cc=31807@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).