all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 52554@debbugs.gnu.org
Subject: bug#52554: 28.0.90; mm-inline-media-tests customization breaks .emacs reading
Date: Sun, 19 Dec 2021 13:01:01 +0100	[thread overview]
Message-ID: <87a6gwvm6a.fsf@gnus.org> (raw)
In-Reply-To: <87r1aco9xm.fsf@gmail.com> (Robert Pluim's message of "Thu, 16 Dec 2021 16:18:13 +0100")

Robert Pluim <rpluim@gmail.com> writes:

> mm-inline-media-tests contains lambda's, and itʼs byte-compiled, so
> when you customize its value, byte-code is saved in your .emacs. One
> of its components looks like this:
>
>      ("text/x-vcard" mm-inline-text-vcard
>       #[257 "\300\301!\206	%0\302\303!\207"
>             [featurep vcard locate-library "vcard"]
>             3 "
>
>      (fn HANDLE)"])

I see that you've fixed the actual bug in a later patch, but I just
wanted to ask -- should that variable be a user option at all?  Long
list variables are seldom useful as user options.  Instead users should
prepend choices with `push' or something.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2021-12-19 12:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 15:18 bug#52554: 28.0.90; mm-inline-media-tests customization breaks .emacs reading Robert Pluim
2021-12-16 15:30 ` Eli Zaretskii
2021-12-16 15:46   ` Robert Pluim
2021-12-16 16:57     ` Eli Zaretskii
2021-12-16 16:13   ` Andreas Schwab
2021-12-16 16:58     ` Eli Zaretskii
2021-12-17  8:23       ` Robert Pluim
2021-12-17  8:29         ` Eli Zaretskii
2021-12-17  8:45           ` Robert Pluim
2021-12-17 12:11             ` Eli Zaretskii
2022-03-16 18:02               ` Robert Pluim
2021-12-19 12:01 ` Lars Ingebrigtsen [this message]
     [not found]   ` <87h7b3ve9a.fsf@gmail.com>
2021-12-20  9:22     ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6gwvm6a.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52554@debbugs.gnu.org \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.