unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 14822-done@debbugs.gnu.org
Subject: bug#14822: ^M in info files
Date: Sat, 13 Jul 2013 13:32:52 +0300	[thread overview]
Message-ID: <83wqou4unf.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STvCfy+LpPjRzp4NyPsyBSxr3DXcFdN8pHFK3B9R2p8NA@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 8 Jul 2013 18:35:54 +0200
> 
> Visiting most info topics (Ada Mode, Emacs Lisp Intro, CC Mode...) on
> Windows gives info buffers detected as Unix-style and with lines
> ending in ^M. Some other topics (Emacs, Emacs Lisp, Gnus) work as
> expected.
> 
> All info files (in both groups) have CRLF endings, were generated with
> the same tool and appear to be correct.
> 
> This is a Windows issue, though there hasn't been any Windows-specific
> coding-related change lately, so it's likely caused by some generic
> change.

This was not a Windows-specific issue: we were ignoring the
inhibit-null-byte-detection flag when decoding, because the machinery
that implements that flag has changed.

Should be fixed in trunk revision 113413.





  parent reply	other threads:[~2013-07-13 10:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 16:35 bug#14822: ^M in info files Juanma Barranquero
2013-07-08 16:52 ` Andreas Schwab
2013-07-08 16:56   ` Juanma Barranquero
2013-07-08 17:09     ` Eli Zaretskii
2013-07-08 17:21       ` Juanma Barranquero
2013-07-09  9:08 ` martin rudalics
2013-07-13  7:47   ` Eli Zaretskii
2013-07-13 11:10     ` martin rudalics
2013-07-13 11:48       ` Eli Zaretskii
2013-07-13 13:56         ` martin rudalics
2013-07-13 14:33           ` Eli Zaretskii
2013-07-13 10:32 ` Eli Zaretskii [this message]
2013-07-15 11:46   ` Juanma Barranquero
2013-07-15 15:43     ` Eli Zaretskii
2013-07-15 15:59       ` Juanma Barranquero

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=83wqou4unf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14822-done@debbugs.gnu.org \
    --cc=lekktu@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).