emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jan Kybic <kybic@fel.cvut.cz>
To: emacs-orgmode@gnu.org
Subject: Re: DAG structure / hard links /  shared subtrees
Date: Fri, 30 Dec 2011 22:11:25 +0100	[thread overview]
Message-ID: <8739c1g3ya.fsf@fel.cvut.cz> (raw)
In-Reply-To: <87ty4iyzgy.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 30 Dec 2011 13:13:17 +0000")

>> I have a feature request. The structure of the org file is a tree. 
>> I wondered if it could be made a directed acyclic graph (DAG) instead. 

Thanks for the reaction. 

>or simply refile the notes?  I always go through the notes I have taken
>at a meeting after the meeting, in my case to define tasks etc.  You
>could refile all the notes into the proper places in the hierarchy at
>this point.  org has very nice refile support.

Yes, I am using a combination of refiling, tags, links and searches, and
it works. However, it looks fragile and ad hoc. As far as I see it, some things
just naturally can be classified using several hierarchies, like
something that concerns project A, was first discussed at meeting B and should
be consulted with person C. Where should I put it? I would like to be
able to find it in all three places. Moreover, I would like to prepare a
meeting with person C, make notes on the subject while we talk and then
have the notes available also when browsing the hierarchy of project A. 
I have to choose one of the three trees and use tags or whatever
other means to make it visible in the other two trees. If I forget to
tag it, it is lost, very difficult to find again.

>> c) I can create the meeting agenda dynamically, by assigning tags to
>>    projects and creating a sparse tree, e.g. from the Agenda
>>    buffer. However, this requires me to mark every issue to be discussed
>>    with a meeting-specific tag. I do not have much control over the order
>>    in which the issues appear. I cannot structure them. The generation
>>    takes time. And it is not straightforward to add new items to the
>>    meeting.
>
>I am not sure how the hard links mechanism you suggest above would help
>in this case?  Preparing an agenda can be difficult.  What you could do
>is have special TODO labels for issues that need to be discussed at the
>next meeting?
>

Even with such TODO labels, how do I sort them into the order I want?
With links, it is easy, I just link all the issues I want to discuss to
the meeting subtree, in the order I want.

Thanks for your help.

Jan

-- 
-------------------------------------------------------------------------
Jan Kybic <kybic@fel.cvut.cz>               tel. +420 2 2435 5721 or 5877
http://cmp.felk.cvut.cz/~kybic                              ICQ 200569450

      reply	other threads:[~2011-12-30 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22 10:11 DAG structure / hard links / shared subtrees Jan Kybic
2011-12-30 13:13 ` Eric S Fraga
2011-12-30 21:11   ` Jan Kybic [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=8739c1g3ya.fsf@fel.cvut.cz \
    --to=kybic@fel.cvut.cz \
    --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).