From: Pierre Neidhardt <ambrevar@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 29110@debbugs.gnu.org
Subject: bug#29110: 25.2; Should push-mark allow duplicates?
Date: Thu, 02 Nov 2017 07:43:25 +0100 [thread overview]
Message-ID: <87d151i3jm.fsf@gmail.com> (raw)
In-Reply-To: <8760ata86n.fsf@users.sourceforge.net>
> Consider this:
>
> mark-ring-max is a variable defined in ‘simple.el’.
> Its value is 16
>
> Documentation:
> Maximum size of mark ring. Start discarding off end if gets this big.
>
> You can customize this variable.
>
> global-mark-ring-max is the same idea.
Damn, I had no clue about that one. Thank you for shattering my
ignorant concern to pieces! :D
That being said, it raises another problem (sorry for being so
annoying): if we have a limit _and_ we allow duplicates, it means that a
lot of duplicates will discard old entries more quickly.
> One thing to note is that push-mark resets markers before discarding
> (so that they no longer point to any buffer).
Thanks a lot, that's an excellent lead. Indeed, that might be the root
of the issue. We will investigate further.
Thanks for all!
--
Pierre Neidhardt
Here is a test to find whether your mission on earth is finished:
if you're alive, it isn't.
next prev parent reply other threads:[~2017-11-02 6:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 22:19 bug#29110: 25.2; Should push-mark allow duplicates? Pierre Neidhardt
2017-11-01 22:43 ` Drew Adams
2017-11-01 23:07 ` Pierre Neidhardt
2017-11-01 23:30 ` Noam Postavsky
2017-11-02 6:43 ` Pierre Neidhardt [this message]
2017-11-02 0:53 ` Drew Adams
2017-11-02 6:40 ` Pierre Neidhardt
2017-11-02 13:34 ` Drew Adams
2017-11-05 14:59 ` Pierre Neidhardt
2017-11-05 18:41 ` Drew Adams
2022-02-08 6:24 ` Lars Ingebrigtsen
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=87d151i3jm.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=29110@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.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).