From: Drew Adams <drew.adams@oracle.com>
To: npostavs@users.sourceforge.net
Cc: 24842@debbugs.gnu.org
Subject: bug#24842: 24.5; `help-make-xrefs': False link-type determinations
Date: Mon, 31 Oct 2016 21:35:14 -0700 (PDT) [thread overview]
Message-ID: <bd840000-09af-4b41-82bc-042688a66bc4@default> (raw)
In-Reply-To: <878tt4qdjq.fsf@users.sourceforge.net>
> What about ZERO WIDTH SPACE?
>
> `isearchp-movement-unit-alist'\t- units and their movement
> functions\u200B
> `isearchp-on-demand-action-function'\t- on-demand action
> function\u200B
> `isearchp-prompt-for-filter-name'\t- when to ask for filter
> name\u200B
Yes, I thought there was such a character, and it could be
used. That is a reasonable workaround, I guess, for a
programmer to override inappropriate behavior that can
occur now.
I should have separated #1 and #2 not as alternatives, but
as two approaches that should both, I think, be taken.
Do you think the code as written in help-mode.el is correct?
Do you not think that the cond clauses are just wrong?
Note that only a couple of the cond clauses have the weird
form of putting part of the test for type in the result,
and not in the test part.
The other clauses have, as one might expect, all of the
testing in the condition part, and only the `help-xref-button'
call in the result part.
(That doesn't prove that the same approach should be taken
for all of them. But it does suggest a possible miscoding.)
I think it would be good to take a close look at this.
And also to document the workaround, letting people know
of a _recommended_ way to override the default behavior.
next prev parent reply other threads:[~2016-11-01 4:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 23:00 bug#24842: 24.5; `help-make-xrefs': False link-type determinations Drew Adams
2016-10-31 23:55 ` npostavs
2016-11-01 4:35 ` Drew Adams [this message]
2016-11-01 15:20 ` Eli Zaretskii
2016-11-01 15:34 ` Noam Postavsky
2016-11-01 16:16 ` Eli Zaretskii
[not found] ` <<83wpgnns4x.fsf@gnu.org>
2016-11-01 16:15 ` Drew Adams
2016-11-01 16:25 ` Eli Zaretskii
[not found] ` <<CAM-tV-_+-Ewzh_vMpi65cc5ukD+T+WHNPGk0dooqQCaJAvmTaQ@mail.gmail.com>
[not found] ` <<83r36vnpjw.fsf@gnu.org>
2016-11-01 16:29 ` Drew Adams
2016-11-01 16:50 ` Eli Zaretskii
2017-02-05 19:27 ` Drew Adams
2018-01-01 21:20 ` Drew Adams
2021-09-07 18:00 ` bug#24842: bug#9445: 24.0.50; `help-make-xrefs' has bad logic Lars Ingebrigtsen
2021-09-07 19:24 ` bug#24842: [External] : " Drew Adams
2021-09-07 19:28 ` Lars Ingebrigtsen
2021-09-07 19:44 ` bug#9445: bug#24842: " Stephen Berman
2021-09-07 19:55 ` Lars Ingebrigtsen
2022-02-15 10:43 ` bug#24842: 24.5; `help-make-xrefs': False link-type determinations Lars Ingebrigtsen
2022-02-15 16:58 ` bug#24842: [External] : " Drew Adams
2022-02-15 19:12 ` Eli Zaretskii
2022-02-15 19:22 ` Drew Adams
2022-02-15 19:33 ` Eli Zaretskii
2021-09-07 20:13 ` bug#24842: [External] : Re: bug#24842: bug#9445: 24.0.50; `help-make-xrefs' has bad logic Drew Adams
[not found] <<919e40a4-f6c4-492d-b50f-b0671e13cb60@default>
[not found] ` <<878tt4qdjq.fsf@users.sourceforge.net>
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=bd840000-09af-4b41-82bc-042688a66bc4@default \
--to=drew.adams@oracle.com \
--cc=24842@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).