Re: ^M in the info files

Re: ^M in the info files

[Eli Zaretskii]

> Date: Sat, 29 Nov 2008 00:39:27 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
> 	handa@m17n.org
> 
> > From: "Drew Adams" <drew.adams@oracle.com>
> > Date: Fri, 28 Nov 2008 13:28:34 -0800
> > Cc: 'Juanma Barranquero' <lekktu@gmail.com>, emacs-devel@gnu.org
> > 
> > Whatever happened to this thread and the associated bugs: #876, #1117, #1284?
> > 
> > It sounds like there were alternative proposals about how to fix this, but there
> > was no discussion to try to reach a consensus or a decision. Is that where
> > things were left?
> > 
> > Meanwhile, it's still impossible to use the index in Info manuals on Windows,
> > and it's impossible to use some manuals (e.g. Viper) at all.
> 
> Don't worry, this will get fixed before Emacs 23 is ready for release.
> 
> I will work on it soon if no one beats me to it.

(Fore some value of "soon", sorry.)

I fixed this bug.

There were two suggestions for how to fix this: one by Handa-san in
this message:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00293.html

followed by a tentative patch by Juanma here:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00316.html

The other suggestion was by Stefan:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00373.html

I decided I liked the first alternative better, since it has much
more local effect than the other one.  What Stefan suggested implied
messing with coding priorities, and I didn't feel that was TRT at this
late stage in Emacs 23.1 development.

The changes I installed are more thorough than what Juanma posted:
they change both detect_coding and detect_coding_system, and also bind
inhibit-null-byte-detection in a couple more places in info.el.

The result was tested on GNU/Linux, MS-Windows, and MS-DOS, both with
compressed and uncompressed Info files, with auto-compression-mode
both on and off.

bug#876: ^M in some Windows info files because of null-byte detection

[Juanma Barranquero]

Some info files in Windows (for example, the Emacs FAQ) are displayed
with spurious ^M characters because of recent changes in null byte
detection.

Kenichi Handa proposed a new inhibit-null-byte-detection variable.
Stefan Monnier counter-proposed inhibit-coding-systems.


emacs-devel discussion:

  http://lists.gnu.org/archive/html/emacs-devel/2008-06/msg00739.html
  http://lists.gnu.org/archive/html/emacs-devel/2008-07/msg00215.html
  http://lists.gnu.org/archive/html/emacs-devel/2008-07/msg00225.html
  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00293.html

bug#876: marked as done (^M in some Windows info files because of null-byte detection)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]


Your message dated Sat, 10 Jan 2009 13:15:51 +0200
with message-id <uab9zjtso.fsf@gnu.org>
and subject line Re: ^M in the info files
has caused the Emacs bug report #876,
regarding ^M in some Windows info files because of null-byte detection
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
876: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=876
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 2791 bytes --]

From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Emacs Bug Tracker" <submit@emacsbugs.donarmstrong.com>
Subject: ^M in some Windows info files because of null-byte detection
Date: Wed, 3 Sep 2008 18:39:11 +0200
Message-ID: <f7ccd24b0809030939l67318d7bkc924a8f1cf780c07@mail.gmail.com>

Some info files in Windows (for example, the Emacs FAQ) are displayed
with spurious ^M characters because of recent changes in null byte
detection.

Kenichi Handa proposed a new inhibit-null-byte-detection variable.
Stefan Monnier counter-proposed inhibit-coding-systems.


emacs-devel discussion:

  http://lists.gnu.org/archive/html/emacs-devel/2008-06/msg00739.html
  http://lists.gnu.org/archive/html/emacs-devel/2008-07/msg00215.html
  http://lists.gnu.org/archive/html/emacs-devel/2008-07/msg00225.html
  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00293.html



[-- Attachment #3: Type: message/rfc822, Size: 3682 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: 876-done@emacsbugs.donarmstrong.com
Cc: emacs-devel@gnu.org, bug-gnu-emacs@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: ^M in the info files
Date: Sat, 10 Jan 2009 13:15:51 +0200
Message-ID: <uab9zjtso.fsf@gnu.org>

> Date: Sat, 29 Nov 2008 00:39:27 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
> 	handa@m17n.org
> 
> > From: "Drew Adams" <drew.adams@oracle.com>
> > Date: Fri, 28 Nov 2008 13:28:34 -0800
> > Cc: 'Juanma Barranquero' <lekktu@gmail.com>, emacs-devel@gnu.org
> > 
> > Whatever happened to this thread and the associated bugs: #876, #1117, #1284?
> > 
> > It sounds like there were alternative proposals about how to fix this, but there
> > was no discussion to try to reach a consensus or a decision. Is that where
> > things were left?
> > 
> > Meanwhile, it's still impossible to use the index in Info manuals on Windows,
> > and it's impossible to use some manuals (e.g. Viper) at all.
> 
> Don't worry, this will get fixed before Emacs 23 is ready for release.
> 
> I will work on it soon if no one beats me to it.

(Fore some value of "soon", sorry.)

I fixed this bug.

There were two suggestions for how to fix this: one by Handa-san in
this message:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00293.html

followed by a tentative patch by Juanma here:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00316.html

The other suggestion was by Stefan:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00373.html

I decided I liked the first alternative better, since it has much
more local effect than the other one.  What Stefan suggested implied
messing with coding priorities, and I didn't feel that was TRT at this
late stage in Emacs 23.1 development.

The changes I installed are more thorough than what Juanma posted:
they change both detect_coding and detect_coding_system, and also bind
inhibit-null-byte-detection in a couple more places in info.el.

The result was tested on GNU/Linux, MS-Windows, and MS-DOS, both with
compressed and uncompressed Info files, with auto-compression-mode
both on and off.

bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line

[Drew Adams]

emacs -Q
C-h i, choose Elisp manual
g Index takes you to the Index node.
 
Each line has a visible ^M at the end of it.
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-10-03 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
 
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t
 
Major mode: Info
 
Minor modes in effect:
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t
 
Recent input:
<help-echo> C-h i <help-echo> <help-echo> <help-echo> 
<down-mouse-2> <mouse-2> <double-down-mouse-2> <double-mouse-2> 
<help-echo> g I n d e x <return> <help-echo> <help-echo> 
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo> 
<help-echo> <help-echo> <help-echo> <menu-bar> <help-menu> 
<send-emacs-bug-report>
 
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Composing main Info directory...done

bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line

[Juanma Barranquero]

> emacs -Q
> C-h i, choose Elisp manual
> g Index takes you to the Index node.
>
> Each line has a visible ^M at the end of it.

That's surely #876?

             Juanma

bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line

[Eli Zaretskii]

> Date: Wed, 8 Oct 2008 10:02:40 +0200
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: 
> 
> > emacs -Q
> > C-h i, choose Elisp manual
> > g Index takes you to the Index node.
> >
> > Each line has a visible ^M at the end of it.
> 
> That's surely #876?

I thought #876 was resolved long ago.  Why wasn't it?

bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line

[Juanma Barranquero]

On Wed, Oct 8, 2008 at 12:01, Eli Zaretskii <eliz@gnu.org> wrote:

> I thought #876 was resolved long ago.  Why wasn't it?

As the bug report says:

  Kenichi Handa proposed a new inhibit-null-byte-detection variable.
  Stefan Monnier counter-proposed inhibit-coding-systems.

Then things stalled.

             Juanma

bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line

[Drew Adams]

> > emacs -Q
> > C-h i, choose Elisp manual
> > g Index takes you to the Index node.
> >
> > Each line has a visible ^M at the end of it.
> 
> That's surely #876?

Yeah, kinda looks like it.

bug#1117: marked as done (23.0.60; Index in Elisp manual has ^M at the end of each line)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]


Your message dated Sat, 10 Jan 2009 13:15:51 +0200
with message-id <uab9zjtso.fsf@gnu.org>
and subject line Re: ^M in the info files
has caused the Emacs bug report #876,
regarding 23.0.60; Index in Elisp manual has ^M at the end of each line
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
876: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=876
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 4071 bytes --]

From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: 23.0.60; Index in Elisp manual has ^M at the end of each line
Date: Tue, 7 Oct 2008 23:49:07 -0700
Message-ID: <008a01c92911$f6510ee0$0200a8c0@us.oracle.com>

emacs -Q
C-h i, choose Elisp manual
g Index takes you to the Index node.
 
Each line has a visible ^M at the end of it.
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-10-03 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
 
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t
 
Major mode: Info
 
Minor modes in effect:
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t
 
Recent input:
<help-echo> C-h i <help-echo> <help-echo> <help-echo> 
<down-mouse-2> <mouse-2> <double-down-mouse-2> <double-mouse-2> 
<help-echo> g I n d e x <return> <help-echo> <help-echo> 
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo> 
<help-echo> <help-echo> <help-echo> <menu-bar> <help-menu> 
<send-emacs-bug-report>
 
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Composing main Info directory...done





[-- Attachment #3: Type: message/rfc822, Size: 3682 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: 876-done@emacsbugs.donarmstrong.com
Cc: emacs-devel@gnu.org, bug-gnu-emacs@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: ^M in the info files
Date: Sat, 10 Jan 2009 13:15:51 +0200
Message-ID: <uab9zjtso.fsf@gnu.org>

> Date: Sat, 29 Nov 2008 00:39:27 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
> 	handa@m17n.org
> 
> > From: "Drew Adams" <drew.adams@oracle.com>
> > Date: Fri, 28 Nov 2008 13:28:34 -0800
> > Cc: 'Juanma Barranquero' <lekktu@gmail.com>, emacs-devel@gnu.org
> > 
> > Whatever happened to this thread and the associated bugs: #876, #1117, #1284?
> > 
> > It sounds like there were alternative proposals about how to fix this, but there
> > was no discussion to try to reach a consensus or a decision. Is that where
> > things were left?
> > 
> > Meanwhile, it's still impossible to use the index in Info manuals on Windows,
> > and it's impossible to use some manuals (e.g. Viper) at all.
> 
> Don't worry, this will get fixed before Emacs 23 is ready for release.
> 
> I will work on it soon if no one beats me to it.

(Fore some value of "soon", sorry.)

I fixed this bug.

There were two suggestions for how to fix this: one by Handa-san in
this message:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00293.html

followed by a tentative patch by Juanma here:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00316.html

The other suggestion was by Stefan:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00373.html

I decided I liked the first alternative better, since it has much
more local effect than the other one.  What Stefan suggested implied
messing with coding priorities, and I didn't feel that was TRT at this
late stage in Emacs 23.1 development.

The changes I installed are more thorough than what Juanma posted:
they change both detect_coding and detect_coding_system, and also bind
inhibit-null-byte-detection in a couple more places in info.el.

The result was tested on GNU/Linux, MS-Windows, and MS-DOS, both with
compressed and uncompressed Info files, with auto-compression-mode
both on and off.

bug#1284: 23.0.60; ^M throughout Viper manual

[Drew Adams]

Subject line says it all
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-10-09 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
 

bug#1284: 23.0.60; ^M throughout Viper manual

[Drew Adams]

Also, the manual name should be listed in `dir' as `Viper', not `VIPER'.
Throughout the Viper manual, Viper is referred to as `Viper', not `VIPER'.

bug#1284: 23.0.60; ^M throughout Viper manual

[Eli Zaretskii]

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Fri, 31 Oct 2008 09:26:02 -0700
> Cc: 
> 
> Also, the manual name should be listed in `dir' as `Viper', not `VIPER'.
> Throughout the Viper manual, Viper is referred to as `Viper', not `VIPER'.

We just honor the manual's request here, which specifies this DIR
entry in viper.texi:

    @direntry
    * VIPER: (viper).       The newest Emacs VI-emulation mode.
			      (also, A VI Plan for Emacs Rescue
			       or the VI PERil.)
    @end direntry

So it sounds like VIPER is actually an acronym, or at least it used to
be.

bug#1284: 23.0.60; ^M throughout Viper manual

[Juanma Barranquero]

reassign 1284 emacs,w32
merge 876 1284
quit

> Subject line says it all

That's bug#876, which you already reported previously as #1117

  Juanma

bug#1284: 23.0.60; ^M throughout Viper manual

[Leo]

On 2008-10-31 15:56 +0000, Drew Adams wrote:
> Subject line says it all

I think a few other info files also has the same problem.

-- 
.:  Leo  :.  [ sdl.web AT gmail.com ]  .:  [ GPG Key: 9283AA3F ]  :.

        Use the better alternative -- http://www.openoffice.org/

bug#1284: marked as done (23.0.60; ^M throughout Viper manual)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 833 bytes --]


Your message dated Sat, 10 Jan 2009 13:15:51 +0200
with message-id <uab9zjtso.fsf@gnu.org>
and subject line Re: ^M in the info files
has caused the Emacs bug report #876,
regarding 23.0.60; ^M throughout Viper manual
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
876: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=876
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 2761 bytes --]

From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: 23.0.60; ^M throughout Viper manual
Date: Fri, 31 Oct 2008 08:56:56 -0700
Message-ID: <001a01c93b71$4d792ce0$0200a8c0@us.oracle.com>

Subject line says it all
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-10-09 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
 




[-- Attachment #3: Type: message/rfc822, Size: 3682 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: 876-done@emacsbugs.donarmstrong.com
Cc: emacs-devel@gnu.org, bug-gnu-emacs@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: ^M in the info files
Date: Sat, 10 Jan 2009 13:15:51 +0200
Message-ID: <uab9zjtso.fsf@gnu.org>

> Date: Sat, 29 Nov 2008 00:39:27 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
> 	handa@m17n.org
> 
> > From: "Drew Adams" <drew.adams@oracle.com>
> > Date: Fri, 28 Nov 2008 13:28:34 -0800
> > Cc: 'Juanma Barranquero' <lekktu@gmail.com>, emacs-devel@gnu.org
> > 
> > Whatever happened to this thread and the associated bugs: #876, #1117, #1284?
> > 
> > It sounds like there were alternative proposals about how to fix this, but there
> > was no discussion to try to reach a consensus or a decision. Is that where
> > things were left?
> > 
> > Meanwhile, it's still impossible to use the index in Info manuals on Windows,
> > and it's impossible to use some manuals (e.g. Viper) at all.
> 
> Don't worry, this will get fixed before Emacs 23 is ready for release.
> 
> I will work on it soon if no one beats me to it.

(Fore some value of "soon", sorry.)

I fixed this bug.

There were two suggestions for how to fix this: one by Handa-san in
this message:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00293.html

followed by a tentative patch by Juanma here:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00316.html

The other suggestion was by Stefan:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00373.html

I decided I liked the first alternative better, since it has much
more local effect than the other one.  What Stefan suggested implied
messing with coding priorities, and I didn't feel that was TRT at this
late stage in Emacs 23.1 development.

The changes I installed are more thorough than what Juanma posted:
they change both detect_coding and detect_coding_system, and also bind
inhibit-null-byte-detection in a couple more places in info.el.

The result was tested on GNU/Linux, MS-Windows, and MS-DOS, both with
compressed and uncompressed Info files, with auto-compression-mode
both on and off.

bug#1816: 23.0.60; ^M in CC mode manual.

[Matzi Kratzi]

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

All (probably most) lines in the CC Mode info manual are ended with ^M.
I use a build from Lennart Borgman.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
c:/Download/emacs-090104/emacs/etc/DEBUG for instructions.


In GNU Emacs 23.0.60.1 (i386-mingw-nt5.0.2195)
 of 2009-01-04 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.0.2195
configured using `configure --with-gcc (3.4) --no-opt --cflags
-Ic:/g/include -fno-crossjumping'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: SVE
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t

Major mode: Info

Minor modes in effect:
  which-function-mode: t
  show-paren-mode: t
  iswitchb-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
C-h i C-s l i b m <return> <return> SPC u u <up> <return>
SPC SPC SPC SPC u u u <up> <return> u <up> <up> <up>
<up> <up> <return> u C-s c c - m o <backspace> <backspace>
<backspace> SPC m o <backspace> <backspace> <backspace>
C-s M-< C-s C-s <return> <return> M-x c o m p <backspace>
<backspace> <backspace> <backspace> r e p o r t SPC
e m a SPC SPC <return>

Recent messages:
Info-extract-pointer: Node has no Up
uncompressing gv.info.gz...done
uncompressing gv.info.gz...done
uncompressing gv.info.gz...done
uncompressing cygwin-ug-net.info.gz...done
uncompressing cygwin-ug-net.info.gz...done
uncompressing cygwin-ug-net.info.gz...done
Mark saved where search started
Mark set
Mark saved where search started

bug#1816: 23.0.60; ^M in CC mode manual.

[Jason Rumney]

merge 876 1816
thanks

Matzi Kratzi wrote:
> All (probably most) lines in the CC Mode info manual are ended with ^M.
> I use a build from Lennart Borgman.
>   

This is a known bug affecting Emacs on Windows.

Processed: Re: bug#1816: 23.0.60; ^M in CC mode manual.

[Emacs bug Tracking System]

Processing commands for control@emacsbugs.donarmstrong.com:

> merge 876 1816
bug#876: ^M in some Windows info files because of null-byte detection
bug#1816: 23.0.60; ^M in CC mode manual.
bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line
bug#1284: 23.0.60; ^M throughout Viper manual
Warning: Unknown package 'w32'
Warning: Unknown package 'w32'
Warning: Unknown package 'w32'
Warning: Unknown package 'w32'
Merged 876 1117 1284 1816.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Don Armstrong
(administrator, Emacs bugs database)

bug#1816: marked as done (23.0.60; ^M in CC mode manual.)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]


Your message dated Sat, 10 Jan 2009 13:15:51 +0200
with message-id <uab9zjtso.fsf@gnu.org>
and subject line Re: ^M in the info files
has caused the Emacs bug report #876,
regarding 23.0.60; ^M in CC mode manual.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
876: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=876
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 5435 bytes --]

From: "Matzi Kratzi" <matzikratzi@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; ^M in CC mode manual.
Date: Wed, 7 Jan 2009 12:55:44 +0100
Message-ID: <7f9b11c90901070355x3842939fo31e7725bc0989b43@mail.gmail.com>

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

All (probably most) lines in the CC Mode info manual are ended with ^M.
I use a build from Lennart Borgman.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
c:/Download/emacs-090104/emacs/etc/DEBUG for instructions.


In GNU Emacs 23.0.60.1 (i386-mingw-nt5.0.2195)
 of 2009-01-04 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.0.2195
configured using `configure --with-gcc (3.4) --no-opt --cflags
-Ic:/g/include -fno-crossjumping'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: SVE
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t

Major mode: Info

Minor modes in effect:
  which-function-mode: t
  show-paren-mode: t
  iswitchb-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
C-h i C-s l i b m <return> <return> SPC u u <up> <return>
SPC SPC SPC SPC u u u <up> <return> u <up> <up> <up>
<up> <up> <return> u C-s c c - m o <backspace> <backspace>
<backspace> SPC m o <backspace> <backspace> <backspace>
C-s M-< C-s C-s <return> <return> M-x c o m p <backspace>
<backspace> <backspace> <backspace> r e p o r t SPC
e m a SPC SPC <return>

Recent messages:
Info-extract-pointer: Node has no Up
uncompressing gv.info.gz...done
uncompressing gv.info.gz...done
uncompressing gv.info.gz...done
uncompressing cygwin-ug-net.info.gz...done
uncompressing cygwin-ug-net.info.gz...done
uncompressing cygwin-ug-net.info.gz...done
Mark saved where search started
Mark set
Mark saved where search started



[-- Attachment #3: Type: message/rfc822, Size: 3682 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: 876-done@emacsbugs.donarmstrong.com
Cc: emacs-devel@gnu.org, bug-gnu-emacs@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: ^M in the info files
Date: Sat, 10 Jan 2009 13:15:51 +0200
Message-ID: <uab9zjtso.fsf@gnu.org>

> Date: Sat, 29 Nov 2008 00:39:27 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
> 	handa@m17n.org
> 
> > From: "Drew Adams" <drew.adams@oracle.com>
> > Date: Fri, 28 Nov 2008 13:28:34 -0800
> > Cc: 'Juanma Barranquero' <lekktu@gmail.com>, emacs-devel@gnu.org
> > 
> > Whatever happened to this thread and the associated bugs: #876, #1117, #1284?
> > 
> > It sounds like there were alternative proposals about how to fix this, but there
> > was no discussion to try to reach a consensus or a decision. Is that where
> > things were left?
> > 
> > Meanwhile, it's still impossible to use the index in Info manuals on Windows,
> > and it's impossible to use some manuals (e.g. Viper) at all.
> 
> Don't worry, this will get fixed before Emacs 23 is ready for release.
> 
> I will work on it soon if no one beats me to it.

(Fore some value of "soon", sorry.)

I fixed this bug.

There were two suggestions for how to fix this: one by Handa-san in
this message:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00293.html

followed by a tentative patch by Juanma here:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00316.html

The other suggestion was by Stefan:

  http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00373.html

I decided I liked the first alternative better, since it has much
more local effect than the other one.  What Stefan suggested implied
messing with coding priorities, and I didn't feel that was TRT at this
late stage in Emacs 23.1 development.

The changes I installed are more thorough than what Juanma posted:
they change both detect_coding and detect_coding_system, and also bind
inhibit-null-byte-detection in a couple more places in info.el.

The result was tested on GNU/Linux, MS-Windows, and MS-DOS, both with
compressed and uncompressed Info files, with auto-compression-mode
both on and off.

RE: ^M in the info files

[Drew Adams]

Thanks for fixing this. 

bug#1845: Acknowledgement (^M in the info files)

[Drew Adams]

Something wrong here, it seems.

I received this ack, and another one (identical) for new bug #1844. I filed no
such new bugs. I simply replied (once) to Eli's message saying that he had fixed
bug #876, by saying thank you.

The bug tracker seems to be inebriated again.

Also, I've recently received acks apparently intended for others, with no
connection to any bug ever filed by me or any mail ever sent by me. I assume
that others have also received such spurious acks.

> From: Emacs bug Tracking System [mailto:owner@emacsbugs.donarmstrong.com] 
> Sent: Saturday, January 10, 2009 8:30 AM
> To: Drew Adams
> Subject: bug#1845: Acknowledgement (^M in the info files)
> 
> 
> Thank you for filing a new bug report with Emacs.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Emacs Bugs <bug-gnu-emacs@gnu.org>
> 
> If you wish to submit further information on this problem, please
> send it to 1845@emacsbugs.donarmstrong.com, as before.
> 
> Please do not send mail to owner@emacsbugs.donarmstrong.com 
> unless you wish to report a problem with the Bug-tracking system.
> 
> -- 
> 1845: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1845
> Emacs Bug Tracking System
> Contact owner@emacsbugs.donarmstrong.com with problems

Re: ^M in the info files

[Stefan Monnier]

Thank you, Eli,

> I decided I liked the first alternative better, since it has much
> more local effect than the other one.  What Stefan suggested implied
> messing with coding priorities, and I didn't feel that was TRT at this
> late stage in Emacs 23.1 development.

[ Obviously my suggestion requires more work to implement, but.. ]
Hmm...curious, why does it involve coding priorities?


        Stefan

Re: ^M in the info files

[Eli Zaretskii]

> X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,
> 	FORGED_RCVD_HELO,SPF_SOFTFAIL autolearn=no version=3.1.0
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 876-done@emacsbugs.donarmstrong.com,  emacs-pretest-bug@gnu.org,  bug-gnu-emacs@gnu.org,  emacs-devel@gnu.org
> Date: Mon, 12 Jan 2009 15:54:38 -0500
> 
> Hmm...curious, why does it involve coding priorities?

You suggested to introduce a way of controlling which possible
encodings will _not_ be acceptable by the caller of
detect-coding-region/string.  These primitives work by scanning the
coding_priorities[] array and checking them against those categories
that has been rejected based on the text in the region/string.  See
detect_coding and detect_coding_system.

bug#876: ^M in the info files

[Glenn Morris]

Please stop cc'ing emacs-pretest-bug@gnu.org and bug-gnu-emacs@gnu.org
in this discussion, it messes up the bug tracker.

bug#876: ^M in the info files

[Eli Zaretskii]

> From: Glenn Morris <rgm@gnu.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 876@emacsbugs.donarmstrong.com,  emacs-devel@gnu.org
> Date: Mon, 12 Jan 2009 17:27:03 -0500
> 
> 
> Please stop cc'ing emacs-pretest-bug@gnu.org and bug-gnu-emacs@gnu.org
> in this discussion, it messes up the bug tracker.

Why won't the tracker get its act together and stop forcing us into
editing mail headers?  I use the Rmail's `r' command, which replies to
all the original "To" and "CC" addressees.  With the amounts of mail
I'm responding to, I cannot afford editing headers of every message I
send.  Even if I try, I will surely sometimes forget.