* Re: ^M in the info files [not found] ` <u1vwvh3vk.fsf@gnu.org> @ 2009-01-10 11:15 ` Eli Zaretskii 2008-09-03 16:39 ` bug#876: ^M in some Windows info files because of null-byte detection Juanma Barranquero ` (5 more replies) 0 siblings, 6 replies; 25+ messages in thread From: Eli Zaretskii @ 2009-01-10 11:15 UTC (permalink / raw) To: 876-done; +Cc: emacs-pretest-bug, bug-gnu-emacs, emacs-devel > 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#876: ^M in some Windows info files because of null-byte detection @ 2008-09-03 16:39 ` Juanma Barranquero 2009-01-10 11:25 ` bug#876: marked as done (^M in some Windows info files because of null-byte detection) Emacs bug Tracking System 0 siblings, 1 reply; 25+ messages in thread From: Juanma Barranquero @ 2008-09-03 16:39 UTC (permalink / raw) To: Emacs Bug Tracker 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#876: marked as done (^M in some Windows info files because of null-byte detection) 2008-09-03 16:39 ` bug#876: ^M in some Windows info files because of null-byte detection Juanma Barranquero @ 2009-01-10 11:25 ` Emacs bug Tracking System 0 siblings, 0 replies; 25+ messages in thread From: Emacs bug Tracking System @ 2009-01-10 11:25 UTC (permalink / raw) To: Eli Zaretskii [-- 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line @ 2008-10-08 6:49 ` Drew Adams 2008-10-08 8:02 ` Juanma Barranquero 2009-01-10 11:25 ` bug#1117: marked as done (23.0.60; Index in Elisp manual has ^M at the end of each line) Emacs bug Tracking System 0 siblings, 2 replies; 25+ messages in thread From: Drew Adams @ 2008-10-08 6:49 UTC (permalink / raw) To: emacs-pretest-bug 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line 2008-10-08 6:49 ` bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line Drew Adams @ 2008-10-08 8:02 ` Juanma Barranquero 2008-10-08 10:01 ` Eli Zaretskii 2008-10-08 14:10 ` Drew Adams 2009-01-10 11:25 ` bug#1117: marked as done (23.0.60; Index in Elisp manual has ^M at the end of each line) Emacs bug Tracking System 1 sibling, 2 replies; 25+ messages in thread From: Juanma Barranquero @ 2008-10-08 8:02 UTC (permalink / raw) To: Drew Adams, 1117 > 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line 2008-10-08 8:02 ` Juanma Barranquero @ 2008-10-08 10:01 ` Eli Zaretskii 2008-10-08 16:52 ` Juanma Barranquero 2008-10-08 14:10 ` Drew Adams 1 sibling, 1 reply; 25+ messages in thread From: Eli Zaretskii @ 2008-10-08 10:01 UTC (permalink / raw) To: Juanma Barranquero, 1117; +Cc: bug-gnu-emacs > 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? ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line 2008-10-08 10:01 ` Eli Zaretskii @ 2008-10-08 16:52 ` Juanma Barranquero 0 siblings, 0 replies; 25+ messages in thread From: Juanma Barranquero @ 2008-10-08 16:52 UTC (permalink / raw) To: Eli Zaretskii; +Cc: 1117 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line 2008-10-08 8:02 ` Juanma Barranquero 2008-10-08 10:01 ` Eli Zaretskii @ 2008-10-08 14:10 ` Drew Adams 1 sibling, 0 replies; 25+ messages in thread From: Drew Adams @ 2008-10-08 14:10 UTC (permalink / raw) To: 'Juanma Barranquero', 1117 > > 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1117: marked as done (23.0.60; Index in Elisp manual has ^M at the end of each line) 2008-10-08 6:49 ` bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line Drew Adams 2008-10-08 8:02 ` Juanma Barranquero @ 2009-01-10 11:25 ` Emacs bug Tracking System 1 sibling, 0 replies; 25+ messages in thread From: Emacs bug Tracking System @ 2009-01-10 11:25 UTC (permalink / raw) To: Eli Zaretskii [-- 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1284: 23.0.60; ^M throughout Viper manual @ 2008-10-31 15:56 ` Drew Adams 2008-10-31 16:26 ` Drew Adams ` (3 more replies) 0 siblings, 4 replies; 25+ messages in thread From: Drew Adams @ 2008-10-31 15:56 UTC (permalink / raw) To: emacs-pretest-bug 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' ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1284: 23.0.60; ^M throughout Viper manual 2008-10-31 15:56 ` bug#1284: 23.0.60; ^M throughout Viper manual Drew Adams @ 2008-10-31 16:26 ` Drew Adams 2008-10-31 18:41 ` Eli Zaretskii 2008-10-31 16:26 ` Juanma Barranquero ` (2 subsequent siblings) 3 siblings, 1 reply; 25+ messages in thread From: Drew Adams @ 2008-10-31 16:26 UTC (permalink / raw) To: 1284, emacs-pretest-bug 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'. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1284: 23.0.60; ^M throughout Viper manual 2008-10-31 16:26 ` Drew Adams @ 2008-10-31 18:41 ` Eli Zaretskii 0 siblings, 0 replies; 25+ messages in thread From: Eli Zaretskii @ 2008-10-31 18:41 UTC (permalink / raw) To: Drew Adams, 1284; +Cc: emacs-pretest-bug, bug-gnu-emacs > 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1284: 23.0.60; ^M throughout Viper manual 2008-10-31 15:56 ` bug#1284: 23.0.60; ^M throughout Viper manual Drew Adams 2008-10-31 16:26 ` Drew Adams @ 2008-10-31 16:26 ` Juanma Barranquero 2008-10-31 20:47 ` Leo 2009-01-10 11:25 ` bug#1284: marked as done (23.0.60; ^M throughout Viper manual) Emacs bug Tracking System 3 siblings, 0 replies; 25+ messages in thread From: Juanma Barranquero @ 2008-10-31 16:26 UTC (permalink / raw) To: Drew Adams; +Cc: 1284 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1284: 23.0.60; ^M throughout Viper manual 2008-10-31 15:56 ` bug#1284: 23.0.60; ^M throughout Viper manual Drew Adams 2008-10-31 16:26 ` Drew Adams 2008-10-31 16:26 ` Juanma Barranquero @ 2008-10-31 20:47 ` Leo 2009-01-10 11:25 ` bug#1284: marked as done (23.0.60; ^M throughout Viper manual) Emacs bug Tracking System 3 siblings, 0 replies; 25+ messages in thread From: Leo @ 2008-10-31 20:47 UTC (permalink / raw) To: emacs-pretest-bug; +Cc: bug-gnu-emacs 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/ ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1284: marked as done (23.0.60; ^M throughout Viper manual) 2008-10-31 15:56 ` bug#1284: 23.0.60; ^M throughout Viper manual Drew Adams ` (2 preceding siblings ...) 2008-10-31 20:47 ` Leo @ 2009-01-10 11:25 ` Emacs bug Tracking System 3 siblings, 0 replies; 25+ messages in thread From: Emacs bug Tracking System @ 2009-01-10 11:25 UTC (permalink / raw) To: Eli Zaretskii [-- 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1816: 23.0.60; ^M in CC mode manual. @ 2009-01-07 11:55 ` Matzi Kratzi 2009-01-07 14:05 ` Jason Rumney 2009-01-10 11:25 ` bug#1816: marked as done (23.0.60; ^M in CC mode manual.) Emacs bug Tracking System 0 siblings, 2 replies; 25+ messages in thread From: Matzi Kratzi @ 2009-01-07 11:55 UTC (permalink / raw) To: emacs-pretest-bug 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1816: 23.0.60; ^M in CC mode manual. 2009-01-07 11:55 ` bug#1816: 23.0.60; ^M in CC mode manual Matzi Kratzi @ 2009-01-07 14:05 ` Jason Rumney 2009-01-07 14:15 ` Processed: " Emacs bug Tracking System 2009-01-10 11:25 ` bug#1816: marked as done (23.0.60; ^M in CC mode manual.) Emacs bug Tracking System 1 sibling, 1 reply; 25+ messages in thread From: Jason Rumney @ 2009-01-07 14:05 UTC (permalink / raw) To: Matzi Kratzi, 1816 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* Processed: Re: bug#1816: 23.0.60; ^M in CC mode manual. 2009-01-07 14:05 ` Jason Rumney @ 2009-01-07 14:15 ` Emacs bug Tracking System 0 siblings, 0 replies; 25+ messages in thread From: Emacs bug Tracking System @ 2009-01-07 14:15 UTC (permalink / raw) To: Jason Rumney; +Cc: Emacs Bugs, w32 for {1816, 1284, 1117, 876} 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) ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#1816: marked as done (23.0.60; ^M in CC mode manual.) 2009-01-07 11:55 ` bug#1816: 23.0.60; ^M in CC mode manual Matzi Kratzi 2009-01-07 14:05 ` Jason Rumney @ 2009-01-10 11:25 ` Emacs bug Tracking System 1 sibling, 0 replies; 25+ messages in thread From: Emacs bug Tracking System @ 2009-01-10 11:25 UTC (permalink / raw) To: Eli Zaretskii [-- 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ^M in the info files 2009-01-10 11:15 ` ^M in the info files Eli Zaretskii ` (3 preceding siblings ...) 2009-01-07 11:55 ` bug#1816: 23.0.60; ^M in CC mode manual Matzi Kratzi @ 2009-01-10 16:21 ` Drew Adams [not found] ` <handler.1845.B.12316045139313.ack@emacsbugs.donarmstrong.com> 2009-01-12 20:54 ` ^M in the info files Stefan Monnier 5 siblings, 1 reply; 25+ messages in thread From: Drew Adams @ 2009-01-10 16:21 UTC (permalink / raw) To: 'Eli Zaretskii', 876-done Cc: emacs-pretest-bug, bug-gnu-emacs, emacs-devel Thanks for fixing this. ^ permalink raw reply [flat|nested] 25+ messages in thread
[parent not found: <handler.1845.B.12316045139313.ack@emacsbugs.donarmstrong.com>]
* bug#1845: Acknowledgement (^M in the info files) [not found] ` <handler.1845.B.12316045139313.ack@emacsbugs.donarmstrong.com> @ 2009-01-10 17:11 ` Drew Adams 0 siblings, 0 replies; 25+ messages in thread From: Drew Adams @ 2009-01-10 17:11 UTC (permalink / raw) To: 1845, owner 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ^M in the info files 2009-01-10 11:15 ` ^M in the info files Eli Zaretskii ` (4 preceding siblings ...) 2009-01-10 16:21 ` ^M in the info files Drew Adams @ 2009-01-12 20:54 ` Stefan Monnier 2009-01-12 22:13 ` Eli Zaretskii 5 siblings, 1 reply; 25+ messages in thread From: Stefan Monnier @ 2009-01-12 20:54 UTC (permalink / raw) To: Eli Zaretskii; +Cc: emacs-pretest-bug, bug-gnu-emacs, 876-done, emacs-devel 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 ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ^M in the info files 2009-01-12 20:54 ` ^M in the info files Stefan Monnier @ 2009-01-12 22:13 ` Eli Zaretskii 2009-01-12 22:27 ` bug#876: " Glenn Morris [not found] ` <iyhc44cg94.fsf@fencepost.gnu.org> 0 siblings, 2 replies; 25+ messages in thread From: Eli Zaretskii @ 2009-01-12 22:13 UTC (permalink / raw) To: Stefan Monnier; +Cc: emacs-pretest-bug, bug-gnu-emacs, 876-done, emacs-devel > 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
* bug#876: ^M in the info files 2009-01-12 22:13 ` Eli Zaretskii @ 2009-01-12 22:27 ` Glenn Morris [not found] ` <iyhc44cg94.fsf@fencepost.gnu.org> 1 sibling, 0 replies; 25+ messages in thread From: Glenn Morris @ 2009-01-12 22:27 UTC (permalink / raw) To: Eli Zaretskii; +Cc: 876, emacs-devel Please stop cc'ing emacs-pretest-bug@gnu.org and bug-gnu-emacs@gnu.org in this discussion, it messes up the bug tracker. ^ permalink raw reply [flat|nested] 25+ messages in thread
[parent not found: <iyhc44cg94.fsf@fencepost.gnu.org>]
* bug#876: ^M in the info files [not found] ` <iyhc44cg94.fsf@fencepost.gnu.org> @ 2009-01-13 4:01 ` Eli Zaretskii 0 siblings, 0 replies; 25+ messages in thread From: Eli Zaretskii @ 2009-01-13 4:01 UTC (permalink / raw) To: Glenn Morris; +Cc: 876, emacs-devel > 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. ^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2009-01-13 4:01 UTC | newest] Thread overview: 25+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <f7ccd24b0808060409x7317e093i6918324c0c057687@mail.gmail.com> [not found] ` <E1KQiBD-00055e-Ie@etlken.m17n.org> [not found] ` <f7ccd24b0808060614h4917f240oc261b8fedff0e8d0@mail.gmail.com> [not found] ` <E1KQtgD-0007i9-1n@etlken.m17n.org> [not found] ` <jwvprokfvbs.fsf-monnier+emacs@gnu.org> [not found] ` <00aa01c951a0$4535a2d0$0200a8c0@us.oracle.com> [not found] ` <u1vwvh3vk.fsf@gnu.org> 2009-01-10 11:15 ` ^M in the info files Eli Zaretskii 2008-09-03 16:39 ` bug#876: ^M in some Windows info files because of null-byte detection Juanma Barranquero 2009-01-10 11:25 ` bug#876: marked as done (^M in some Windows info files because of null-byte detection) Emacs bug Tracking System 2008-10-08 6:49 ` bug#1117: 23.0.60; Index in Elisp manual has ^M at the end of each line Drew Adams 2008-10-08 8:02 ` Juanma Barranquero 2008-10-08 10:01 ` Eli Zaretskii 2008-10-08 16:52 ` Juanma Barranquero 2008-10-08 14:10 ` Drew Adams 2009-01-10 11:25 ` bug#1117: marked as done (23.0.60; Index in Elisp manual has ^M at the end of each line) Emacs bug Tracking System 2008-10-31 15:56 ` bug#1284: 23.0.60; ^M throughout Viper manual Drew Adams 2008-10-31 16:26 ` Drew Adams 2008-10-31 18:41 ` Eli Zaretskii 2008-10-31 16:26 ` Juanma Barranquero 2008-10-31 20:47 ` Leo 2009-01-10 11:25 ` bug#1284: marked as done (23.0.60; ^M throughout Viper manual) Emacs bug Tracking System 2009-01-07 11:55 ` bug#1816: 23.0.60; ^M in CC mode manual Matzi Kratzi 2009-01-07 14:05 ` Jason Rumney 2009-01-07 14:15 ` Processed: " Emacs bug Tracking System 2009-01-10 11:25 ` bug#1816: marked as done (23.0.60; ^M in CC mode manual.) Emacs bug Tracking System 2009-01-10 16:21 ` ^M in the info files Drew Adams [not found] ` <handler.1845.B.12316045139313.ack@emacsbugs.donarmstrong.com> 2009-01-10 17:11 ` bug#1845: Acknowledgement (^M in the info files) Drew Adams 2009-01-12 20:54 ` ^M in the info files Stefan Monnier 2009-01-12 22:13 ` Eli Zaretskii 2009-01-12 22:27 ` bug#876: " Glenn Morris [not found] ` <iyhc44cg94.fsf@fencepost.gnu.org> 2009-01-13 4:01 ` Eli Zaretskii
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).