unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: Lunar Phases in Calendar
Date: Thu, 19 Nov 2020 13:05:18 +0100	[thread overview]
Message-ID: <trinity-d6b77fd1-e240-4a1b-b437-c5c80047fdc1-1605787517820@3c-app-mailcom-bs05> (raw)
In-Reply-To: <20201119090509.GA29352@tuxteam.de>

Trying to fit people's calendar together?  Impossible.  Stick with the moon
and with the sun my friend,  ;)

> Sent: Thursday, November 19, 2020 at 10:05 AM
> From: tomas@tuxteam.de
> To: help-gnu-emacs@gnu.org
> Subject: Re: Lunar Phases in Calendar
>
> On Thu, Nov 19, 2020 at 04:34:49AM +0100, Christopher Dimech wrote:
> > Not Complicated.  Just a ball rotating.
>
> That depends on whether you're talking about the
> moon itself (then "a ball rotating" is a pretty
> good approximation indeed, although, if you look
> closely, you're into N-body problems, but I don't
> have to tell that to /you/, I think ;-)
>
> Or whether you're approaching it from the viewpoint
> of human calendars, trying to make sense of several
> incommensurable (and not really constant) observational
> constants (solar day, solar year, lunar month) and
> to try to fit them into each other. There, the human
> creativity has been impressive indeed :-)
>
> So those kinds of "calendars" are, as Byung-Hee politely
> puts it, "complicated".
>
> Cheers
>  - t
>



  parent reply	other threads:[~2020-11-19 12:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 14:59 Lunar Phases in Calendar Christopher Dimech
2020-11-18 15:48 ` Jean Louis
2020-11-18 18:30   ` Michael Heerdegen
2020-11-18 19:00     ` Christopher Dimech
2020-11-18 20:30       ` Jean Louis
2020-11-18 20:12     ` Jean Louis
2020-11-18 17:18 ` Christopher Dimech
2020-11-18 17:56   ` Jean Louis
2020-11-18 18:08     ` Christopher Dimech
2020-11-18 20:36 ` Michael Heerdegen
2020-11-18 20:47   ` Christopher Dimech
2020-11-19  2:46 ` 황병희
2020-11-19  3:34   ` Christopher Dimech
2020-11-19  9:05     ` tomas
2020-11-19  9:32       ` Colin Baxter
2020-11-19 12:05       ` Christopher Dimech [this message]
2020-11-19 14:36         ` Jude DaShiell
2020-11-19 14:52           ` Christopher Dimech
2020-11-19 15:17           ` Jean Louis
2020-11-19 17:23             ` Jude DaShiell
2020-11-19 17:37               ` Christopher Dimech
2020-11-19 18:18                 ` Jude DaShiell
2020-11-19 18:21                   ` Jean Louis
2020-11-19 18:38                     ` Christopher Dimech
2020-11-19 18:32                   ` Christopher Dimech
2020-11-19 18:19                 ` Jean Louis
2020-11-19 18:35                   ` Christopher Dimech
2020-11-19 18:15               ` Jean Louis

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=trinity-d6b77fd1-e240-4a1b-b437-c5c80047fdc1-1605787517820@3c-app-mailcom-bs05 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tomas@tuxteam.de \
    /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.
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).