From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: tags/search on specific files
Date: Sat, 15 Jan 2011 19:00:09 +0000 (UTC) [thread overview]
Message-ID: <87wrm6t4vq.fsf@mean.albasani.net> (raw)
In-Reply-To: loom.20110115T094448-297@post.gmane.org
knubee <knubee@gmail.com> writes:
> i tried to find the information by searching the web for different variations of
> "org-mode", "search tags", and "current file".
May I ask: Why not info?
When searching, I find myself (still) sometimes asking google first, but
each time I draw the conclusion, that asking emacs is actually faster.
I just tried to find the `<' command in the info file using
`i limit' and `i restrict' in "This manual is for Org version
7.01trans." and got
Info-index: No `limit' in index
Info-index: No `restrict' in index
Could these be added to the index for
,----[ (org) Agenda files ]
| `C-c C-x <'
| Permanently restrict the agenda to the current subtree. When with
| a prefix argument, or with the cursor before the first headline in
| a file, the agenda scope is set to the entire file. This
| restriction remains in effect until removed with `C-c C-x >', or
| by typing either `<' or `>' in the agenda dispatcher. If there is
| a window displaying an agenda view, the new restriction takes
| effect immediately.
|
| `C-c C-x >'
| Remove the permanent restriction created by `C-c C-x <'.
`----
and
,----[ (org) Agenda dispatcher ]
| `<'
| Restrict an agenda command to the current buffer(1). After
| pressing `<', you still need to press the character selecting the
| command.
|
| `< <'
| If there is an active region, restrict the following agenda
| command to the region. Otherwise, restrict it to the current
| subtree(2). After pressing `< <', you still need to press the
| character selecting the command.
`----
?
Memnon
prev parent reply other threads:[~2011-01-15 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 5:58 tags/search on specific files knubee
2011-01-09 11:25 ` Bernt Hansen
2011-01-09 12:21 ` knubee
2011-01-09 18:44 ` Matt Lundin
2011-01-09 22:55 ` knubee
2011-01-09 23:08 ` Carsten Dominik
2011-01-15 9:03 ` knubee
2011-01-15 19:00 ` Memnon Anon [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=87wrm6t4vq.fsf@mean.albasani.net \
--to=gegendosenfleisch@googlemail.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).