From: Nick Dokos <nicholas.dokos@hp.com>
To: nicholas.dokos@hp.com
Cc: nt=5FBela=3DEFche=3F=3D?= <vincent.b.1@hotmail.fr>,
"Org mode" <emacs-orgmode@gnu.org>,
"Noorul Islam K M" <noorul@noorul.com>
Subject: Re: Re: does #+PROPERTY still exist ?
Date: Wed, 22 Sep 2010 04:09:53 -0400 [thread overview]
Message-ID: <19364.1285142993@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Wed, 22 Sep 2010 03:36:46 EDT." <18525.1285141006@gamaville.dokosmarshall.org>
Nick Dokos <nicholas.dokos@hp.com> wrote:
> Noorul Islam K M <noorul@noorul.com> wrote:
>
> >
> > In the below example
> >
> > ----------------------------------------------------------------
> > #+PROPERTY: Age 25
> > #+COLUMNS: %25ITEM %Age
> >
> > * Heading 1
> > * Heading 2
> > ----------------------------------------------------------------
> >
> > When I try to use column view to edit the property it is not using the
> > format that I mentioned at the file level.
> >
> > But the following one works
> >
> > ----------------------------------------------------------------
> > * Heading 1
> > :PROPERTIES:
> > :Age: 25
> > :COLUMNS: %25ITEM %Age
> > :END:
> > * Heading 2
> > ----------------------------------------------------------------
> >
> > Looks like the file level settings are not working.
> >
>
> If I evaluate the form
>
> (org-entry-get (point) "Age" t)
>
> with the point at any heading, I get "25". OTOH, even with
> org-use-property-inheritance set to t, column view does not
> show it. Ergo, it's a column view bug.
>
> In org-columns-compute, I see
>
> ...
> (while (re-search-backward re beg t)
> (setq sumpos (match-beginning 0)
> last-level level
> level (org-outline-level)
> val (org-entry-get nil property)
> ...
>
> I suspect the val line needs to be
>
> val (org-entry-get nil property org-use-property-inheritance)
>
> instead.
>
No, that's not it. I think the basic problem is that
org-entry-properties ignores inheritance altogether (in particular,
it parses property names explicitly instead of using org-entry-get)[1].
Nick
[1] ... but it's late, I'm tired and I may very well be wrong - again.
next prev parent reply other threads:[~2010-09-22 8:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 5:21 does #+PROPERTY still exist ? Vincent Belaïche
2010-09-22 6:10 ` Nick Dokos
2010-09-22 6:58 ` Noorul Islam K M
2010-09-22 7:36 ` Nick Dokos
2010-09-22 8:09 ` Nick Dokos [this message]
2010-09-22 8:43 ` Noorul Islam K M
2010-09-22 8:56 ` Noorul Islam
2010-09-22 9:05 ` Carsten Dominik
2010-09-22 9:17 ` Noorul Islam K M
2010-09-22 9:39 ` Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2010-09-23 3:13 Vincent Belaïche
2010-09-23 3:26 ` Erik Iverson
2010-09-23 4:23 ` Nick Dokos
2010-09-23 4:34 ` Nick Dokos
2010-09-23 5:19 ` Vincent Belaïche
2010-09-23 6:28 ` Carsten Dominik
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19364.1285142993@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=noorul@noorul.com \
--cc=vincent.b.1@hotmail.fr \
/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 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).