emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gijs Hillenius <gijs@hillenius.net>
To: emacs-orgmode@gnu.org
Subject: Re: Syncing methods for org files and org-mobile.el
Date: Fri, 13 Jan 2017 12:00:22 +0100	[thread overview]
Message-ID: <87o9zb2pix.fsf@hillenius.net> (raw)
In-Reply-To: <87ziivdzy5.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 13 Jan 2017 10:19:46 +0000")

[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Friday, 13 Jan 2017 at 08:50, Anssi Saari wrote:
>> When I tried MobileOrg I think I used Dropbox. But since initiating
>> manual sync from Emacs seemed mandatory I just didn't get much use out
>> of MobileOrg.
>
> But automatic sync in Emacs should be quite straightforward and is
> independent of the mobile end.  You can use a timer, for instance:
>
> ,----[ C-h f run-with-idle-timer RET ]
> | run-with-idle-timer is an interactive compiled Lisp function in
> | ‘timer.el’.
> | 
> | (run-with-idle-timer SECS REPEAT FUNCTION &rest ARGS)
> | 
> | Perform an action the next time Emacs is idle for SECS seconds.
> | The action is to call FUNCTION with arguments ARGS.
> | SECS may be an integer, a floating point number, or the internal
> | time format returned by, e.g., ‘current-idle-time’.
> | If Emacs is currently idle, and has been idle for N seconds (N < SECS),
> | then it will call FUNCTION in SECS - N seconds from now.  Using
> | SECS <= N is not recommended if this function is invoked from an idle
> | timer, because FUNCTION will then be called immediately.
> | 
> | If REPEAT is non-nil, do the action each time Emacs has been idle for
> | exactly SECS seconds (that is, only once for each time Emacs becomes idle).
> | 
> | This function returns a timer object which you can use in ‘cancel-timer’.
> | 
> | [back]
> `----
>
>>
>> So whatever you want to provide, make sure sync is automatic. And
>> preferably supporting private sync options too.

I have this in my emacs init.el 

(run-at-time "10:15" 86400 'org-mobile-push)

This works in combination with a cron job (a few minutes later) that
syncs the files to my 'cloud', where my phone picks them up.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-01-13 11:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  3:30 Syncing methods for org files and org-mobile.el Sean Escriva
2017-01-12  9:31 ` Alan Schmitt
2017-01-12 15:48   ` Eric Abrahamsen
2017-01-13  8:50 ` Anssi Saari
     [not found] ` <f526a3a2b7c64704b31745155948bef4@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-13 10:19   ` Eric S Fraga
2017-01-13 11:00     ` Gijs Hillenius [this message]
2017-01-13 14:13     ` Anssi Saari
     [not found]     ` <5ac759095a61410cb97fa7addd9665b8@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-13 15:44       ` Eric S Fraga
2017-01-13 16:18         ` Nick Dokos
2017-01-16 14:48 ` Karl Voit
2017-01-16 22:05   ` FAb

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=87o9zb2pix.fsf@hillenius.net \
    --to=gijs@hillenius.net \
    --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).