Re: ASCII-folded search [was: Re: Upcoming loss of usability ...]

[Kaushal <kaushal.modi@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]

@Juri
I read that that bug report is more than 2 years old. Did you recently
submit a patch? Or were you referring to a patch from Drew in that bug
report?

@ Artur
Using the modeline is a very neat idea!

There is one package (anzu) I know of that makes partial use of the mode
line to display the search pattern counts.

We will need a solution that doesn't break these other packages. Or should
the info be simply added to `minor-mode-alist` with "button click
properties"? (I forgot the exact property name).

abo-abo creates a pseudo minibuffer on top of the actual minibuffer to
display the hints in his hydra.el package. That could also work here?

My earlier suggestion was simply based in the current code. I saw that a
`sleep-for` was used to flash the isearch setting change momentarily. I
wondered if we just keep that isearch setting change display static and
then remove that at the next search character input by the user.

Let's say that the user is search for "abc" and he has already typed "ab".

> Isearch: ab|

Now the user decides to toggle one of the isearch toggles, let's say
case-fold toggle and hits `M-c`. Then the minibuffer can display this

> Isearch: ab| [case-sensitive]

That should stay like that till the user continues typing

> Isearch: abc|

But, showing the isearch settings persistently in a separate area is a
better idea.

On Jun 26, 2015 5:32 AM, "Artur Malabarba" <bruce.connor.am@gmail.com>
wrote:

>
> > - If we don't want to flash that message, the message can be displayed
>> and
>> > be allowed to stay there till user starts/resumes typing in the
>> minibuffer.
>> >
>> > Thoughts?
>>
>> This will be fixed by bug#12988.  I'll send the latest patch there.
>>
>
> I don't know how you're planning on solving doing this,  but I was going
> to suggest that isearch could just take over the mode-line while in effect,
> that would it give it a lot of space to verbosely display the searching
> options (and maybe even list the key binds for each) and each option could
> be a button that toggles itself.
>

[-- Attachment #2: Type: text/html, Size: 2818 bytes --]