unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca
Subject: Re: Word search
Date: Thu, 13 Mar 2008 04:17:22 +0200	[thread overview]
Message-ID: <87abl38qw5.fsf@jurta.org> (raw)
In-Reply-To: <000601c88475$d41ba240$c2b22382@us.oracle.com> (Drew Adams's message of "Wed, 12 Mar 2008 11:18:17 -0800")

> 1. It might be OK to have C-w do something different when the region is
> empty. At least for those people who use transient-mark mode (so that
> "active region" means something).
>
> 2. That is not limited to the minibuffer, logically. That is, there is
> nothing special about the minibuffer in this regard.
>
> 3. It is OK to have some minibuffer key yank text from the current buffer -
> for example, text at or near point.
>
> 4. We have discussed #3 before. I suggested behavior that lets you yank
> different kinds of things at point and behavior that lets you yank
> successive things at point. Nothing has come of that, so far.
>
> 5. HOWEVER: If an approach such as #1 is used, it should not be combined
> with #3, and especially not using `C-w'. That is trying to be too clever by
> half, and it doesn't help.
>
> That is, there is no reason to combine these features you propose. And doing
> so limits design for the future. And the use of C-w then becomes confusing
> for users: sometimes cut (kill), sometimes paste (yank). That's not good UI,
> IMO.
>
> So if you do #3, please use a different key. And if you do #1, consider
> doing so in every buffer, not just the minibuffer.

C-w in the search string editing minibuffer is a natural extension of
C-w in isearch mode (`isearch-yank-word-or-char') because there will be
no difference between `C-s C-w C-w ...' and `C-s M-e C-w C-w ...'.

Since `isearch-edit-string' uses a normal minibuffer, it would be
natural to extend this C-w feature to other minibuffers.

But it is true that such dual nature of C-w might cause troubles
when transient-mark-mode is off.

Maybe, we could accept C-w as a yanking key only at the beginning of
the minibuffer?

-- 
Juri Linkov
http://www.jurta.org/emacs/




  parent reply	other threads:[~2008-03-13  2:17 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AD44E90D-EAA9-4E0B-AED7-CB4505DC73F9@t-online.de>
     [not found] ` <87myp99rd3.fsf@jurta.org>
2008-03-09 21:59   ` First two elements of search-ring shown twice in minibuffer when using M-p multiple times? Juri Linkov
2008-03-10 14:31     ` Stefan Monnier
2008-03-10 17:12       ` Word search (was: First two elements of search-ring shown twice in minibuffer when using M-p multiple times?) Juri Linkov
2008-03-10 18:34         ` Word search Stefan Monnier
2008-03-10 22:38           ` Juri Linkov
2008-03-11 18:47             ` Stefan Monnier
2008-03-12  0:35               ` Juri Linkov
2008-03-12  1:49                 ` Stefan Monnier
2008-03-12 10:38                   ` Juri Linkov
2008-03-12 14:09                     ` Stefan Monnier
2008-03-12 17:51                 ` Richard Stallman
2008-03-11 20:24             ` Richard Stallman
2008-03-12  0:37               ` Juri Linkov
2008-03-12 17:51                 ` Richard Stallman
2008-03-13  2:08                   ` Juri Linkov
2008-03-13 22:24                     ` Richard Stallman
2008-03-13 10:55                   ` René Kyllingstad
2008-03-14  1:08                     ` Juri Linkov
2008-03-12 19:18                 ` Drew Adams
2008-03-13  1:06                   ` Richard Stallman
2008-03-13  2:17                   ` Juri Linkov [this message]
2008-03-13 22:24                     ` Richard Stallman
2008-03-10 16:36     ` First two elements of search-ring shown twice in minibuffer when using M-p multiple times? Tobias Bading
2008-03-10 16:55       ` Juri Linkov
2008-03-10 17:59     ` isearch-push-state (was: First two elements of search-ring shown twice in minibuffer when using M-p multiple times?) Juri Linkov
2008-03-11 17:55       ` isearch-push-state Stefan Monnier
2008-03-12 10:36         ` isearch-push-state Juri Linkov
2008-03-12 14:07           ` isearch-push-state Stefan Monnier
2008-03-10 18:28     ` First two elements of search-ring shown twice in minibuffer when using M-p multiple times? Juri Linkov
2008-03-25  8:13 Word search Vincent Belaïche
2008-03-25 10:24 ` Jason Rumney
2008-03-25 21:48   ` Juri Linkov
2008-03-25 14:12 ` Drew Adams
2008-03-25 14:42 ` Johan Bockgård
  -- strict thread matches above, loose matches on Subject: below --
2008-03-25 16:43 Vincent Belaïche
2008-03-25 18:02 ` Drew Adams
2008-03-26 20:47 Vincent Belaïche
2008-03-26 21:16 ` Drew Adams
2008-03-30  6:13   ` Vincent Belaïche
2008-03-30  6:45     ` Drew Adams
2008-03-30  7:02       ` Vincent Belaïche
2008-03-30 16:58         ` Drew Adams
2008-03-30 21:59     ` Johan Bockgård

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=87abl38qw5.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).