From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20398@debbugs.gnu.org
Subject: bug#20398: 25.0.50; Clicking `window-divider-last-pixel' in help for `window-divider'
Date: Wed, 22 Apr 2015 18:50:13 -0400 [thread overview]
Message-ID: <g7egnbhj6i.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <838udk4fx7.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 Apr 2015 13:26:44 +0300")
Eli Zaretskii wrote:
>> M-x customize-face RET window-divider RET
>>
>> and mouse-clicking 'window-divider-first-pixel' in the doc-string.
>
> That doesn't cause an error, just a message that it's not a variable.
widget-documentation-link-action is surprisingly simplistic.
It doesn't even know that faces exist.
It should do what `help-make-xrefs' does, and use the presence of "face"
etc in the doc string as a cue. Ideally it would reuse the same code.
next prev parent reply other threads:[~2015-04-22 22:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 20:02 bug#20398: 25.0.50; Clicking `window-divider-last-pixel' in help for `window-divider' Drew Adams
2015-04-22 8:08 ` Eli Zaretskii
2015-04-22 9:34 ` martin rudalics
2015-04-22 10:26 ` Eli Zaretskii
2015-04-22 22:50 ` Glenn Morris [this message]
2015-04-23 7:50 ` martin rudalics
2015-04-23 10:37 ` Eli Zaretskii
2015-05-02 8:57 ` martin rudalics
2015-05-02 9:09 ` Eli Zaretskii
2015-05-03 5:42 ` Stefan Monnier
2015-05-03 15:04 ` martin rudalics
2015-05-04 1:56 ` Stefan Monnier
2016-04-30 18:28 ` Lars Ingebrigtsen
2016-04-30 18:51 ` Stefan Monnier
2016-04-30 19:27 ` Stefan Monnier
2016-05-01 8:23 ` martin rudalics
2016-05-01 13:15 ` Stefan Monnier
2016-05-02 8:00 ` martin rudalics
2016-05-02 17:13 ` Lars Ingebrigtsen
2016-05-03 6:44 ` martin rudalics
2016-05-03 16:42 ` Stefan Monnier
2016-05-01 8:23 ` martin rudalics
[not found] <<05342534-126d-44f4-b415-3159c44740f1@default>
[not found] ` <<83bnig4mav.fsf@gnu.org>
[not found] ` <<55376B18.5090103@gmx.at>
[not found] ` <<838udk4fx7.fsf@gnu.org>
2015-04-22 13:42 ` Drew Adams
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=g7egnbhj6i.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=20398@debbugs.gnu.org \
--cc=eliz@gnu.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.