From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: Bookmarks in registers Date: Mon, 18 Dec 2023 00:57:43 -0500 Message-ID: <87y1ds9hns.fsf@red-bean.com> References: <87a5xalag4.fsf@posteo.net> Reply-To: Karl Fogel Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27280"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Drew Adams , Philip Kaludercic , "emacs-devel@gnu.org" To: Christopher Howard Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 18 06:58:56 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 1rF6eV-0006sd-Ft for ged-emacs-devel@m.gmane-mx.org; Mon, 18 Dec 2023 06:58:55 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rF6dU-00018o-2U; Mon, 18 Dec 2023 00:57:52 -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 1rF6dS-000180-DJ for emacs-devel@gnu.org; Mon, 18 Dec 2023 00:57:50 -0500 Original-Received: from sanpietro.red-bean.com ([45.79.25.59]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rF6dQ-0004B7-IA for emacs-devel@gnu.org; Mon, 18 Dec 2023 00:57:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=red-bean.com; s=202005newsp; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:Reply-To:References:In-Reply-To:Subject:Cc:To: From:Sender:Content-ID:Content-Description; bh=g7OnkOsARJQDIdwNbXY85wP65tGoVG/QVdQnjarLC6Q=; t=1702879067; x=1704088667; b=CyHA9AWKBtV0F7EDVZbBZZOiVIHYyR1ilcCz5wgH+/d750eO6f7dxCJXGfkQ8EctDxTb9vQ/HFc zgbEZiooT5M8moqLixrZpfaNhmT1sJutQ/5KMDqz8qIY+KUWxJpj+zDgUrXRigfwFgPdxrIr2Hy7v E2rNmaJU+JsqJGsxs20+BNQfmDiPPiaaRJqbSPzd6ZOzt4iqxKxl5KN0XfIuRMoo7oSREGg4vzdfc Ill1Y0XQwzxOL45rUtJvrVzgGju3Y/BadvwQGvXofvB9IYiEa3YZD5i1tC6zpV8wmlXgnct7u8KfV waIc3vOC0ltWmPfd85AZxvjKJqGVtjd8wC3A==; Original-Received: from [2601:240:c400:76::5755] (port=54140 helo=libq) by sanpietro.red-bean.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rF6dM-006A8c-HD; Mon, 18 Dec 2023 05:57:44 +0000 In-Reply-To: (Christopher Howard's message of "Thu, 8 Jun 2023 07:41:26 -0800") Received-SPF: pass client-ip=45.79.25.59; envelope-from=kfogel@red-bean.com; helo=sanpietro.red-bean.com 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:313973 Archived-At: On 08 Jun 2023, Christopher Howard wrote: >Thank you. I think, looking bookmark+ over, I would still rather=20 >use >the solution I've already coded, which seems slightly more >convenient. With bookmark+, you would not need to confirm a=20 >bookmark >name, but you would still need later to figure out what was the >correct bookmark name to jump to, as opposed to just remembering=20 >"I >always put that last bookmark I need in register 1". It does look=20 >like >bookmark+ has a temporary bookmark functionality, but you either=20 >have >to consciousless enable it / disable it for individual bookmarks,=20 >or >go into a special mode. That being said, if I hadn't already=20 >coded the >register functions that work great for me, I think I would=20 >explore >bookmark+ a little more. > >I certainly don't mean to create a ton of work for other people =E2=80=94= =20 >my >thought was just that if it was pretty easy for me to figure out=20 >how >to store a bookmark in a register, then maybe an emacs dev with=20 >all >the knowledge of patch-making and proper naming and such could=20 >add the >functionality easily. Due to my life time-constraints, I don't=20 >think >I'd be able to dive more deeply into for another four or five=20 >months >at least. One part that I also was unsure about was creating the >proper CL method so that `list-registers' properly displays the >register value when a bookmark is stored in it =E2=80=94 maybe that is >something that would be trivial to somebody else. I think it's an interesting idea and would be a convenience for=20 some people! Have you found yourself using this much? The hard part here is not the coding itself. Indeed, Philip=20 Kaludercic's follow-up to your original post basically showed the=20 code :-). The real task is deciding exactly how/where this would=20 fit into existing bookmark and register functionality (e.g., would=20 it imply any other changes?), where the code would live (in=20 bookmark.el? in register.el?), what Info pages and other=20 documentation would need to be updated, whether there should be=20 keybindigs and if so what they should be, etc. By the way, the original thing you linked to=20 (https://gem.librehacker.com/gemlog/starlog/20230607-0.gmi)=20 appears to be gone now. All my understanding of the proposal=20 comes from this email thread, therefore, in particular Philip=20 Kaludercic's follow-up. Best regards, -Karl