From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31790@debbugs.gnu.org
Subject: bug#31790: 27.0; Mention Isearch key bindings of Isedarch variables that are bound by default in Isearch
Date: Sat, 16 Jun 2018 15:57:21 -0700 (PDT) [thread overview]
Message-ID: <1a1d806c-4f7f-4af4-a9e2-b4b6f474e792@default> (raw)
In-Reply-To: <83in6izrow.fsf@gnu.org>
> And having that in a doc string of a non-user variable will make it
> easier to pick up?
Yes.
> > It just makes sense to point out, in the doc for these
> > two variables that, by default, `M-s SPC' toggles them
> > while searching.
>
> Like I said, I disagree.
>
> Maybe we should provide defcustoms that would initialize the values of
> these variables. Then it would make sense to tell what you want in
> those defcustoms' doc strings, like we do with search-invisible, for
> example.
That takes care of letting users set the default behavior,
yes.
It doesn't, however, tell them anything about being able
to hit a key while searching to toggle the current behavior.
If you add defcustoms and then mention in their doc strings
that the _current_ behavior can be toggled with `M-s SPC'
then that would take care of this bug report.
Users will naturally want to (1) set their preferred default
behavior or (2) toggle the current behavior, or both. The
point is to help them better to know how they can do these
things (which they can do already).
next prev parent reply other threads:[~2018-06-16 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<ef3d41cc-ef6d-4248-bfec-3fec23022762@default>
[not found] ` <<83vaajynvp.fsf@gnu.org>
2018-06-16 13:19 ` bug#31790: 27.0; Mention Isearch key bindings of Isedarch variables that are bound by default in Isearch Drew Adams
2018-06-16 15:17 ` Eli Zaretskii
2018-06-16 22:57 ` Drew Adams [this message]
2018-06-11 22:16 Drew Adams
2018-06-16 11:25 ` Eli Zaretskii
2021-09-02 7:57 ` 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
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=1a1d806c-4f7f-4af4-a9e2-b4b6f474e792@default \
--to=drew.adams@oracle.com \
--cc=31790@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 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).