From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brett Witty Subject: Re: [Feature Request] HEADLINE special property Date: Tue, 21 Oct 2014 09:20:24 +1100 Message-ID: References: <878ulbn0kx.fsf@nicolasgoaziou.fr> <87iojqkad8.fsf@bzg.ath.cx> <871tq22850.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e013c65c270ceac0505e221a1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XgLK9-0005Yz-HK for emacs-orgmode@gnu.org; Mon, 20 Oct 2014 18:21:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XgLK8-00031w-40 for emacs-orgmode@gnu.org; Mon, 20 Oct 2014 18:21:09 -0400 In-Reply-To: <871tq22850.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien , Brett Witty , Org mailing list --089e013c65c270ceac0505e221a1 Content-Type: text/plain; charset=UTF-8 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 wrote: > Hello, > > Bastien writes: > > > Nicolas Goaziou 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 > --089e013c65c270ceac0505e221a1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Seems like a good solution. Although how about HEADLI= NE_LEVEL, OUTLINE_LEVEL or some abbreviation to make it more unlikely to cl= ash with user defined properties?

BrettW

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

Bastien <bzg@gnu.org> writes:

> Nicolas Goaziou <mail@nic= olasgoaziou.fr> writes:
>
>> I think "ITEM" is expected return the headline without a= ll 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

=C2=A0 #+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

--089e013c65c270ceac0505e221a1--