all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Juri Linkov <juri@jurta.org>
Cc: Geoff Gole <geoffgole@gmail.com>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: yank-pop error unnecessary and annoying
Date: Mon, 14 Jun 2010 18:57:37 -0400	[thread overview]
Message-ID: <871vc91au6.fsf@stupidchicken.com> (raw)
In-Reply-To: <87vd9lziqo.fsf@mail.jurta.org> (Juri Linkov's message of "Mon, 14 Jun 2010 19:20:50 +0300")

Juri Linkov <juri@jurta.org> writes:

> We have a proposal to do more useful things for yank-pop
> without a previous yank:
>
> http://thread.gmane.org/gmane.emacs.devel/122139/focus=122670

That is a proposal to do something different (prompt for an entry on the
kill ring).

But usually, what people have in mind when they do a spurious yank-pop
is "delete the stretch of text that I most recently yanked, and replace
it with the next item in the kill ring".  At least, that's what
frequently happens to me, usually when I inadvertently do some cursor
motion after yanking.

(In fact, the error is frequent enough that the above proposed behavior
might be annoying, since I don't just want to yank; I want to *replace*
the text; so I would end up doing an extra C-g to quit out of the
prompt.)

It Would Be Nice (tm) if the "yank-pop without previous yank by deleting
last yank" behavior could be implemented, but I don't know how easy or
difficult it is.  I assume the main complication is how to handle the
case where the buffer is modified since the last yank.



  parent reply	other threads:[~2010-06-14 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 16:00 yank-pop error unnecessary and annoying Geoff Gole
2010-06-14 16:20 ` Juri Linkov
2010-06-14 16:47   ` Geoff Gole
2010-06-14 22:57   ` Chong Yidong [this message]
2010-06-15  2:31     ` Stephen J. Turnbull
2010-06-14 22:16 ` Richard Stallman
2010-06-15  0:52   ` Geoff Gole

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871vc91au6.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=geoffgole@gmail.com \
    --cc=juri@jurta.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.