From: Eli Zaretskii <eliz@gnu.org>
To: 34318@debbugs.gnu.org, rudalics@gmx.at, schwab@linux-m68k.org
Subject: bug#34318: 26.1.90; Strange behavior of two line message with running shell
Date: Tue, 05 Feb 2019 12:36:18 +0200 [thread overview]
Message-ID: <07F7084B-E728-4D6E-BA75-542D686AFCF6@gnu.org> (raw)
In-Reply-To: <5C5963BE.6080800@gmx.at>
On February 5, 2019 12:21:50 PM GMT+02:00, martin rudalics <rudalics@gmx.at> wrote:
> > What is the value of print-escape-newlines?
>
> So it's
>
> commit a92e7b4ef6915e079a97e4e33e45b11508170cb1
> Author: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed Apr 25 12:20:04 2018 -0700
>
> Don’t set print-escape-newlines in the minibuffer
>
> This appears to be an unnecessary and possibly-confusing
> revenant from ancient code (Bug#31251). See thread containing:
> https://lists.gnu.org/r/emacs-devel/2018-04/msg00654.html
> * src/minibuf.c (read_minibuf): Do not set print-escape-newlines.
> * src/print.c (syms_of_print): Do not defsym print-escape-newlines
> or print-escape-control-characters, as these symbols are not used
> in C code.
>
> that fixed the behavior for Emacs 27. Since it apparently worked
> until Emacs 25 we have a regression in Emacs 26 though.
>
> Thanks for spotting it, martin
What regression is that? Maybe I'm missing something, but I don't see any problem with the latest pretest of Emacs 26.2.
next prev parent reply other threads:[~2019-02-05 10:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 18:52 bug#34318: 26.1.90; Strange behavior of two line message with running shell martin rudalics
2019-02-04 22:19 ` Andreas Schwab
2019-02-04 23:44 ` Glenn Morris
2019-02-05 8:36 ` martin rudalics
2019-02-05 9:05 ` Eli Zaretskii
2019-02-05 10:21 ` martin rudalics
2019-02-05 9:12 ` Andreas Schwab
2019-02-05 10:21 ` martin rudalics
2019-02-05 8:36 ` martin rudalics
2019-02-05 9:37 ` Andreas Schwab
2019-02-05 10:21 ` martin rudalics
2019-02-05 10:36 ` Eli Zaretskii [this message]
2019-02-05 11:39 ` Andreas Schwab
2019-02-05 13:25 ` Eli Zaretskii
2019-02-05 13:44 ` Andreas Schwab
2019-02-08 9:58 ` martin rudalics
2019-02-12 21:34 ` Stefan Monnier
2019-02-19 9:00 ` martin rudalics
2019-02-19 12:52 ` Stefan Monnier
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=07F7084B-E728-4D6E-BA75-542D686AFCF6@gnu.org \
--to=eliz@gnu.org \
--cc=34318@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=schwab@linux-m68k.org \
/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).