From: Nicolas Petton <nicolas@petton.fr>
To: John Wiegley <johnw@newartisans.com>,
Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Exposing Isearch toggleable options
Date: Thu, 29 Oct 2015 10:29:21 +0100 [thread overview]
Message-ID: <87y4emf2fi.fsf@petton.fr> (raw)
In-Reply-To: <m28u6mqkyw.fsf@newartisans.com>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
John Wiegley <johnw@newartisans.com> writes:
>>>>>> Artur Malabarba <bruce.connor.am@gmail.com> writes:
>
>> Basically, as soon as isearch starts, you should see something like this.
>> Toggles [M-s]: [w] Word OFF [_] Symbol OFF ['] Character-Fold ON [r] Regexp
>> OFF I-search: search string here
>
> Artur, does this mean the I-search prompt would be two-lines high in the
> minibuffer, instead of one-line? If so, I would definitely want a way to
> disable it; if I already know the options, it shortens the text window for
> documentation I wouldn't need.
>
> For new users, I'm not sure whether it should be on by default or not. It's
> handy, for sure, but distracting maybe? I can't say without that mindset. I'd
> love to hear from some users to see what they think.
Hi,
Magit displays all options for each Git action in a separate window,
which I still find useful, even now that I know most of them. The same
goes for org-mode export, it is very handy. I think this kind of
usability improvements are worth it, even if they take a significant
amount of screen space.
However, I'm afraid that with your changes Artur new users might think
that these visible options are the only ones isearch supports. I know I
wouldn't look for more options than the one displayed when doing a Git
operation with Magit.
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2015-10-29 9:29 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
2015-10-29 21:42 ` Artur Malabarba
2015-10-29 5:53 ` John Wiegley
2015-10-29 9:29 ` Nicolas Petton [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4emf2fi.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@newartisans.com \
/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.