GNU bug report logs - #23585
25.0.93; Win32: spurious ^M pop up at byte offset 65536

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23585 in the body.
You can then email your comments to 23585 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Anders Lindgren <andlind <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.0.93; Win32: spurious ^M pop up at byte offset 65536
Date: Fri, 20 May 2016 12:16:51 +0200

[Message part 1 (text/plain, inline)]

Hi!

I've noticed that sometimes an extra carriage return character pops up in
my source files, when running Emacs under Windows. They are always located
at the end of a line. I use auto-revert mode and I've only seen this in
files already open in Emacs.

Today I noticed that one such carriage return character was placed at
buffer position 62879 in line 2658. This corresponds to byte position 65536
(or hex 0x10000) in the file. Clearly, this can't be a coincidence.

By the way, I'm not sure Emacs is the culprit here -- I use subversion as a
version control system and Visual Studio for debugging and sometimes minor
edits.

    -- Anders

[Message part 2 (text/html, inline)]

Message #8 received at 23585 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Anders Lindgren <andlind <at> gmail.com>
Cc: 23585 <at> debbugs.gnu.org
Subject: Re: bug#23585: 25.0.93; Win32: spurious ^M pop up at byte offset 65536
Date: Fri, 20 May 2016 16:29:54 +0300

> Date: Fri, 20 May 2016 12:16:51 +0200
> From: Anders Lindgren <andlind <at> gmail.com>
> 
> I've noticed that sometimes an extra carriage return character pops up in my source files, when running
> Emacs under Windows. They are always located at the end of a line. I use auto-revert mode and I've only
> seen this in files already open in Emacs.
> 
> Today I noticed that one such carriage return character was placed at buffer position 62879 in line 2658. This
> corresponds to byte position 65536 (or hex 0x10000) in the file. Clearly, this can't be a coincidence.
> 
> By the way, I'm not sure Emacs is the culprit here -- I use subversion as a version control system and Visual
> Studio for debugging and sometimes minor edits.

If you can come up with a reproducible recipe, we could debug this.

Thanks.

Message #11 received at 23585 <at> debbugs.gnu.org (full text, mbox):

From: Anders Lindgren <andlind <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 23585 <at> debbugs.gnu.org
Subject: Re: bug#23585: 25.0.93; Win32: spurious ^M pop up at byte offset 65536
Date: Fri, 20 May 2016 15:38:06 +0200

[Message part 1 (text/plain, inline)]

>
> If you can come up with a reproducible recipe, we could debug this.
>
>
I wish I could. Whoever, they seem to pop up about once every few weeks,
and I only discover them after I've continued working with the file. The
main reason why I posted the bug without a recipe was to see if anybody
else had seen anything similar, or if anybody would have a hunch on what
the cause is.

Of course, one could try to provoke this by creating and appending to files
with a carriage return/newline at the critical location and see if Emacs
loads or reverts them incorrectly.

    -- Anders

[Message part 2 (text/html, inline)]

Message #18 received at 23585-done <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 23585-done <at> debbugs.gnu.org
Subject: Re: bug#23585: 25.0.93; Win32: spurious ^M pop up at byte offset 65536
Date: Wed, 07 Dec 2016 17:11:07 -0500

Without a recipe, I can't see this going anywhere, so closing.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.