From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Question about org-search-view and org-occur-in-agenda-files
Date: Tue, 26 Jul 2011 04:04:28 +0200 [thread overview]
Message-ID: <CAMXnza0sfjj42aRLFrb5b5d8+NyNzfz2eCLrWQ0kPM23YtjNmQ@mail.gmail.com> (raw)
In-Reply-To: <87tya94z39.fsf@norang.ca>
Hi Bernt,
On Tue, Jul 26, 2011 at 3:20 AM, Bernt Hansen <bernt@norang.ca> wrote:
>>> You can set the org-agenda-files and
>>> org-agenda-text-search-extra-files to point to the old project for
>>> some custom search.
>>>
>
> You can also restrict agenda to a single file with C-u C-c C-x <.
> Subsequent agenda commands and searches will only use the current file
> until you remove the restriction with C-c C-x >
>
My problem was I wanted to search a whole slew of files in a directory
tree. Also I was misreading some of the the org-agenda documentation.
After reading the article on custom agenda commands on Worg, many of my
misconceptions were resolved. Now I have written a function to find org
files recursively from a directory tree and I use this list to
selectively search project directories.
e.g.:
(setq org-agenda-custom-commands
'(("W" "Search tutorials on Worg" search ""
((org-agenda-files nil)
(org-agenda-text-search-extra-files
(find-org-file-recursively "~/org/Worg/org-tutorials"))))))
> -Bernt
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-07-26 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 17:36 Question about org-search-view and org-occur-in-agenda-files suvayu ali
2011-07-25 18:29 ` Darlan Cavalcante Moreira
2011-07-25 20:07 ` suvayu ali
2011-07-26 1:20 ` Bernt Hansen
2011-07-26 2:04 ` suvayu ali [this message]
2011-07-26 3:09 ` Matt Lundin
2011-07-26 9:50 ` suvayu ali
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=CAMXnza0sfjj42aRLFrb5b5d8+NyNzfz2eCLrWQ0kPM23YtjNmQ@mail.gmail.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=bernt@norang.ca \
--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 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.