From: John Magolske <listmail@b79.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Challenges around displaying phase of moon in calfw
Date: Wed, 31 May 2017 22:29:12 -0700 [thread overview]
Message-ID: <20170601052912.GB15070@s70206.gridserver.com> (raw)
In-Reply-To: <20170528081730.GA17308@s70206.gridserver.com>
* John Magolske <listmail@b79.net> [170528 02:05]:
> [...] the lunar phases show up in calfw, but for some
> reason the time is displayed twice, like so:
>
> 19:48 ◐ q1↑ 7:48pm (PDT)
> 14:40 ● Full 2:40pm (PDT)
> 12:46 ◯ New 12:46pm (PDT)
>
> I think what's going on is that each phase is considered an event
> which somehow gets prefixed with its time in 24hr format...
I'm wondering if this issue may be related to this post on emacs-devel:
calendar/diary/appt: diary-lunar-phases should not create appointments
Hi,
I have
&%%(diary-sunrise-sunset)
&%%(diary-lunar-phases)
which results in emacs nagging me about moon phases and sunsets.
I don't think this is right: I want to be able to see the times when the
lunar phases and sunsets happen (and, btw, moon rises and moon sets, but
they are not available), but I do not want to do anything when they
actually do happen.
Is there a way to prevent some diary entries containing times from being
interpreted as appointments?
url:
https://lists.gnu.org/archive/html/emacs-devel/2011-11/msg00329.html
no resolution...picked up again a few years later:
https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg01347.html
... still no resolution.
John
--
John Magolske
http://b79.net/contact
next prev parent reply other threads:[~2017-06-01 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 8:23 Challenges around displaying phase of moon in calfw John Magolske
2017-06-01 5:29 ` John Magolske [this message]
2017-06-01 14:43 ` Jude DaShiell
2017-06-01 14:51 ` Óscar Fuentes
2017-06-01 15:13 ` tomas
2017-06-01 15:40 ` Jude DaShiell
2017-06-01 16:05 ` Óscar Fuentes
2017-06-01 20:30 ` John Ankarström
2017-06-04 2:13 ` John Magolske
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=20170601052912.GB15070@s70206.gridserver.com \
--to=listmail@b79.net \
--cc=help-gnu-emacs@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 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.