all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: bruce.connor.am@gmail.com, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, kaushal.modi@gmail.com,
	stephen@xemacs.org, juri@linkov.net
Subject: Re: Displaying the state of isearch toggles [was Re: ASCII-folded search]
Date: Tue, 30 Jun 2015 18:03:34 +0300	[thread overview]
Message-ID: <837fql44s9.fsf@gnu.org> (raw)
In-Reply-To: <d9b5bdf0-9a8f-48b8-b24f-1b7ead67220f@default>

> Date: Mon, 29 Jun 2015 15:26:53 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, bruce.connor.am@gmail.com,
>         kaushal.modi@gmail.com, stephen@xemacs.org, emacs-devel@gnu.org,
>         monnier@iro.umontreal.ca
> 
> I have nothing against *also* offering a dialog-box interface, but
> that should not be the main approach or the goal.

Why not?  Is this some kind of principle, or are there specific
arguments related to this specific feature?

> 1. On demand info (e.g., pop up a help window when you hit a key -
>    either one window with all the info or separate help echoes for
>    different keys).
> 
>    Currently, for example, you can hit `M-c` to see the echo message
>    telling you the (new) state wrt case sensitivity.  So `M-c M-c`
>    is a no-op that tells you the current state.  That's a rudimentary
>    way to see the case-sensitivity state, but it works, and is quick.

IMO, showing this in echo area doesn't scale: it could work for a few
options, but not when there are a dozen of them.

A help window is free from this limitation, but it's not different
from the dialog-type UI that you rejected, so I'm not sure what I'm
missing here.

> 2. Persistent feedback showing the current state.  This is possible
>    for at least some of the more important state qualities.  I gave
>    some examples using the mode-line lighter.

Again, I don't see how this will scale to a situation where we have a
dozen optional modifiers.  Will we show one letter for each, and hope
the user will remember what each one of them means?  There simply
isn't enough space on the mode line for that.

> 3. Toggling of individual state attributes.  One suggestion is to
>    use the lighter (minor mode) menu for this.

IMO, a menu is inappropriate for turning on or off several independent
option.

> In sum, I'd suggest that we stick close to the traditional Emacs
> design: provide keyboard toggle keys, pop up info windows, etc.

The creeping featurism in isearch way exceeds any other feature I know
of; perhaps it's high time we admit that it no longer fits within
"traditional Emacs design", and some new ideas are required.



  reply	other threads:[~2015-06-30 15:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<CAAdUY-K3x4i+7wFvbEstvKVKuSZyM-DL4wB+Pe7ZbsHcVYXOfw@mail.gmail.com>
     [not found] ` <<831tgv7vbr.fsf@gnu.org>
2015-06-28 17:02   ` Displaying the state of isearch toggles [was Re: ASCII-folded search] Drew Adams
2015-06-28 17:29     ` Drew Adams
2015-06-29 22:03     ` Juri Linkov
2015-06-29 22:26       ` Drew Adams
2015-06-30 15:03         ` Eli Zaretskii [this message]
2015-06-30  2:43       ` Eli Zaretskii
2015-06-30  7:53         ` Oleh Krehel
     [not found]   ` <<ddcd0bf6-a60e-406b-a79d-088c13c2ac61@default>
     [not found]     ` <<87h9pq18ae.fsf@mail.linkov.net>
     [not found]       ` <<83a8vh5316.fsf@gnu.org>
2015-06-30  4:39         ` Drew Adams
2015-06-30  6:25           ` Artur Malabarba
2015-06-30 14:04             ` Drew Adams
2015-06-30 14:41               ` Artur Malabarba
2015-06-30 15:06           ` Eli Zaretskii
     [not found]         ` <<9da72b40-0236-4edd-983e-90c54ca7f827@default>
     [not found]           ` <<83616544o3.fsf@gnu.org>
2015-06-30 17:17             ` Drew Adams
     [not found]       ` <<d9b5bdf0-9a8f-48b8-b24f-1b7ead67220f@default>
     [not found]         ` <<837fql44s9.fsf@gnu.org>
2015-06-30 17:14           ` Drew Adams
2015-06-30 17:22             ` Eli Zaretskii
2015-06-28 10:47 Artur Malabarba
2015-06-28 14:37 ` Eli Zaretskii
2015-06-28 15:08   ` Kaushal

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=837fql44s9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bruce.connor.am@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=kaushal.modi@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stephen@xemacs.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.