From: Glenn Morris <rgm@gnu.org>
To: peromsik@ptc.com
Cc: 23709@debbugs.gnu.org
Subject: bug#23709: 24.5; inhibit-eol-conversion breaks archive-7z-summarize
Date: Tue, 04 Apr 2017 16:10:39 -0400 [thread overview]
Message-ID: <6zo9wcc4sg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <9zpeg8a0yxz.fsf@PEROMSIK0D.i-did-not-set--mail-host-address--so-tickle-me> (peromsik@ptc.com's message of "Mon, 6 Jun 2016 17:50:16 -0400")
> M-x set-variable inhibit-eol-conversion t
>
> Then try to open a 7z file. The expected summary does not appear. In the
> *Messages* buffer (quoted below) you can see that the re-search-forward
> call in archive-7z-summarize is confused by the ^M in the output of the
> 7za command. Perhaps adding inhibit-eol-conversion nil to that function's
> let block would be in order?
Thanks for the report. I wonder if inhibit-eol-conversion should not
apply to processes, or should only apply to buffers visiting files, or
if there should be a process-specific version of i-e-c? Because as it
stands I think several places will break if ^M appears in process output
(eg vc-bzr). Binding inhibit-eol-conversion to nil around every single
process call doesn't sound sensible. But then term.el does the opposite,
binding it to t. Hmm. So maybe a process-specific version of
inhibit-eol-conversion, defaulting to nil?
next prev parent reply other threads:[~2017-04-04 20:10 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 [this message]
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
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=6zo9wcc4sg.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=23709@debbugs.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).