unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: emacsq <laszlomail@protonmail.com>
Cc: 53945@debbugs.gnu.org
Subject: bug#53945: saveplace should save the buffer's mark list too
Date: Sun, 13 Feb 2022 20:38:29 +0200	[thread overview]
Message-ID: <86wnhzvsme.fsf@mail.linkov.net> (raw)
In-Reply-To: <TaOqB2iiNig7mcwrl2ULjoRDfCbCfz4Bsl9LVtmA2Y4xzMLqwNI16yd2bOip5_-8SdE67eSGukbM6nMrhWvPArZT7NGrm8juolYOIMoeve4=@protonmail.com> (emacsq's message of "Sat, 12 Feb 2022 20:09:53 +0000")

>> Did you know that desktop-save-mode saves the mark ring of every buffer?
>
> No, but I don't use desktop mode, I like to start with  no buffers
> when I restart emacs. But when I open a file then I like it when it
> puts the cursor to where it was last time. That's why I use saveplace
> to save this location info and also saving other useful locations in the
> file (the mark ring) is a logical and handy improvement to it.

The format used by saveplace.el allows adding more data,
so it's easy to add the mark ring.

But are you sure that the package with the name "saveplace"
is a suitable place to save the mark ring?

For example, saveplace.el is optimized to not save the location
when point is at the beginning of the buffer.  So in such cases
the mark ring will not be saved too.

You said that don't want to use the desktop mode.
What if someone would like to save only the mark ring,
but not to save locations in files?





  reply	other threads:[~2022-02-13 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 21:36 bug#53945: saveplace should save the buffer's mark list too emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 19:30 ` Juri Linkov
2022-02-12 20:09   ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13 18:38     ` Juri Linkov [this message]
2022-02-13 19:20       ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86wnhzvsme.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=53945@debbugs.gnu.org \
    --cc=laszlomail@protonmail.com \
    /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).