From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 15682@debbugs.gnu.org, 52@debbugs.gnu.org
Subject: bug#15682: 24.3.50; `:link' in `defgroup' does not respect `mouse-1-click-follows-link'
Date: Wed, 27 Apr 2016 09:24:34 -0700 (PDT) [thread overview]
Message-ID: <89237c28-b7ed-4621-9baf-908fe99a6c9d@default> (raw)
In-Reply-To: <87inz3hw40.fsf@gnus.org>
> I've had another peek at this,
Thanks for looking into it.
> but the main problem is that I don't quite understand why the
> Widget code is so... complicated.
I sympathize, and I agree that is difficult to fathom.
Can't help with the understanding, however.
> Why does it do all the stuff below? I mean, no other modes
> that react to mouse clicks need to ... do all that...
Dunno. But just because the code can be difficult to follow
is not a reason to assume that it does unnecessary things, in
general. The widget code that I've been able to follow does
DTRT, generally (AFAICT).
I doubt that anyone left understands the widget code well.
Maybe you can find Per Abrahamsen and get him to take a look?
The URLs for him listed here are dead, but maybe looking here
would be a start: https://www.emacswiki.org/emacs/PerAbrahamsen.
next prev parent reply other threads:[~2016-04-27 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 15:28 bug#15682: 24.3.50; `:link' in `defgroup' does not respect `mouse-1-click-follows-link' Drew Adams
2016-04-27 16:09 ` bug#52: " Lars Ingebrigtsen
2016-04-27 16:24 ` Drew Adams [this message]
2016-04-27 16:53 ` Lars Ingebrigtsen
2016-04-27 17:18 ` Drew Adams
2019-08-23 20:41 ` Mauro Aranda
2019-08-25 5:47 ` Lars Ingebrigtsen
2019-08-25 15:07 ` Mauro Aranda
2019-08-25 16:19 ` Drew Adams
2019-08-25 16:22 ` Drew Adams
2019-08-25 16:41 ` Eli Zaretskii
2019-08-25 16:50 ` Noam Postavsky
2019-08-25 16:58 ` Mauro Aranda
2019-08-27 6:42 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89237c28-b7ed-4621-9baf-908fe99a6c9d@default \
--to=drew.adams@oracle.com \
--cc=15682@debbugs.gnu.org \
--cc=52@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.