emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Org mode mailing list <emacs-orgmode@gnu.org>
Subject: [BUG] tags sparse tree broken
Date: Thu, 9 Feb 2012 03:22:55 +0100	[thread overview]
Message-ID: <20120209032255.431e8197@kuru.dyndns-at-home.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]


I believe the sparse tree search is broken. It has been broken for a
while I think. Searching for tags returns no matches. I get the
following backtrace with debug enabled on a minimal emacs on using
`next-error' after a tag search which should return a positive result.

Debugger entered--Lisp error: (error "No more matches")
  signal(error ("No more matches"))
  error("No more matches")
  byte-code("\b`\305\"\211\x11\2036  org-occur-next-match(1 nil)
  call-interactively(next-error nil nil)

To replicate this, open the attached org file and search for the tag Qn.

C-c / m Q n RET

I tried running a quick edebug on org-sparse-tree, but I am having a
problem in answering the prompt and stepping forward with the edebug
simultaneously. Hopefully someone else will have a better luck.



Open source is the future. It sets us free.

[-- Attachment #2: tag-test.org --]
[-- Type: text/plain, Size: 224 bytes --]

* Bs⁰ decay
** Decay model								 :Qn:
1. Justify neglecting CP violation
   - in decay for the DsK channel
   - in Bs mixing for both DsK and Dsπ channels
2. Verify master equations

** Build PDF								 :Qn:

             reply	other threads:[~2012-02-09  2:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  2:22 Suvayu Ali [this message]
2012-02-12 18:41 ` [BUG] tags sparse tree broken David Maus
2012-02-12 20:48   ` 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:

  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=20120209032255.431e8197@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).