From: Kaushal Modi <kaushal.modi@gmail.com>
To: Karl Voit <news1142@karl-voit.at>
Cc: emacs-orgmode@gnu.org
Subject: Re: Make tag inheritance explicit
Date: Tue, 23 Jan 2018 15:15:13 +0000 [thread overview]
Message-ID: <CAFyQvY3YzahYpuqz7_h87Fr0E2Vw32pkoU+859u8CtVD8Xh+uA@mail.gmail.com> (raw)
In-Reply-To: <2018-01-23T15-38-21@devnull.Karl-Voit.at>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
On Tue, Jan 23, 2018 at 9:45 AM Karl Voit <devnull@karl-voit.at> wrote:
>
> > 2. Use `org-get-tags-at' with point on "Task 1" heading in your example.
> > `org-get-tags' returns a list of tags *only* at the current heading.
> > `org-get-tags-at' returns inherited tags too.
>
> You mean for developing a custom-made function that provides the
> feature I was asking for?
>
By "feature", you mean copying all the inherited tags to the heading at
point?
My suggestion implied that you can skip that copying step altogether and
directly use org-get-tags-at to gets all the inherited tags for the current
heading. That way, you wouldn't need to add redundant information to your
Org file.
> Yes, this helps a lot to me.
>
Great! :)
First, I wanted to get a confirmation that this feature is not
> already part of Org-mode because (as usual) this seemed obvious to
> me when using export functionality ;-)
>
It's not clear what you mean by "feature is not already part of Org-mode".
Org mode provides `org-get-tags-at', which any Org exporter can use. How
that function is used is, I think, very subjective. The way I use it in
ox-hugo is probably not used in other exporters.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2019 bytes --]
next prev parent reply other threads:[~2018-01-23 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 10:22 Make tag inheritance explicit Karl Voit
2018-01-23 12:16 ` Kaushal Modi
2018-01-23 14:44 ` Karl Voit
2018-01-23 15:15 ` Kaushal Modi [this message]
2018-01-23 17:33 ` Karl Voit
2018-01-23 12:17 ` Carsten Dominik
2018-01-23 14:55 ` Karl Voit
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=CAFyQvY3YzahYpuqz7_h87Fr0E2Vw32pkoU+859u8CtVD8Xh+uA@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@karl-voit.at \
/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.