From: Stig Brautaset <stig@brautaset.org>
To: emacs-orgmode@gnu.org
Subject: Best strategy for sharing agenda between two machines?
Date: Mon, 24 Feb 2020 21:04:52 +0000 [thread overview]
Message-ID: <m27e0bwvbf.fsf@brautaset.org> (raw)
Hi,
I use Org mode & agenda on both my personal and work machines, in a
private git repo repository. I use auto-commit and push automatically
from each machine. It works alright. New items go in inbox.org, and I
refile most to tasks.org, which has a structure a little like this:
* Home :@home:
** TODO Some task to do at home
** TODO Another task to do at home
* Work :@work:
** TODO A task to do at work
** TODO Another work task
* TODO Some task that is not inherently work/home
* WAITING Another task that blurs the barriers
The different sections for Home and Work means that there are not too
many merge conflicts. However, inbox.org is a different matter. My todo
template adds a LOGBOOK with an `Added' property, and it's almost
impossible to resolve the conflicts that result.
I see that
https://orgmode.org/worg/org-contrib/gsoc2012/student-projects/git-merge-tool/
sadly never produced a tool. But I'm wondering if people have some
strategy for how to best deal with git conflicts (perhaps a non-default
merge strategy works better with Org?) or maybe even better: how not to
create conflicts in the first place!
I could use a different default agenda file for each machine, since the
inbox.org is worst affected. Is anyone doing this? I could extend this
to use {work,home}_tasks.org too, but I kinda like having that "neither
@work nor @home" option... Decisions decisions.
Stig
next reply other threads:[~2020-02-24 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 21:04 Stig Brautaset [this message]
2020-02-25 17:12 ` Best strategy for sharing agenda between two machines? Günter Lichtenberg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m27e0bwvbf.fsf@brautaset.org \
--to=stig@brautaset.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.