From: Takaaki ISHIKAWA <takaxp@ieee.org>
To: Tom <adatgyujto@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-search-goto.el - full text search to go to locations in your org buffers
Date: Tue, 13 Dec 2011 00:48:57 +0900 [thread overview]
Message-ID: <5CF8AF79-7B05-4E43-A400-0E75845C0096@ieee.org> (raw)
In-Reply-To: <loom.20111212T153757-916@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Dear Tom,
Hi. Thanks for your comment.
I have verified the `org-agenda-files' is available for org-search-goto
once I call org-agenda command.
The solution for `org-directory' is good for active buffers.
But I actually don't want to keep opening archived org files only for searching.
So I will find another solution :-)
Best regards,
Takaaki Ishikawa
@takaxp
On 2011/12/12, at 23:50, Tom wrote:
> Takaaki ISHIKAWA <takaxp <at> ieee.org> writes:
>
>>
>> If this package can handle `org-directory' having org files,
>> or `org-agenda-files', it is more handy.
>
> org-agenda-files should be no problem, since this package searches in
> all opened org buffers, and org opens all agenda files when building
> the agenda.
>
> As for org-directory the simplest solution is to have all org files
> opened from there and then this tool will search in those too.
>
> Since the invention of iswitchb, ido and similar tools we don't travel
> the buffer list sequentialy anymore, so you can have all of your org files
> opened in emacs all the time, because it doesn't matter if 5 files are
> open or 20.
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2011-12-12 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 8:52 org-search-goto.el - full text search to go to locations in your org buffers Tom
2011-12-11 15:59 ` Bastien
2011-12-12 3:13 ` Takaaki ISHIKAWA
2011-12-12 14:50 ` Tom
2011-12-12 15:48 ` Takaaki ISHIKAWA [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=5CF8AF79-7B05-4E43-A400-0E75845C0096@ieee.org \
--to=takaxp@ieee.org \
--cc=adatgyujto@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).