unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: RE: move to fail position in Isearch edit
Date: Tue, 11 Nov 2008 12:16:57 -0800	[thread overview]
Message-ID: <004d01c9443a$72957840$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <87ljvqdv69.fsf@jurta.org>

> > Any interest in this? I bind it to `M-e' in 
> > `minibuffer-local-isearch-map', so
> > `M-e M-e' puts the cursor at the match failure position.
> >
> > If you type a search string quickly and mistype a char or 
> > two, this lets you correct the typo without discarding
> > and retyping the rest of the search string:
> > `M-e M-e <corrections> C-s'.
> 
> Isn't it more convenient to type a new key to immediately remove the
> failed part without entering the minibuffer for editing?  For example,
> after typing `M-e' (selecting a good key is a difficult issue) it will
> remove the failed part of the search string, go to the 
> previous successful matching point, and all this without activating
> the minibuffer.

Maybe we're miscommunicating. If you just want to remove the failed suffix,
simply use `C-g'. No need for any new feature to do that.

This is not about that. This is about keeping the failed suffix but letting you
do something at the place where failure starts: delete chars, insert chars. IOW,
it's about editing the search string, starting at the position where match
failure begins.





  reply	other threads:[~2008-11-11 20:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  6:42 move to fail position in Isearch edit Drew Adams
2008-11-11  7:13 ` Mathias Dahl
2008-11-11 15:07 ` Isearch: always try to find longest successful prefix [was: move to fail position in Isearch edit] Drew Adams
2008-11-11 17:32   ` Juri Linkov
2008-11-11 20:19     ` Drew Adams
2008-11-11 17:33 ` move to fail position in Isearch edit Juri Linkov
2008-11-11 20:16   ` Drew Adams [this message]
2008-11-11 20:33   ` Mathias Dahl
2008-11-11 21:02     ` Drew Adams
2008-11-11 21:36       ` Juri Linkov

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='004d01c9443a$72957840$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).