Nick Dokos <ndo...@gmail.com> writes: > Thorsten Jolitz <tjol...@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