From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Shynur Xie <one.last.kiss@outlook.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"65700@debbugs.gnu.org" <65700@debbugs.gnu.org>
Subject: bug#65700: time when gcs-done is updated needs to be clarified
Date: Thu, 07 Sep 2023 12:52:50 -0400 [thread overview]
Message-ID: <jwvedjadj5k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <PH0PR11MB747079C03D3AA87ABD1CA6DFD7EEA@PH0PR11MB7470.namprd11.prod.outlook.com> (Shynur Xie's message of "Thu, 7 Sep 2023 15:23:08 +0000")
>> Hmm... that doesn't really explain in which way this affects your
>> code.
> It does.
At least not in a way that I understand, then :-(
>> `gcs-done` will be always smaller by 1
> That's it.
Why do you care if it starts at 4 rather than at 5?
Maybe we should make it start at some random number instead, to make it
clear that 0 is meaningless :-)
Stefan
next prev parent reply other threads:[~2023-09-07 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 13:00 bug#65700: time when gcs-done is updated needs to be clarified Shynur Xie
2023-09-07 9:14 ` Eli Zaretskii
2023-09-07 13:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 14:35 ` Shynur Xie
2023-09-07 14:47 ` Eli Zaretskii
2023-09-07 15:23 ` Shynur Xie
2023-09-07 16:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-07 17:19 ` Shynur Xie
2023-09-12 10:14 ` Shynur Xie
2023-09-12 12:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 18:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 14:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 15:08 ` Eli Zaretskii
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=jwvedjadj5k.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=65700@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=one.last.kiss@outlook.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.