From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: isearch and yank word doubt
Date: Fri, 31 May 2013 12:38:35 +0200 [thread overview]
Message-ID: <86bo7r5t90.fsf@somewhere.org> (raw)
In-Reply-To: mailman.751.1369988981.22516.help-gnu-emacs@gnu.org
Kevin Rodgers wrote:
> On 5/31/13 1:32 AM, Sebastien Vauban wrote:
>> Kevin Rodgers wrote:
>>> On 5/30/13 12:42 AM, Luca Ferrari wrote:
>>>> Hi all,
>>>> according to the manual the C-s C-w yanks the next word the cursor is
>>>> on as the string to search with isearch. Often I found myself having
>>>> the cursor in the middle of a word, so I have to go back to the
>>>> beginning and then do the yank, is there a better way to instrument
>>>> C-s C-w to get the word the cursor is in?
>>>
>>> I like it!
>>
>> One detail I don't like in the above: when C-s C-w'ing, it directly jumps to
>> the next occurrence of the searched string. I find it'd be better if it'd stay
>> on the current word, highlighting it completely.
>
> That may be very difficult to implement, and it doesn't make sense to
> me: isearch by definition searches the buffer from point to the end, so
> if the search string includes text preceding point it cannot match the
> occurrence that straddles point.
>
> Of course, the occurrence that straddles point is eventually matched if
> the search is wrapped past the end of the buffer. And even before
> wrapping, the occurrence is highlighted with the lazy-highlight face --
> although it may no longer be visible, depending on how far away is the
> next occurrence.
That's it: in many cases, you don't see anymore the original word you were on.
And you don't know if you needed to press another time on C-w, if word stopped
at `-' and you want to add the rest, for example.
> That highlighting does seem intuitive, so I'll try to come up with a clean
> implementation of the behavior you want (that does not actually move point
> out of the middle of the word)...
So, IIUC, you would not move point (OK, I see no reason why it absolutely
should), and stay on the "reference" search string, that's it?
Thanks anyway...
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2013-05-31 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 6:42 isearch and yank word doubt Luca Ferrari
2013-05-31 4:57 ` Kevin Rodgers
[not found] ` <mailman.745.1369976220.22516.help-gnu-emacs@gnu.org>
2013-05-31 7:32 ` Sebastien Vauban
2013-05-31 8:30 ` Kevin Rodgers
[not found] ` <mailman.751.1369988981.22516.help-gnu-emacs@gnu.org>
2013-05-31 10:38 ` Sebastien Vauban [this message]
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=86bo7r5t90.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.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.
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).