From: Brady Trainor <algebrat@uw.edu>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: calfw-org, view single org file; very ugly hack
Date: Mon, 21 Apr 2014 00:04:58 -0700 [thread overview]
Message-ID: <5354C31A.8080108@uw.edu> (raw)
In-Reply-To: <87ha5oqzlv.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 2532 bytes --]
On 04/19/2014 11:33 PM, Bastien wrote:
> Brady Trainor <algebrat@uw.edu> writes:
>
>> Was there a better way (outside of joining development of
>> calfw-org)?
>
> PS: Joining forces for development always seems like a good idea :)
>
Of course, Bastien you have answered this question well in 2007. Link:
http://lists.gnu.org/archive/html/help-gnu-emacs/2007-10/msg00708.html
That is, I tried several things, and I'm ending up with pretty much the
recipe you describe.
I can use icalendar.el to simply convert .ics files to diary format.
I can cut and paste between a diary and org-mode file if I want to. I
can simply edit the .ics calendar from another app if I feel it's
easier. I could even view the .ics file in Emacs with calfw-ical. I
could compare these dates with plain text (diary and org-mode),
calfw-ical, calfw-cal, calfw-org, and agenda-view.
I found the org-caldav too limiting in the syntax, as I'd like the
freedom to use more diary sexp in my org files (won't allow times with
diary sexp at this time). My use of org-mode is just to organic right
now, so I prefer less restrictions by my use of .ics files. There seem
to be many ical2org scripts out there, but I think I'd prefer at this
point to just shoot for a cleaner break between .ics and Emacs formats.
I do find the conversion from .ics to diary to be sufficient, and will
probably use this to empty out my .ics files from time to time and keep
records in plain text diary format.
I think this is more or less a simple enough and effective system for my
needs for now. And it should be flexible enough as well, if I want to
try a different calendaring system down the road.
Brady
#+BEGIN_SRC dot :file ./gv/caldiagram.png :cache yes :cmdline -Tpng
digraph {
{ rank = same
orgmode
diary
}
gcal -> ics [ dir = "both" label = "GCALDaemon (sync)" ]
// owncloud -> ics2 [ dir = "both" ]
// ics2 -> orgmode [ dir = "both" label = "org-caldav" ]
// ics2 [ label = "ics" ]
ics -> diary [ dir = "both"
label = "icalendar.el (manual)"
]
diary -> agendaview
// orgmode -> ics [ constraint = false
// label =
"org-export-icalendar-combine-agenda-files"
// ]
orgmode -> agendaview
// diary -> calendar
diary -> calfw
ics -> calfw
orgmode -> calfw [ constraint = false ]
}
#+END_SRC
[-- Attachment #2: caldiagram.png --]
[-- Type: image/png, Size: 29551 bytes --]
prev parent reply other threads:[~2014-04-21 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 1:04 calfw-org, view single org file; very ugly hack Brady Trainor
2014-04-20 6:33 ` Bastien
2014-04-21 7:04 ` Brady Trainor [this message]
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=5354C31A.8080108@uw.edu \
--to=algebrat@uw.edu \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@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 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).