From: Carsten Dominik <carsten.dominik@gmail.com>
To: Ian Barton <lists@manor-farm.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: iPhone ----> org-mode
Date: Tue, 24 Mar 2009 09:38:23 +0100 [thread overview]
Message-ID: <5C86EAAE-AE58-41A0-BF4B-0910B456A2E2@gmail.com> (raw)
In-Reply-To: <49C89A2B.60303@manor-farm.org>
On Mar 24, 2009, at 9:30 AM, Ian Barton wrote:
>>> This is nice, no more superfluous flat file... thanks!
>> I don't think so! Because if I see this correctly, your own
>> solution will allow new entries to be refiled to other files,
>> removed or archived, without the script adding them again. If you
>> do this in Ians solution, I think they will be added again.
> Theoretically my script shouldn't add things twice. It stores the
> item's guid as a PROPERTY and checks to see if the guid exists in
> the org file before it adds the item. I am assuming here that guids
> in reqall are unique.
Yes, I understand.
However, if the user refiles the task to a different file, that
information will be gone and the item re-added.
- Carsten
>
> Having investigated reqall a bit further, it seems that messages are
> assigned various categories e.g. "Note", "Meeting". The latest
> incarnation of my script will store the item from the rss feed in a
> file according to its category. When the script is a bit more
> stable, I'll upload it to github.
>
> I have also done some work in adapting the jabberbot that I use with
> my MythTV set up, so I can get a list of my tasks and post new one
> via Google Talk.
>
> Ian.
next prev parent reply other threads:[~2009-03-24 8:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 10:38 iPhone ----> org-mode Brad Bozarth
2009-03-22 13:52 ` Carsten Dominik
2009-03-23 8:32 ` Brad Bozarth
2009-03-23 13:47 ` Ian Barton
2009-03-24 0:43 ` Brad Bozarth
2009-03-24 7:37 ` Carsten Dominik
2009-03-24 8:30 ` Ian Barton
2009-03-24 8:38 ` Carsten Dominik [this message]
2009-03-24 10:20 ` Ian Barton
2009-03-24 7:03 ` Rob Weir
2009-03-25 5:56 ` Brad Bozarth
2009-03-25 8:00 ` Brad Bozarth
2009-03-22 21:23 ` John Rakestraw
2009-03-24 11:32 ` Carsten Dominik
2009-03-24 18:21 ` Brad Bozarth
2009-03-25 8:28 ` Carsten Dominik
2009-03-25 8:36 ` Carsten Dominik
2009-03-25 8:50 ` Brad Bozarth
2009-03-25 19:52 ` Carsten Dominik
2009-03-25 20:39 ` John Rakestraw
2009-03-25 20:40 ` Carsten Dominik
2009-03-25 9:06 ` Brad Bozarth
2009-03-25 9:09 ` Carsten Dominik
2009-03-25 9:25 ` Carsten Dominik
2009-03-25 9:35 ` Ian Barton
2009-03-25 10:57 ` William Henney
2009-03-26 15:39 ` Carsten Dominik
2009-03-26 17:07 ` William Henney
2009-03-26 18:20 ` Richard Riley
[not found] ` <71454fac0903261121u79e85c3bq2538a294701e4c78@mail.gmail.com>
2009-03-27 9:15 ` Carsten Dominik
2009-03-27 15:45 ` Sven Bretfeld
2009-03-27 17:29 ` Carsten Dominik
2009-03-27 18:07 ` David Bremner
2009-03-25 14:29 ` Bernt Hansen
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=5C86EAAE-AE58-41A0-BF4B-0910B456A2E2@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lists@manor-farm.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).