From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.devel Subject: Re: Recentish C-s M-y change Date: Sat, 30 Jan 2021 10:42:25 +0000 Message-ID: <5bbae1bd19fadee709b0@heytings.org> References: <87r1na4tyu.fsf@gnus.org> <87tus6tj7s.fsf@mail.linkov.net> <87a6txigm1.fsf@gnus.org> <874kk5lzew.fsf@mail.linkov.net> <87eej8ifll.fsf@mail.linkov.net> <87h7o3k5b5.fsf@mail.linkov.net> <87wnwslhdr.fsf@mail.linkov.net> <87sg74itrx.fsf@mail.linkov.net> <87o8h9h1yo.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21364"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 30 11:43:13 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l5nii-0005SP-3M for ged-emacs-devel@m.gmane-mx.org; Sat, 30 Jan 2021 11:43:12 +0100 Original-Received: from localhost ([::1]:56086 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l5nih-0003ah-5a for ged-emacs-devel@m.gmane-mx.org; Sat, 30 Jan 2021 05:43:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38216) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l5ni1-00039u-Sq for emacs-devel@gnu.org; Sat, 30 Jan 2021 05:42:29 -0500 Original-Received: from heytings.org ([95.142.160.155]:58204) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l5nhz-0004U5-Jo for emacs-devel@gnu.org; Sat, 30 Jan 2021 05:42:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1612003345; bh=q0YXC6uK7Rqli5OOznnA6afJWeMHWMQcz/0+nrT4p48=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=FMqqitWRHKTG/qE1C2SmoR/KQqEC/8W8VqDcZk9aKBaIesRcEhm9VTwrJvJ8EFjRJ r5XqvfmeDmJBiklCgpDJaDPt4FSjQb/VgZxImvni1qIvOkQuCleTR7votFPDruLwAe smgH7Homtbht4xdy4/rRp4pDGAy+CaRkd2VSaGHjDzBBWT4k2D+QM2bNQNWM6Coi0d dllkFB8mG++e2fW8CACFzOgGKJRMpwMvlzYOOqmHzX4YOGR8b32wS89/gUYJy34QIw 9hSVrL1dN9RFfjGe9yZZ+j49Pl+cvkUtYiJBsMLUyhyC0NcPKTdqS+2TatEY0QmGzT jxGRhdTCWeuvA== In-Reply-To: <87o8h9h1yo.fsf@mail.linkov.net> Received-SPF: pass client-ip=95.142.160.155; envelope-from=gregory@heytings.org; helo=heytings.org X-Spam_score_int: -19 X-Spam_score: -2.0 X-Spam_bar: -- X-Spam_report: (-2.0 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, GAPPY_SUBJECT=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:263604 Archived-At: >> But... could you perhaps also add C-s C-u C-y, as I suggested? If not, >> why not? The prefix argument is currently ignored by C-y. > > The current interface of isearch-yank-kill and isearch-yank-pop > corresponds exactly to the global commands yank and yank-pop. So their > behaviors are mirrors, but adding C-u to one of them will break > consistency, i.e. C-u of yank and isearch-yank-kill would have a > completely different meaning. > I understand, but the consistency is broken anyway: C-u has an effect on yank, and no effect on isearch-yank-kill. And mirroring the effect of C-u on yank (exchanging point and mark) in isearch-yank-kill is not possible. I stand by my suggestion: using the universal argument on isearch-yank-kill to immediately enter the interactive selection of an element of the kill-ring with C-s C-u C-y without releasing the control modifier. >> I believe accessing the new feature with both C-s C-u C-y and C-s C-u >> M-y is useful: C-s C-u C-y is useful to immediately enter an >> interactive selection (it's convenient because it only uses the control >> modifier), and C-s C-y M-y ... C-u M-y is useful to enter an >> interactive selection while using the non-interactive selection. > > BTW, such sequence might not do what you want. I mean that often after > typing C-s C-y M-y ... C-u M-y, the second C-u M-y doesn't replace the > search string with a string from the kill-ring, it appends it. > That's not correct. C-s C-y M-y ... or C-s M-y M-y ... cycle through the kill-ring entries. Typing C-u M-y enters an interactive selection of the kill-ring elements in the minibuffer. What you probably meant is that C-s C-y M-y ... or C-s M-y M-y ... cycle through the kill-ring entries and appends each of them in turn to the , and that typing C-u M-y discards the and enters the interactive selection of a kill-ring element in the minibuffer. It could indeed make sense to use C-u C-u M-y (for example) to enter an interactive selection of a kill-ring element prepended with the , but I'm not convinced it would be very useful in practice.