From: Juri Linkov <juri@jurta.org>
Cc: acm@muc.de, miles@gnu.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: faq.texi
Date: Fri, 17 Feb 2006 23:52:09 +0200 [thread overview]
Message-ID: <877j7twp2e.fsf@jurta.org> (raw)
In-Reply-To: <jemzgr7xvw.fsf@sykes.suse.de> (Andreas Schwab's message of "Thu, 16 Feb 2006 23:16:19 +0100")
>> But whatever, I still wouldn't want to lose C-y from within searches.
>> Sometimes C-y followed by M-e and a few backspaces is more convenient
>> than repeated C-w.
>
> I second that. I'm also using C-y in isearch quite often. Another
> application for it on diffs is to do C-s C-y on a context line, then
> change to the file that this diff is based on and do C-s C-s to find
> the context line here.
This is one of the typical examples when I use C-y in isearch too.
Another one is to check two multi-line sections of the same buffer
(such duplicate sections can appear after merge conflicts or after
copying from different sources) and to find the first different line.
But this doesn't mean that I like C-y as a keybinding. I need only
its function isearch-yank-line, and would accept any other keybinding.
BTW, there is one problem with multi-line lazy highlighting: isearch
doesn't highlight partially visible matches, i.e. when a match begins
before (window-end) and ends after it. This is due to the meaning of the
argument `limit' of `search-forward' which specifies the lower bound of
the search, i.e. (match-end 0). Without an ability to specify the
upper bound of the search, isearch lazy highlighting can't highlight
partially visible matches whose (match-beginning 0) is before (window-end),
and (match-end 0) is after (window-end).
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2006-02-17 21:52 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 4:17 faq.texi Richard M. Stallman
2006-02-02 22:34 ` faq.texi Romain Francoise
2006-02-03 23:43 ` faq.texi Richard M. Stallman
2006-02-05 13:07 ` faq.texi Romain Francoise
2006-02-05 20:24 ` faq.texi Eli Zaretskii
2006-02-06 2:06 ` faq.texi Richard M. Stallman
2006-02-06 8:55 ` faq.texi Romain Francoise
2006-02-06 14:18 ` faq.texi Frank Schmitt
2006-02-07 19:20 ` faq.texi Romain Francoise
2006-02-07 20:31 ` (efaq)Inserting > at the beginning of each line (was: faq.texi) Reiner Steib
2006-02-08 22:02 ` (efaq)Inserting > at the beginning of each line Romain Francoise
2006-02-10 1:12 ` Richard M. Stallman
2006-02-07 20:51 ` faq.texi Kevin Rodgers
2006-02-07 21:06 ` faq.texi Frank Schmitt
2006-02-08 6:36 ` faq.texi Eli Zaretskii
2006-02-08 20:38 ` faq.texi Romain Francoise
2006-02-08 21:55 ` faq.texi Eli Zaretskii
2006-02-08 22:10 ` faq.texi Romain Francoise
2006-02-09 17:31 ` faq.texi Juri Linkov
2006-02-09 20:41 ` faq.texi Eli Zaretskii
2006-02-09 21:48 ` faq.texi Juri Linkov
2006-02-09 22:07 ` faq.texi Eli Zaretskii
2006-02-10 0:54 ` faq.texi Juri Linkov
2006-02-10 10:58 ` faq.texi Miles Bader
2006-02-10 23:01 ` faq.texi Richard M. Stallman
2006-02-14 1:48 ` faq.texi Juri Linkov
2006-02-14 22:17 ` faq.texi Richard M. Stallman
2006-02-15 2:22 ` faq.texi Miles Bader
2006-02-15 7:14 ` faq.texi Alan Mackenzie
2006-02-15 18:49 ` faq.texi Drew Adams
2006-02-15 22:03 ` faq.texi Alan Mackenzie
2006-02-15 23:10 ` faq.texi Miles Bader
2006-02-16 0:13 ` faq.texi Drew Adams
2006-02-16 4:40 ` faq.texi Richard M. Stallman
2006-02-16 10:34 ` faq.texi Miles Bader
2006-02-17 3:20 ` faq.texi Richard M. Stallman
2006-02-17 3:44 ` faq.texi Miles Bader
2006-02-17 21:56 ` faq.texi Juri Linkov
2006-02-18 18:33 ` faq.texi Richard M. Stallman
2006-02-18 0:06 ` faq.texi Richard M. Stallman
2006-02-16 12:06 ` faq.texi Alan Mackenzie
2006-02-16 21:17 ` faq.texi Drew Adams
2006-02-17 21:54 ` faq.texi Juri Linkov
2006-02-18 3:05 ` faq.texi Drew Adams
2006-02-16 22:16 ` faq.texi Andreas Schwab
2006-02-17 21:52 ` Juri Linkov [this message]
2006-02-18 22:41 ` faq.texi Miles Bader
2006-02-17 3:21 ` faq.texi Richard M. Stallman
2006-02-17 3:30 ` faq.texi Miles Bader
2006-02-15 16:05 ` faq.texi Robert J. Chassell
2006-02-20 0:48 ` faq.texi Juri Linkov
2006-02-20 22:05 ` faq.texi Richard M. Stallman
2006-02-10 23:02 ` faq.texi Richard M. Stallman
2006-02-11 10:44 ` faq.texi Eli Zaretskii
2006-02-12 4:31 ` faq.texi Richard M. Stallman
2006-02-09 19:04 ` faq.texi Kevin Rodgers
2006-02-09 22:14 ` faq.texi Eli Zaretskii
2006-02-10 1:12 ` faq.texi Richard M. Stallman
2006-02-08 22:05 ` faq.texi Romain Francoise
2006-02-09 17:43 ` faq.texi Juri Linkov
2006-02-25 13:05 ` faq.texi Romain Francoise
2006-02-07 20:41 ` faq.texi Eli Zaretskii
2006-02-08 19:04 ` faq.texi Richard M. Stallman
2006-02-09 7:25 ` faq.texi Eli Zaretskii
2006-02-10 1:13 ` faq.texi Richard M. Stallman
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=877j7twp2e.fsf@jurta.org \
--to=juri@jurta.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=rms@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 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).