Hi, The tags search for org-sparse-tree seems to be broken. With a minimal setup, C-c / m <match> RET doesn't perform a tags search. I bisected the problem to this commit. dfcb6faef11a2439b56b18a6289803361d402130 is the first bad commit commit dfcb6faef11a2439b56b18a6289803361d402130 Author: Nicolas Goaziou <n.goaziou@gmail.com> Date: Thu Aug 25 01:58:29 2011 +0200 Provide more consistent regexps for headlines HTH -- Suvayu Open source is the future. It sets us free.
suvayu ali <fatkasuvayu+linux@gmail.com> writes:
Hi, suvayu
>
> The tags search for org-sparse-tree seems to be broken.
> With a minimal
> setup, C-c / m <match> RET doesn't perform a tags search.
well, with my org-version, 2 commits before the leading edge:
Org-mode version 7.7 679a0e1fe93d630820185f931087328d32e81077
GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600) of 2011-03-10 on 3249CTO
I cannot reproduce it.
C-c m / tag on this file
-----------------------------------
-*- mode: org; -*-
* [2011-10-26 mer]
** number one
*** hello :tag:
*** one
*** two
** game
*** game2 :tag:
**** game 3
---------------------------------------------------
C-c m / tag gives:
* [2011-10-26 mer]
** number one
*** hello
*:tag:
** game
*** game2 :tag:
**** game 3
/// /// ///
cheers,
Giovanni
Hi Giovanni, On Wed, 26 Oct 2011 15:40:53 +0200 Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> wrote: > suvayu ali <fatkasuvayu+linux@gmail.com> writes: > > Hi, suvayu > > > > The tags search for org-sparse-tree seems to be broken. > > With a minimal > > setup, C-c / m <match> RET doesn't perform a tags search. > > well, with my org-version, 2 commits before the leading edge: > > Org-mode version 7.7 679a0e1fe93d630820185f931087328d32e81077 > GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600) of 2011-03-10 on 3249CTO > > I cannot reproduce it. > Are the matched headlines highlighted? Can you move to the next match with next-error (C-x ` or M-g n)? When I try to move through the matches with M-g n or M-g p, I get the following error. Debugger entered--Lisp error: (error "No more matches") signal(error ("No more matches")) error("No more matches") byte-code(..) org-occur-next-match(1 nil) next-error(nil) call-interactively(next-error nil nil) > cheers, > Giovanni > -- Suvayu Open source is the future. It sets us free.
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes: Hi, Suvayu > Are the matched headlines highlighted? No. you're right, there's a bug > Can you move to the next match with next-error > (C-x ` or M-g n)? No. bug. :-/ > When I try to move through the > matches with M-g n or M-g p, I get the following error. > > Debugger entered--Lisp error: (error "No more matches") me too. thanks for explaining. cheers, Giovanni