From: Stephen Berman <stephen.berman@gmx.net>
To: uzibalqa <uzibalqa@proton.me>
Cc: uzibalqa via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Using button-label in pcase
Date: Tue, 25 Jul 2023 00:53:23 +0200 [thread overview]
Message-ID: <87cz0gx6os.fsf@gmx.net> (raw)
In-Reply-To: <tqktDrXgWeHSPVGi15HKA_rbABv2W49VCOTVUIi8rbY59dfWCnHuuwuGoQgvOY9p0JFnKCbRVCB3BiWc2_1gom90LPPVjVlG5ZA9klqFTb4=@proton.me> (uzibalqa@proton.me's message of "Mon, 24 Jul 2023 22:40:03 +0000")
On Mon, 24 Jul 2023 22:40:03 +0000 uzibalqa <uzibalqa@proton.me> wrote:
> ------- Original Message -------
> On Tuesday, July 25th, 2023 at 10:36 AM, Stephen Berman
> <stephen.berman@gmx.net> wrote:
>
>
>> On Mon, 24 Jul 2023 22:24:33 +0000 uzibalqa uzibalqa@proton.me wrote:
>>
>> > ------- Original Message -------
>> > On Tuesday, July 25th, 2023 at 9:51 AM, Stephen Berman
>> > stephen.berman@gmx.net wrote:
>> >
>> > > On Mon, 24 Jul 2023 21:35:44 +0000 uzibalqa uzibalqa@proton.me wrote:
>> > >
>> > > > ------- Original Message -------
>> > > > On Tuesday, July 25th, 2023 at 8:07 AM, Stephen Berman
>> > > > stephen.berman@gmx.net wrote:
>> > > >
>> > > > > On Mon, 24 Jul 2023 19:14:27 +0000 uzibalqa uzibalqa@proton.me wrote:
>> > > > >
>> > > > > > Want to print some text as a result of clicking a button. With the
>> > > > > > code below
>> > > > > > I end up with
>> > > > > >
>> > > > > > (wrong-type-argument integer-or-marker-p nil)
>> > > > > > buffer-substring-no-properties(nil nil)
>> > > > > > button-label(#<overlay in no buffer>)
>> > > > > > (let* ((val (button-label button))) (if (equal val '"[FA]") (let nil
>> > > > > > (insert qrh-c))))
>> > > > > > (closure ((button . #<overlay in no buffer>)) nil (let* ((val
>> > > > > > (button-label button))) (if (equal val '"[FA]") (let nil (insert
>> > > > > > qrh-c)))))()
>> > > > > > help--window-setup("Help" (closure ((button . #<overlay in no buffer>))
>> > > > > > nil (let* ((val (button-label button))) (if (equal val '"[FA]") (let nil
>> > > > > > (insert qrh-c))))))
>> > > > > > qrh-b(#<overlay in no buffer>)
>> > > > > > button-activate(#<overlay in no buffer> t)
>> > > > > > push-button(3 t)
>> > > > > >
>> > > > > > What is going on. Is there a fix?
>> > > > > >
>> > > > > > (defconst qrh-c "[FA] Some Text")
>> > > > > >
>> > > > > > (defun qrh-b (button)
>> > > > > > "Prints information about how to install emacs."
>> > > > > > (with-help-window (help-buffer)
>> > > > > > (pcase (button-label button)
>> > > > > > ("[FA]" (insert qrh-c))) ))
>> > > > > >
>> > > > > > (defun qrh-a ()
>> > > > > > "Prints information about how to install emacs."
>> > > > > > (interactive)
>> > > > > > (with-help-window (help-buffer)
>> > > > > > (insert-button "[FC]"
>> > > > > > 'action 'qrh-b 'follow-link t) ))
>> > > > >
>> > > > > The error is raised because qrh-b calls with-help-window with the Help
>> > > > > buffer current, but with-help-window erases the buffer, so when
>> > > > > `(button-label button)' is evaluated, there is no button and this
>> > > > > signals the error.
>> > > >
>> > > > That what was wrong then.
>> > >
>> > > That there was no button. When you execute your command qrh-a and then
>> > > in the resulting Help buffer press the button, it disappears.
>> > >
>> > > > > If you want to use the existing Help buffer, just remove the call to
>> > > > > with-help-window in qrh-b.
>> > > >
>> > > > > However, Help buffers are read-only, so
>> > > > > trying to insert text will raise another error. To avoid this, you can
>> > > > > let-bind buffer-read-only in qrh-b.
>> > > >
>> > > > I do not experience the problem you mention. What error are you referring to,
>> > > > and how can it be triggered ?
>> > >
>> > > Did you remove the call the with-help-window in qrh-b and correct the
>> > > match condtion (or change the string in qrh-a to match the one in
>> > > qrh-b)? If so, then when you press the button in the Help buffer, you
>> > > will get the error "Buffer is read-only: #<buffer Help>".
>> >
>> > > Steve Berman
>> >
>> > I did the changes and have the following
>> >
>> > (pcase (button-label button)
>> > ("[FA]"
>> > (with-help-window (help-buffer) ; Print in help buffer
>> > (insert qrh-c)))
>>
>>
>> Sure, that's a fine way to avoid the problem with the read-only state of
>> the Help buffer.
>>
>> Steve Berman
>
> I replicated the error you mentioned though. Why does it happen ? Is that because
> the insert would be within an (with-help-window (help-buffer) ?
I get no error using the last code snippet you provided, because the
button-label is evaluated before with-help-window erases the buffer, and
with-help-window makes the *Help* buffer temporarily writeable.
Steve Berman
next prev parent reply other threads:[~2023-07-24 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 19:14 Using button-label in pcase uzibalqa
2023-07-24 20:07 ` Stephen Berman
2023-07-24 21:35 ` uzibalqa
2023-07-24 21:51 ` Stephen Berman
2023-07-24 22:24 ` uzibalqa
2023-07-24 22:36 ` Stephen Berman
2023-07-24 22:40 ` uzibalqa
2023-07-24 22:53 ` Stephen Berman [this message]
2023-07-24 23:40 ` uzibalqa
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=87cz0gx6os.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=help-gnu-emacs@gnu.org \
--cc=uzibalqa@proton.me \
/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).