emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: text search and restriction lock bugs
Date: Sun, 28 Feb 2021 15:06:08 -0700	[thread overview]
Message-ID: <CAJcAo8uXVmDZXQ=+SbvW_o-uztKCopC+MppK4p2mVuVrxDiGiA@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8tt44PEVkYGqJiG7x1m7NX9WgA9b3RaQLgqOYfa49UH8w@mail.gmail.com>

On 9/5/17, Samuel Wales <samologist@gmail.com> wrote:
> is it expected behavior that if you do a restriction lock on
> a subtree, then do a text search, it will include matches
> from org-agenda-text-search-extra-files?  imo it should not.

this was fixed, but i am starting to see it in maint again.  if i
create a new file, set restriction lock to subtree using < in the
stars, then run a text search, text search extra files entries show
up.  i have not tried it in -Q because of hte setup required that i
can't do atm.

  parent reply	other threads:[~2021-02-28 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 21:42 Samuel Wales
2017-09-07 13:58 ` Nicolas Goaziou
2017-09-07 22:44   ` Samuel Wales
2021-02-28 22:06 ` Samuel Wales [this message]
2021-03-27 23:02   ` Samuel Wales

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='CAJcAo8uXVmDZXQ=+SbvW_o-uztKCopC+MppK4p2mVuVrxDiGiA@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: text search and restriction lock bugs' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).