From: Sean McAfee <eefacm@gmail.com>
To: 74438@debbugs.gnu.org
Subject: bug#74438: 29.1; global-mark-ring does not work as described
Date: Fri, 22 Nov 2024 10:48:33 -0800 [thread overview]
Message-ID: <CANan03bjW-mohB0xprJ8R6aLtpfFELWjBSrV4maJgw5wt5YnGA@mail.gmail.com> (raw)
In-Reply-To: <64684e77-0a4d-41b7-b24d-842f6db2b151@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On Fri, Nov 22, 2024 at 4:39 AM Nikolay Kudryavtsev <
nikolay.kudryavtsev@gmail.com> wrote:
> But be aware that you're never really safe if you're relying on the mark
> ring here. If json-diff is an interactive command, nothing is stopping
> the user from pushing another mark to the ring in between of specifying
> file-a and file-b.
Yes. The command is intended to be used after setting a mark at the start
of a JSON sexp and moving to the start of a JSON sexp somewhere else, and
doing nothing else in between.
> Also, I don't know where did you get the last-global-mark thing, it's
> not something that's in the Emacs 29 or 30's core.
>
Indeed not. It's from the workaround I described in this thread just
yesterday.
Welp, I'm done. I've invested more effort into this bug report than I ever
thought would be necessary. It's the second time in a row that I've
reported a bug to a free software project and had it devolve into me having
to defend my use case. Fix the code or the docs, or don't. I'll just use
my workaround.
[-- Attachment #2: Type: text/html, Size: 1650 bytes --]
next prev parent reply other threads:[~2024-11-22 18:48 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
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 [this message]
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=CANan03bjW-mohB0xprJ8R6aLtpfFELWjBSrV4maJgw5wt5YnGA@mail.gmail.com \
--to=eefacm@gmail.com \
--cc=74438@debbugs.gnu.org \
/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).