unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: Drew Adams <drew.adams@oracle.com>,
	 Philip Kaludercic <philipk@posteo.net>,
	 "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: Bookmarks in registers
Date: Mon, 18 Dec 2023 00:57:43 -0500	[thread overview]
Message-ID: <87y1ds9hns.fsf@red-bean.com> (raw)
In-Reply-To: <ZIH2pu_s4WlxiFSp@theoden> (Christopher Howard's message of "Thu,  8 Jun 2023 07:41:26 -0800")

On 08 Jun 2023, Christopher Howard wrote:
>Thank you. I think, looking bookmark+ over, I would still rather 
>use
>the solution I've already coded, which seems slightly more
>convenient. With bookmark+, you would not need to confirm a 
>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 
>"I
>always put that last bookmark I need in register 1". It does look 
>like
>bookmark+ has a temporary bookmark functionality, but you either 
>have
>to consciousless enable it / disable it for individual bookmarks, 
>or
>go into a special mode. That being said, if I hadn't already 
>coded the
>register functions that work great for me, I think I would 
>explore
>bookmark+ a little more.
>
>I certainly don't mean to create a ton of work for other people — 
>my
>thought was just that if it was pretty easy for me to figure out 
>how
>to store a bookmark in a register, then maybe an emacs dev with 
>all
>the knowledge of patch-making and proper naming and such could 
>add the
>functionality easily. Due to my life time-constraints, I don't 
>think
>I'd be able to dive more deeply into for another four or five 
>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 — maybe that is
>something that would be trivial to somebody else.

I think it's an interesting idea and would be a convenience for 
some people!  Have you found yourself using this much?

The hard part here is not the coding itself.  Indeed, Philip 
Kaludercic's follow-up to your original post basically showed the 
code :-).  The real task is deciding exactly how/where this would 
fit into existing bookmark and register functionality (e.g., would 
it imply any other changes?), where the code would live (in 
bookmark.el?  in register.el?), what Info pages and other 
documentation would need to be updated, whether there should be 
keybindigs and if so what they should be, etc.

By the way, the original thing you linked to 
(https://gem.librehacker.com/gemlog/starlog/20230607-0.gmi) 
appears to be gone now.  All my understanding of the proposal 
comes from this email thread, therefore, in particular Philip 
Kaludercic's follow-up.

Best regards,
-Karl



      reply	other threads:[~2023-12-18  5:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 21:28 Bookmarks in registers Christopher Howard
2023-06-08  6:44 ` Philip Kaludercic
2023-06-08 14:13   ` [External] : " Drew Adams
2023-06-08 15:41     ` Christopher Howard
2023-12-18  5:57       ` Karl Fogel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1ds9hns.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=christopher@librehacker.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).