emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Adrian C." <anrxc@sysphere.org>
To: emacs-orgmode@gnu.org
Subject: Merging a list and wildcard expansion in org-agenda-files
Date: Sat, 9 Apr 2011 21:46:40 +0200	[thread overview]
Message-ID: <alpine.LNX.2.00.1104092134340.28264@flfcurer.bet> (raw)

Hello, 
I read the FAQ entry "How can include all org files in a directory in my 
agenda?" and I'd like to merge both examples from the answer for my 
agenda-files.

To include all org files in a directory I would use 
(setq org-agenda-files '("~/org/")).

I have a special projects directory with the format 
~/projects/<projectname>/project.org for that I would use

(setq org-agenda-files (file-expand-wildcards 
~"/projects/*/project.org"))


I tried to define a single org-agenda-files with both, unfortunately I 
don't know a lot of elisp so my tries like using list() all failed. For 
the first directory I guess I could also use file-expand-widlcards with 
*.org, but wasn't succesful in merging two file-expand-wildcards either.


On a simillar note I'd like to pitch in another questions. If someone is 
able to help me, then my agenda view combined would have 30 to 50 files, 
previously I never wondered why all the files end up opened in emacs 
buffers. But now if I combined them all each time I view the agenda I 
will be loading all the files. Any way to avoid opening 30 new buffers? 
Thank you.

             reply	other threads:[~2011-04-09 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09 19:46 Adrian C. [this message]
2011-04-10 14:06 ` Merging a list and wildcard expansion in org-agenda-files Puneeth Chaganti
2011-04-10 14:12   ` Puneeth Chaganti
2011-04-10 17:21     ` Adrian C.
2011-04-10 17:31       ` Puneeth Chaganti
2011-04-10 17:35         ` Adrian C.

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.1104092134340.28264@flfcurer.bet \
    --to=anrxc@sysphere.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).