From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Disable org-babel-inline-result-wrap per inline code?
Date: Wed, 21 Sep 2016 10:11:26 -0400 [thread overview]
Message-ID: <878tul2vht.fsf@gmail.com> (raw)
In-Reply-To: a862b88c-494d-76cb-942e-861988ae9735@dagertech.net
"David A. Gershman" <dagershman@dagertech.net> writes:
> Forgive my several questions/emails. I'm working on getting lecture
> notes ready for next week and thus am running into several questions
> with Org HTML Export. Unfortunately, my searches typically result
> in manual page hits, but my problems seem to be a-typical. So...
>
> Given the following line:
>
> * Date: src_perl[:results output :exports none]{print 2016;}
>
> The result '2016' is surrounded by '=' so that HTML export results
> in <code></code> tags surrounding the '2016'.
>
I think that should be :exports results, not none.
> According to the manual section 14.5, 'org-babel-inline-result-wrap'
> defines how the results are wrapped. Executing a (print
> org-babel-inline-result-wrap), I get:
>
> {blank line}
> =%s=
> =%s=
>
C-h v org-babel-inline-result-wrap says that it has to have a %s in
it: you can't just set it to "".
> so I attempted the following:
>
> * Date: src_emacs-lisp[:exports none]{(setq org-babel-inline-result-wrap "")} src_perl[:results output :exports none]{print 2016;} src_emacs-lisp[:exports none]{(setq
> org-babel-inline-result-wrap "=%s=")}
>
OTOH, modifying your attempt a bit to conform to the above did not work for me either:
* Date: src_emacs-lisp[:exports none :results none ]{(setq org-babel-inline-result-wrap "%s")} src_perl[:results output :exports results]{print 2016;} src_emacs-lisp[:exports none :results none]{(setq org-babel-inline-result-wrap "=%s=")}
still gives me the <code></code> tags. When I C-c C-c by hand on the
lisp src blocks, the variable does change value, so I don't understand
why putting the whole thing together does not work.
> in the hopes of temporarily disabling the '=' wrapping. Sadly no luck.
>
> I don't want to globally, or even for the whole buffer turn off the
> '=%s='...just on a case-by-case basis.
>
> Any ideas?
>
> --dag
>
> P.S. In reality, 2016 will be replaced with a function call which
> takes an integer and converts it to a full blown date based on a
> starting point. Thus, the headlines will result in "Date: September
> 20, 2016" where each date is different based on the integer. This
> will allow me to set the starting date at the top of the .org file
> and all the date-based headlines can be computed.
>
--
Nick
next prev parent reply other threads:[~2016-09-21 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 6:07 Disable org-babel-inline-result-wrap per inline code? David A. Gershman
2016-09-21 11:49 ` Adam Porter
2016-09-21 14:23 ` David A. Gershman
2016-09-21 20:04 ` Adam Porter
2016-09-21 14:11 ` Nick Dokos [this message]
[not found] <d406cbbb44ac455abd5c0a77c95b63ab@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-21 7:11 ` Eric S Fraga
2016-09-21 14:15 ` David A. Gershman
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=878tul2vht.fsf@gmail.com \
--to=ndokos@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).