* What is the most practical workflow for capturing things in Mobileorg and later integrating them into the main files?
@ 2015-09-11 14:00 Jorge
2015-09-11 16:23 ` Ken Mankoff
2015-09-11 16:52 ` Ramon Diaz-Uriarte
0 siblings, 2 replies; 4+ messages in thread
From: Jorge @ 2015-09-11 14:00 UTC (permalink / raw)
To: emacs-orgmode
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: What is the most practical workflow for capturing things in Mobileorg and later integrating them into the main files?
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
2015-09-13 15:29 ` Jorge
2015-09-11 16:52 ` Ramon Diaz-Uriarte
1 sibling, 1 reply; 4+ messages in thread
From: Ken Mankoff @ 2015-09-11 16:23 UTC (permalink / raw)
To: Jorge; +Cc: emacs-orgmode
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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: What is the most practical workflow for capturing things in Mobileorg and later integrating them into the main files?
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
@ 2015-09-11 16:52 ` Ramon Diaz-Uriarte
1 sibling, 0 replies; 4+ messages in thread
From: Ramon Diaz-Uriarte @ 2015-09-11 16:52 UTC (permalink / raw)
To: Jorge; +Cc: emacs-orgmode
On Fri, 11-09-2015, at 16: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?
>
That is more or less what I do/what happens in my case:
I get a notification that flagged.org has changed (though I don't recall
ever having configured myself anything explicitly; I guess it is just that
the buffer is open). And when I feel like it, I visit it, add the info
wherever I need to, delete everything from it, and save flagged.org empty.
Best,
R.
> Regards
--
Ramon Diaz-Uriarte
Department of Biochemistry, Lab B-25
Facultad de Medicina
Universidad Autónoma de Madrid
Arzobispo Morcillo, 4
28029 Madrid
Spain
Phone: +34-91-497-2412
Email: rdiaz02@gmail.com
ramon.diaz@iib.uam.es
http://ligarto.org/rdiaz
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-09-13 15:29 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2015-09-13 15:29 ` Jorge
2015-09-11 16:52 ` Ramon Diaz-Uriarte
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).