GNU bug report logs -
#34318
26.1.90; Strange behavior of two line message with running shell
Previous Next
Reported by: martin rudalics <rudalics <at> gmx.at>
Date: Mon, 4 Feb 2019 18:53:01 UTC
Severity: normal
Found in version 26.1.90
Fixed in version 26.2
Done: Noam Postavsky <npostavs <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
On February 5, 2019 12:21:50 PM GMT+02:00, martin rudalics <rudalics <at> gmx.at> wrote:
> > What is the value of print-escape-newlines?
>
> So it's
>
> commit a92e7b4ef6915e079a97e4e33e45b11508170cb1
> Author: Paul Eggert <eggert <at> 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.
This bug report was last modified 6 years and 107 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.