From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Multiple occurrence of tasks
Date: Sun, 08 Jan 2012 22:12:11 +0100 [thread overview]
Message-ID: <bedpt8xkdv.ln2@news.c0t0d0s0.de> (raw)
In-Reply-To: 87sjjqqduh.fsf@fester.com
Hello,
Mueen Nawaz <mailinglists@nawaz.org> writes:
> Michael Welle <mwe012008@gmx.net> writes:
>
>> to work on open tasks. My plan is to collect the tasks I want to work on
>> on a special tasksatfosdem.org file. How can I implement that? Copying
>> the tasks is not a solution ;), some kind of a link is needed. Maybe I
>> should use tags and an agenda view? I like the idea of having an org
>
> Tags makes the most sense.
>
>> file with the usual conference notes combined with the tasks I worked on
>> at the conference. How can I 'materialise' the agenda view as a section
>> in an org file? Other hints? How do you implement this?
>
> I understand that what you're asking for is a way to transform the
> results of a query to org mode format, replete with headlines and all?
yepp, if that is the solution to my initial problem.
> Not sure it's possible. However, something like sparse trees may help.
One can put elisp code in an org file, that can be invoked. So somehow
this would be doable. But on the other hand it is not clear to me what
happens if I change the state of a task or if I edit the task. Is this
state change reflected at the original position, i.e. the other org
file, of the task? Remember, the buffer holding org file with the
'copies' of the tasks isn't in agenda mode. IIRC in planner-mode tasks
can have ids, so editing a task changes all tasks with the same id in
all files.
Regards
hmw
--
biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html
Flood - Your friendly network packet generator
http://www.c0t0d0s0.de/flood/flood.html
prev parent reply other threads:[~2012-01-08 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 11:05 Multiple occurrence of tasks Michael Welle
2012-01-08 15:35 ` Karl Voit
2012-01-08 21:19 ` Michael Welle
2012-01-08 17:54 ` Mueen Nawaz
2012-01-08 21:12 ` Michael Welle [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=bedpt8xkdv.ln2@news.c0t0d0s0.de \
--to=mwe012008@gmx.net \
--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).