From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 34150@debbugs.gnu.org
Subject: bug#34150: 26.1; Document filtering with `isearch-filter-predicate' in Elisp manual
Date: Mon, 21 Jan 2019 10:40:36 -0800 (PST) [thread overview]
Message-ID: <208f2037-8fa0-4475-a9cf-b2417613af5c@default> (raw)
In-Reply-To: <<83h8e1amsu.fsf@gnu.org>>
> > But it and its consequences are not necessarily
> > obvious - especially to a user searching, as opposed
> > to a programmer writing a filter predicate.
>
> This is not a user-level facility, so the user perspective is not
> relevant.
The "user perspective" is always relevant for Emacs.
We are all users.
Searching is a user-level facility. If a search
imposes/provides filtering, that certainly affects
user-visible behavior. Users should understand
that behavior.
Anyone imposing such filtering on users should
consider its effects on users, including the
considerations raised by this bug report. That
starts with making the behavior and consequences
clear to filter implementors.
next parent reply other threads:[~2019-01-21 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<8c207ca2-39ae-4ec1-acbd-358165964319@default>
[not found] ` <<83o98a9e2l.fsf@gnu.org>
[not found] ` <<8c88ff94-e322-4754-b74a-c792512ec277@default>
[not found] ` <<83h8e1amsu.fsf@gnu.org>
2019-01-21 18:40 ` Drew Adams [this message]
2019-01-21 19:05 ` bug#34150: 26.1; Document filtering with `isearch-filter-predicate' in Elisp manual Eli Zaretskii
[not found] <<<8c207ca2-39ae-4ec1-acbd-358165964319@default>
[not found] ` <<<83o98a9e2l.fsf@gnu.org>
[not found] ` <<<8c88ff94-e322-4754-b74a-c792512ec277@default>
[not found] ` <<<83h8e1amsu.fsf@gnu.org>
[not found] ` <<208f2037-8fa0-4475-a9cf-b2417613af5c@default>
[not found] ` <<83ef95al1s.fsf@gnu.org>
2019-01-21 23:10 ` Drew Adams
2019-01-21 0:17 Drew Adams
2019-01-21 16:21 ` Eli Zaretskii
2019-01-21 18:18 ` Drew Adams
2019-01-21 18:27 ` Eli Zaretskii
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=208f2037-8fa0-4475-a9cf-b2417613af5c@default \
--to=drew.adams@oracle.com \
--cc=34150@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.