unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14742@debbugs.gnu.org
Subject: bug#14742: 24.3.50; enhancement request: be able to prepend stuff from buffer when search backward
Date: Thu, 04 Jul 2013 01:57:02 +0300	[thread overview]
Message-ID: <87k3l79seh.fsf@mail.jurta.org> (raw)
In-Reply-To: <cf8e54e1-6ff2-460e-bfa0-d8d5465d5b99@default> (Drew Adams's message of "Tue, 2 Jul 2013 22:40:27 -0700 (PDT)")

> Is this the idea: cursor movements would extend isearch by yanking the
> text the cursor would move over in the buffer, starting from `point'
> (where isearch starts)?
>
> E.g., for forward search C-f, M-f, C-M-f, C-e, etc. would yank the next
> char, word, symbol, line etc. to the end of the search string.  And for
> reverse search C-b, M-b, C-M-b, C-a, etc. would yank the previous (next
> going backward) char, word, symbol, line etc. to the beginning of the
> search string.
>
> And presumably backward cursor movements when searching forward (e.g.,
> C-b, M-b, C-M-b, C-a) would undo, in the sense of removing yanked text
> (but only yanked text, presumably) from the end.  And forward cursor
> movements when searching backward would remove yanked text from the
> beginning.
>
> Is that the idea?

Exactly.

> Do you have this working already?  Have you described what you have in
> mind somewhere?  Did you bring this up in emacs-devel?  If not, please
> consider it - that is the best place to toss such an idea around.

Yes, it is working and I described it on emacs-devel a month ago.
Now I'll prepare a minimal patch that implements low-level support, then
send separate high-level code to activate it, so everyone could try it.





  reply	other threads:[~2013-07-03 22:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 18:17 bug#14742: 24.3.50; enhancement request: be able to prepend stuff from buffer when search backward Drew Adams
2013-06-28 21:43 ` Juri Linkov
2013-06-28 22:00   ` Drew Adams
2013-06-29 21:50     ` Juri Linkov
2013-06-29 23:02       ` Drew Adams
2013-07-02 22:39         ` Juri Linkov
2013-07-02 23:42           ` Drew Adams
2013-07-02 23:53             ` Juri Linkov
2013-07-03  1:07               ` Drew Adams
2013-07-03  5:40                 ` Drew Adams
2013-07-03 22:57                   ` Juri Linkov [this message]
2013-07-04  0:17                     ` Drew Adams
2013-07-04 23:34                       ` Juri Linkov
2013-07-05 10:37                         ` Stefan Monnier
2013-07-05 22:28                           ` Juri Linkov
2013-07-05 22:59                             ` Stefan Monnier
2013-07-05 23:17                               ` Juri Linkov
2013-07-06  0:40                                 ` Stefan Monnier
2020-09-18 14:30                             ` Lars Ingebrigtsen
2020-09-18 16:11                               ` Drew Adams
2020-09-21 19:07                                 ` Juri Linkov

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=87k3l79seh.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=14742@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).