From: Eli Zaretskii <eliz@gnu.org>
To: Rupert Swarbrick <rswarbrick@gmail.com>
Cc: 36573@debbugs.gnu.org
Subject: bug#36573: 26.1; bufferpos-to-filepos assumes coding-system-eol-type gives integer
Date: Fri, 12 Jul 2019 21:17:47 +0300 [thread overview]
Message-ID: <837e8n2k38.fsf@gnu.org> (raw)
In-Reply-To: <87o91zs2sm.fsf@halibut> (message from Rupert Swarbrick on Fri, 12 Jul 2019 16:14:33 +0100)
> From: Rupert Swarbrick <rswarbrick@gmail.com>
> Date: Fri, 12 Jul 2019 16:14:33 +0100
>
> Thank you for the reply. I've now found the "culprit" (bisecting
> my init.el starting with emacs -Q). The dubious setting was:
>
> '(file-coding-system-alist
> (quote
> (("\\.dz\\'" no-conversion . no-conversion)
> ("\\.g?z\\(~\\|\\.~[0-9]+~\\)?\\'" no-conversion .
> no-conversion)
> ("\\.tgz\\'" no-conversion . no-conversion)
> ("\\.tbz\\'" no-conversion . no-conversion)
> ("\\.bz2\\(~\\|\\.~[0-9]+~\\)?\\'" no-conversion .
> no-conversion)
> ("\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'" no-conversion .
> no-conversion)
> ("\\.elc\\'" emacs-mule . emacs-mule)
> ("\\.utf\\(-8\\)?\\'" . utf-8)
> ("\\(\\`\\|/\\)loaddefs.el\\'" raw-text . raw-text-unix)
> ("\\.tar\\'" no-conversion . no-conversion)
> ("\\.po[tx]?\\'\\|\\.po\\." . po-find-file-coding-system)
> ("\\.lisp\\'" . utf-8-unix))))
Was the Info file compressed, i.e. did it have one of extensions that
caused no-conversion to be used?
> I think it probably still makes sense to add a note to the manual
> for bufferpos-to-filepos and filepos-to-bufferpos to point out
> that they don't work if the line ending convention is unknown.
>
> For bonus points, maybe it makes sense to add something to fail
> earlier (and more understandably!) in the info reading code. I'm
> not sure exactly where that would be, though.
Yes, something should be done there, thanks.
next prev parent reply other threads:[~2019-07-12 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 10:52 bug#36573: 26.1; bufferpos-to-filepos assumes coding-system-eol-type gives integer Rupert Swarbrick
2019-07-10 14:52 ` Eli Zaretskii
2019-07-12 15:14 ` Rupert Swarbrick
2019-07-12 18:17 ` Eli Zaretskii [this message]
2021-08-11 18:42 ` Lars Ingebrigtsen
2021-08-12 8:21 ` Eli Zaretskii
2021-08-12 12:54 ` Lars Ingebrigtsen
2021-08-12 13:08 ` Eli Zaretskii
2021-08-13 11:07 ` Lars Ingebrigtsen
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=837e8n2k38.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36573@debbugs.gnu.org \
--cc=rswarbrick@gmail.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 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).