unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: A few bugs not in the bug tracker (I think)
Date: Wed, 06 Aug 2008 21:04:04 +0300	[thread overview]
Message-ID: <ur692ja0b.fsf@gnu.org> (raw)
In-Reply-To: <E1KQiBD-00055e-Ie@etlken.m17n.org>

> From: Kenichi Handa <handa@m17n.org>
> Date: Wed, 06 Aug 2008 21:31:51 +0900
> Cc: emacs-devel@gnu.org
> 
> > - ^M in the info files [Windows]
> >   http://lists.gnu.org/archive/html/emacs-devel/2008-06/msg00739.html
> >   http://lists.gnu.org/archive/html/emacs-devel/2008-07/msg00215.html
> 
> The problem is the newly introduced null-byte detection
> mechanism, but the discussion divergented to encoding of
> non-ascii characters, and for the original problem of
> null-byte in info file, no one replied to the question in
> this mail:
>   http://lists.gnu.org/archive/html/emacs-devel/2008-07/msg00225.html

I think the best solution would be that Emacs never tries to detect
whether Info files are binary.




  parent reply	other threads:[~2008-08-06 18:04 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 11:09 A few bugs not in the bug tracker (I think) Juanma Barranquero
2008-08-06 12:31 ` Kenichi Handa
2008-08-06 13:14   ` Juanma Barranquero
2008-08-06 13:36     ` Juanma Barranquero
2008-08-07  4:25       ` Miles Bader
2008-08-07 11:26         ` Juanma Barranquero
2008-08-07  0:48     ` ^M in the info files Kenichi Handa
2008-08-07  3:20       ` Eli Zaretskii
2008-08-07  3:22       ` Juanma Barranquero
2008-08-07  3:47         ` Kenichi Handa
2008-08-07 13:01           ` Juanma Barranquero
2008-08-08  1:28             ` Kenichi Handa
2008-08-08 11:02               ` Juanma Barranquero
2008-08-13 10:08                 ` Kenichi Handa
2008-08-15 23:09                   ` Juanma Barranquero
2008-08-07 20:18       ` Stefan Monnier
2008-11-28 21:28         ` Drew Adams
2008-11-28 22:39           ` Eli Zaretskii
2008-11-28 22:44             ` Juanma Barranquero
2008-11-29 10:50               ` Eli Zaretskii
2008-11-29 11:56                 ` Juanma Barranquero
2008-11-28 22:49             ` Drew Adams
2008-11-29 10:51               ` Eli Zaretskii
2009-01-10 11:15             ` Eli Zaretskii
2009-01-10 12:14               ` Eli Zaretskii
2009-01-12 20:56                 ` Stefan Monnier
2009-01-12 22:04                   ` Eli Zaretskii
2009-01-10 14:07               ` Juanma Barranquero
2009-01-10 15:13                 ` Eli Zaretskii
2009-01-10 18:23                   ` Juanma Barranquero
2009-01-10 19:08                     ` Eli Zaretskii
2009-01-10 19:12                     ` Eli Zaretskii
2009-01-10 19:19                     ` Eli Zaretskii
2009-01-10 21:04                       ` Juanma Barranquero
2009-01-10 16:21               ` Drew Adams
2009-01-10 23:16                 ` Lennart Borgman
2009-01-11  5:41                   ` dhruva
2009-01-11  5:51                   ` dhruva
2009-01-12 20:54               ` Stefan Monnier
2009-01-12 22:13                 ` Eli Zaretskii
2009-01-12 22:27                   ` Glenn Morris
2009-01-13  4:01                     ` Eli Zaretskii
2009-01-13  4:24                       ` bug bugs [was Re: ^M in the info files] Glenn Morris
2009-01-13 18:56                         ` Eli Zaretskii
2009-01-13 20:50                           ` bug bugs Glenn Morris
2009-01-14  4:12                             ` Eli Zaretskii
2009-01-14 13:45                               ` Chong Yidong
2009-01-14 19:13                                 ` Eli Zaretskii
2009-01-15  0:30                                   ` Stephen J. Turnbull
2009-01-14 19:40                               ` Glenn Morris
2008-08-06 18:04   ` Eli Zaretskii [this message]
2008-08-06 13:35 ` A few bugs not in the bug tracker (I think) Don Armstrong
2008-08-06 13:38   ` 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=ur692ja0b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).