From: andrea <andrea.crotti.0@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Tips on maintaining a knowledge-base ?
Date: Sun, 10 Jan 2010 12:20:34 +0100 [thread overview]
Message-ID: <m1skaexl31.fsf@gmail.com> (raw)
In-Reply-To: 000e0ce0d5d8ec0c7a047cbbd544@google.com
d.sturb@gmail.com writes:
> I've been using org-mode for a little while, I've kept it really simple
> for now, with only two files :
> - one to act as an inbox, with remember-mode
> - another where I stick just about anything that's been processed from the
> inbox
>
> This is great for managing somewhat 'actionable' items, fitting a
> projects/tasks paradigm, but I keep adding things of a more general
> nature, that I won't be needing on a day-to-day basis.
> i.e. outlines describing a general topic, some sysadmin how-tos, reading
> notes etc
> I see these notes more as an archive of knowledge nuggets on selected
> topics, rather than something I'd need to show up in my agenda view.
> Ideally they would be heavily interlinked in a wiki fashon for easy
> navigation when referring to it int he future, but I haven't put much
> effort into that yet (well it's all in one file for now...).
>
> I was wondering if anyone uses org-mode for this kind of use, and would
> really be interested in reading how you maintain such a system.
> I'm especially interested in methods that relate to structuring and
> 'querying' the knowledge base, since it's of no use if information can't
> be found easily.
>
> regards, julien.
>
> PS : by the way, first post here, so hey everyone !
A nice "trick" but very simple I'm using is to automatically add to my
org-agenda-files every org file that I create.
In this way everything is always reachable via grep/tags/whatever.
Just do this:
--8<---------------cut here---------------start------------->8---
(defun org-add-eventually()
"Adding a file to org-agenda when saved"
(interactive)
(if (string= major-mode "org-mode")
(org-agenda-file-to-front)))
(add-hook 'before-save-hook 'org-add-eventually)
--8<---------------cut here---------------end--------------->8---
prev parent reply other threads:[~2010-01-10 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 14:08 Tips on maintaining a knowledge-base ? d.sturb
2010-01-09 14:56 ` Ian Barton
2010-01-09 22:58 ` Memnon Anon
2010-01-10 11:20 ` andrea [this message]
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=m1skaexl31.fsf@gmail.com \
--to=andrea.crotti.0@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
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).