From: Daniel Clemente <n142857@gmail.com>
To: Tristan Strange <tristan.strange@gmail.com>
Cc: Org-mode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: How are people handling their calendars?
Date: Mon, 24 Oct 2016 15:17:24 +0200 [thread overview]
Message-ID: <CAJKAhPB8OW48eFFt-25P4poPXgLNmYoSC8_gi3Xsx23b3FUP2A@mail.gmail.com> (raw)
In-Reply-To: <CABQkF0mCxH57kXRSojbHYh9mKvj4rr-d1GPg1Gj2TknWZJwdsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
I only tried the visualization part a few days ago, by exporting to
iCalendar (.ics). But the process was too slow: after fixing some export
errors it was still taking more than 1 hour for a large .org file.
After that I wanted to use Iceowl/Lightning (extension to
Icedove/Thunderbird) to open the .ics. But there might be better .ics
browsers (that run in local).
On Mon, Oct 24, 2016 at 1:36 AM, Tristan Strange <tristan.strange@gmail.com>
wrote:
> The world of calendars is a murky one isn't it? After a couple of weeks of
> fiddling around I finally decided I'd keep my TODO's, deadlines, etc in a
> TODO.org and have org-gcal fetch (note not synchronise) my calendar from
> Google.
>
> That way I do all my daily TODO mangling in orgmode, edit calendar when on
> Desktop or Mobile and pull results in to org agenda for easier viewing.
>
> So how do you lot handle your calendars?
>
> Do any of you have a working two way set up with CalDAV or anything?
>
> Cheers,
> Tristan
>
[-- Attachment #2: Type: text/html, Size: 1425 bytes --]
next prev parent reply other threads:[~2016-10-24 13:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 23:36 How are people handling their calendars? Tristan Strange
2016-10-24 4:20 ` zv
2016-10-24 5:10 ` B.V. Raghav
2016-10-24 6:07 ` Eric Abrahamsen
2016-10-24 6:38 ` Saša Janiška
2016-10-24 7:06 ` Eric Abrahamsen
2016-10-24 11:20 ` Saša Janiška
2016-10-25 5:34 ` Eric Abrahamsen
2016-10-26 18:42 ` Eric Abrahamsen
2016-10-24 10:02 ` Samuel Loury
2016-10-24 13:17 ` Daniel Clemente [this message]
2016-10-24 17:27 ` Philip Hudson
2016-10-25 0:49 ` Scott Randby
[not found] ` <da1598bae16f4c389f9d6318622c0ad0@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-25 9:59 ` Eric S Fraga
2016-10-25 15:31 ` Scott Randby
[not found] ` <21ce04ca420949f3bbc7c34f027a80ed@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-25 19:50 ` Eric S Fraga
[not found] <55f8276ed2d044288dc1602a9a10f9e9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-24 12:20 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
2016-10-25 10:49 Bartholomaios Edessa
2016-10-25 11:09 ` Saša Janiška
2016-10-25 16:26 Bala Ramadurai
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJKAhPB8OW48eFFt-25P4poPXgLNmYoSC8_gi3Xsx23b3FUP2A@mail.gmail.com \
--to=n142857@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tristan.strange@gmail.com \
/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/org-mode.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).