From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: isearch and region ?
Date: Tue, 7 Nov 2017 18:08:47 +0900 [thread overview]
Message-ID: <53A25592-F1EF-4216-A85A-63CDDBF41A4D@gmail.com> (raw)
In-Reply-To: <CAP_d_8Ux9d2OL=CUVr1JKeYOuGrdv8K0GL84wich+-763tvOUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
Thank you Yuri.
> On Nov 7, 2017, at 17:31, Yuri Khan <yuri.v.khan@gmail.com> wrote:
>
> 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.
But search is not incremental and does not return a region either. It just puts point at the end of the match. I guess that's useful when you are trying to create a region from the original point (where you'd put the mark) to the end of the matching string, but that's quite a limited use. Or is search designed only for navigation in the document? What's the point having a search that does not *find*?
Is there a search that returns the matching string as a region?
> * 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.
I see that there are lots of isearch-yank commands, but no isearch-kill...
On the help list, I was suggested to use C-backspace after an isearch since the point is at the end of the match, but that only deletes a "word" and not the full match.
By the way, what is the status of the beginning of the match as highlighted by isearch? It is not a mark, and it is not point...
> 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.
I understand that.
> On the other hand, some commands could work right out of isearch mode,
> if suitably implemented:
>
> * Deleting with Delete.
> * Cutting (killing) and copying.
Jean-Christophe Helary
-----------------------------------------------
@brandelune http://mac4translators.blogspot.com
[-- Attachment #2: Type: text/html, Size: 4148 bytes --]
next prev parent reply other threads:[~2017-11-07 9:08 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
2017-11-07 9:08 ` Jean-Christophe Helary [this message]
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=53A25592-F1EF-4216-A85A-63CDDBF41A4D@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=emacs-devel@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.
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.