GNU bug report logs - #34506
27.0.50: push-button bug with basic text-property button

Previous Next

Full log

Message #26 received at 34506 <at> debbugs.gnu.org (full text, mbox):

From: "Basil L. Contovounesios" <contovob <at> tcd.ie>
To: Robert Weiner <rsw <at> gnu.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, rswgnu <at> gmail.com, 34506 <at> debbugs.gnu.org
Subject: Re: bug#34506: 27.0.50: push-button bug with basic text-property
 button
Date: Mon, 18 Feb 2019 20:52:27 +0000

Robert Weiner <rsw <at> gnu.org> writes:

> Thanks Eli, that is much clearer.  I can work with that explanation.
>
> Your last paragraph indicates that the button API by itself could use
> some improvement.  How does one obtain a button to send to button-type
> if not button-at?

You can use button-at if you want to be agnostic of the button (not
widget) type.  If you're only dealing with text (not overlay) buttons,
you can avoid creating markers by passing a buffer position like (point)
directly to button-type.

If you are dealing with widgets, on the other hand, you should use
widget-at and widget-type in place of button-at and button-type,
respectively.  The widget and button APIs are mutually incompatible.

-- 
Basil

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.