unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: emacsq via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 53945@debbugs.gnu.org
Subject: bug#53945: saveplace should save the buffer's mark list too
Date: Sun, 13 Feb 2022 19:20:11 +0000	[thread overview]
Message-ID: <G6ncIHHdezpbsHxOyoM5sRV74BJEs5vzdaOn6sUX_NjV6jTrZ96kNKOTtLy_2DAD-Bo457p53RLOapRgsoLvL5dZDxuEyXe2wmfHSm8C56s=@protonmail.com> (raw)
In-Reply-To: <86wnhzvsme.fsf@mail.linkov.net>


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

Since marks are also places in the file it's not unnatural if
saveplace saves other places too.  .

> 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.

I guess it's not hard to disable this optimization if marks are
also saved.

> What if someone would like to save only the mark ring,
> but not to save locations in files?

This can be solved with a new option if the need ever arises,
and the option may not even affect the saving part (who cares
if the current location is saved along with the marks, just
one more number), only the restoring of the position is skipped
when the file is opened.






      reply	other threads:[~2022-02-13 19:20 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
2022-02-13 19:20       ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors [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='G6ncIHHdezpbsHxOyoM5sRV74BJEs5vzdaOn6sUX_NjV6jTrZ96kNKOTtLy_2DAD-Bo457p53RLOapRgsoLvL5dZDxuEyXe2wmfHSm8C56s=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53945@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --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).