* bug#31251: read-from-minibuffer sets print-escape-newlines; why?
@ 2018-04-24 21:31 Paul Eggert
2018-04-25 19:31 ` Paul Eggert
0 siblings, 1 reply; 2+ messages in thread
From: Paul Eggert @ 2018-04-24 21:31 UTC (permalink / raw)
To: 31251
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-04-25 19:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-04-24 21:31 bug#31251: read-from-minibuffer sets print-escape-newlines; why? Paul Eggert
2018-04-25 19:31 ` Paul Eggert
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).