From: Lawrence Bottorff <borgauf@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Ad-hoc, mix-and-match tag hierarchies?
Date: Thu, 1 Feb 2018 14:45:10 -0500 [thread overview]
Message-ID: <CAFAhFSUPxONW7j51qOXhi814GNnjsJgnWCj-EcoLFQKQVDk7TA@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY2FiF36kcjbTb1=NRxjZjH1zvROxL8=7JrehGjsw1T-fQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]
So a left-to-right listing of (colon-separated) tags after the heading
cannot imply a higher-to-lower hierarchical order? So there is no hierarchy
unless you create it, e.g.,
(setq org-tag-alist '((:startgrouptag)
("GTD")
(:grouptags)
("Control")
("Persp") ...
-- is what I'm hearing.
What I meant to do is to be able to use tags alone or together. And when
used together, to somehow imply hierarchy. So if I have
* header 1 :emacs:
** header 1.1 :orgmode:
*** header 1.1.1 :lisp:
stuff about Emacs' org-mode's lisp code
this implies subject hierarchy simply from the headers' hierarchy. However
this
* header 1 :emacs:
stuff about Emacs
* header 2 :emacs:orgmode:lisp
stuff about Emacs' org-mode's lisp code
* header 3 :lisp:
stuff about just Common Lisp
* header 4 :emacs:orgmode:
stuff about Emacs' org-mode
* header 5 :emacs:
more stuff about Emacs
is all peers header-wise, while the tags (if using left-to-right listing to
mean higher to lower in hierarchy) tell us the depth level of
specialization of a topic. The first set of headers is relying (clumsily)
on the header level to indicate depth of specialization, which is not
always realistic. If I wanted, ad-hoc, to indicate levels of some hierarchy
with tags, that is, not be forced to create empty superior headers, it
seems there's no prescribed way to do this. And creating tag hierarchies
by hand, i.e., (setq org-tag-alist '((:startgrouptag)..., makes me play the
combinatorics game of imagining all different possible hierarchy
combinations. Or am I missing something?
On Thu, Feb 1, 2018 at 10:36 AM, Kaushal Modi <kaushal.modi@gmail.com>
wrote:
> On Thu, Feb 1, 2018 at 10:30 AM John Kitchin <jkitchin@andrew.cmu.edu>
> wrote:
>
>> I was not aware of any implied hierarchy with tags. The order is not
>> important as far as I know, and what you describe as mix-and-match seems
>> ok. There is an idea of inheritance, e.g. sub-headings can inherit tags
>> from higher headings.
>>
>
> Same here.
>
>
>> I am not sure about the org-mode tag.
>>
>
> "-" is an invalid tag character.. the tag can be "org_mode", but not
> "org-mode". Last time I tried using hyphen, I remember that the tag
> auto-alignment would stop working (C-u C-c C-q) and also the tag face won't
> be applied.
>
> @Lawrence:
>
> You can have tag inheritance this way:
>
> * Emacs :emacs:
> Emacs stuff
> ** Lisp :lisp:
> Emacs lisp stuff here
> *** Org :org_mode:
> Emacs + Lisp + Org mode stuff
> ** Org :org_mode:
> Emacs + Org mode stuff (but not lisp)
> --
>
> Kaushal Modi
>
[-- Attachment #2: Type: text/html, Size: 4326 bytes --]
next prev parent reply other threads:[~2018-02-01 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 15:07 Ad-hoc, mix-and-match tag hierarchies? Lawrence Bottorff
2018-02-01 15:28 ` John Kitchin
2018-02-01 15:36 ` Kaushal Modi
2018-02-01 19:45 ` Lawrence Bottorff [this message]
2018-02-04 3:18 ` John Kitchin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFAhFSUPxONW7j51qOXhi814GNnjsJgnWCj-EcoLFQKQVDk7TA@mail.gmail.com \
--to=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=kaushal.modi@gmail.com \
/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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.