From: pietru@caramail.com
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Toggle appointment notification
Date: Fri, 4 Dec 2020 00:59:06 +0100 [thread overview]
Message-ID: <trinity-c719434e-5d27-499e-9eea-56ea0fafed5e-1607039946666@3c-app-mailcom-bs11> (raw)
In-Reply-To: <875z5ibigp.fsf@web.de>
> Sent: Friday, December 04, 2020 at 12:03 AM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Toggle appointment notification
>
> pietru@caramail.com writes:
>
> > Fair enough, but the response could easily be interpreter to be
> > addressed to us rather than to every emacs user. I understand we
> > asked for points of view, but that was after Michael informed us that
> > he was planning some work on diary appointments and he asked me for
> > suggestions on our planned use and strategy. Emanuel confirmed that
> > changes will became part of the official release.
>
> I'm sorry, but there was some misunderstanding. I'm a user of calendar,
> diary, org and diary, and plan to donate some related stuff to Gnu
> Elpa. I dunno to what Emanuel answered.
He said to me that changes will be Gnu Software. I know Gnu Elpa
is a Package Archive, but not familiar with the details.
For official purposes, we would like to record what we use as part
of the Official Gnu Software. Else, a lot of questions will be asked
and would have to answer to.
> I'm interested in making diary expressions more common and useful. I
> want to have something better than appointments, and a better
> integration of these things with Org. But I'm not an Org developer.
I will have to see who is involved with what, but understand if you are
not an org developer. Would this mean we concentrate on Diary and Calendar?
I think the work was done quite long ago, and interest in them stopped.
> I'm just curious about how people are currently using this stuff, as an
> inspiration for the direction of development of my stuff, so that it may
> end up in something useful for others.
>
> Regards,
>
> Michael.
>
>
>
next prev parent reply other threads:[~2020-12-03 23:59 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 3:47 Toggle appointment notification pietru
2020-12-01 4:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-01 5:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-01 18:35 ` pietru
2020-12-01 18:52 ` Jean Louis
2020-12-01 19:01 ` pietru
2020-12-01 19:13 ` pietru
2020-12-01 19:23 ` Jean Louis
2020-12-01 19:38 ` pietru
2020-12-01 19:53 ` tomas
2020-12-01 19:58 ` pietru
2020-12-02 15:00 ` pietru
2020-12-02 15:15 ` pietru
2020-12-02 15:47 ` Michael Heerdegen
2020-12-02 15:58 ` pietru
2020-12-02 17:39 ` pietru
2020-12-02 17:46 ` pietru
2020-12-03 1:39 ` Michael Heerdegen
2020-12-03 2:18 ` pietru
2020-12-03 22:32 ` Michael Heerdegen
2020-12-03 1:50 ` Michael Heerdegen
2020-12-03 2:14 ` pietru
2020-12-03 3:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-03 4:06 ` pietru
2020-12-03 4:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-03 22:38 ` Michael Heerdegen
2020-12-12 1:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 1:26 ` Christopher Dimech
2020-12-12 1:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 1:48 ` Christopher Dimech
2020-12-12 1:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 1:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 3:55 ` Michael Heerdegen
2020-12-12 4:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 22:42 ` Michael Heerdegen
2020-12-17 4:31 ` Michael Heerdegen
2020-12-03 2:17 ` daniela-spit
2020-12-03 3:19 ` Pankaj Jangid
2020-12-03 5:35 ` pietru
2020-12-03 15:19 ` pietru
2020-12-03 17:09 ` Jean Louis
2020-12-03 17:20 ` pietru
2020-12-03 17:58 ` Jean Louis
2020-12-03 18:29 ` pietru
2020-12-03 19:41 ` Jean Louis
2020-12-03 19:58 ` Jean Louis
2020-12-03 20:23 ` pietru
2020-12-03 20:38 ` Jean Louis
2020-12-03 21:30 ` Christopher Dimech
2020-12-03 22:43 ` Arthur Miller
2020-12-03 22:51 ` Christopher Dimech
2020-12-03 23:12 ` Michael Heerdegen
2020-12-03 23:03 ` Michael Heerdegen
2020-12-03 23:49 ` Jean Louis
2020-12-04 0:28 ` pietru
2020-12-04 5:59 ` Jean Louis
2020-12-04 6:28 ` pietru
2020-12-04 7:11 ` Jean Louis
2020-12-03 23:59 ` pietru [this message]
2020-12-04 1:13 ` Michael Heerdegen
2020-12-04 1:39 ` pietru
2020-12-03 10:19 ` Jean Louis
2020-12-01 21:44 ` Michael Heerdegen
2020-12-02 8:41 ` tomas
2020-12-02 12:05 ` Christopher Dimech
2020-12-02 12:37 ` tomas
2020-12-02 13:15 ` Christopher Dimech
2020-12-02 13:52 ` tomas
2020-12-02 14:10 ` Christopher Dimech
2020-12-02 14:20 ` Robert Pluim
2020-12-02 15:04 ` Christopher Dimech
2020-12-02 15:08 ` Jean Louis
2020-12-02 21:14 ` tomas
2020-12-02 21:41 ` Jean Louis
2020-12-02 22:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 22:54 ` Jean Louis
2020-12-02 15:25 ` Drew Adams
2020-12-02 15:04 ` Jean Louis
2020-12-02 1:54 ` daniela-spit
2020-12-02 2:47 ` Michael Heerdegen
2020-12-02 3:04 ` daniela-spit
2020-12-02 3:23 ` Michael Heerdegen
2020-12-02 4:16 ` daniela-spit
2020-12-02 4:26 ` daniela-spit
2020-12-02 4:59 ` Jean Louis
2020-12-01 9:13 ` Andreas
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-c719434e-5d27-499e-9eea-56ea0fafed5e-1607039946666@3c-app-mailcom-bs11 \
--to=pietru@caramail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.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).