From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: 74438@debbugs.gnu.org, eefacm@gmail.com
Subject: bug#74438: 29.1; global-mark-ring does not work as described
Date: Wed, 20 Nov 2024 16:35:13 +0200 [thread overview]
Message-ID: <86o72arn1a.fsf@gnu.org> (raw)
In-Reply-To: <cf1cea06-4318-4f06-b132-7d58d2d63a75@gmail.com> (message from Nikolay Kudryavtsev on Wed, 20 Nov 2024 13:18:00 +0300)
> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Date: Wed, 20 Nov 2024 13:18:00 +0300
>
> Emacs won't allow you to set multiple marks in the same position, it's just going to activate the current mark.
> Hence your reproduction recipe can be simplified to:
>
> 1 C-x C-f foo
> 2 C-SPC => Mark set
> 3 C-SPC => Mark deactivated
> 4 C-SPC => Mark activated
> 5 C-SPC => Mark deactivated
> 6 C-SPC => Mark activated
>
> See how you're not getting "Mark set" any time after the first message?
Yes, technically, it doesn't set a mark, it just activates the
existing mark. And the global-mark-ring section says that Emacs
pushes a mark on the ring when it sets the mark in some buffer. Which
is not what happens here.
> Maybe a couple of sentences should be added to the manual regarding this behavior, because mark ring is
> often a source of confusion for the new users.
If you can tell what are the confusions, I could work on clarifying
them.
next prev parent reply other threads:[~2024-11-20 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 20:24 bug#74438: 29.1; global-mark-ring does not work as described Sean McAfee
2024-11-20 10:18 ` Nikolay Kudryavtsev
2024-11-20 14:35 ` Eli Zaretskii [this message]
2024-11-21 7:51 ` Nikolay Kudryavtsev
2024-11-21 9:49 ` Eli Zaretskii
2024-11-20 19:16 ` Sean McAfee
2024-11-21 8:09 ` Nikolay Kudryavtsev
2024-11-21 19:49 ` Sean McAfee
2024-11-21 20:32 ` Nikolay Kudryavtsev
2024-11-21 21:03 ` Sean McAfee
2024-11-22 12:39 ` Nikolay Kudryavtsev
2024-11-22 18:48 ` Sean McAfee
2024-11-22 21:16 ` Nikolay Kudryavtsev
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=86o72arn1a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74438@debbugs.gnu.org \
--cc=eefacm@gmail.com \
--cc=nikolay.kudryavtsev@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 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).