Hi John,
John Kitchin jkitc...@andrew.cmu.edu writes:
excellent, that is exactly where I would have expected it, in the
documentation for org-entry-put.
it would also make sense to say in org-entry-get that you get a
string.
I just added
Return the value as a string.
in the docstring.
Hi John,
John Kitchin jkitc...@andrew.cmu.edu writes:
2. I guess it makes sense that properties would be read as strings,
but that wasn't obvious from the documentation they would be strings.
3. It also wasn't obvious that you have to give org-entry-put a
string. If you try to set it to an
Bastien writes:
3. It also wasn't obvious that you have to give org-entry-put a
string. If you try to set it to an integer, you get strange control
characters like ^A or ^C.
Can you tell which place in the documentation you expect to find this
information? In functions' docstrings or in the
Achim Gratz strom...@nexgo.de writes:
Bastien writes:
3. It also wasn't obvious that you have to give org-entry-put a
string. If you try to set it to an integer, you get strange control
characters like ^A or ^C.
Can you tell which place in the documentation you expect to find this
excellent, that is exactly where I would have expected it, in the
documentation for org-entry-put.
it would also make sense to say in org-entry-get that you get a string. if
you store a number in a property, it is not obvious you can't just get it
and do math on it.
Thanks!
John
Happy New Year!
I was playing around with storing data in heading properties and then using
links to modify them. For example, a heading might be a quiz question, and
the links are the possible answers. Clicking on a link stores which link
was clicked on as a property, and also counts the number
