all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: eefacm@gmail.com, 74438-done@debbugs.gnu.org
Subject: bug#74438: 29.1; global-mark-ring does not work as described
Date: Sat, 07 Dec 2024 14:02:46 +0200	[thread overview]
Message-ID: <86bjxnk8ex.fsf@gnu.org> (raw)
In-Reply-To: <a7593eb4-d02d-4992-ac9f-df05d5bed22f@gmail.com> (message from Nikolay Kudryavtsev on Sat, 23 Nov 2024 00:16:53 +0300)

> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Date: Sat, 23 Nov 2024 00:16:53 +0300
> 
> Don't get me wrong, I'm not trying to attack your use case in any way, 
> just trying to help you solve it in the most efficient way possible.
> 
> Also trying to make sure that your use-case is really affected by this 
> behavior. Because if I now understand correctly, this should only affect 
> you if you are breaking the "doing nothing else in between" constraint.
> 
> Anyway, I feel like you can easily get rid of the "doing nothing else in 
> between" limitation if you rework your code to just work with a 
> particular register.

No further comments, so I'm now closing this bug.





      reply	other threads:[~2024-12-07 12:02 UTC|newest]

Thread overview: 14+ 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
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
2024-12-07 12:02                   ` Eli Zaretskii [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=86bjxnk8ex.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74438-done@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 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.