all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brett Viren <bv@bnl.gov>
To: Louis <lbmlist@hethcote.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode for knowledge management
Date: Mon, 13 Oct 2014 09:11:04 -0400	[thread overview]
Message-ID: <ir4y4sk2jyv.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <alpine.DEB.2.11.1410091554260.17286@caritas.hethcote.pvt> (Louis's message of "Thu, 9 Oct 2014 16:17:45 -0600 (MDT)")

[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]

Hi Louis,

Louis <lbmlist@hethcote.com> writes:

> I've been using org-mode for a variety of purposes for a few years. I
> find that it suffers from the same problem that other such tools
> do. The problem is me. I can't remember week to week how I may have
> classified some scrap of information. Did I drop it into
> notes/someproduct.org or was it procedures/someprocess.org?

I hear you.  My strategy so far has been: just write org content and an
ideal lookup solution will eventually be found (via threads like this
one!).

This weekend I took a first step and *finally* got agenda-based
searching to work.  For better or worse, my setup intentionally spreads
org content over a few areas:

For a few explicit, "global" files (eg, todo.org)
  ~/org/*.org          

For daily, private notes:
  ~/org/web/notes/<YYYY>/<MM>/<DD>/notes.org   

For a wiki-like blog / knowledge bank:
  ~/org-pub/topics/<TOPIC>/index.org

By default, my attempts with org agenda search was not finding files in
these areas.  Particularly the latter two were difficult for me to
figure out how to tell org about.  The final solution was to walk these
directories at initialization time and add all .org files found to
org-agenda-text-search-extra-files.  Here is the most concise way to do
that which I found after various searches:

(require 'find-lisp)
(setq  
 org-agenda-files (list "~/org")
 org-agenda-text-search-extra-files 
 (append
  (find-lisp-find-files "~/org-pub/topics/" "\\.org$")
  (find-lisp-find-files "~/org/web/notes/" "\\.org$"))
)

If anyone knows better ways to do this, I'm all ears.  I'm particularly
wondering how long-running org sessions will handle newly created topics
or notes in this setup.

-Brett.

[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]

      parent reply	other threads:[~2014-10-13 13:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 22:17 org-mode for knowledge management Louis
2014-10-09 23:54 ` Marcin Borkowski
2014-10-10 15:46   ` Daniel Clemente
2014-10-10 21:40     ` mbork
2014-10-10 21:48     ` John Hendy
2014-10-11  2:53       ` Eric Abrahamsen
2014-10-12  4:54         ` John Hendy
2014-10-13  2:42           ` Eric Abrahamsen
2014-10-13  3:15             ` Daniel Clemente
2014-10-13  5:17               ` Samuel Wales
2014-10-14  3:47                 ` Daniel Clemente
2014-10-14  1:14               ` Eric Abrahamsen
2014-10-11 11:36       ` Daniel Clemente
2014-10-11 19:45         ` Brady Trainor
2014-10-12  4:29           ` Daniel Clemente
2014-10-12  5:03         ` John Hendy
2014-10-12  7:48           ` Daniel Clemente
2014-10-14  2:14             ` John Hendy
2014-10-10  0:18 ` Thomas S. Dye
2014-10-10  2:32   ` Louis
2014-10-10  2:34   ` Louis
2014-10-13 19:29   ` Louis
2014-10-13 19:36     ` Thomas S. Dye
2014-10-13 23:10       ` Louis
2014-10-13 13:11 ` Brett Viren [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ir4y4sk2jyv.fsf@lycastus.phy.bnl.gov \
    --to=bv@bnl.gov \
    --cc=emacs-orgmode@gnu.org \
    --cc=lbmlist@hethcote.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.