From: Heime <heimeborgia@protonmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Stephen Berman <stephen.berman@gmx.net>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Buttons in help buffer that displays contents of variables
Date: Sun, 23 Jul 2023 20:05:41 +0000 [thread overview]
Message-ID: <ZKp2yPAsZNRRw5kb2DbN-ruZGAvMfY32BzEeRqW0-8d776FEOVCf5J2Tb0O9usYInCeV5tS9CPanKArNkhxrdxxIl0Xi6s0slkwm-ZmHVB4=@protonmail.com> (raw)
In-Reply-To: <CAP_d_8WQOLRjR3ywfAKa5ELY0i5=w95EDqiSCOeqqH_H9rDi8g@mail.gmail.com>
------- Original Message -------
On Monday, July 24th, 2023 at 7:57 AM, Yuri Khan <yuri.v.khan@gmail.com> wrote:
> On Mon, 24 Jul 2023 at 02:34, Heime heimeborgia@protonmail.com wrote:
>
> > Does the function associated with the button be restricted to a single argument,
> > meaning that users cannot pass any additional data to it ?
>
>
> Passing the button is sufficiently general. An action can reach into
> the button’s properties and/or use the button’s identity or one of its
> properties to look up in an external alist. And, of course, you can
> always create lexical closures over a multi-argument function,
> adapting it to the action interface.
Are the things you describe done often with buttons in emacs source code ?
prev parent reply other threads:[~2023-07-23 20:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 14:40 Buttons in help buffer that displays contents of variables Heime
2023-07-22 19:18 ` Heime
2023-07-22 20:14 ` Stephen Berman
2023-07-22 20:24 ` Heime
2023-07-22 20:48 ` Stephen Berman
2023-07-22 21:24 ` Heime
2023-07-22 21:46 ` Stephen Berman
2023-07-22 22:02 ` Heime
2023-07-22 22:13 ` Heime
2023-07-22 22:28 ` Stephen Berman
2023-07-22 22:42 ` Heime
2023-07-22 22:50 ` Stephen Berman
2023-07-22 23:13 ` Heime
2023-07-23 7:45 ` Yuri Khan
2023-07-23 19:34 ` Heime
2023-07-23 19:57 ` Yuri Khan
2023-07-23 20:05 ` Heime [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ZKp2yPAsZNRRw5kb2DbN-ruZGAvMfY32BzEeRqW0-8d776FEOVCf5J2Tb0O9usYInCeV5tS9CPanKArNkhxrdxxIl0Xi6s0slkwm-ZmHVB4=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=stephen.berman@gmx.net \
--cc=yuri.v.khan@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).