Re: [O] Bug in export of call lines

2014-03-11 Thread Thomas S. Dye
Eric Schulte writes: > I think it is allowable for raw results to include newlines. After if R > returns a newline, the purpose of raw results is specifically to *not* > change the result. I believe the best approach is to customize the > inline results wrap as above, and then use non-raw proce

Re: [O] Bug in export of call lines

2014-03-11 Thread Eric Schulte
t...@tsdye.com (Thomas S. Dye) writes: > Hi Eric, > > Eric Schulte writes: > >> This actually is also an issue with shell code blocks. The fix is to >> customize the org-babel-inline-result-wrap variable (e.g., as follows) >> instead of setting the result type to RAW. >> >> (setq org-babel-inl

Re: [O] Bug in export of call lines

2014-03-11 Thread Thomas S. Dye
Hi Eric, Eric Schulte writes: > This actually is also an issue with shell code blocks. The fix is to > customize the org-babel-inline-result-wrap variable (e.g., as follows) > instead of setting the result type to RAW. > > (setq org-babel-inline-result-wrap "%s") > > Perhaps a note about this

Re: [O] Bug in export of call lines

2014-03-11 Thread Eric Schulte
Hi Tom, This actually is also an issue with shell code blocks. The fix is to customize the org-babel-inline-result-wrap variable (e.g., as follows) instead of setting the result type to RAW. (setq org-babel-inline-result-wrap "%s") Perhaps a note about this variable should be added to the des

Re: [O] Bug in export of call lines

2014-03-10 Thread Thomas S. Dye
Eric Schulte writes: > Somehow this doesn't seem to be a problem with other languages, so I > believe the necessary fix may be R specific. Following is a small test that appears to indicate that the bug is R specific and only bites when the source code block has :results raw. #+DATE: \today

Re: [O] Bug in export of call lines

2014-03-10 Thread Eric Schulte
t...@tsdye.com (Thomas S. Dye) writes: > Aloha Nicolas, > > Nicolas Goaziou writes: > >> Hello, >> >> t...@tsdye.com (Thomas S. Dye) writes: >> >>> I've been dusting off a draft paper written when the new export >>> framework was still in contrib. Now that I've brought the file >>> up-to-date so

Re: [O] Bug in export of call lines

2014-03-10 Thread Thomas S. Dye
Aloha Nicolas, Nicolas Goaziou writes: > Hello, > > t...@tsdye.com (Thomas S. Dye) writes: > >> I've been dusting off a draft paper written when the new export >> framework was still in contrib. Now that I've brought the file >> up-to-date so that it exports asynchronously again, I'm getting an

Re: [O] Bug in export of call lines

2014-03-10 Thread Nicolas Goaziou
Hello, t...@tsdye.com (Thomas S. Dye) writes: > I've been dusting off a draft paper written when the new export > framework was still in contrib. Now that I've brought the file > up-to-date so that it exports asynchronously again, I'm getting an error > that wasn't there before. [...] > Note th

[O] Bug in export of call lines

2014-03-06 Thread Thomas S. Dye
Aloha all, I've been dusting off a draft paper written when the new export framework was still in contrib. Now that I've brought the file up-to-date so that it exports asynchronously again, I'm getting an error that wasn't there before. This Org mode input: - B.01397 :: This is an unusual tool