From: Karl Fogel <kfogel@red-bean.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: PATCH: isearch-yank-until-char
Date: Fri, 16 Aug 2019 00:11:50 -0500 [thread overview]
Message-ID: <87pnl5pucp.fsf@red-bean.com> (raw)
In-Reply-To: <jwvsgq34c7g.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 14 Aug 2019 18:26:23 -0400")
On 14 Aug 2019, Stefan Monnier wrote:
>> This patch implements 'isearch-yank-until-char', a new yank command in isearch.
>
>I like the idea, but would welcome even more warmly an isearch which
>yanks "whatever text is skipped by the next command" so it can be used
>to yank the next word, sexp, char, ...
I think Juri's point that for the generalized case one should just set `isearch-yank-on-move' to `t' may be the right answer.
After all, the command most commonly used to skip over some text is isearch itself :-). Aside from that and the sexp motion commands, the things one would normally use to skip over a predictable amount of text are already represented in isearch-mode. For example, the equivalent of M-f in normal mode is C-w in isearch-mode (`isearch-yank-word-or-char'). and the equivalent of C-e in normal mode is M-s C-e (`isearch-yank-line') in isearch-mode. It's hard for me to think of further generalizations that aren't already adequately handled by setting `isearch-yank-on-move' to t.
In practice, I find that when I use `isearch-yank-until-char', it's in a macro in a programming mode or markup language mode, and the relevant syntax delimiter is some single character. This is such a common case that IMHO it's worth supporting directly in isearch. But Juri's idea of defining a new function `skip-to-char' and relying on `isearch-yank-on-move' is also interesting (and not mutually exclusive, of course).
Best regards,
-Karl
next prev parent reply other threads:[~2019-08-16 5:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 3:05 PATCH: isearch-yank-until-char Karl Fogel
2019-08-14 14:20 ` Eli Zaretskii
2019-08-14 16:41 ` Karl Fogel
2019-08-14 16:48 ` Drew Adams
2019-08-14 17:20 ` Eli Zaretskii
2019-08-14 17:22 ` Karl Fogel
2019-08-14 17:51 ` Eli Zaretskii
2019-08-14 17:59 ` Noam Postavsky
2019-08-14 20:39 ` Juri Linkov
2019-08-14 20:34 ` Juri Linkov
2019-08-16 4:53 ` Karl Fogel
2019-08-16 17:52 ` Juri Linkov
2019-08-25 2:14 ` Karl Fogel
2019-08-25 3:22 ` Drew Adams
2019-08-25 20:03 ` Juri Linkov
2019-08-26 1:14 ` Drew Adams
2019-08-26 5:20 ` Karl Fogel
2019-08-26 14:50 ` Drew Adams
2019-08-26 17:51 ` Karl Fogel
2019-08-26 19:36 ` Drew Adams
2019-08-26 21:29 ` Karl Fogel
2019-08-26 21:57 ` Drew Adams
2019-08-26 22:21 ` Karl Fogel
2019-08-26 22:43 ` Drew Adams
2019-09-04 16:47 ` Karl Fogel
2019-09-04 17:00 ` Eli Zaretskii
2019-09-12 17:44 ` Karl Fogel
2019-09-16 21:24 ` Drew Adams
2019-09-17 16:02 ` Karl Fogel
2019-08-26 21:46 ` Juri Linkov
2019-08-26 21:52 ` Karl Fogel
2019-08-26 22:03 ` Drew Adams
2019-08-26 22:19 ` Juri Linkov
2019-08-26 22:33 ` Karl Fogel
2019-08-26 22:40 ` Drew Adams
2019-08-27 21:31 ` Juri Linkov
2019-08-27 22:52 ` Drew Adams
2019-08-27 23:15 ` Drew Adams
2019-08-25 19:58 ` Juri Linkov
2019-08-14 22:26 ` Stefan Monnier
2019-08-15 18:24 ` Juri Linkov
2019-08-17 12:31 ` Stefan Monnier
2019-08-17 22:51 ` Juri Linkov
2019-08-16 5:11 ` Karl Fogel [this message]
[not found] <<87tvakfnv4.fsf@red-bean.com>
[not found] ` <<835zmzsuau.fsf@gnu.org>
2019-08-14 15:24 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnl5pucp.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.