From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Lars Ingebrigtsen <larsi@gnus.org>, ndame <emacsuser@freemail.hu>,
36826@debbugs.gnu.org
Subject: bug#36826: 26.1; request: add variable value editing feature to the *Help* buffer
Date: Mon, 29 Jul 2019 21:15:18 +0300 [thread overview]
Message-ID: <87a7cxf8sh.fsf@mail.linkov.net> (raw)
In-Reply-To: <717c1376-ac78-4ff8-84a2-5c9a64ba16f3@default> (Drew Adams's message of "Sun, 28 Jul 2019 21:35:32 -0700 (PDT)")
> I mentioned `set-variable'. But it is only for user options.
I use such advice to workaround this restriction:
;; Allow set-variable to set all variables, not only customizable ones:
(advice-add 'set-variable :around
(lambda (orig-fun &rest args)
(interactive (lambda (spec)
(cl-letf (((symbol-function 'custom-variable-p)
(lambda (v)
(and (symbolp v) (boundp v)))))
(advice-eval-interactive-spec spec))))
(cl-flet ((custom-variable-p (v) t))
(apply orig-fun args)))
'((name . override-custom-variable)))
But I agree with Michael this should be allowed only to developers.
next prev parent reply other threads:[~2019-07-29 18:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 6:08 bug#36826: 26.1; request: add variable value editing feature to the *Help* buffer ndame
2019-07-28 16:51 ` Drew Adams
2019-07-28 17:53 ` ndame
2019-07-28 18:01 ` Lars Ingebrigtsen
2019-07-29 4:00 ` Basil L. Contovounesios
2019-07-29 4:35 ` Drew Adams
2019-07-29 18:15 ` Juri Linkov [this message]
2019-07-29 13:55 ` Lars Ingebrigtsen
2019-07-29 14:18 ` Drew Adams
2019-07-29 4:28 ` Michael Heerdegen
2019-07-29 4:38 ` ndame
2019-07-29 14:22 ` Eli Zaretskii
2019-07-30 0:59 ` Michael Heerdegen
2019-07-30 2:43 ` Drew Adams
2019-07-30 4:02 ` Michael Heerdegen
2019-07-30 18:53 ` Drew Adams
2019-07-30 21:32 ` Michael Heerdegen
2019-07-29 4:46 ` Drew Adams
2022-04-17 17:00 ` 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=87a7cxf8sh.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=36826@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=drew.adams@oracle.com \
--cc=emacsuser@freemail.hu \
--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.