Space after an inline emacs call affects output on export

Space after an inline emacs call affects output on export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

Could anybody explain why these two lines give different outputs for the
inline elisp calculation?

First line:

@@latex:\fbox{@@ src_emacs-lisp{(setq var-Q1 (string-to-number (calc-eval "evalv(15.357*(184.2-80))")))} @@latex:}@@

Second line:

@@latex:\fbox{@@ src_emacs-lisp{(setq var-Q1 (string-to-number (calc-eval "evalv(15.357*(184.2-80))")))}@@latex:}@@

The only difference in these two lines is a space before the last LaTeX
directive.

Screen shot attached.


[-- Attachment #2: screendump-20160406132404.png --]
[-- Type: image/png, Size: 4627 bytes --]

[-- Attachment #3: Type: text/plain, Size: 134 bytes --]


The first is what I want, by the way.

thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-705-g716e33

Re: Space after an inline emacs call affects output on export

[Nicolas Goaziou]

Hello,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Could anybody explain why these two lines give different outputs for the
> inline elisp calculation?
>
> First line:
>
> @@latex:\fbox{@@ src_emacs-lisp{(setq var-Q1 (string-to-number (calc-eval "evalv(15.357*(184.2-80))")))} @@latex:}@@
>
> Second line:
>
> @@latex:\fbox{@@ src_emacs-lisp{(setq var-Q1 (string-to-number (calc-eval "evalv(15.357*(184.2-80))")))}@@latex:}@@
>
> The only difference in these two lines is a space before the last LaTeX
> directive.

Wild guess. You forbade ":" after emphasis markers in
`org-emphasis-regexp-components'.

Regards,

-- 
Nicolas Goaziou

Re: Space after an inline emacs call affects output on export

[Eric S Fraga]

On Wednesday,  6 Apr 2016 at 14:37, Nicolas Goaziou wrote:
> Wild guess. You forbade ":" after emphasis markers in
> `org-emphasis-regexp-components'.

Ummm, I've never touched org-emphasis-regexp-components...

But I have played around with org-emphasis-alist, introducing @ as an
emphasis marker (as I did a long time ago to introduce \alert{} for
beamer per v8).  <blush>  So although @@latex:@@ etc. still works fine,
it has implications elsewhere.  I will remove my change to
org-emphasis-alist.

However, I am curious as to why the output from the inline source
evaluation is different?  I.e. why =xxx= versus xxx?  What is the
rationale for one versus the other?

Thanks,
eric
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-705-g716e33

Re: Space after an inline emacs call affects output on export

[Nicolas Goaziou]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> However, I am curious as to why the output from the inline source
> evaluation is different?  I.e. why =xxx= versus xxx?  What is the
> rationale for one versus the other?

The result of the inline source evaluation is =xxx= (I'll ignore the
no-op results macro around it). If =xxx= can be parsed as a verbatim
object, it becomes \textt{xxx} in the output. If it cannot, = signs
appear as-is in the output.

In the second case, something is preventing =xxx= from being parsed as
a verbatim object.


Regards,

Re: Space after an inline emacs call affects output on export

[Eric S Fraga]

On Wednesday,  6 Apr 2016 at 15:21, Nicolas Goaziou wrote:
> In the second case, something is preventing =xxx= from being parsed as
> a verbatim object.

Ah, I see.  Makes perfect sense.  Thanks.
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-705-g716e33