From: Nicolas Goaziou <email@example.com> To: Samuel Wales <firstname.lastname@example.org> Cc: email@example.com Subject: Re: text search and restriction lock bugs Date: Thu, 07 Sep 2017 15:58:30 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAJcAo8tt44PEVkYGqJiG7x1m7NX9WgA9b3RaQLgqOYfa49UH8w@mail.gmail.com> (Samuel Wales's message of "Tue, 5 Sep 2017 14:42:32 -0700") Hello, Samuel Wales <email@example.com> writes: > recent maint. these are separate, but 1 and 3 might be related, and 1 and > 2 might be related, so i hope you don't mind if i put them together. > > 1. > > 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. Agreed. Fixed. > 2. > > if you remove the restriction lock and refresh the agenda, > it will produce different results. > > imo, should act as if the restriction lock were still in place. g > should refresh with the settings that were present at invocation. > sometimes you change buffer name, and run a new agenda, so that you > can have 2 agendas, one restricted and one not. Not sure I agree. > the restriction lock is not fontified nicely so it can be desirable to > remove it for editing. Is this a different bug report? > 3. > > finally, a user will sometimes bind org-agenda-files to a > list that includes some of the > org-agenda-text-search-extra-files files. to avoid showing > the same match twice, the user currently has to do > remove-duplicates. imo the agenda could do > remove-duplicates to alleviate that burden. Agreed. Fixed. Thank you. -- Nicolas Goaziou
next prev parent reply other threads:[~2017-09-07 13:58 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 [this message] 2017-09-07 22:44 ` Samuel Wales 2021-02-28 22:06 ` Samuel Wales 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: 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: text search and restriction lock bugs' \ /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
Code repositories for project(s) associated with this 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).