unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 61460@debbugs.gnu.org
Subject: bug#61460: 30.0.50; Calendar shows eclipse for quarter moon
Date: Tue, 14 Feb 2023 06:30:33 +0100	[thread overview]
Message-ID: <875yc4q0ee.fsf@web.de> (raw)
In-Reply-To: <uzg9hc3jr@gentoo.org> (Ulrich Mueller's message of "Mon, 13 Feb 2023 10:34:00 +0100")

Ulrich Mueller <ulm@gentoo.org> writes:

> https://en.wikipedia.org/wiki/Argument_of_latitude
> | It is the sum of the more commonly used true anomaly and argument
> | of periapsis.

I did not find good discussions of the eclipse limits in the English
Wikipedia version; I found good explanations in German however:

  https://de.wikipedia.org/wiki/Finsternis-Limit#Finsternis-Limite_bei_Sonnenfinsternissen

  https://de.wikipedia.org/wiki/Finsterniszyklus

AFAIU you can indeed use similar values for lunar vs. solar eclipses.
But in the case of the moon, we are then including penumbral lunar
eclipses - in the total version see

  https://en.wikipedia.org/wiki/Total_penumbral_lunar_eclipse

which are probably not really interesting (moon gets only a bit darker).

The limits for an eclipse to happen are not really constant, but taking
this into account is probably out of scope of the currently available
code in lunar.el.

Michael.





  parent reply	other threads:[~2023-02-14  5:30 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 19:57 bug#61460: 30.0.50; Calendar shows eclipse for quarter moon Ulrich Mueller
2023-02-12 20:07 ` Ulrich Müller
2023-02-12 20:19   ` Eli Zaretskii
2023-02-12 21:13     ` Ulrich Mueller
2023-02-13  3:24       ` Eli Zaretskii
2023-02-13  3:25   ` Michael Heerdegen
2023-02-13  4:52     ` Michael Heerdegen
2023-02-13  5:13     ` Michael Heerdegen
2023-02-13  6:01       ` Michael Heerdegen
2023-02-13  7:28       ` Ulrich Mueller
2023-02-13  8:13         ` Michael Heerdegen
2023-02-13  8:52           ` Michael Heerdegen
2023-02-13  9:34             ` Ulrich Mueller
2023-02-13 10:04               ` Michael Heerdegen
2023-02-13 13:03                 ` Eli Zaretskii
2023-02-13 13:30                   ` Ulrich Mueller
2023-02-13 14:05                     ` Eli Zaretskii
2023-02-14  5:30               ` Michael Heerdegen [this message]
2023-02-14  7:59                 ` Ulrich Mueller
2023-02-14  9:15                   ` Michael Heerdegen
2023-02-14 10:22                     ` Ulrich Müller
2023-02-14 10:56                       ` Michael Heerdegen
2023-02-16 20:26                         ` Ulrich Müller
2023-02-17  5:25                           ` Michael Heerdegen
2023-02-17  7:03                             ` Ulrich Müller
2023-02-17  7:20                               ` Michael Heerdegen
2023-02-18  5:53                                 ` Michael Heerdegen
2023-02-18  8:56                                   ` Ulrich Mueller
2023-02-18  9:16                                     ` Michael Heerdegen
2023-02-21 15:15                                       ` Michael Heerdegen
2023-02-22  9:00                                         ` Ulrich Mueller
2023-02-22  9:45                                           ` Andreas Schwab
2023-02-22 10:03                                           ` Michael Heerdegen
2023-02-22 11:32                                             ` Ulrich Mueller
2023-02-22 14:19                                               ` Michael Heerdegen
2023-02-22 15:46                                                 ` Ulrich Mueller
2023-02-22 16:26                                                   ` Michael Heerdegen
2023-02-25 16:13                                                     ` Michael Heerdegen
2023-02-14 13:31                       ` Eli Zaretskii
2023-02-14 10:49                     ` Ulrich Mueller
2023-02-13  6:21     ` Ulrich Mueller
2023-02-13  7:08       ` Michael Heerdegen

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=875yc4q0ee.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=61460@debbugs.gnu.org \
    --cc=ulm@gentoo.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).