eol in emacs23

eol in emacs23

[Seweryn Kokot]

Hello,

In Emacs manual (info "(emacs)Recognize Coding")

,----[ (info "(emacs)Recognize Coding") ]
|    Emacs recognizes which kind of end-of-line conversion to use based on
| the contents of the file: if it sees only carriage-returns, or only
| carriage-return linefeed sequences, then it chooses the end-of-line
| conversion accordingly.  You can inhibit the automatic use of
| end-of-line conversion by setting the variable `inhibit-eol-conversion'
| to non-`nil'.  If you do that, DOS-style files will be displayed with
| the `^M' characters visible in the buffer; some people prefer this to
| the more subtle `(DOS)' end-of-line type indication near the left edge
| of the mode line (*note eol-mnemonic: Mode Line.).
`----

it is written that if inhibit-eol-conversion is non-nil
then I will see ^M at every line instead of (DOS) in modeline. However
no matter to what inhibit-eol-conversion is set (t or nil) I always get
(DOS) and no ^M when visiting a DOS file.

Any idea what is wrong?

Thanks in advance.
-- 
regards,
Seweryn

Re: eol in emacs23

[Eli Zaretskii]

> From: Seweryn Kokot <sewkokot@gmail.com>
> Date: Tue, 03 Feb 2009 11:26:38 +0100
> 
> it is written that if inhibit-eol-conversion is non-nil
> then I will see ^M at every line instead of (DOS) in modeline. However
> no matter to what inhibit-eol-conversion is set (t or nil) I always get
> (DOS) and no ^M when visiting a DOS file.
> 
> Any idea what is wrong?

It's a bug.  Please use "M-x report-emacs-bug RET" to submit a bug
report about this.

Thanks.

Re: eol in emacs23

[Seweryn Kokot]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Seweryn Kokot <sewkokot@gmail.com>
>> Date: Tue, 03 Feb 2009 11:26:38 +0100
>> 
>> it is written that if inhibit-eol-conversion is non-nil
>> then I will see ^M at every line instead of (DOS) in modeline. However
>> no matter to what inhibit-eol-conversion is set (t or nil) I always get
>> (DOS) and no ^M when visiting a DOS file.
>> 
>> Any idea what is wrong?
>
> It's a bug.  Please use "M-x report-emacs-bug RET" to submit a bug
> report about this.
>
> Thanks.

In fact it is a bug since it works correctly in emacs22.
I submitted the bug report.

-- 
regards,
Seweryn