From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: larsi@gnus.org, charles@aurox.ch, 28350@debbugs.gnu.org
Subject: bug#28350: enriched.el code execution
Date: Mon, 11 Sep 2017 05:39:27 +0300 [thread overview]
Message-ID: <83ingqt0v4.fsf@gnu.org> (raw)
In-Reply-To: <89bf7f23-d065-572c-ad54-bce7cb9a02e7@cs.ucla.edu> (message from Paul Eggert on Sun, 10 Sep 2017 14:46:59 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 10 Sep 2017 14:46:59 -0700
> Cc: larsi@gnus.org, 28350@debbugs.gnu.org
>
> > (eval-after-load "enriched"
> > '(defun enriched-decode-display-prop (start end &optional param)
> > (list start end)))
> >
> > But it may not work in Emacs earlier than 23 (I can't test it).
>
> It should work, since eval-after-load predates Emacs 19.29. Though it assumes
> that x-display is the only problem here.
x-display _is_ the only problem, because only it allows arbitrary Lisp
forms.
next prev parent reply other threads:[~2017-09-11 2:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 19:24 bug#28350: enriched.el code execution Charles A. Roelli
2017-09-06 19:25 ` Charles A. Roelli
2017-09-07 2:34 ` Eli Zaretskii
2017-09-09 12:23 ` Charles A. Roelli
2017-09-09 13:45 ` Eli Zaretskii
2017-09-09 15:57 ` Charles A. Roelli
2017-09-09 16:55 ` Eli Zaretskii
2017-09-09 20:37 ` Charles A. Roelli
2017-09-10 17:01 ` Eli Zaretskii
2017-09-11 16:32 ` Glenn Morris
2017-09-11 17:01 ` Eli Zaretskii
2017-09-09 22:43 ` Paul Eggert
2017-09-10 18:54 ` Charles A. Roelli
2017-09-10 21:46 ` Paul Eggert
2017-09-11 2:39 ` Eli Zaretskii [this message]
2017-09-11 14:22 ` Eli Zaretskii
2017-09-11 15:18 ` Eli Zaretskii
2017-09-11 18:44 ` Charles A. Roelli
2017-09-11 19:07 ` Eli Zaretskii
2017-09-16 9:48 ` Eli Zaretskii
2017-09-11 15:33 ` Glenn Morris
2017-09-11 16:38 ` Paul Eggert
2017-09-11 21:16 ` Glenn Morris
2017-09-12 19:59 ` Paul Eggert
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=83ingqt0v4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28350@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
/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.