From: Dmitry Gusev <dmitry.p.gusev@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Incremental search don't append wrongly typed characters
Date: Thu, 13 Dec 2012 01:55:58 +0300 [thread overview]
Message-ID: <CAArzU-r37A1L7Lc4zABs5Bc32QQjdDYZJckNGeWFerzW4czJJA@mail.gmail.com> (raw)
In-Reply-To: <2EABD5DB8D2642EA824C1AA2972F25BF@us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
Drew, thanks for the answer. Unfortunately I need a different behavior in
my particular case. I was proposed with similar work-around also on stack
overflow. Though, I'm often using incremental search for query specific
tags in a large text file which is used like database system with help of
some configuration and scripts. Before each incremental search there is a
macro which places me to BOF and afterwards starts incremental search. For
this scheme it would be very convenient just not to append mismatched part
at all. I understand that it's not that standard feature and I use
different approach when let's say coding or typing text but again for this
particular case I need the mentioned behavior. It will save me some
additional clicks to backspace and/or c-s c-g. In other words: I'm
looking for a way of not showing mismatched characters during incremental
search. Thanks a lot for your time.
On Thu, Dec 13, 2012 at 2:14 AM, Drew Adams <drew.adams@oracle.com> wrote:
> > How can I [get] this behaviour:
> > Start incremental search and search for "keyz"
> > "key" is displayed in the search echo area and the "key"
> > part in "keywords" is higlighted
> > Press s
> > "keys" is found and highlited
>
> I don't have an answer for you, but the suggestion is an interesting one.
>
> A variant that could be useful (which I also don't have a recipe for):
>
> Type `keyz'.
> The `z' is highlighted as a mismatch (this is already available).
> Hit a key to delete the mismatched part (in this case, just `z'.
> Type `s' and continue.
>
> When I introduced highlighting of the mismatch part, I took it from Icicles
> highlighting of completion input mismatch. There, you can hit `C-l' twice
> to
> remove the mismatched part. (The first `C-l' just moves the cursor to the
> mismatch beginning, so you can insert there.)
>
> In Isearch there is no equivalent - no key that removes the mismatched
> part.
> Maybe I'll add that possibility. What you can do is hit `M-e', which puts
> you
> in editing mode and moves the cursor to the mismatch beginning. Then hit
> `C-k'
> to kill the mismatch portion, then `C-s' to resume searching. So `M-e C-k
> C-s'.
>
>
[-- Attachment #2: Type: text/html, Size: 2636 bytes --]
next prev parent reply other threads:[~2012-12-12 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 22:00 Incremental search don't append wrongly typed characters dmgus
2012-12-12 22:14 ` Drew Adams
2012-12-12 22:55 ` Dmitry Gusev [this message]
2012-12-12 23:07 ` Drew Adams
2012-12-12 23:54 ` Drew Adams
2012-12-13 2:53 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAArzU-r37A1L7Lc4zABs5Bc32QQjdDYZJckNGeWFerzW4czJJA@mail.gmail.com \
--to=dmitry.p.gusev@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).