Re: Exposing Isearch toggleable options

[Kaushal Modi]

The hydra option looks good. A user can even customize that hydra if they want to. But as Marcin said, do we then need to bundle hydra with emacs.

In addition to that option, it would be nice to always show the toggle starts in the mode-line. The hydra can also show the current states of all the toggles. But it would be useful to show "a representation of the toggle states" in the mode-line so that the user does not need to launch the hydra just to see the states.

By "representation", I recall what Drew had mentioned in one of the earlier threads discussing this:

If modeline shows: "AbCd", the search will be case sensitive, without char folding.

If modeline shows: "abcd", the search will be case insensitive, without char folding.

If modeline shows: "âbcd", the search will be case insensitive, with char folding.

And so on...

But then "abcd" example might not fit the bill for all toggles.

Instead, should we have 2-letter acronyms for all toggles in the modeline and change their face based on the toggle state?

Let's say, these are the acronyms:

Cs - Case sensitive
RE - Regular expressions
ČF - Char folding
LW - Lax Whitespace
... And so on.

This list of 2-char acronyms can again be made user customizable. But the association of acronyms to the toggle var should be kept fixed to prevent confusion and unneeded complication.

Those acronyms will be displayed with sort of a dimmed out, gray face when the respective toggle is disabled. But the face will be changed to something like bold green when enabled. It goes without saying that the faces would be customizable.

What do you guys think?