unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Christopher Howard <christopher@librehacker.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bookmarks in registers
Date: Thu, 08 Jun 2023 06:44:43 +0000	[thread overview]
Message-ID: <87a5xalag4.fsf@posteo.net> (raw)
In-Reply-To: <ZID2ZvB3S-FZsYE_@theoden> (Christopher Howard's message of "Wed,  7 Jun 2023 13:28:06 -0800")

Christopher Howard <christopher@librehacker.com> writes:

> Hi, I explored this idea recently, and was wondering if it could be something easily added to the next release of emacs:
>
> http://gem.librehacker.com/gemlog/starlog/20230607-0.gmi

For those who don't want to open the link:

--8<---------------cut here---------------start------------->8---
(defun bookmark-point-to-register ()
  (interactive)
  (set-register
   (register-read-with-preview "register: ")
   (bookmark-make-record)))

(defun bookmark-register-to-point ()
  (interactive)
  (bookmark--jump-via
   (get-register
    (register-read-with-preview "register: "))
   'pop-to-buffer-same-window))
--8<---------------cut here---------------end--------------->8---

> Maybe some active Emacs developer would want to run with this basic idea and throw together a patch?

Getting other people to write a patch for you is usually not productive.
I'd recommend trying to do so yourself (check out the CONTRIBUTE file in
emacs.git), in which case there is something concrete to discuss.

> I've found in my workflow that it is convenient to be able to put an
> anonymous bookmark into a register. For example, if you are
> temporarily moving around between a few different info manuals.

How is this different from `point-to-register' and `jump-to-register'?



  reply	other threads:[~2023-06-08  6:44 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 [this message]
2023-06-08 14:13   ` [External] : " Drew Adams
2023-06-08 15:41     ` Christopher Howard
2023-12-18  5:57       ` Karl Fogel

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=87a5xalag4.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=christopher@librehacker.com \
    --cc=emacs-devel@gnu.org \
    /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).