emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Jorge <jorge13515@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: What is the most practical workflow for capturing things in Mobileorg and later integrating them into the main files?
Date: Fri, 11 Sep 2015 12:23:29 -0400	[thread overview]
Message-ID: <m2y4gcx6v2.fsf@gmail.com> (raw)
In-Reply-To: <CAJR3QndELXE7QFy3Xaho7k5gNuGhU1GdmmjwCj75N+vwj=j4Ng@mail.gmail.com>

Hi Jorge,

My mobile capture work flow is:

1) Automatically pull whenever changes are made

2) Pulled items go into "refile.org"

3) refile.org tags all items as REFILE with:
   #+FILETAGS: REFILE
   as the top line
   
4) My default (custom) agenda shows a REFILE section if and only if it exists.

In more detail,

1)

;; Pull whenever mobileorg.org changes http://stackoverflow.com/questions/3456782/emacs-lisp-how-to-monitor-changes-of-a-file-directory
(defvar monitor-attributes nil "Cached file attributes to be monitored.")
(defun install-monitor (file secs)
  (run-with-timer
   0 secs
   (lambda (f p)
     (let ((att (elt (file-attributes f) 5)))
       (unless (or (null monitor-attributes) (equalp monitor-attributes att))
         (org-mobile-pull)
		 (org-mobile-push)
		 )
       (setq monitor-attributes att)))
   file secs))
(defvar monitor-timer (install-monitor (concat org-mobile-directory "/mobileorg.org") 5)   "Check if MobileOrg/mobileorg.org is changed every 5s.")


And 4)

  (setq org-agenda-custom-commands
        '(
          ("c" "My Custom Agenda"
           (
            (tags "REFILE" ((org-agenda-overriding-header "REFILE")))
            ...etc...

AND

https://lists.gnu.org/archive/html/emacs-orgmode/2015-06/msg00266.html

to only show the REFILE section if items are there.

Hope this helps,

  -k.


On 2015-09-11 at 10:00, Jorge <jorge13515@gmail.com> wrote:
> Hi.  When I capture something in MobileOrg, it by default is classified as
> "Captures" and, when I do org-mobile-pull, those captures /silently/ go into
> ~/org/from-mobile.org.  This is bad.
>
> So one workflow would be to write some code that warns me if
> ~/org/from-mobile.org is non-empty, and find a way of hooking it into
> org-mobile-pull.  Then:
> 1) Capture something in MobileOrg
> 2) Do org-mobile-pull
> 3) If the code I wrote as above warns me that ~/org/from-mobile.org is
>    non-empty, then visit it, go through the entries, fix them (adding more
>    information now that I have a real keyboard) and use org-refile.
>
> Is there a more practical and easier option?
>
> Regards

  reply	other threads:[~2015-09-11 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 14:00 What is the most practical workflow for capturing things in Mobileorg and later integrating them into the main files? Jorge
2015-09-11 16:23 ` Ken Mankoff [this message]
2015-09-13 15:29   ` Jorge
2015-09-11 16:52 ` Ramon Diaz-Uriarte

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=m2y4gcx6v2.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jorge13515@gmail.com \
    /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).