From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: install org-element, org-db
Date: Fri, 28 Aug 2015 20:17:02 +0200 [thread overview]
Message-ID: <87si7346sh.fsf@gmx.us> (raw)
In-Reply-To: CAFAhFSVZkjk+E-yADfbO=orriT__adKXArTjLbK9RkLAs7pKNA@mail.gmail.com
Lawrence Bottorff <borgauf@gmail.com> writes:
> Yes, I got confused when I did M-x org-element-interpret-data and got
> nothing. I used it in a code block and it worked fine. Beginner question
> for sure: Why do these functions not work as M-x commands, rather, just in
> elisp code?
The technical reason: Function that are not marked as interactive won't
show up in M-x. See the the docstring of interactive and the elisp manual
for details.
Why wasn't it marked interactive [note, I'm speculating here]? It's
unlikely that you could want or should to run org-element-interpret-data
with "hand-written" input. The org-element form becomes quite long (check
org-element-at-point on your favorite element). In any case, when you
need it just do M-:.
> BTW, how would I run org-element-interpret-data and have it just place the
> output directly into my buffer without placing it in the #+RESULTS: output
> format? I see I can customize the #+RESULTS: word itself, and, of
> course, *:results
> raw* almost gets it, but still puts the #+RESULTS: label at the top.
To the best of my knowledge I would say no. If I'm wrong Nick D will
surely chim in with the correct answer.
Rasmus
--
May contains speling mistake
next prev parent reply other threads:[~2015-08-28 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 16:12 install org-element, org-db Lawrence Bottorff
2015-08-28 16:27 ` Rasmus
2015-08-28 18:02 ` Lawrence Bottorff
2015-08-28 18:17 ` Rasmus [this message]
2015-08-28 18:21 ` Nick Dokos
2015-08-28 18:34 ` Nick Dokos
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=87si7346sh.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).