unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 6232@debbugs.gnu.org
Subject: bug#6232: Suggestion for isearch: in backward search yank to front of search string
Date: Fri, 21 May 2010 20:31:12 +0200	[thread overview]
Message-ID: <AANLkTin5SBdjhKWxgS_ht9MKDpLKejmt-889A8KzmuNM@mail.gmail.com> (raw)
In-Reply-To: <m34oi1irf1.fsf@hase.home>

On Fri, May 21, 2010 at 10:34 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> 2) Using the same keybindings make them easy to remember.
>>
>> 3) It does seem rather logical that the yanking is done at the other
>> end when search direction is reversed.
>
> It would be totally confusing behaviour.  Normal characters are always
> added at the end, so yanking should always behave the same.


I can see your point, but my gut feeling is perhaps not the same.

Also consider the 4th point I made:


> 4) Maybe more important: The marker in isearch that shows the
> direction will be at the position where the yanking is done. Or at
> least nearly. So the semantics is in a sense the same since yanking is
> done forward from that marker.


I any case I think it is important that the key sequences for adding
at the beginning and end of the search string are similar. There are 4
yank commands in isearch for adding at the end. How about adding shift
to these to add at the beginning?





  reply	other threads:[~2010-05-21 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 16:09 bug#6232: Suggestion for isearch: in backward search yank to front of search string Lennart Borgman
2010-05-21  0:09 ` Juri Linkov
2010-05-21  1:18   ` Lennart Borgman
2010-05-21  8:34     ` Andreas Schwab
2010-05-21 18:31       ` Lennart Borgman [this message]
2012-02-22  2:40       ` Glenn Morris
2010-05-21 21:09     ` Richard Stallman
2010-05-21 21:19       ` Lennart Borgman
2010-05-21  8:27 ` Andreas Schwab
2010-05-21  9:54   ` Leo

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=AANLkTin5SBdjhKWxgS_ht9MKDpLKejmt-889A8KzmuNM@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=6232@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).