From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Restricting admisible tags depending on header
Date: Sat, 04 Jun 2016 07:31:02 -0400
Message-ID: <m28tylry15.fsf@Johns-MacBook-Air.local>
References: <87inxpbplv.fsf@wanadoo.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44511)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <johnrkitchin@gmail.com>) id 1b99nK-0003kM-AK
	for emacs-orgmode@gnu.org; Sat, 04 Jun 2016 07:31:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <johnrkitchin@gmail.com>) id 1b99nE-0001pG-9f
	for emacs-orgmode@gnu.org; Sat, 04 Jun 2016 07:31:09 -0400
Received: from mail-qt0-x233.google.com ([2607:f8b0:400d:c0d::233]:36030)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <johnrkitchin@gmail.com>) id 1b99nE-0001p8-4R
	for emacs-orgmode@gnu.org; Sat, 04 Jun 2016 07:31:04 -0400
Received: by mail-qt0-x233.google.com with SMTP id t13so3916302qtc.3
	for <emacs-orgmode@gnu.org>; Sat, 04 Jun 2016 04:31:03 -0700 (PDT)
In-reply-to: <87inxpbplv.fsf@wanadoo.es>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: =?utf-8?Q?=C3=93scar?= Fuentes <ofv@wanadoo.es>
Cc: emacs-orgmode@gnu.org

This looks more like TODO states to me.

You can do that on a file basis like this I think:

#+TODO: OPEN CLOSED

It is an interesting idea to make them heading specific though. I guess
you should store them in a property on the headline though.

Otherwise I would suggest using something like counsel-org-tag which
wouldn't have the same limitations.

Óscar Fuentes writes:

> I'll like to offer only certain tags depending on the contents of the
> current header. For instance, if the header is
>
> * Status
>
> I want to see only "open" and "closed" on the options shown by
> org-fast-tag-selection.
>
> Currently I define quite a lot of tags with #+TAGS:, most of them are
> intended to be assigned to a specific header. Having so many tags
> displayed by org-fast-tag-selection is confusing, error-prone and breaks
> the selection method (org-fast-tag-selection runs out of letters).
>
> I'm thinking on advising org-fast-tag-selection and prune the list of
> acceptable tags before calling the real function, but maybe there is a
> better method.


-- 
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu