From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org
Subject: Bug: Agenda Org-mode searches are limited by buffer narrowing [6.33trans (release_6.33c.18.ga606)]
Date: Wed, 18 Nov 2009 12:33:06 -0500 [thread overview]
Message-ID: <874ooru4a5.fsf@gollum.intra.norang.ca> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
------------------------------------------------------------------------
The org-agenda multi-occur search command (C-c a /) does not return
results on buffers that are currently narrowed if the search would
normally match outside the narrowed region. This prevents possible
matches from being displayed.
Narrowing should probably be disabled during searches so it's possible
to find all of the occurrences.
I'm working in file A, and have it narrowed to subtree. I get
interrupted and move to file B, then I want to add details to a
project I know exists and I use the agenda search to find it ... but
it's in file A outside the narrowed region and no results are
returned. I forgot file A was narrowed but I don't think this should
affect the search results.
I think the agenda restriction lock should be the only thing that
affects agenda search results.
-Bernt
Emacs : GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
of 2008-11-09 on raven, modified by Debian
Package: Org-mode version 6.33trans (release_6.33c.18.ga606)
next reply other threads:[~2009-11-18 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 17:33 Bernt Hansen [this message]
2009-11-19 13:27 ` Bug: Agenda Org-mode searches are limited by buffer narrowing [6.33trans (release_6.33c.18.ga606)] Carsten Dominik
2009-11-19 14:11 ` Bernt Hansen
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=874ooru4a5.fsf@gollum.intra.norang.ca \
--to=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 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).