* bug#65512: 30.0.50; Docstring current-idle-time: PSEC?
@ 2023-08-25 3:27 Michael Heerdegen
2023-08-25 5:54 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Michael Heerdegen @ 2023-08-25 3:27 UTC (permalink / raw)
To: 65512
Hello,
C-h f current-idle-time
| Return the current length of Emacs idleness, or nil.
| [...]
| PSEC is a multiple of the system clock resolution.
But PSEC is not an argument of that function and appears nowhere else in
the docstring.
TIA,
Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#65512: 30.0.50; Docstring current-idle-time: PSEC?
2023-08-25 3:27 bug#65512: 30.0.50; Docstring current-idle-time: PSEC? Michael Heerdegen
@ 2023-08-25 5:54 ` Eli Zaretskii
2023-08-25 23:04 ` Michael Heerdegen
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2023-08-25 5:54 UTC (permalink / raw)
To: Michael Heerdegen; +Cc: 65512
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Fri, 25 Aug 2023 05:27:41 +0200
>
> C-h f current-idle-time
> | Return the current length of Emacs idleness, or nil.
> | [...]
> | PSEC is a multiple of the system clock resolution.
>
> But PSEC is not an argument of that function and appears nowhere else in
> the docstring.
PSEC is not an argument, it's the last member of a 4-member list. I
hope I've clarified this now in the doc string.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#65512: 30.0.50; Docstring current-idle-time: PSEC?
2023-08-25 5:54 ` Eli Zaretskii
@ 2023-08-25 23:04 ` Michael Heerdegen
2023-08-26 5:28 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Michael Heerdegen @ 2023-08-25 23:04 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 65512
Eli Zaretskii <eliz@gnu.org> writes:
> PSEC is not an argument, it's the last member of a 4-member list. I
> hope I've clarified this now in the doc string.
Thanks.
Is there a reason why we mention this detail that's also in the
`current-time' docstring, but not others? With other words: could we
just remove the mention of PSEC? Just wondering.
Thx,
Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#65512: 30.0.50; Docstring current-idle-time: PSEC?
2023-08-25 23:04 ` Michael Heerdegen
@ 2023-08-26 5:28 ` Eli Zaretskii
2023-08-27 4:17 ` Michael Heerdegen
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2023-08-26 5:28 UTC (permalink / raw)
To: Michael Heerdegen; +Cc: 65512
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 65512@debbugs.gnu.org
> Date: Sat, 26 Aug 2023 01:04:01 +0200
>
> Is there a reason why we mention this detail that's also in the
> `current-time' docstring, but not others? With other words: could we
> just remove the mention of PSEC? Just wondering.
In general, the 4-member list doesn't have to satisfy that condition,
and the doc string refers to current-time only for the possible
formats of the value, not for anything else.
Also, this remark was always in the doc string of current-idle-time,
so it's possible it is important to some applications. So IMO we
should leave that there.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#65512: 30.0.50; Docstring current-idle-time: PSEC?
2023-08-26 5:28 ` Eli Zaretskii
@ 2023-08-27 4:17 ` Michael Heerdegen
0 siblings, 0 replies; 5+ messages in thread
From: Michael Heerdegen @ 2023-08-27 4:17 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 65512-done
Hello Eli,
ok, in that case thank you for your fix. I'm closing this bug.
Michael.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-08-27 4:17 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-25 3:27 bug#65512: 30.0.50; Docstring current-idle-time: PSEC? Michael Heerdegen
2023-08-25 5:54 ` Eli Zaretskii
2023-08-25 23:04 ` Michael Heerdegen
2023-08-26 5:28 ` Eli Zaretskii
2023-08-27 4:17 ` Michael Heerdegen
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).