From: Drew Adams <drew.adams@oracle.com>
To: Mauro Aranda <maurooaranda@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>
Cc: Oleh Krehel <ohwoeowho@gmail.com>, 20664@debbugs.gnu.org
Subject: bug#20664: 25.0.50; Customize: Link option or face name to the source definition
Date: Thu, 17 Sep 2020 20:30:59 +0000 (UTC) [thread overview]
Message-ID: <d8ea5a34-01dc-46c5-9783-8b8cb3f0295d@default> (raw)
In-Reply-To: <CABczVwf0RpHfSk1Dq1OW2iqFmCi848SBq2QwcktuC3cQFJCnwA@mail.gmail.com>
>> Makes sense to me. I tweaked it a bit before applying, though -- used
>> insert-text-button for convenience.
>
> Why a button.el button, and not a link widget? Using a
> button.el button makes it look like TAB is inconsistent,
> because it skips the button, so you can't get to the
> button by just pressing TAB.
>
> And given there are links to which you can get to by
> pressing TAB, not being able to reach this one makes
> it feel like something is wrong.
[Caveat: I haven't tried the updated code.]
Yes, it's important that the fix fit well with Customize,
both from a UI/user point of view and from a coding
point of view.
Please also do make sure that `mouse-1-click-follows-link'
is effective, i.e., that it has its expected effect when
either nil or non-nil. (I have it set to nil, BTW.)
next prev parent reply other threads:[~2020-09-17 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 20:41 bug#20664: 25.0.50; Customize: Link option or face name to the source definition Drew Adams
2015-05-27 13:19 ` Oleh Krehel
2015-05-27 14:09 ` martin rudalics
2015-05-27 14:28 ` Oleh Krehel
2015-05-27 14:59 ` Drew Adams
2015-05-27 15:16 ` Oleh Krehel
2015-05-27 15:28 ` Drew Adams
2015-05-27 14:15 ` Drew Adams
2015-05-27 14:30 ` Oleh Krehel
2020-09-17 18:46 ` Lars Ingebrigtsen
2020-09-17 20:16 ` Mauro Aranda
2020-09-17 20:30 ` Drew Adams [this message]
2020-09-18 11:28 ` Lars Ingebrigtsen
2020-09-18 11:39 ` Mauro Aranda
2020-09-17 21:41 ` Mauro Aranda
2020-09-17 21:46 ` 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=d8ea5a34-01dc-46c5-9783-8b8cb3f0295d@default \
--to=drew.adams@oracle.com \
--cc=20664@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=maurooaranda@gmail.com \
--cc=ohwoeowho@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.
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.