From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Alfred M. Szmidt" Newsgroups: gmane.emacs.devel Subject: Re: Please, Restore Previous Behavior for jump-to-register Date: Thu, 14 Dec 2023 10:55:34 -0500 Message-ID: References: <87h6kr9817.fsf@posteo.net> <87a5qi1vui.fsf@posteo.net> <87bkayjoga.fsf@linux-m68k.org> <83wmtmumud.fsf@gnu.org> <874jgq0zdh.fsf@posteo.net> <25974.5401.926181.432049@retriever.mtv.corp.google.com> <25974.24010.49674.989981@retriever.mtv.corp.google.com> <83lea0vs8w.fsf@gnu.org> <83ttolql64.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23483"; mail-complaints-to="usenet@ciao.gmane.io" Cc: eliz@gnu.org, emacs-devel@gnu.org, raman@google.com, thievol@posteo.net, eduardoochs@gmail.com, schwab@linux-m68k.org, eller.helmut@gmail.com, tino.calancha@gmail.com To: =?UTF-8?Q?To=3A_Jo=C3=83=C2=A3o_T=C3=83=C2=A1vora_=3Cjoaotavora=40gmail?= =?UTF-8?Q?=2Ecom=3E=0A?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 14 16:56:50 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 1rDo4v-0005rO-06 for ged-emacs-devel@m.gmane-mx.org; Thu, 14 Dec 2023 16:56:49 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rDo3v-0006BV-PA; Thu, 14 Dec 2023 10:55: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 1rDo3m-0005tK-CV for emacs-devel@gnu.org; Thu, 14 Dec 2023 10:55:41 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rDo3j-00073X-0S; Thu, 14 Dec 2023 10:55:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=xLZU7yzglWOZ9uSAF/jmqchToF4lVTu0kBm+zjuZYcQ=; b=mSdiGlUztb/5 Mp46NhEiHNbuqR36F19+5OUFgObXljIsdK3pkxMfb9SrZelzoPYzHxXOs+kGF3ymJVT9czszz8pk4 J7Khum/UDLX0C4eQt4WburRtJPgBf70OjF45BuUY54y4ChdH/oPBVP17JlxvlC7W4vZyKlEmc/0ax 2IL/bTnnH7p8Ah6iT11+K/CekiY+KxnuuMbbbl77DioQTcMKtFCrLzCQ2ObhdngSik/FyCu0N4eH4 z6yZQp2XzoGnORo4WiSmiRQMA5cbJswZjaW1bGIH/DAjcTgwnxAGOcc8v3VYP+5a84e5/WqkLP/SS 1h99rZ4CZtb0xG+rMopyWg==; Original-Received: from ams by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1rDo3i-0007tH-7C; Thu, 14 Dec 2023 10:55:34 -0500 In-Reply-To: =?UTF-8?Q?In-Reply-To=3A_=09=3CCALDnm50JiT0pTkQoQWUZ58wnoVk98L15QZYtFFMDy?= =?UTF-8?Q?SMVsiD5OA=40mail=2Egmail=2Ecom=3E=0A=09=28message_from_Jo=C3=83?= =?UTF-8?Q?=C2=A3o_T=C3=83=C2=A1vora_on_Thu=2C_14_Dec_2023_15=3A31=3A43_+0?= =?UTF-8?Q?000=29=0A?= 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:313784 Archived-At: > Unless it wasn't clear -- I think it is a bad idea, it makes registers > the same as bookmarks. I can really emphatize with this. If we want confirmation prompts, visual popups, etc, why don't we add those to bookmark.el? It already has a completing-read UI that is much more suitable for this, and would allow these features much more naturally. There are a bunch of completing-read-friendly extensions for bells and whistles out there. This would keep the register workflow intact, solve the same code-navigation problems and relieve us of multiple patch iterations with complicated customization options noone seems to agree on. E.g., bookmarks does not warn about overwriting an existing bookmark. That would be a good place for such a warning, and even prompt would make sense and a change I think nobody would even object to. Bookmarks doesn't do the whole preview thing, which in it self is nice even for registers when you only have a delay. And for bookmarks it would make even _more_ sense, where for registers it mostly does not --- "position 17777777" is not very useful in the output even misleading if you are narrowing your view, for bookmarks this could be actual line or something. If the issue is the temporary aspect of registers or not being able to set bookmarks in some contexts (buffers without a associated file, e.g.), I'm sure that can be solved by allowing bookmarks and registers to co-exist in some form and showing that in the bookmark-list/preview accordingly and then hooking bookmark-set/jump to use the relevant register functions instead under the hood. I'm beyond convinced that those who want to use registers with confirmation really should be using bookmarks and that this change is simply not needed.