From: Glenn Morris <rgm@gnu.org>
To: Ryo Furue <furue@hawaii.edu>
Cc: cyd@stupidchicken.com, 6187@debbugs.gnu.org
Subject: bug#6187: 23.1; can't save: "Wrong type argument: number-of-marker-p, nil"
Date: Thu, 17 Jun 2010 03:52:07 -0400 [thread overview]
Message-ID: <hxwrtyxfiw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20100525.091136.153182870.furue@hawaii.edu> (Ryo Furue's message of "Tue\, 25 May 2010 09\:11\:36 -1000 \(HST\)")
Ryo Furue wrote:
> apply(min nil)
> select-safe-coding-system-interactively(1 1362 (utf-8
> adobe-standard-encoding next mac-roman gb18030 utf-7 utf-16
> utf-16be-with-signature utf-16le-with-signature utf-16be utf-16le
> x-ctext iso-2022-7bit utf-8-auto utf-8-with-signature emacs-mule
> raw-text iso-2022-8bit-ss2 utf-7-imap utf-8-emacs no-conversion
> compound-text-with-extensions ctext-no-compositions
> iso-2022-7bit-lock iso-2022-7bit-ss2) (japanese-iso-8bit-unix) nil
> utf-8)
So:
select-safe-coding-system-interactively is called with
UNSAFE = (japanese-iso-8bit-unix)
This is presumably because it does not appear in the list of codings
returned by the call to find-coding-systems-region in
select-safe-coding-system (passed to
select-safe-coding-system-interactively as 3rd argument above).
Yet when select-safe-coding-system-interactively calls
unencodable-char-position with coding == japanese-iso-8bit-unix, it
returns nil, meaning it can encode the region.
So apparently it both can and cannot encode the region.
One could paper over this by excluding non-numeric elements in
(goto-char (apply 'min (mapcar #'(lambda (x) (car (cadr x)))
unsafe))))
But I guess the real bug is that find-coding-systems-region and
unencodable-char-position somehow manage to disagree.
An example of a file that triggers the problem would probably be
very helpful.
next prev parent reply other threads:[~2010-06-17 7:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 5:30 bug#6187: 23.1; can't save: "Wrong type argument: number-of-marker-p, nil" Ryo Furue
2010-05-21 4:18 ` Glenn Morris
2010-05-25 3:08 ` Ryo Furue
2010-05-25 6:11 ` Ryo Furue
2010-05-25 16:04 ` Chong Yidong
2010-05-25 19:11 ` Ryo Furue
2010-06-17 7:52 ` Glenn Morris [this message]
[not found] ` <20100616.224611.65962251.furue@hawaii.edu>
2010-06-18 18:58 ` Glenn Morris
2010-06-18 23:07 ` Ryo Furue
2010-06-25 21:28 ` Stefan Monnier
2010-06-25 21:47 ` Ryo Furue
2010-06-26 3:01 ` Ryo Furue
2011-08-12 13:54 ` bug#6187: Wrong type argument: number-of-marker-p, nil Christophe TROESTLER
2011-08-12 22:34 ` Christophe TROESTLER
2011-08-12 22:42 ` Christophe TROESTLER
2011-08-12 22:58 ` Christophe TROESTLER
2011-08-13 0:14 ` Johan Bockgård
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=hxwrtyxfiw.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=6187@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=furue@hawaii.edu \
/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).