emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: "E.L.K." <some.any.key@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode patch: when building sparse tree, suggest only local tags in minibuffer
Date: Sat, 05 Sep 2020 11:10:56 +0200	[thread overview]
Message-ID: <87tuwc7fmn.fsf@gnu.org> (raw)
In-Reply-To: <CAF+cOoN1jjhz3FvL0tr6EOr3fJACcKe8U36VB8zHA=C_j+SaMg@mail.gmail.com> (E. L. K.'s message of "Tue, 16 Jun 2020 14:15:39 +0300")


"E.L.K." <some.any.key@gmail.com> writes:

> I found that if I do "C-c C-c" on heading, it suggests only local
> tags in the minibuffer, but when I do "C-m / m" (build sparse tree)
> it suggests agenda tags together with local tags.
> It does not make sense to build sparse tree in buffer using tags that
> are not in this buffer, I think. So there is small patch in attempt
> to fix it.

thanks for the patch.  I add a Changelog and documented the new
parameter `only-local-tags' in the docstring, then applied it as
f2d41de3e in maint.

If you can provide complete patches for the next ones, that'd be
great, thanks in advance.



  reply	other threads:[~2020-09-05  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 11:15 Org mode patch: when building sparse tree, suggest only local tags in minibuffer E.L.K.
2020-09-05  9:10 ` Bastien [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-15 18:55 E.L.K.

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=87tuwc7fmn.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=some.any.key@gmail.com \


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