From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Please, Restore Previous Behavior for jump-to-register Date: Sun, 10 Dec 2023 11:26:39 -0500 Message-ID: <87fs0ahvgx.fsf@dancol.org> References: <87h6kr9817.fsf@posteo.net> <87a5qi1vui.fsf@posteo.net> <87bkayjoga.fsf@linux-m68k.org> <83wmtmumud.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33021"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.11.14; emacs 30.0.50 Cc: ams@gnu.org, schwab@linux-m68k.org, thievol@posteo.net, raman@google.com, eller.helmut@gmail.com, tino.calancha@gmail.com, emacs-devel@gnu.org To: Eduardo Ochs , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 10 17:30:03 2023 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 1rCMgr-0008Ni-3n for ged-emacs-devel@m.gmane-mx.org; Sun, 10 Dec 2023 17:30:01 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rCMgd-0005Gl-An; Sun, 10 Dec 2023 11:29:47 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rCMgb-0005GV-V9 for emacs-devel@gnu.org; Sun, 10 Dec 2023 11:29:46 -0500 Original-Received: from dancol.org ([2600:3c01:e000:3d8::1]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rCMga-0000Fq-5E; Sun, 10 Dec 2023 11:29:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Type:MIME-Version:Message-ID:In-reply-to:Date:Subject:Cc:To: From:References:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=4NmopE7toLcQZis/X162HiAaf3BOAn4fLqo9v3CpVDg=; b=WPLahbmz/EGk/lKaNMRQGcN4GZ 0fRV6zE2Lsoj4K3WaDBaCbfNRLmAf8yyF2COZZMlPWMUC+1ks2Cj49YL/2rbEbwUCZrqMQ1BCVFIt AAlsJ7NDYKbZIEvIXwSNruPRXlLN/3YviPuoJna8n3B5BzO0xy8a+PJoKXEUTtCNzEiSRutAGluj8 bwomay6f8t9w3jctczRcFJSFHi6w5oGqA6nZ9IR1a4YAmtmKit6iqUSu15qBOcv48wYu7bzIzuuCy ehy0Jrq9ftIGmyH8mCp85yeLCCDzWjcC2Z57r9fkLvGq5+ibw41gLys1nOrcTVb2s/bsRHLtMyQcl tWtoxqNw==; Original-Received: from 2603-9001-4203-1ab2-d885-8c5b-d12d-91f6.inf6.spectrum.com ([2603:9001:4203:1ab2:d885:8c5b:d12d:91f6]:35806 helo=localhost) by dancol.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rCMgS-0003Yr-Lb; Sun, 10 Dec 2023 11:29:37 -0500 In-reply-to: <83wmtmumud.fsf@gnu.org> Received-SPF: pass client-ip=2600:3c01:e000:3d8::1; envelope-from=dancol@dancol.org; helo=dancol.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313680 Archived-At: Eli Zaretskii writes: >> From: Eduardo Ochs >> Date: Sun, 10 Dec 2023 09:34:32 -0300 >> Cc: Andreas Schwab , thievol@posteo.net, >> raman@google.com, >> eller.helmut@gmail.com, tino.calancha@gmail.com, emacs-devel@gnu.org >> >> 1) please introduce variables that would let us use the old behavior >> - the one without any RETs, > > Which situations currently require a RET when register-use-preview is > set to 'never'? You have shown one of them, but are there others, or > is that the only one that needs to be solved for this item to be > fulfilled? > >> 2) please write the functions in a way in which it would be easy - >> either with a bit of Lisp or with none - to define four key >> sequences, one for point-to-register-with-RETs, one for >> point-to-register-without-RETs, one for >> jump-to-register-with-RETs and one for >> jump-to-register-without-RETs, > > Why do you need separate functions? Would a user option that allows > to choose either with or without RET be enough? If not, why not? > >> 3) add a few sentences to the docstrings of point-to-register and >> jump-to-register to explain that the old behavior was without any >> RETs - but with `?' showing previews - and some people prefer >> that way, and to configure the behavior see that variables such >> and such and the functions such and such. That would make >> everything easy to discover > > We will revisit the documentation once the code is in its final shape. I have to concur with all the people decrying the new behavior. I don't understand why one would want to add friction to this core interaction. I strongly prefer editing fluidity over any kind of preview mechanism. Please keep the traditional behavior.