From: Miles Bader <miles@gnu.org>
Cc: Juri Linkov <juri@jurta.org>,
eliz@gnu.org, romain@orebokech.com, emacs-devel@gnu.org
Subject: Re: faq.texi
Date: Wed, 15 Feb 2006 11:22:41 +0900 [thread overview]
Message-ID: <fc339e4a0602141822q30c0d6b3q8e3499f0b2888010@mail.gmail.com> (raw)
In-Reply-To: <E1F98UH-0007t0-GE@fencepost.gnu.org>
On 2/15/06, Richard M. Stallman <rms@gnu.org> wrote:
> Either way we should find a replacement keybinding for isearch-yank-line,
> and this is not easy.
>
> Is it really useful? C-w in a search is definitely useful, but I have
> never seen a use for C-y. In general, a whole line of text is more
> than one needs to search for.
Maybe I'm weird, but I do tend to use C-y reasonably often in a
specific circumstance: when i want to see how well two regions of
text match, I go to the beginning of one, and hit C-y until the search
fails; this could be done with C-w too but it's a lot more tedious for
big regions.
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2006-02-15 2:22 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 ` Miles Bader [this message]
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 ` faq.texi Juri Linkov
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=fc339e4a0602141822q30c0d6b3q8e3499f0b2888010@mail.gmail.com \
--to=miles@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=romain@orebokech.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 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).