From: Christopher DeMarco <demarco@maya.com>
To: emacs-orgmode@gnu.org
Subject: Re: Print headlines including DEADLINE?
Date: Mon, 15 Dec 2008 22:12:43 -0500 [thread overview]
Message-ID: <20081216031243.GA11318@owl.prv.maya.com> (raw)
In-Reply-To: <977E5D4C-1B7A-4779-AAE6-E068E7C4344E@uva.nl>
On Tue, Dec 09, 2008 at 08:17:38AM +0100, Carsten Dominik wrote:
> you may want to take a look at column view, which can show the deadline.
> Get back here when you cannot figure out how to do this.
OK, so I can't figure out how to do this :-)
First, how I'm using org-mode:
Inside ~/working I have nested project directories; some for home and
some for work; projects within projects within projects. Whenever I
need a new PROJECTNAME.org, I create it wherever in the hierarchy it
belongs, and then symlink it into the proper toplevel (which roughly
corresponds to the start of a particular SVN or Git repository). This
way, I have much smaller list of org-agenda-files to maintain.
I have some custom agenda views defined, that tell me things like what
I have to do today, and what to do in various contexts etc. For this
I aggregate all of the .org files I've written.
I don't want to go adding a :COLUMNS: property to every .org file that
I want to include in a custom view; I'd rather define :COLUMNS: for
"types" of views that I want. Where would I define this? I suppose
that I could write definitions in "hidden" files that get explicitly
sourced based on what view I want, but that seems roundabout...
Thanks... and org-mode rocks!
--
Christopher DeMarco <demarco@maya.com>
IT Director
MAYA Group
+1-412-708-9660
next prev parent reply other threads:[~2008-12-16 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 19:29 Print headlines including DEADLINE? Christopher DeMarco
2008-12-09 7:17 ` Carsten Dominik
2008-12-16 3:12 ` Christopher DeMarco [this message]
2008-12-17 9:00 ` Carsten Dominik
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=20081216031243.GA11318@owl.prv.maya.com \
--to=demarco@maya.com \
--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).