unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: peromsik@ptc.com, 23709@debbugs.gnu.org
Subject: bug#23709: 24.5; inhibit-eol-conversion breaks archive-7z-summarize
Date: Wed, 14 Feb 2018 06:33:50 -0500	[thread overview]
Message-ID: <87wozf955t.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83mvbuomxj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Apr 2017 19:10:16 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> It's a customizable user option. It seems perfectly valid to me to set
>> it globally, for the reasons given in the manual:
>> 
>>   some people prefer this to the more subtle '(DOS)' end-of-line type
>>   indication near the left edge of the mode line
>> 
>> I've had it set in my own .emacs for years, as it happens.
>
> I'm guessing this variable was made a defcustom under pressure from
> people who didn't want to see "(DOS)".

I think it's rather from people who *can't* see "(DOS)" (not literally
"can't", but find the indicator easy to miss).  I came across a post [1]
about this recently (the post itself is from 2016):

    Many versions ago, if you opened a dos-line-end file on Linux you
    would see the extra ^M codes. Now it automatically recognizes the
    situation and puts "DOS" in the info bar and hides the extra ^Ms.

    How can I exit "DOS" mode and switch back to Unix mode? How can I
    disable the auto-detection and force the files to be opened with
    Unix line endings and the DOS CR shown as ^M?

And a further comment from the OP about it:

    I guess there isn't really a compelling reason for it except that I
    only occasionally encounter dos files and I was used to that obvious
    visual cue of all the ^M's when I open one.

So this does sound like it's all about files.  If inhibit-eol-conversion
is problematic, maybe a setting for file-coding-system-alist would be a
better recommendation?

[1]: https://emacs.stackexchange.com/questions/24984/how-to-disable-automatic-dos-mode/38576





  parent reply	other threads:[~2018-02-14 11:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 21:50 bug#23709: 24.5; inhibit-eol-conversion breaks archive-7z-summarize peromsik
2017-04-04 20:10 ` Glenn Morris
2017-04-05  2:29   ` Eli Zaretskii
2017-04-05 14:14     ` Peromsik, Aaron
2017-04-05 16:00       ` Eli Zaretskii
2017-04-06 21:58         ` Peromsik, Aaron
2017-04-07  7:05           ` Eli Zaretskii
2017-04-05 15:56     ` Glenn Morris
2017-04-05 16:10       ` Eli Zaretskii
2017-04-05 19:58         ` Glenn Morris
2017-04-06  2:33           ` Eli Zaretskii
2018-02-14 11:33         ` Noam Postavsky [this message]
2018-02-14 11:51           ` Andreas Schwab
2018-02-15  1:39             ` Noam Postavsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wozf955t.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=23709@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=peromsik@ptc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).