emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: tony day <zygomega@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: org-anywhere
Date: Thu, 18 Oct 2012 12:16:22 +1100	[thread overview]
Message-ID: <26E1F5C1-BE45-4DC4-ACA5-D974D1A856AD@gmail.com> (raw)
In-Reply-To: <87y5j5vtji.fsf@Rainer.invalid>

I've been catching up on the mailing list, and thinking about my
personal use case versus other typical patterns.  I thought I would
share a thought with the group.

I would divide use cases into three main cohorts:
- /org-planning/: org files consist mostly of planning and
  tracking content (lets call this =flow=). What is being worked on in
  this type of usage (lets call this =stuff=) exists predominantly
  outside the org-mode environment.
- /org-everywhere/: both the =stuff= and the =flow= exist within
  an org file.  Org-mode is everywhere (and that's how we like it, oi!).
- /org-anywhere/: where the =flow= gets applied to the =stuff=
  by making the =stuff= an org file.  But it's more about the =stuff= then the =flow=.

I'm in the /org-anywhere/ category. I use org-mode as a plain-text
content creation tool utilising headers, plain lists, tables, babel
and export technology (=stuff=) and, sometimes, I use scheduling,
deadlines, =todo= state tracking and the agenda (=flow=). 

As a result, I
- don't like the visual clutter of dates outside of drawers, or drawers
- love column view and header cycling
- often find myself stripping an org file completely of org =flow= guff and
  not just to export but because seeing a deadline way in the past is
  bad for morale (just saying).
- I can and do ignore the agenda for weeks at a time.

So, for the way my brain thinks, there are a few org-mode design
features that get in the way.
- a =blank= =todo= state is implicitly seen as not a state at all.  I
  see it as a state (which often is =done=).
- scheduled and deadline dates cannot be stored in drawers
- drawers cannot be completely hidden
- I would like a org-remove-all-(flow)-guff option

Does anyone have similar issues?  I'd like to have a go at fixing
some of this but would like to know if it would be generally useful
to others, and what priorities may be. 

Tony

next prev parent reply	other threads:[~2012-10-18  1:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-13 21:37 Error reloading Org features Thomas S. Dye
2012-10-17 18:32 ` Achim Gratz
2012-10-18  1:16   ` tony day [this message]
2012-10-18 11:50     ` org-anywhere Rasmus
2012-10-18 22:23       ` org-anywhere tony day
2012-12-18 14:02         ` org-anywhere Bastien
2012-12-18 14:01       ` org-anywhere Bastien

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=26E1F5C1-BE45-4DC4-ACA5-D974D1A856AD@gmail.com \
    --to=zygomega@gmail.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

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).