[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Isearch interaction model

From: Daniel Colascione
Subject: Re: Isearch interaction model
Date: Sat, 10 Mar 2018 13:36:41 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

On 03/10/2018 01:20 PM, Juri Linkov wrote:
But people _do_ switch from regex to literal mode and back. That's why M-r
is a convenient isearch binding for doing exactly that, and on prevision
occasions when this topic has come up for discussion, others have indicated
that they use this M-r binding.

I can't imagine the usefulness of switching from regex to literal mode
when the search string contains a complex regexp.

But it you want to share string and regexp histories, it's easy to implement
by another layer of indirection like for query-replace history variables:

(defcustom query-replace-from-history-variable 'query-replace-history
(defcustom query-replace-to-history-variable 'query-replace-history

Sure. It's possible to make this behavior customizable.

But then perhaps search-ring-yank-pointer and regexp-search-ring-yank-pointer
need similar indirection, or code could be smart enough to detect such
indirection and compute the right pointer depending on where such variables
point to.

I really think you're over-thinking this problem. Let's just try a unified history and see whether it causes problems in practice. I suspect it'll feel perfectly natural, and we won't need complex indirection layers.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]