emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ethan Ligon <ligon@are.berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: org-feeds, atom, authentication & gdata
Date: Wed, 18 Aug 2010 04:47:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100818T063435-296@post.gmane.org> (raw)

I've been messing around in an ineffectual way with better ways to get
data from various google services (importantly gcalender and gmail)
into org.

I'd like gcalendar to talk to calendar, and I'd like gmail to feed
threads into headings.  The latter seems very close to the idea behind
org-feeds.

I long ago hacked together a system for gcalendar that involved a wget
on an *.ics file and some elisp to get this into calendar entries.
This works, in a hackish way, but is neither elegant nor particularly
robust.

I think that a much better system would be to use org-feeds to
subscribe to the atom feed that gcalendar provides.  But I don't see
how org-feeds manages authentication, which would be necessary for
this or other (e.g., gmail services). 

T. V. Raman posted a couple of years ago 
(http://article.gmane.org/gmane.emacs.orgmode/3499/) regarding code
he'd written to read google's atom feeds.  This seems like a huge step
in the right direction, but my elisp-fu isn't strong enough to manage
the additional steps of integrating this into org-mode.

Has anyone else tackled this problem?  I'm used to discovering that
all my clever ideas about ways to extend org's functionality have
already been thought of, so I'm expecting one of you to point me to a
thread from three years ago and point to the code that's sitting right
there in contrib.

Thanks!
-Ethan

             reply	other threads:[~2010-08-18  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  4:47 Ethan Ligon [this message]
2010-08-18  9:43 ` org-feeds, atom, authentication & gdata Bastien
2010-08-18 10:16   ` Eric S Fraga
2010-08-18 10:23     ` Bastien
2010-08-18 10:42       ` Eric S Fraga

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=loom.20100818T063435-296@post.gmane.org \
    --to=ligon@are.berkeley.edu \
    --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).