[Feature Request] HEADLINE special property

[Feature Request] HEADLINE special property

[Brett Witty]

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

(Following Thorsten's helpful response:
http://article.gmane.org/gmane.emacs.orgmode/90768)

I'd like an extra special property of HEADLINE which is ITEM without all
the other metadata. Specifically the output of:

(org-get-heading t t)

I find the ITEM special property too noisy inside of a table, and I have
all the metadata without the actual headline by itself.

I'm unsure if the special properties "HEADING" and "ITEM" are confusing as
being slightly different concepts, so a better name might be good.

Brett Witty

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

Re: [Feature Request] HEADLINE special property

[Nicolas Goaziou]

Hello,

Brett Witty <brettwitty@brettwitty.net> writes:

> (Following Thorsten's helpful response:
> http://article.gmane.org/gmane.emacs.orgmode/90768)
>
> I'd like an extra special property of HEADLINE which is ITEM without all
> the other metadata. Specifically the output of:
>
> (org-get-heading t t)
>
> I find the ITEM special property too noisy inside of a table, and I have
> all the metadata without the actual headline by itself.
>
> I'm unsure if the special properties "HEADING" and "ITEM" are confusing as
> being slightly different concepts, so a better name might be good.

I think "ITEM" is expected return the headline without all the meta
data. If no one objects, I'll change it so in master.


Regards,

-- 
Nicolas Goaziou

Re: [Feature Request] HEADLINE special property

[Bastien]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> I think "ITEM" is expected return the headline without all the meta
> data. If no one objects, I'll change it so in master.

Yes, thanks for this,

-- 
 Bastien

Re: [Feature Request] HEADLINE special property

[Nicolas Goaziou]

Hello,

Bastien <bzg@gnu.org> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> I think "ITEM" is expected return the headline without all the meta
>> data. If no one objects, I'll change it so in master.
>
> Yes, thanks for this,

Here is the current state:

ITEM property includes stars, TODO keyword, priority, headline and tags,
but only if they do not have already a dedicated column. So, in the
following example

  #+COLUMNS: %25ITEM %TODO %PRIORITY %TAGS

ITEM will contain only stars and headline. This cannot properly work in,
e.g., a clock table, which doesn't know about columns.

We can get rid of this "smart" behaviour and remove TODO keyword,
priority and tags in all cases.

However the situation is not so simple for the stars, since there is no
LEVEL special property. IOW, if we remove the stars, it is actually not
possible anymore to know the level of the headline.

If we want to remove them, I suggest adding a new LEVEL special
property. Note that in this case, user defined properties cannot be
labelled "level" anymore. Another option, as the OP suggested, is to
create a new special property, e.g., HEADLINE, which will contain only
the title.

WDYT?


Regards,

-- 
Nicolas Goaziou

Re: [Feature Request] HEADLINE special property

[Brett Witty]

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

Seems like a good solution. Although how about HEADLINE_LEVEL,
OUTLINE_LEVEL or some abbreviation to make it more unlikely to clash with
user defined properties?

BrettW

On Tue, Oct 21, 2014 at 12:16 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Bastien <bzg@gnu.org> writes:
>
> > Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> >
> >> I think "ITEM" is expected return the headline without all the meta
> >> data. If no one objects, I'll change it so in master.
> >
> > Yes, thanks for this,
>
> Here is the current state:
>
> ITEM property includes stars, TODO keyword, priority, headline and tags,
> but only if they do not have already a dedicated column. So, in the
> following example
>
>   #+COLUMNS: %25ITEM %TODO %PRIORITY %TAGS
>
> ITEM will contain only stars and headline. This cannot properly work in,
> e.g., a clock table, which doesn't know about columns.
>
> We can get rid of this "smart" behaviour and remove TODO keyword,
> priority and tags in all cases.
>
> However the situation is not so simple for the stars, since there is no
> LEVEL special property. IOW, if we remove the stars, it is actually not
> possible anymore to know the level of the headline.
>
> If we want to remove them, I suggest adding a new LEVEL special
> property. Note that in this case, user defined properties cannot be
> labelled "level" anymore. Another option, as the OP suggested, is to
> create a new special property, e.g., HEADLINE, which will contain only
> the title.
>
> WDYT?
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

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

Re: [Feature Request] HEADLINE special property

[Nicolas Goaziou]

Brett Witty <brettwitty@brettwitty.net> writes:

> Seems like a good solution. Although how about HEADLINE_LEVEL,
> OUTLINE_LEVEL or some abbreviation to make it more unlikely to clash with
> user defined properties?

I stripped all meta-data from "ITEM" special property in master.
However, I kept the stars as they inform about relationship between
headlines in a columnview table.

Please report if you encounter any bug.


Regards,