From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Bastien <bzg@gnu.org>
Cc: Achim Gratz <Stromeko@nexgo.de>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: are heading properties always strings?
Date: Fri, 3 Jan 2014 16:14:03 -0500 [thread overview]
Message-ID: <CAJ51ETpCbjwheP+wjQtoMF2vgL_AFMA9-Ag2BfNsdgqv=M99kg@mail.gmail.com> (raw)
In-Reply-To: <8761q1we4i.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
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
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Fri, Jan 3, 2014 at 5:31 AM, Bastien <bzg@gnu.org> wrote:
> Achim Gratz <Stromeko@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
> >> information? In functions' docstrings or in the manual?
> >
> > Besides documenting the requirement, I guess it makes sense to check for
> > stringiness before using the argument.
>
> Indeed, done here:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=9758f2
>
> --
> Bastien
>
>
[-- Attachment #2: Type: text/html, Size: 1962 bytes --]
next prev parent reply other threads:[~2014-01-03 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 14:36 are heading properties always strings? John Kitchin
2014-01-03 8:48 ` Bastien
2014-01-03 8:52 ` Achim Gratz
2014-01-03 10:31 ` Bastien
2014-01-03 21:14 ` John Kitchin [this message]
2014-01-04 13:49 ` Bastien
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='CAJ51ETpCbjwheP+wjQtoMF2vgL_AFMA9-Ag2BfNsdgqv=M99kg@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=Stromeko@nexgo.de \
--cc=bzg@gnu.org \
--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).