From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Parser - which values are possible for `archivedp'?
Date: Tue, 04 Mar 2014 17:19:22 +0100 [thread overview]
Message-ID: <87wqgaj5rp.fsf@gmail.com> (raw)
In-Reply-To: 87y50q55or.fsf@alphaville.bos.redhat.com
Nick Dokos <ndokos@gmail.com> writes:
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>>> > So if non-nil, it will be a list of tags, starting with the
>>> value of
>>> > org-archive-tag. AFAICT, the rest of the tags can be arbitrary.
>>>
>>>
>>>
>>> ** Second Level 2 :tag:my:ARCHIVE:
>>>
>>>
>>> ,------------------------------------------------
>>> | :tags ("tag" "my") [...] :archivedp ("ARCHIVE")
>>> `------------------------------------------------
>>>
>>> Change the order of the tags so that Archive comes before the others
>>> and you get:
>>>
>>> ** Second level 2 :ARCHIVE:tag:my:
>>> :tags ("tag" "my") :archivedp ("ARCHIVE" "tag" "my")
>>
>> A very useful feature of the `member' function in lisp programming, but
>> not that great in this case I would say ... why not use (car (member
>> ...))?
>> Then its just a string, and the single value of interest.
>
> Why? All that matters is whether it's nil or not.
Why not? With a tiny change in the code one would get rid of potential
redundancy in the parse tree, would cause less surprise for people who
look at the parsers output (what does ":archivedp ("ARCHIVE" "tag"
"my")" mean?) and would get something more logical (the value of
:archivedp is either nil or the string in org-archive-tag).
But its not really that important I guess, I just needed to know what
kind of values to expect in that place - thanks for the hints. I
use that in another program where it does matter if its a boolean, a
string or a list of strings ...
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-03-04 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 14:16 Parser - which values are possible for `archivedp'? Thorsten Jolitz
2014-03-04 14:35 ` Nick Dokos
2014-03-04 14:47 ` Thorsten Jolitz
2014-03-04 14:51 ` Jonathan Leech-Pepin
2014-03-04 14:58 ` Thorsten Jolitz
2014-03-04 15:44 ` Nick Dokos
2014-03-04 16:19 ` Thorsten Jolitz [this message]
2014-03-04 14:52 ` Thorsten Jolitz
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=87wqgaj5rp.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).