unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Madhu <enometh@meer.net>
Cc: 66192@debbugs.gnu.org
Subject: bug#66192: 30.0.50; lisp/buttons.el (push-button) fails to handle the <return> action on gui emacs
Date: Tue, 26 Sep 2023 08:50:28 +0800	[thread overview]
Message-ID: <87jzsdoizv.fsf@yahoo.com> (raw)
In-Reply-To: <20230925.204020.1677927434335496083.enometh@meer.net> (Madhu's message of "Mon, 25 Sep 2023 20:40:20 +0530 (IST)")

Madhu <enometh@meer.net> writes:

> * commit a496509cedb17109d0e6297a74e2ff8ed526333c
> |Commit:     Po Lu <luangruo@yahoo.com>
> |CommitDate: Thu Jan 19 22:19:06 2023 +0800
>
> Introduced a change to lisp/button.el:(push-button) which causes the
> following recipe to fail. Consider a buffer with the following
> contents:
>
> ```
> ;;text-button
>
> (defvar-keymap my-button-map :parent button-map "<return>" 'push-button)
> (setq $but (make-text-button 1 10
> 			     'action #'(lambda(b) (message "push-button %S" b))
> 			     'keymap my-button-map))
> ```
>
> evaluating the buffer sets up a text button in the first line. In a gui
> emacs Hitting RET on the button fails with an error:
> 	"push-button: Wrong type argument: listp, return".
>
> The following patch fixes it for me but maybe there is some other issue?
>
>>From e69be9cf0af72c5fcda8cda05b50a556741009b2 Mon Sep 17 00:00:00 2001
> From: Madhu <enometh@net.meer>
> Date: Mon, 25 Sep 2023 20:20:05 +0530
> Subject: [PATCH] lisp/button.el: (push-button): handle kbd <return>
>
> ---
>  lisp/button.el | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lisp/button.el b/lisp/button.el
> index b01595943fc..0e98ec722d9 100644
> --- a/lisp/button.el
> +++ b/lisp/button.el
> @@ -492,7 +492,7 @@ push-button
>  	    (if str-button
>  	        ;; mode-line, header-line, or display string event.
>  	        (button-activate str t)
> -              (if (eq (car pos) 'touchscreen-down)
> +              (if (and (listp pos) (eq (car pos) 'touchscreen-down))
>                    ;; If touch-screen-track tap returns nil, then the
>                    ;; tap was cancelled.
>                    (when (touch-screen-track-tap pos)

Thanks, but I elected to fix this differently.  Please test.





  reply	other threads:[~2023-09-26  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 15:10 bug#66192: 30.0.50; lisp/buttons.el (push-button) fails to handle the <return> action on gui emacs Madhu
2023-09-26  0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-26  0:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-26  1:35   ` Madhu
2023-09-26 11:38     ` Stefan Kangas

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=87jzsdoizv.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=66192@debbugs.gnu.org \
    --cc=enometh@meer.net \
    --cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).