From: Ramon Diaz-Uriarte <rdiaz02@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 18:52:03 +0200 [thread overview]
Message-ID: <87613gnbkc.fsf@gmail.com> (raw)
In-Reply-To: <CAJR3QndELXE7QFy3Xaho7k5gNuGhU1GdmmjwCj75N+vwj=j4Ng@mail.gmail.com>
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
prev parent reply other threads:[~2015-09-11 16:52 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
2015-09-13 15:29 ` Jorge
2015-09-11 16:52 ` Ramon Diaz-Uriarte [this message]
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=87613gnbkc.fsf@gmail.com \
--to=rdiaz02@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).