From: Drew Adams <drew.adams@oracle.com>
To: bruce.connor.am@gmail.com
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: RE: Exposing Isearch toggleable options
Date: Thu, 29 Oct 2015 07:02:00 -0700 (PDT) [thread overview]
Message-ID: <c9bb058c-607d-47fb-a190-2994cdc7cb23@default> (raw)
In-Reply-To: <CAAdUY-Kb7bc=RSuRvNqyjZHu+4D8+bZVM6eLiRkJaPuyvL4c4Q@mail.gmail.com>
> I agree with you partially. The information of which options are
> active or relevant is a state info. Bit the info of which key
> toggles them is of general use (and I'd like to expose it to users
> who don't read the manual).
I didn't propose that they be limited to getting such info from the
manual. What I suggested is that they get it (and other info about
Isearch) from `C-h' during Isearch.
next prev parent reply other threads:[~2015-10-29 14:02 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 0:20 Exposing Isearch toggleable options Artur Malabarba
2015-10-29 0:27 ` Juri Linkov
2015-10-29 0:38 ` Artur Malabarba
2015-10-29 23:58 ` Juri Linkov
2015-10-30 3:00 ` Random832
2015-10-30 9:48 ` Oleh Krehel
2015-10-30 9:56 ` Artur Malabarba
2015-10-30 10:42 ` Artur Malabarba
2015-10-30 11:03 ` Marcin Borkowski
2015-10-30 11:56 ` Artur Malabarba
2015-10-30 15:17 ` Marcin Borkowski
2015-10-30 12:01 ` Kaushal Modi
2015-10-30 12:21 ` Oleh Krehel
2015-10-30 14:07 ` Random832
2015-10-30 14:52 ` Kaushal Modi
2015-10-30 14:29 ` Oleh Krehel
2015-10-31 0:27 ` Juri Linkov
2015-11-01 12:42 ` Artur Malabarba
2015-11-01 16:01 ` Drew Adams
2015-11-01 19:34 ` Artur Malabarba
2015-11-02 0:20 ` Drew Adams
2015-11-02 20:19 ` John Wiegley
2015-11-04 11:51 ` Artur Malabarba
2015-11-04 15:39 ` John Wiegley
2015-11-05 0:24 ` Juri Linkov
2015-11-05 0:55 ` Artur Malabarba
2015-11-05 0:59 ` Dmitry Gutov
2015-11-05 22:44 ` Richard Stallman
2015-11-05 22:44 ` Richard Stallman
2015-11-05 23:28 ` Alan Mackenzie
2015-11-06 21:40 ` Richard Stallman
2015-11-06 2:15 ` John Wiegley
2015-11-06 13:48 ` Stephen Leake
2015-11-06 13:56 ` Gian Uberto Lauri
2015-11-06 15:27 ` Ashton Kemerling
2015-11-06 15:44 ` John Wiegley
2015-11-07 1:32 ` Xue Fuqiao
2015-11-06 15:54 ` Dmitry Gutov
2015-11-06 16:04 ` Artur Malabarba
2015-10-29 1:19 ` Drew Adams
2015-10-29 10:10 ` Artur Malabarba
2015-10-29 14:02 ` Drew Adams [this message]
2015-10-29 21:42 ` Artur Malabarba
2015-10-29 5:53 ` John Wiegley
2015-10-29 9:29 ` Nicolas Petton
2015-10-29 10:34 ` Artur Malabarba
2015-10-29 10:50 ` Nicolas Petton
2015-10-29 11:18 ` Kaushal Modi
2015-10-29 17:53 ` John Wiegley
2015-10-29 10:30 ` Artur Malabarba
2015-10-29 10:49 ` Oleh Krehel
2015-10-29 20:52 ` Rasmus
2015-10-29 21:27 ` Drew Adams
2015-10-29 16:18 ` Eli Zaretskii
[not found] ` <<8337wt3axe.fsf@gnu.org>
2015-10-29 17:19 ` Drew Adams
2015-10-29 18:33 ` Aldric Giacomoni
2015-10-29 18:54 ` John Wiegley
2015-10-29 19:14 ` Óscar Fuentes
2015-10-29 21:27 ` 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
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=c9bb058c-607d-47fb-a190-2994cdc7cb23@default \
--to=drew.adams@oracle.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@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).