From: Thomas Shannon <tshanno@bearingthenews.com>
To: help-gnu-emacs@gnu.org
Subject: Re: What are Emacs best uses?
Date: Wed, 14 Aug 2013 03:21:16 -0500 [thread overview]
Message-ID: <m2ob90of7n.fsf@bearingthenews.com> (raw)
In-Reply-To: <87bo51mv8q.fsf@motoko.kusanagi> (W. Greenhouse's message of "Tue, 13 Aug 2013 16:05:41 +0000")
wgreenhouse@riseup.net (W. Greenhouse) writes:
>> Is it a good calendar? Can you easily collaborate with colleagues who
>> use Google Calendar?
>
> I find Org's agenda combined with the Emacs calendar to be very
> effective. In the past, it was easier to use Emacs to collaborate with
> GCal users, because there are several Elisp libraries to interface with
> the standard iCal API; today this has become more difficult because
> Google has discontinued its iCal support. The elimination of all
> third-party Google Calendar clients, the better to attract eyeballs to
> the web interface, cannot be far behind.
>
> My solution for the moment is to use my phone for any Google Calendar
> stuff (and other non-free API junk). The phone's calendar shows both
> GCal events with others and my private MobileOrg calendare events.
Thank you for this answer which caught me attention. I have thus far
resisted org mode for a few reasons one of which is that I have my own
system for keeping a diary and journal and I like using it. However, I
*would* like to be able to view my diary on my iPhone. Its not an
org-mode file per se. Just a regular text file (actually a LaTeX file).
Can mobileorg allow me to work with it?
Thanks,
Tom S.
next prev parent reply other threads:[~2013-08-14 8:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 17:05 What are Emacs best uses? Jorge
2013-08-12 18:52 ` Peter Dyballa
2013-08-13 4:04 ` Charles Philip Chan
2013-08-17 14:11 ` Jorge
2013-08-17 20:20 ` Charles Philip Chan
2013-08-18 10:31 ` Jorge
2013-08-19 11:09 ` Phillip Lord
2013-08-19 20:21 ` Charles Philip Chan
2013-08-19 2:46 ` Eric Abrahamsen
2013-08-13 11:30 ` Phillip Lord
2013-08-13 14:43 ` Drew Adams
2013-08-13 16:05 ` W. Greenhouse
2013-08-14 8:21 ` Thomas Shannon [this message]
2013-08-15 14:41 ` W. Greenhouse
2013-08-16 9:49 ` Thomas Shannon
2013-08-14 14:51 ` Ken Goldman
2013-08-14 19:04 ` Nikolay Kudryavtsev
2013-08-19 13:52 ` Luca Ferrari
[not found] ` <mailman.340.1376920365.10748.help-gnu-emacs@gnu.org>
2013-08-19 14:04 ` Sebastien Vauban
2013-08-19 14:35 ` Luca Ferrari
[not found] ` <mailman.342.1376922920.10748.help-gnu-emacs@gnu.org>
2013-08-20 8:25 ` Sebastien Vauban
2013-08-20 10:56 ` Luca Ferrari
[not found] ` <mailman.401.1376996210.10748.help-gnu-emacs@gnu.org>
2013-08-20 12:44 ` Sebastien Vauban
2013-08-21 1:58 ` Jason Rumney
2013-08-21 6:25 ` Luca Ferrari
[not found] <mailman.3062.1376327401.12400.help-gnu-emacs@gnu.org>
2013-08-12 18:08 ` Pascal J. Bourguignon
2013-08-12 18:45 ` Andreas Röhler
2013-08-13 13:34 ` Joe Corneli
2013-08-13 1:52 ` Emanuel Berg
2013-08-13 3:29 ` Rustom Mody
2013-08-13 11:52 ` Dan Espen
2013-08-13 12:27 ` Filipp Gunbin
[not found] ` <mailman.3116.1376396894.12400.help-gnu-emacs@gnu.org>
2013-08-13 12:33 ` Dan Espen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ob90of7n.fsf@bearingthenews.com \
--to=tshanno@bearingthenews.com \
--cc=help-gnu-emacs@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.
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).