bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#7524: 24.0.50; backquote converts newlines in strings to "\n"


From: Mauro Aranda
Subject: bug#7524: 24.0.50; backquote converts newlines in strings to "\n"
Date: Thu, 22 Oct 2020 09:24:55 -0300

tags 7524 patch
quit

"Drew Adams" <drew.adams@oracle.com> writes:

>> > (This is particularly messy when used in defcustom values.)
>>
>> I don't know what you're referring to.  I'll keep the bug
>> open for now, assuming that the defcustom issue will be
>> the actual bug.
>
> You're right of course about the chars "\n" and a ^J char in a Lisp string.
>
> `defcustom' does different things in this regard, depending on the :type (and
> whether there is a mismatch, but that's something else no doubt).
>
> See what the \n representation does, for example, with the file I sent to
> emacs-devel yesterday, thread "Variable behavior for `mouse-3' second click at
> same spot".  Here's a direct URL to the file.
>
> http://www.emacswiki.org/emacs/mouse3.el
>
> Eval the defcustom for `mouse3-region-popup-submenus', then use `M-x customize',
> and you'll see how messy (how wide) the display is.
>

If I understand this bug report correctly, the wishlist item is about
pretty printing restricted-sexp values, which makes sense to me.  Values
of the sexp widget already get pretty-printed, but not the values of the
restricted-sexp widget.

I attach a patch to pretty-print restricted sexp values too, by using the
same function that the sexp widget uses.

Attachment: 0001-Pretty-print-restricted-sexp-values-too.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]