From: "Robert P. Goldman" <rpgoldman@sift.info>
To: Bernt Hansen <bernt@norang.ca>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Request for suggestions: multiple revision control systems/repositories + org
Date: Sun, 19 Dec 2010 21:46:30 -0600 [thread overview]
Message-ID: <1fad2a0e-2a3a-4f35-a019-42a1adea0454@email.android.com> (raw)
In-Reply-To: <87mxo1ciyv.fsf@norang.ca>
That is what I had done originally, but I thought mobile org required that all the org files be in the same directory. Was I wrong about that?
Thanks,
R
"Bernt Hansen" <bernt@norang.ca> wrote:
>Robert Goldman <rpgoldman@sift.info> writes:
>
>> I am looking for hints. I have a number of org files, typically one
>for
>> each major project plus two or three for my personal life.
>>
>> These must often live in different revision control systems: my work
>> projects, in particular, have different repositories; I have a main
>set
>> of org files for work in ~/org/, tracked by my employers' svn;
>> occasionally, I do something outside, like work on a paper with
>someone
>> outside my company in a dedicated git repo; and I'd like to stuff my
>> personal materials off in a git repo of my own.
>>
>> I have been pulling all of these together into my ~/org directory,
>using
>> symbolic links, for the benefit of mobile org. That is, my ~/org
>> directory has my main work org files, plus links to a bunch of
>others.
>>
>> That works well for syncing with mobile org. Unfortunately, it's a
>mess
>> for Emacs's version control mode. VC mode sees the .svn directory in
>> that place, and can handle the local files, but gets horribly
>confused
>> by the sym-linked files.
>>
>> Anyone have a similar need to gather together a mess of org files,
>and
>> have a cleaner solution?
>>
>> Extra credit if you have a way of creating the same set of symlinks
>on
>> more than one machine! ;-)
>
>How about keeping the separate projects in separate repositories and
>just add the files from those multiple projects to your
>org-agenda-files
>variable?
>
>Then you see a consolidated view of multiple org projects (and the
>files
>that contribute to that view can be individually set per machine - you
>don't need all projects for all machines - but any repositories that
>are
>available can contribute to your agenda.
>
>Each of the projects are completely independent and don't need to know
>about each other - just the org-agenda-files variable pulls them into
>your agenda view.
>
>Regards,
>Bernt
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2010-12-20 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 0:13 Request for suggestions: multiple revision control systems/repositories + org Robert Goldman
2010-12-20 0:31 ` suvayu ali
2010-12-20 1:48 ` Bernt Hansen
2010-12-20 3:46 ` Robert P. Goldman [this message]
2010-12-20 4:25 ` Bernt Hansen
2010-12-20 7:03 ` Rémi Vanicat
2010-12-20 14:46 ` Robert Goldman
2010-12-20 16:35 ` Matt Lundin
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=1fad2a0e-2a3a-4f35-a019-42a1adea0454@email.android.com \
--to=rpgoldman@sift.info \
--cc=bernt@norang.ca \
--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).