emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: daniela-spit@gmx.it
Cc: emacs-orgmode@gnu.org
Subject: Re: Adding Org Files to org-agenda-files
Date: Sun, 29 Nov 2020 14:51:23 +1100	[thread overview]
Message-ID: <87k0u4zupw.fsf@gmail.com> (raw)
In-Reply-To: <trinity-c5fb8f53-923b-40cc-8eed-c1144be404d5-1606618460250@3c-app-mailcom-bs11>


daniela-spit@gmx.it writes:

>  #44935
>
>> Initially, I put pretty much everything into the agenda file list. This
>> worked fairly well until the size of these files began to get very
>> large. The biggest problem I had was my agendas were just getting too
>> large and complicated/distracting.
>
> I have constructed four different Capture Templates and four Org Agendas
> and then I can fire up the ones I want as I am working.
>
>> I then moved to a workflow where the agenda files really only contained
>> tasks and notes, references, pretty much everything else was put into
>> other org files not part of the agenda file list. I didn't like that
>> workflow. It complicated refiling and I lost the ability to keep all
>> related things together in a meaningful way.
>
> Have made capture and agenda by project, and then some functions
> that group some of them together.  Not so sure how good it is going
> to until I have used for proper work.
>

I went down a similar route initially. In the end, found it was much
better to define your capture templates to be generic i.e. not tied to a
specific project, but rather based on what you are capturing and then
use things like tags and properties (which you can have capture prompt
for) to capture project specific information.

So I have the following capture templates

- TODO to capture basic tasks

- phone which I use to capture phone call information and track time.
  Actually, although it is called phone, I use it for any meeting type
  thing. I have to track time for billing purposes and need to record
  date and time of call for tracking purposes

- Mail to track important emails. Adds a link to the original message (I
  read email using mu4e).

- Notes For capturing general note information

- Bookmarks - I have a bookmarks.org file where I keep links to
  'interesting' things. Might be web sites, man pages, info pages etc.

- protocol capture - for org protocol capture handler e.g. capturing
  info from web pages in chrome.

That is about it. My approach is to make capture as quick and easy as
possible. I usually just want to capture something and file it away to
get it out of my head and let me focus on what I was doing.

All my capture templates write to a file called refile.org. When
capturing data, I don't need to think about where it goes, just capture
it an move on. At the start of each day, I open up the refile.org file
and 'refile' the entries, which is just a couple of key presses, into
the most appropriate org file. Many (not all) of the headings I refile
under will add appropriate tags via the org tag inheritance process,
which I use in various agenda views. This reminds me of what I have on
my plate and helps me plan my day. I was initially worried that having
to do this refiling every day would be a hassle. In fact, it has turned
out to be a bonus and rarely takes more than a couple of minutes, yet
not having to worry about where to file something right when I'm
capturing it is a great bonus as it makes it really fast. A meeting or
phone conversation which a client might result in me using capture
several times as I record tasks or notes.

I have a few stored agenda searches and a couple of customised agenda
views, plus I frequently make use of the tags to do ad hoc searches. I
have also defined additional TODO states (TODO, NEXT, STARTED, HOLD,
DELEGATED, CANCELLED and DONE). Some are setup to prompt for an
additional note e.g. DELEGATED to let me specify who it is delegated to
and HOLD to specify why it is on hold).

The rest of my org customisation is mainly about data exports (tweaking
PDFs, HTML, Markdown exports, babel settings and specialised reports,
such as timesheets or invoices). I use org for all my documentation and
some work situations and clients want these documents to comply with
their corporate standards e.g. include logos, specific colours and fonts
etc).

Tim

--
Tim Cross


  reply	other threads:[~2020-11-29  3:51 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 [this message]
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
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=87k0u4zupw.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --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).