all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: isearch and region ?
Date: Tue, 7 Nov 2017 15:31:34 +0700	[thread overview]
Message-ID: <CAP_d_8Ux9d2OL=CUVr1JKeYOuGrdv8K0GL84wich+-763tvOUA@mail.gmail.com> (raw)
In-Reply-To: <DC555F77-DDAD-42E0-B2E3-0964D9548C88@gmail.com>

On Tue, Nov 7, 2017 at 2:39 PM, Jean-Christophe Helary
<jean.christophe.helary@gmail.com> wrote:
> I would like to know why isearch has been designed so that it does not create a region with the matching string. The thing that appears in the buffer looks like a region, but it is not, and that keeps the user from immediately interacting with the matching string (deleting, overwriting, killing or yanking, etc.)

isearch is incremental, so most of the region-affecting actions would
conflict with it.

* Deleting with Backspace deletes the last character of the pattern
(conflicts with deleting the region).
* Typing text adds to the pattern (conflicts with overwriting the region).
* Pasting (yanking) adds to the pattern, too.

You would need an isearch command that (1) marks the current
occurrence as a region, and (2) exits isearch mode so you can affect
the region with your next command.

On the other hand, some commands could work right out of isearch mode,
if suitably implemented:

* Deleting with Delete.
* Cutting (killing) and copying.



  reply	other threads:[~2017-11-07  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  7:39 isearch and region ? Jean-Christophe Helary
2017-11-07  8:31 ` Yuri Khan [this message]
2017-11-07  9:08   ` Jean-Christophe Helary
2017-11-07 15:26     ` Drew Adams
2017-11-07 15:54       ` Jean-Christophe Helary
2017-11-07  9:13 ` Damien Wyart

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP_d_8Ux9d2OL=CUVr1JKeYOuGrdv8K0GL84wich+-763tvOUA@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.