From: Jean Louis <bugs@gnu.support>
To: daniela-spit@gmx.it
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Adding Org Files to org-agenda-files
Date: Sun, 29 Nov 2020 08:51:15 +0300 [thread overview]
Message-ID: <X8M202VRCyEKuYCJ@protected.rcdrun.com> (raw)
In-Reply-To: <trinity-4a54d490-55dc-4210-bf81-9db92c4df3b0-1606606575303@3c-app-mailcom-bs11>
* daniela-spit@gmx.it <daniela-spit@gmx.it> [2020-11-29 02:37]:
> Jeremie,
>
> Have you ever tried to send an entry of org-capture to two files?
Based on your use case I am thinking if I ever had use to "capture"
task in multiple files. I was mostly using tasks that are in my
database, not necessarily Org related. So I have groups of tasks:
- normal tasks, managed in the database, curated, can be separate or
otherwise relate to people, organizations, cases, opportunities,
- quick tasks, normally one key capture from email, without
description and nothing else, it just helps to connect to email
message as I know what is to be done from person's name and subject
- administrative tasks, which belong to well organized project
planning,
- Org tasks which are worse among the above groups as they are not
structured as database tasks.
- various text file based tasks
All tasks from above groups at my side are assigned to somebody. They
may be assigned to me personally by default, often they are assigned
to other people.
Sometimes they are assigned to a group. In that case my Org header
could look something like this:
#+PROPERTY: ASSIGNED_ALL Ezekiel James TeamTZ Mark
And TeamTZ is group of people.
Then I have properties:
***** TODO Alfeo CB Officer <2018-10-02 Tue>
SCHEDULED: <2019-07-01 Mon>
:PROPERTIES:
:ASSIGNED: James
:ID: c9d68b39-f01e-4624-929a-a25fd1866183
:CREATED: [2018-10-06 Sat 09:56]
:END:
This way the task becomes mine, maybe for supervision, but James is
handling the task. This is somewhat similar to putting task in two
files, one for me, one for James, but as there is relation in the
heading I need not keep it in two files.
Deriving from idea of making relations then I think on your use case.
You need to have a main list of tasks while some tasks could be done
TODAY. And you wish to filter those that could be done today.
One way could be in using properties as above. You could just assign property:
*** Task
:PROPERTIES:
:TASK-TYPE: QUICK
:END:
By using property you could use agenda feature to find those with that
property.
Other way to assign attribute to task could be by using tags:
*** Task :QUICK:
By using both methods you could easily filter out with agenda those
tasks you could be completing today.
Jean
next prev parent reply other threads:[~2020-11-29 5:52 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 15:39 Adding Org Files to org-agenda-files daniela-spit
2020-11-28 16:51 ` Jeremie Juste
2020-11-28 16:54 ` daniela-spit
2020-11-28 17:01 ` daniela-spit
2020-11-28 17:41 ` Jeremie Juste
2020-11-28 18:12 ` daniela-spit
2020-11-28 18:30 ` daniela-spit
2020-11-28 18:43 ` daniela-spit
2020-11-28 19:01 ` Jeremie Juste
2020-11-28 19:16 ` daniela-spit
2020-11-28 19:26 ` Detlef Steuer
2020-11-28 19:44 ` daniela-spit
2020-11-28 19:55 ` Jeremie Juste
2020-11-28 20:06 ` daniela-spit
2020-11-28 20:11 ` daniela-spit
2020-11-28 20:27 ` Jeremie Juste
2020-11-28 20:40 ` daniela-spit
2020-11-28 21:32 ` Jeremie Juste
2020-11-28 21:45 ` daniela-spit
2020-11-28 23:18 ` Jeremie Juste
2020-11-28 23:29 ` daniela-spit
2020-11-29 1:36 ` Tim Cross
2020-11-29 2:54 ` daniela-spit
2020-11-29 3:51 ` Tim Cross
2020-11-29 4:05 ` daniela-spit
2020-11-29 5:23 ` Tim Cross
2020-11-29 9:30 ` Jean Louis
2020-11-29 6:50 ` Jean Louis
2020-11-29 6:41 ` Jean Louis
2020-11-29 12:28 ` Ihor Radchenko
2020-11-29 13:00 ` Tim Cross
2020-11-29 17:11 ` Jean Louis
2020-11-29 17:05 ` Jean Louis
2020-12-01 2:24 ` Ihor Radchenko
2020-12-01 8:59 ` Jean Louis
2020-12-13 15:36 ` Ihor Radchenko
2020-12-13 16:27 ` steve-humphreys
2020-12-25 2:17 ` Ihor Radchenko
2020-12-13 20:21 ` Jean Louis
2020-12-13 20:59 ` Tim Cross
2020-12-13 21:59 ` pietru
2020-12-13 23:28 ` Jean Louis
2020-11-29 4:46 ` Jean Louis
2020-11-29 14:46 ` daniela-spit
2020-11-29 17:01 ` Tim Cross
2020-11-29 17:38 ` daniela-spit
2020-11-29 20:55 ` Jeremie Juste
2020-11-30 0:21 ` Tim Cross
2020-11-28 23:36 ` daniela-spit
2020-11-29 5:51 ` Jean Louis [this message]
2020-11-28 20:28 ` daniela-spit
2020-11-28 18:50 ` daniela-spit
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=X8M202VRCyEKuYCJ@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=daniela-spit@gmx.it \
--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).