From: "W.Bentley MacLeod" <bentley.macleod@columbia.edu>
To: Benjamin Andresen <benny@in-ulm.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: FAQ incorrect
Date: Tue, 27 Oct 2009 11:03:54 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.00.0910271103430.12852@wbm1.site> (raw)
In-Reply-To: <87eioonb68.fsf@in-ulm.de>
perfect. b.
____________________________
Professor W. Bentley MacLeod
Columbia University in the City of New York, NY 10027
http://www.columbia.edu/~wbm2103/
____________________________
On Tue, 27 Oct 2009, Benjamin Andresen wrote:
> Hey W.,
>
> "W.Bentley MacLeod" <bentley.macleod@columbia.edu> writes:
>
>> FAQ on how to include all org files in a directory is incorrect (view 85).
>> Correct code is:
>> (setq org-agenda-files (file-expand-wildcards "~/org-files/*.org"))
>
> You are right.
>
> This isn't valid: (setq org-agenda-files "~/my/special/path/org/")
>
> M-x org-agenda RET will reply with: `org-agenda-files' cannot be a single directory
>
> I propose the following for the FAQ:
>
> (setq org-agenda-directory "~/Org/")
> (setq org-agenda-files (directory-files (expand-file-name org-agenda-directory) t "^[^\.][^#][[:alnum:]]+\.org$"))
>
> That will add every org file. I've had the problem of normal glob
> expansion to include emacs lock files that are in this format:
> .#todo.org
>
> I was under the impression that org-agenda-directory set to
> ~/my/special/path/org/ would Just Work(tm) because if you do C-c a a v A
> it pulls in the right files for me.
>
>> best bm
>
> br,
> benny
>
>
>
next prev parent reply other threads:[~2009-10-27 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 13:10 FAQ incorrect W.Bentley MacLeod
2009-10-27 14:50 ` Benjamin Andresen
2009-10-27 15:03 ` W.Bentley MacLeod [this message]
2009-10-27 15:05 ` W.Bentley MacLeod
2009-10-27 14:56 ` Nick Dokos
2009-10-27 15:21 ` Carsten Dominik
2009-10-27 15:29 ` Nick Dokos
2009-10-27 17:02 ` Matt Lundin
2009-10-27 15:00 ` Matt Lundin
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=alpine.LNX.2.00.0910271103430.12852@wbm1.site \
--to=bentley.macleod@columbia.edu \
--cc=benny@in-ulm.de \
--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).