GNU bug report logs - #31251
read-from-minibuffer sets print-escape-newlines; why?

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31251 in the body.
You can then email your comments to 31251 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: bug-gnu-emacs <at> gnu.org
Subject: read-from-minibuffer sets print-escape-newlines; why?
Date: Tue, 24 Apr 2018 14:31:55 -0700

read-from-minibuffer and related functions set print-escape-newlines in 
the minibuffer, but there's no clear reason why: these functions do not 
call 'prin1' or 'print' directly, and setting print-escape-newlines 
affects behavior only in seemingly unrelated areas, such as code 
executed indirectly via activate-input-method or minibuffer-setup-hook. 
If there's no need to set print-escape-newlines then it shouldn't be 
set; if there is a need, the need should be documented. For now I'll add 
a FIXME comment about this to Emacs master.

Message #10 received at 31251-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: 31251-done <at> debbugs.gnu.org
Subject: read-from-minibuffer sets print-escape-newlines; why?
Date: Wed, 25 Apr 2018 12:31:51 -0700

I removed the code lines in question and am closing bug#31251. See the 
thread containing:

https://lists.gnu.org/r/emacs-devel/2018-04/msg00654.html

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.