* BUG? Extra colon for inherited tags in agenda @ 2019-09-04 22:44 David Masterson 2019-09-05 5:50 ` Carsten Dominik 0 siblings, 1 reply; 4+ messages in thread From: David Masterson @ 2019-09-04 22:44 UTC (permalink / raw) To: emacs-orgmode@gnu.org 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: BUG? Extra colon for inherited tags in agenda 2019-09-04 22:44 BUG? Extra colon for inherited tags in agenda David Masterson @ 2019-09-05 5:50 ` Carsten Dominik 2019-09-06 23:14 ` David Masterson 0 siblings, 1 reply; 4+ messages in thread From: Carsten Dominik @ 2019-09-05 5:50 UTC (permalink / raw) To: David Masterson; +Cc: org-mode list [-- 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 --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: BUG? Extra colon for inherited tags in agenda 2019-09-05 5:50 ` Carsten Dominik @ 2019-09-06 23:14 ` David Masterson 2019-09-07 6:53 ` Carsten Dominik 0 siblings, 1 reply; 4+ messages in thread From: David Masterson @ 2019-09-06 23:14 UTC (permalink / raw) To: Carsten Dominik; +Cc: org-mode list 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: BUG? Extra colon for inherited tags in agenda 2019-09-06 23:14 ` David Masterson @ 2019-09-07 6:53 ` Carsten Dominik 0 siblings, 0 replies; 4+ messages in thread From: Carsten Dominik @ 2019-09-07 6:53 UTC (permalink / raw) To: David Masterson; +Cc: org-mode list [-- 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 --] ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-09-07 6:53 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-09-04 22:44 BUG? Extra colon for inherited tags in agenda David Masterson 2019-09-05 5:50 ` Carsten Dominik 2019-09-06 23:14 ` David Masterson 2019-09-07 6:53 ` Carsten Dominik
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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).