From: Magnus Henoch <magnus.henoch@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-feed: support Atom
Date: Wed, 15 Apr 2009 15:43:41 +0100 [thread overview]
Message-ID: <84k55m3rky.fsf@linux-b2a3.site> (raw)
In-Reply-To: 4209AE59-A7BF-4352-BBCA-EA26E0C8CB75@gmail.com
Carsten Dominik <carsten.dominik@gmail.com> writes:
> Hi Magnus,
>
> On Apr 15, 2009, at 3:00 PM, Magnus Henoch wrote:
>
>> I hacked org-feed to make it support different parsers, and wrote a
>> simple Atom parser.
>
>
> This sounds very good!
>
> However, it does not mean anything to me. :-)
>
> Web-dump as I am, I have no clue what
> "Atom" means. And since I would like to understand
> the changes, would you mind explaining what this is
> useful for, and maybe show an example?
Sure. The great thing about standards is that there are so many of them
to choose from, and feeds are no exception. The current version of
org-feed.el supports RSS - I'm not sure exactly which version;
http://en.wikipedia.org/wiki/Rss#Variants lists six versions of RSS with
various levels of intercompatibility. The Atom format is an attempt to
clear up this mess by starting from scratch, and some web applications
have only Atom feeds.
One example of an Atom feed can be found at
https://bugzilla.mozilla.org/. Go to "Bugs Filed Today", get the feed
by clicking the "radio wave" icon in the Firefox location bar, and use
that URL for org-feed-alist. You will need my patches for that to work,
and "Parse Feed" and "Parse Entry" need to be set to the Atom ones.
Then, you have a low-maintenance list of Mozilla bugs in an Org-mode
page.
>> I have assigned copyright for Emacs; would that be good enough for
>> Orgmode?
>
> If it says "future changes" and is for Emacs, yes, this will be
> sufficient.
It does, yes.
Magnus
next prev parent reply other threads:[~2009-04-15 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 13:00 org-feed: support Atom Magnus Henoch
2009-04-15 13:26 ` Carsten Dominik
2009-04-15 14:43 ` Magnus Henoch [this message]
2009-04-15 14:58 ` Carsten Dominik
2009-04-15 14:42 ` Carsten Dominik
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=84k55m3rky.fsf@linux-b2a3.site \
--to=magnus.henoch@gmail.com \
--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).