From: Lars Ingebrigtsen <larsi@gnus.org>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: 29110@debbugs.gnu.org
Subject: bug#29110: 25.2; Should push-mark allow duplicates?
Date: Tue, 08 Feb 2022 07:24:48 +0100 [thread overview]
Message-ID: <87sfstub7z.fsf@gnus.org> (raw)
In-Reply-To: <87h8udiqv3.fsf@gmail.com> (Pierre Neidhardt's message of "Wed, 01 Nov 2017 23:19:44 +0100")
Pierre Neidhardt <ambrevar@gmail.com> writes:
> The `push-mark' function allows for duplicate marks. I fail to see a
> use case, but otherwise I think it's rather inconvenient:
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I think the argument for not filtering duplicates is that it makes
traversing the history less predictable -- if you do two point-setting
commands, you know that you have to pop the stack twice to get back to
before that.
And we can't change the default of such a basic command, because it'd
annoy too many people. (If somebody wants push-mark to filter
duplicates, it'd be easy to add advice to push-mark to do that.)
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-02-08 6:24 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfstub7z.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=29110@debbugs.gnu.org \
--cc=ambrevar@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.