emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: turn off monospace in src result
Date: Thu, 17 Jul 2014 22:50:18 +0100	[thread overview]
Message-ID: <olu1ttjven9.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87k37b4qew.fsf@alphaville.bos.redhat.com

Hi Nick,

Nick Dokos <ndokos@gmail.com> writes:

> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>> Hi regcl,
>> regcl <regcl@channing.harvard.edu> writes:
>>> With this line in my .org file ...
>>> This is src_R{foo<-"FOO"; paste(foo)}.
>>> ... when I publish to html or pdf, I get ...
>>> This is FOO.
>>> ... which is wonderful, except that "FOO" is monospace.  
>>> Can I turn off monospace for all results of inline source?
>> I do not know, how to do that for all inline source blocks.  But you can
>> turn it off
>> 1. per code block as in src_R[:results raw]{foo<-"FOO"; paste(foo)}
> Looks like
> This is src_R[:results raw]{foo<-"FOO"; paste(foo)}.
> produces a newline after the evaluated code block in the HTML file,
> which is rendered as a space between the word FOO and the period.  Bug?

I tend to agree.  There was some discussion on this last year [fn:1] that went
dead after a while.  I still think that modifying raw results (as in
adding newline) should be avoided -- at least in inline source blocks.



[fn:1] http://article.gmane.org/gmane.emacs.orgmode/71385

  reply	other threads:[~2014-07-17 21:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20  3:39 :exclude sub folder in org-publish regcl
2014-06-20 15:15 ` Nick Dokos
2014-06-25  8:49 ` Bastien
2014-07-17 16:14   ` turn off monospace in src result regcl
2014-07-17 21:28     ` Andreas Leha
2014-07-17 21:38       ` Nick Dokos
2014-07-17 21:50         ` Andreas Leha [this message]
2014-07-21 19:47   ` :exclude sub folder in org-publish regcl
2014-07-28 15:49     ` Bastien
2014-08-06 22:23       ` regcl

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:

  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=olu1ttjven9.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).