Strange Python problem on Linux.

Forrest Cahoon fcahoon at
Thu Mar 2 00:51:20 CET 2000

In article <38BC8DB1.F3F26298 at>,
  "Thomas A. Bryan" <tbryan at> wrote:
> ....
> At work, Xemacs shows the ^M in the file.  I must have copied the
> files onto a floppy over samba at work and gotten the \r before the
> \n at the end of the line.  I had been editing the file in Emacs here
> at home, and I didn't even think of the possibility of their being
> hidden carriage returns in the file.  I suppose Emacs hides them
> from me so that I don't have to see them. :-/ In this case, the
> was less than ideal...but it was a fun puzzle, no?

Early versions of GNU Emacs 20 (up to 20.3, IIRC) show MS-DOS style
line endings by a "\" in the status line (instead of a ":" for unix
single-lf style).  This change of behavior from Emacs 19.x cost me a
long time on another problem, because I _expected_ to see the ^Ms at
the end of the line, so I "knew" that wasn't the problem :-(.

The most recent versions of GNU Emacs show "(DOS)" in the status line
instead of the more cryptic "\".  Once you learn that's what's going
on, it's actually _nicer_ than seeing all those ^Ms.

But when you don't, it sucks.

(I'm tempted to throw in some comment about this being an invisible
whitespace problem, but I think I'll refrain :-))

> Thanks for the help.
> ---Tom

Sent via
Before you buy.

More information about the Python-list mailing list