From: Rick Moynihan <rick@calicojack.co.uk>
To: David O'Toole <dto@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: community writing?
Date: Fri, 08 Jun 2007 15:21:38 +0100 [thread overview]
Message-ID: <466965F2.2020404@calicojack.co.uk> (raw)
In-Reply-To: <m33b12potc.fsf@gnu.org>
I think this is a great idea. My use of org-mode is improving, but I'm
not yet 100% comfortable with it. I recently refactored how I have been
using org-mode; and I'm not there yet.
There's no question that org-mode is a fantastic tool for organising
yourself. Its power comes from it not imposing a structure or workflow
on you. Unfortunately; this means that it takes commitment and time
before you become proficient. When you have a small system going in
org-mode you can get away with mistakes, unfortunately as you add more
information it gets harder if the structures you've defined don't scale.
The various org-mode guides out there are a great start, but I like you
think we need something more. I'd also be interested in seeing the
pro's and con's to the various org-mode tools, e.g. KEYWORDS, TAGS,
OUTLINES, and patterns suited to their usage etc...
David O'Toole wrote:
> I notice the planner world has some pages where they discuss the
> various ways people use planner. I think it would be cool for us to
> collectively post some org-mode usage strategies, perhaps on an
> emacswiki page.
>
> Or, people could prepare a small .org file and send it to me, and I
> could paste it into a page of my site. it could be a collaboratively
> written "Org-Mode Strategy and Tactics"
>
> If anyone enjoys this, I'll get started by writing my own entry.
>
--
Rick Moynihan
Software Engineer
Calico Jack LTD
http://www.calicojack.co.uk/
next prev parent reply other threads:[~2007-06-08 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 13:18 community writing? David O'Toole
2007-06-08 14:21 ` Rick Moynihan [this message]
2007-06-08 16:43 ` Bastien
2007-06-08 16:41 ` Bastien
2007-06-09 18:39 ` Piotr Zielinski
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=466965F2.2020404@calicojack.co.uk \
--to=rick@calicojack.co.uk \
--cc=dto@gnu.org \
--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).