unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 19:34:05 +0000	[thread overview]
Message-ID: <IU8glhLxjCXAwI5ZRmWFzn7mVDHvmGMkbOAc2yCluUNchI9TuKAe1BJjNkEqEq31b6BykwOUxFL-VZsszWCVYCjjlDqlz0dVb34pjeHh1G8=@protonmail.com> (raw)
In-Reply-To: <CAP_d_8UBgS6DRcCN4CrRsJqSo1adkcfLksbkHV0nkfgJAxzoXw@mail.gmail.com>

----- Original Message -------
On Sunday, July 23rd, 2023 at 7:45 PM, Yuri Khan <yuri.v.khan@gmail.com> wrote:


> On Sun, 23 Jul 2023 at 06:14, Heime heimeborgia@protonmail.com wrote:
> 
> > What does the button.el use as object to push to the action associated function
> > that would be sensible. Would it be "action" ?

Does the function associated with the button be restricted to a single argument,
meaning that users cannot pass any additional data to it ?
 
> The documentation quoted upthread states the argument is named BUTTON.
> It is easy to conclude that the action function, when called, will
> receive as its argument a reference to the button object that was
> clicked.
> 
> This pattern is widespread in GUI frameworks. It lets you create a
> bunch of slightly different buttons and assign them all the same
> single action, and it will be able to do slightly different things for
> each button.





  reply	other threads:[~2023-07-23 19:34 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 [this message]
2023-07-23 19:57                             ` Yuri Khan
2023-07-23 20:05                               ` Heime

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='IU8glhLxjCXAwI5ZRmWFzn7mVDHvmGMkbOAc2yCluUNchI9TuKAe1BJjNkEqEq31b6BykwOUxFL-VZsszWCVYCjjlDqlz0dVb34pjeHh1G8=@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).