[debbugs-tracker] bug#31251: closed (read-from-minibuffer sets print-escape-newlines; why?)

[GNU bug Tracking System]

Your message dated Wed, 25 Apr 2018 12:31:51 -0700
with message-id <address@hidden>
and subject line read-from-minibuffer sets print-escape-newlines; why?
has caused the debbugs.gnu.org bug report #31251,
regarding read-from-minibuffer sets print-escape-newlines; why?
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
31251: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31251
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> read-from-minibuffer sets print-escape-newlines; why?
>
>
>
>
> Date: 
>
> Tue, 24 Apr 2018 14:31:55 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
>
>
>
>
> 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.
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> read-from-minibuffer sets print-escape-newlines; why?
>
>
>
>
> Date: 
>
> Wed, 25 Apr 2018 12:31:51 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
>
>
>
>
> 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
>
>
>
> --- End Message ---