BUG? Extra colon for inherited tags in agenda

BUG? Extra colon for inherited tags in agenda

[David Masterson]

I see that, for tags picked up via inheritance from parent headlines,
when the tags are produced in the agenda, the current agenda item will
have an extra colon after the inherited tags.  Is this by design?  Can
that be controlled?

Example Parent          :tag1:
Example child of Parent :tag1::
--
David

Re: BUG? Extra colon for inherited tags in agenda

[Carsten Dominik]

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

Hi,




On Thu, Sep 5, 2019, 00:45 David Masterson <dsmasterson@outlook.com> wrote:

> I see that, for tags picked up via inheritance from parent headlines,
> when the tags are produced in the agenda, the current agenda item will
> have an extra colon after the inherited tags.  Is this by design?


Yes, it is by design, for display in the agenda only, to show the
difference between direct and inherited tags.

Why would. You want to change it?

Carsten


Can
> that be controlled?
>
> Example Parent          :tag1:
> Example child of Parent :tag1::
> --
> David
>
>

[-- Attachment #2: Type: text/html, Size: 1298 bytes --]

Re: BUG? Extra colon for inherited tags in agenda

[David Masterson]

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On Thu, Sep 5, 2019, 00:45 David Masterson <dsmasterson@outlook.com> wrote:

>>  I see that, for tags picked up via inheritance from parent headlines,
>>  when the tags are produced in the agenda, the current agenda item will
>>  have an extra colon after the inherited tags.  Is this by design? 

> Yes, it is by design, for display in the agenda only, to show the
> difference between direct and inherited tags. 
>
> Why would. You want to change it? 

Maybe not. Didn't remember seeing it in the documentation, so, at first,
I thought it might be a bug, but it made sense after I thought about it.
As to in the agenda only, I could also see this being something that
export backend might want access to (if it doen't already have access
to it).  Other than that, it's good.
--
David

Re: BUG? Extra colon for inherited tags in agenda

[Carsten Dominik]

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

Hi David

On Sat, Sep 7, 2019 at 1:14 AM David Masterson <dsmasterson@outlook.com>
wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
> > On Thu, Sep 5, 2019, 00:45 David Masterson <dsmasterson@outlook.com>
> wrote:
>
> >>  I see that, for tags picked up via inheritance from parent headlines,
> >>  when the tags are produced in the agenda, the current agenda item will
> >>  have an extra colon after the inherited tags.  Is this by design?
>
> > Yes, it is by design, for display in the agenda only, to show the
> > difference between direct and inherited tags.
> >
> > Why would. You want to change it?
>
> Maybe not. Didn't remember seeing it in the documentation, so, at first,
> I thought it might be a bug, but it made sense after I thought about it.
> As to in the agenda only, I could also see this being something that
> export backend might want access to (if it doen't already have access
> to it).  Other than that, it's good.
>

Yes, if an export backend wanted to show inherited tags at entries, the
same syntax could be used.  I don't know if any backend is trying to show
inherited tags.

In the Agenda this is necessary because entries are shown outside of their
normal hierarchy.  In an Org buffer, or in an exported version of it, the
original hierarchy is still in place.

Cheers

Carsten


> --
> David
>

[-- Attachment #2: Type: text/html, Size: 2141 bytes --]