From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Org Mode <emacs-orgmode@gnu.org>, rpgoldman@sift.info
Subject: Re: Possible bug in ordered tasks
Date: Sat, 26 Jun 2010 07:55:20 +0200 [thread overview]
Message-ID: <3A51DA88-E03E-40EE-8CB4-51C8589E1108@gmail.com> (raw)
In-Reply-To: <87eifvdjsm.fsf@gollum.intra.norang.ca>
On Jun 25, 2010, at 8:55 PM, Bernt Hansen wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Jun 25, 2010, at 3:23 PM, Robert Goldman wrote:
>>
>>> Question: what is the proper way to get a NIL into a property? Are
>>> we
>>> to use () instead of "nil"? Or are property values always
>>> interpreted
>>> as strings?
>>>
>>> Apologies in advance if this is a stupid question!
>>
>> Not a stupid question at all.
>>
>> There is no way, currently. Property values are string - the only
>> way to make
>> org-entry-get return nil is to not have the property defined at all.
>
> I've wanted a similar thing in the past for the LOGGING property where
> the parent task has special logging set via the LOGGING property but I
> want to undo that for some of the child tasks so they use the default
> logging setup.
>
> Having a way to undefine a property would be good in general I think.
This does now work, the property value "nil" will now be interpreted as
explicit undefine of a property.
- Carsten
next prev parent reply other threads:[~2010-06-26 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 15:42 Possible bug in ordered tasks Robert Goldman
2010-06-25 7:03 ` Carsten Dominik
2010-06-25 13:23 ` Robert Goldman
2010-06-25 14:12 ` Carsten Dominik
2010-06-25 14:48 ` Robert Goldman
2010-06-25 16:21 ` Carsten Dominik
2010-06-25 18:55 ` Bernt Hansen
2010-06-26 5:55 ` Carsten Dominik [this message]
2010-06-26 11:34 ` Bernt Hansen
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=3A51DA88-E03E-40EE-8CB4-51C8589E1108@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=rpgoldman@sift.info \
/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).