From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Copley Newsgroups: gmane.emacs.devel Subject: Re: Undoing yank-pop Date: Thu, 13 Jun 2013 23:04:04 +0100 Message-ID: References: <1371087820.76480.YahooMailClassic@web141102.mail.bf1.yahoo.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c38f10ffcd6c04df104e1d X-Trace: ger.gmane.org 1371161053 15131 80.91.229.3 (13 Jun 2013 22:04:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Jun 2013 22:04:13 +0000 (UTC) Cc: Emacs Development To: Kelly Dean Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 14 00:04:14 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UnFcr-0008Kh-As for ged-emacs-devel@m.gmane.org; Fri, 14 Jun 2013 00:04:13 +0200 Original-Received: from localhost ([::1]:55722 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UnFcq-0007v3-UH for ged-emacs-devel@m.gmane.org; Thu, 13 Jun 2013 18:04:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UnFcl-0007qr-Qd for emacs-devel@gnu.org; Thu, 13 Jun 2013 18:04:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UnFck-0003bx-7J for emacs-devel@gnu.org; Thu, 13 Jun 2013 18:04:07 -0400 Original-Received: from mail-ee0-x235.google.com ([2a00:1450:4013:c00::235]:61791) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UnFck-0003bY-04 for emacs-devel@gnu.org; Thu, 13 Jun 2013 18:04:06 -0400 Original-Received: by mail-ee0-f53.google.com with SMTP id c41so5483601eek.12 for ; Thu, 13 Jun 2013 15:04:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u2zCiajC/7E1I0NkQiqWVN5RxFGGOkTIc/bwgxtjfD4=; b=aSaKexeCf+dIM7pRbCyw+wJPqONhWifmNPtBIBzvg4t0glGVnAljdKtEyPZ53I99Uu p2fWy+lPpc1+/8K4CESKX2u59tW9pzt8XdUlKoVRP3IP3eBOmAFwbh65TAg3CRmve4xJ eHJLmLeNXCOlhGI3ysDtJHL3CRGdOdXhJsAS1a31QRwetzMpQ0PzMAHlSgR1lpsQiuQM nPzV/7fOD9HmNqGbu6+ZerXOGF/VMTO3zo2H5TQtJJ1q0k5GDgOMI7XGtXz4WLjM7qK8 cGc8pYdLRCCyuTeZ8Xit+RDBwYussn//jc/LNykG0tMeaPWArPVf53FXSo7VlmMz3A21 mLgA== X-Received: by 10.15.53.132 with SMTP id r4mr2798098eew.43.1371161044690; Thu, 13 Jun 2013 15:04:04 -0700 (PDT) Original-Received: by 10.15.22.193 with HTTP; Thu, 13 Jun 2013 15:04:04 -0700 (PDT) In-Reply-To: <1371087820.76480.YahooMailClassic@web141102.mail.bf1.yahoo.com> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:160422 Archived-At: --001a11c38f10ffcd6c04df104e1d Content-Type: text/plain; charset=ISO-8859-1 On 13 June 2013 02:43, Kelly Dean wrote: > Michael Heerdegen wrote: > >I often do C-y M-y M-y ... like most of us, I think. > >Currently, if you `undo' after that, each of the M-y's are undone > >separately. > [...] > >I would suggest that undo simply undoes until before the first yank. > > I agree. I think if you put an undo boundary before yank, and before any > change besides yank-pop that follows yank, but don't put one before > yank-pop, then when undoing and redoing, it would act like the text > insertion done by the last yank-pop was the only thing that happened. > > Andreas Schwab wrote: > >You can always redo if you overshot. > > Yes, but having to undo through all the yank-pop events in the first place > is annoying when you only did them for the purpose of reviewing the last > few items on the ring, and didn't intend to leave the text inserted. And if > you overshoot while doing yank-pop, you don't need undo to go back anyway, > since you can use a negative arg with yank-pop (which I do so often that I > have a yank-pop-rev command that does that, with a dedicated key chord > bound to it) Uh huh. IMO there should be such a keychord by default and it should be short and advertised. --001a11c38f10ffcd6c04df104e1d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 1= 3 June 2013 02:43, Kelly Dean <kellydeanch@yahoo.com> wr= ote:
Michael Heerdegen wrote:
>I often do C-y M-y M-y ... like most of us, I think.
>Currently, if you `undo' after that, each of the M-y's are undo= ne
>separately.
[...]
>I would suggest that undo simply undoes until before = the first yank.

I agree. I think if you put an undo boundary before yank, and before = any change besides yank-pop that follows yank, but don't put one before= yank-pop, then when undoing and redoing, it would act like the text insert= ion done by the last yank-pop was the only thing that happened.

Andreas Schwab wrote:
>You can always redo if you overshot.

Yes, but having to undo through all the yank-pop events in the first = place is annoying when you only did them for the purpose of reviewing the l= ast few items on the ring, and didn't intend to leave the text inserted= . And if you overshoot while doing yank-pop, you don't need undo to go = back anyway, since you can use a negative arg with yank-pop (which I do so = often that I have a yank-pop-rev command that does that, with a dedicated k= ey chord bound to it)

Uh huh. IMO there should be such a keychord by default = and it should be short and advertised.

--001a11c38f10ffcd6c04df104e1d--