Hi,
I've temporarily removed the use of the org-babel-temp-directory due to
this problem, and other issues it is causing on shutdown with older
versions of Emacs.
I will revisit this issue next week when I'm back from vacation and have
time to work out a full solution.
Thanks for the reports --
Hi Steven,
If your R blocks are outputting actual R code, then you can use the
"code" argument to the :results header argument to have the output
exported as R code under listings instead of within verbatim blocks.
--8<---cut here---start->8---
#+begin_src R :re
Hi John,
Thanks for compiling all of this information on this issue.
As recall from investigating this last time it came up, the current
state is that
1) Babel relies on gnuplot-mode for session based evaluation
2) gnuplot-mode does not work on windows
Which results in the need to add a ":sessio
Hi Giorgio,
This is currently not possible as we're not currently expanding
#+include links during tangling. I agree this would be useful behavior.
This seems to be related to a recent theme on the mailing list of
unifying tangling with the rest of the Org-mode export functionality.
Once/if tang
Hi Sébastien,
This is a tricky problem indeed. After some debugging, it appears that
the problem is the result of the "org" code block calling
`org-export-as-latex' on its body, while `org-export-as-latex' is
already called on the entire org-mode file. Apparently the Org-mode
exporter is not cur
Sébastien Vauban writes:
> Hi Eric,
>
>> 1) Babel relies on gnuplot-mode for session based evaluation
>> 2) gnuplot-mode does not work on windows
>>
>> Which results in the need to add a ":session none" header argument on
>> windows to avoid session based evaluation.
>
> I thought that =:session
Hi Seb,
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>>> The error occurs with such a simple document:
>>>
>>> #+TITLE: Org-isodoc
>>> #+LANGUAGE: en_US
>>>
>>> * Context
>>>
>>> Thi
Thanks Harri!
I've just applied this patch to the repository.
If you think you'll want to contribute patches longer than 10 lines
please consider the FSF assignment process described at
http://orgmode.org/worg/org-contribute.php
Thanks -- Eric
Harri Kiiskinen writes:
> The attaches patch adds
R :var data=whatever :var file=file-name
R code...
#+end_src
and then call the function with the file name passed in as a variable
assignment
#+call: the-function(data=whatever, file=fig-one.pdf)
Best -- Eric
>
> Cheers,
> Chris
>
> On 10 September 2010 20:06, Eric Schulte wrot
o
the original org file to collect header arguments in context during
export. This appears to resolve the issue (at least for me). Please
let me know if it works for you.
Best -- Eric
Tom Short writes:
> Eric Schulte gmail.com> writes:
>
>>
>> Hi Austin,
>>
&g
Hi Richard,
This is a good idea, I too frequently find myself splitting code blocks.
How about this following alternative implementation which should be
smart enough to notice if it is inside of a code block, and should work
across any code block type.
--8<---cut here---sta
Hi Aidan,
This is not a bug, this is the expected behavior of
org-babel-lob-ingest, if you would like a file to always be loaded into
your library of babel, then you can add the call to org-babel-lob-ingest
to your .emacs initialization file.
Best -- Eric
Aidan Gauland writes:
> Calling org-ba
Hi Ista,
You're correct, currently the caching mechanism employed by Babel only
checks that the same code blocks are used to assign variable, and
doesn't check that the results of those code blocks are the same.
I'll look into what would be required to include variable values in
cache hash calcul
Hi Richard,
Richard Riley writes:
> Richard Riley writes:
>
>> "Eric Schulte" writes:
>>
>>>
>>> Let me know what you think. I notice your implementation uses
>>> regions,
>>
>> It puts the begin/src markers around the region
Jambunathan K writes:
> "Eric Schulte" writes:
>
>> Hi Aidan,
>>
>> This is not a bug, this is the expected behavior of
>> org-babel-lob-ingest, if you would like a file to always be loaded into
>> your library of babel, then you can add the
Hi Tom,
The following should inhibit the exportation of code block names.
(setq org-export-latex-listings-w-names nil)
This is something we've been meaning to make customizable for a while,
but it has yet to rise to the top of the Babel task stack.
Best -- Eric
"Thomas S. Dye" writes:
> Al
| I'd like to write a concluding email for this thread for future
> | searchers to find. This easy solution is brought to you by Eric
> | Schulte and Christian Moe.
> |
> | Place the following in your .emacs or init.el file:
> | ;; org-mode color
> | (org-add-link-type
> |
Jambunathan K writes:
[...]
>
> If headlines are considered as code blocks one actually inflate
> headlines and execute them for interesting side-effects.
Rather than create new syntax allowing headlines to be interpreted as
Org-mode code blocks, we could implement this ability of finding and
ex
Hi Seb,
Would such an environment be in addition too or in place of wrapping
results in the example environment? What would you suggest for tabular
results?
One very nice property of the current setup is that it relies solely on
vanilla Org-mode for export features. If the example export of Org
Richard Riley writes:
> "Eric Schulte" writes:
>
>> Hi Richard,
>>
>> Richard Riley writes:
>>
>>> Richard Riley writes:
>>>
>>>> "Eric Schulte" writes:
>>>>
>>>>>
>>>>
Hi Seb,
Thanks for pointing this out, I've pushed up a fix to this spacing
issue.
Best -- Eric
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> I've just added [org-babel-demarcate-block] to the org-mode repo.
>
> A comment. Consider
Sébastien Vauban writes:
> Hi Eric,
>
> Sébastien Vauban wrote:
>> "Eric Schulte" wrote:
>>> I've just added [org-babel-demarcate-block] to the org-mode repo.
>>
>>> For now it still lives in the babel keymap behind (C-c C-v d) since it is
&
Hi Achim,
Thanks for pointing these warnings out, they are now fixed.
Achim Gratz writes:
> Hi Eric,
>
> your commit 88b8b839 raises the following warnings during compile on
> EMACS 23.1:
>
> In org-babel-demarcate-block:
> ob.el:1157:27:Warning: `previous-line' used from Lisp code
> That comma
Hi Christian,
I agree generalizing this function over all block types would be very
useful. When I find the time I will make this change.
Thanks -- Eric
Christian Moe writes:
> Hi,
>
> I'm late to this discussion, but just a lateral thought:
>
> Would you consider rewriting this as `org-demar
Hi Seb,
I think you've made a good point for adding this functionality. I'll
put this on the Babel TODO stack, and reply to this email when we get
something implemented.
Best -- Eric
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>>
Yes,
I've had this marked for reply for some time now, I'll be sure to look
at it by the end of the week.
Best -- Eric
Carsten Dominik writes:
> Hi Eric,
>
> could I ask you to take a look at this?
>
> Thanks
>
> - Carsten
>
> On Sep 7, 2010, at 12:57 AM, Jambunathan K wrote:
>
>>
Is it p
Hi,
Inquisitive Scientist writes:
> Dear Experts,
>
> I'd like to make a suggestion/feature-request for people who write dynamic
> blocks (which are very cool):
>
> 1. It would be really handy to have a parameter of the form :tname
> which puts a #+TBLNAME: into the top of the table created b
rent-level) 0) ?*) " ")))
> X (insert (concat (if (looking-at "^") "" "\n")
> X (if arg (concat stars "\n") "")
> X "#+begin_src " (read-from-minibuffer "Lang: ") "\n"
> X
>
>
Sébastien Vauban writes:
> Hi Eric and all the others,
>
> "Eric Schulte" wrote:
>> Sébastien Vauban writes:
>>> "Eric Schulte" wrote:
>>>>> The error occurs with such a simple document:
>>>>>
>>>>> #+T
Hi Rainer,
Sorry about the delayed reply.
Rainer M Krug writes:
> On 10/09/10 20:40, Eric Schulte wrote:
>> Hi Rainer,
>>
>> If you could send me an example of how to generate an svg image using
>> plantuml on the command line, I'll add that functionality to
Hi Christian,
Thanks for the complete bug report and reproduction information.
Unfortunately I was unable to reproduce the error you described. Does
the file /Users/CM/org/test2.org exist on your system? Presumably that
is the file from which you are exporting. Is it saved before you
export?
T
Hi Richard,
I think this is a really great idea. I agree this could greatly raise
awareness of Org-mode and Org-mode features both for the completely
uninitiated and for the seasoned users.
We've been meaning to put together a Babel screencast, but as of yet
have not found the time or software.
Hi Jambunathan,
I've finally had a chance to test out this patch, and it's great! I'd
love to apply this to the core Org repository, however given the size I
have to ask, have you (or are you willing to) signed the FSF papers?
http://orgmode.org/worg/org-contribute.php
Cheers -- Eric
Jambunath
>>
>> The listings package throws an error when it sees language=org.
>
> Normal. It is unknown... unluckily!
>
I've used the following for org-mode listings
--8<---cut here---start->8---
\lstdefinelanguage{org}
{
morekeywords={:results, :session, :var,
Jambunathan K writes:
> Hello Eric
>
> Eric> Hi Jambunathan,
> Eric>
> Eric> I've finally had a chance to test out this patch, and it's great!
> Eric> I'd love to apply this to the core Org repository, however given
> Eric> the size I have to ask, have you (or are you willing to) signed
> Eric> t
Hi Seb,
Thanks for the suggestions, I've just implemented them.
Best -- Eric
Sébastien Vauban writes:
> Hi Eric and Richard,
>
> "Eric Schulte" wrote:
>> Applied, Thanks
>
> Two comments about that great function:
>
> - Would it be possible to leave
Hi Bill,
The `org-confirm-babel-evaluate' variable can be set to a function which
can query the user to confirm code block evaluation. The following code
does two things.
1) it creates and maintains a list of the files that the user has said
are safe for evaluation (this list will need to be r
Hi Seb,
I plan to extend the block demarcation function to all block types, but
haven't yet found the time.
Best -- Eric
Sébastien Vauban writes:
> Hi Eric,
>
> Sébastien Vauban wrote:
>> "Eric Schulte" wrote:
>>> Sébastien Vauban
>>> write
Bill Harris writes:
> "Eric Schulte" writes:
[...]
>> Note: the above requires that you pull down the latest version of
>> Org-mode.
>
> I've got 7.01h. I presume you mean something newer than that?
>
Yes, you'll need to pull a copy of Org-mode fr
Scot Becker writes:
> Dan,
[...]
>> - Would it make sense to have two different packages available via ELPA,
>
> To me, yes. I like using git for the development tree, but I expect
> that ELPA makes for a nice way for Windows users (and others who don't
> want to or can't use git) to get the l
Hi Rainer,
I'm not sure that code blocks are the solution for this particular
problem. The following simple function should do what you want.
--8<---cut here---start->8---
(defun schulte/current-table-to-tex (file)
"Export the current table as latex to FILE.
"Thomas S. Dye" writes:
> Aloha Rainer,
>
> Perhaps this will work? Eric Schulte wrote a function to make a LaTeX
> table out of an Org-mode table.
Ah, thanks for suggesting this Tom, I'd forgotten about that function.
If you'll indulge me, I'd like to e
Hi,
I've re-enabled this functionality, I believe the problems should be
fixed, from the commit message...
,
| commit a37072786c1da98ccfe6e6b4f481bfc83d61c4d2
| Author: Eric Schulte
| Date: Thu Sep 30 07:31:14 2010 -0600
|
| using `org-babel-temporary-directory' to collect
Fixed, Thanks -- Eric
Achim Gratz writes:
> "Eric Schulte" writes:
>> Thanks for the suggestions, I've just implemented them.
>
> This likely relates to commit eb0068e9, which raises this warning
>
> In org-babel-demarcate-block:
> ob.el:1141:49:Warning
Ah, Fixed, Thanks -- Eric
Rainer M Krug writes:
> Hi
>
> I just found a bug in ob-plantuml.el
>
> (if (string= (file-name-extension out-file) "svg")
> "-tsvg" "")
>
> needs to be changed to
>
> (if (string= (file-name-extension out-file) "svg")
> " -tsvg" "")
>
>
> as otherwise, when usi
I'm not sure,
Babel uses the existing speed-commands infrastructure already existing
in Org-mode for headlines, so the behavior should be the same, whatever
that behavior may be...
Best -- Eric
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> I
Achim Gratz writes:
> "Eric Schulte" writes:
>> I've re-enabled this functionality, I believe the problems should be
>> fixed, from the commit message...
>
> Byte compile warns:
>
> In org-babel-temp-file:
> ob.el:1792:36:Warning: reference to free
has
>
> (set-buffer (get-file-buffer org-current-export-file))
>
> But the value of org-current-exp-file is nil for a temporary buffer.
>
> The following commit brought in that change.
>
> commit efdf78172d9f7c0070c781d136a9b49a2a56fcc4
> Author: Eric Schulte
> Date: S
Hi,
This is exciting.
Rather than impose a complete directory/layout schema before-hand I'd
lean towards starting with a little more chaos and then letting the
structure of the test directory develop /naturally/. From the
discussion below it sounds like an initial structure of
testing/lisp/
tes
Jambunathan K writes:
> I managed to create an elpa compatible tar for orgmode. Recording here
> what I did in the hope that it will be useful.
>
> Creating ELPA-compatible tar:
>
> 1. Add the enclosed changes to Makefile.
> 2. Create an ELPA-compatible tarfile with
>$ make TAG=20100930 elpa
Hi Sebastian,
Sebastian Rose writes:
> "Eric Schulte" writes:
>> Hi,
>>
>> This is exciting.
>>
>> Rather than impose a complete directory/layout schema before-hand I'd
>> lean towards starting with a little more chaos and then letting the
"Eric Schulte" writes:
[...]
>
> Could we just load every test in tests/lisp by default, and then use the
> existing `ert' selection method to select and run tests. For example if
> we enforce our conventions on the level of test function name rather
> than on file
w
Sebastian Rose writes:
> "Eric Schulte" writes:
>> "Eric Schulte" writes:
>> To illustrate my suggestions, I've thrown together a couple simple Babel
>> tests roughly following this outline, currently up in the
>> `schulte-testing' branch
Hi Jambunathan,
Jambunathan K writes:
> Hello Eric
>
> "Eric Schulte" writes:
>> Jambunathan K writes:
>>
[...]
>>>
>>> ELPA Server-side setup:
>>>
>>
>> I think we can ignore the server-side setup, since that should be
Hi Bryan,
I have the following in my config which works for me
(add-to-list 'org-export-html-inline-image-extensions "svg")
Best -- Eric
Bryan Emrys writes:
> Hello all,
>
> I'm exporting an org page to xhtml and I'm trying to show an svg file in an
> xhtml page the same way that a png file
Hi Giovanni,
I'm unable to reproduce your bug. I can successfully export the
following to html w/o issue.
--8<---cut here---start->8---
Now let's see what happens:
#+begin_src python :results output :exports both
print "Babel"
limits = [1,2,3,4,5,6,7,8,9,10]
Puneeth writes:
> Hi Eric,
>>
>> You can still export to a temporary buffer (`A' instead of `a', `H'
>> instead of `h') ...
>
> Yes. And this fails when there is an org-babel src block in the buffer.
>
> -- Puneeth
Hi Puneeth,
I've just tried exporting an org-mode buffer containing babel code
b
Hi,
Could you send an example of the contents of such a cell, and what it is
converted to? Maybe it will be possible to improve the parsing of
numerals in Babel s.t. we don't lose precision in these cases.
Thanks -- Eric
Marc-Oliver Ihm writes:
> Hello !
>
> Currently org-babel, when passing
Hi Jambunathan,
Would you mind re-sending your original Makefile patch un-commented so
that it will be captured by the patchwork system, and dropped into the
org-mode development review process?
Thanks -- Eric
"Eric Schulte" writes:
> Hi Jambunathan,
>
> Jambunathan K writ
"Eric Schulte" writes:
[...]
>
> "Giovanni Moretti" writes:
>
>> I'm just starting with Babel and have been puzzled about why one file
>> worked and another didn't.
>>
>> I have been playing in a new file without any headers at al
Ok,
Thanks for your persistence in explaining this to me. I've just pushed
up a change which should fix this issue.
Best -- Eric
Puneeth writes:
> Hi Eric,
>
> On Mon, Oct 4, 2010 at 6:43 PM, Eric Schulte
>> I've just tried exporting an org-mode buffer containing
sed recently?
> See this thread:
> http://thread.gmane.org/gmane.emacs.orgmode/31241/focus=31289
>
> Jörg
>
> On 10/4/10 3:48 PM, Eric Schulte wrote:
>> "Eric Schulte" writes:
>>
>> [...]
>>> "Giovanni Moretti" writes:
>>&g
ke my test driven bug
fixing a much smoother process, and would remove the need to rebase the
combined-testing branch against master and "git push -f" the changes up
to repo.or.cz which just feels wrong.
Thoughts?
-- Eric
Sebastian Rose writes:
> "Eric Schulte" writes:
>&
Hi,
This issue is fixed in the "combined-testing" branch of the repository,
I hope to merge that branch into the master branch soon.
If anyone is interested, some of my thoughts on this commit which has
caused these couple of recent problems... It seems that by using
org-links to find the locati
Sebastian Rose writes:
> "Eric Schulte" writes:
>> Hi,
>>
>> So, I've been using the framework in the combined-testing branch this
>> morning writing tests to strap down my daily Babel bug fixes, and I'm
>> really liking ERT.
>>
>&g
A test framework based on ert [1] is now included in the testing
directory of the org-mode repository. Directions for use are included
in testing/README.org.
This is based on work by Sebastian Rose and myself.
Enjoy -- Eric
Footnotes:
[1] http://github.com/ohler/ert
Bernt Hansen writes:
> "Eric Schulte" writes:
>
>> So, I've been using the framework in the combined-testing branch this
>> morning writing tests to strap down my daily Babel bug fixes, and I'm
>> really liking ERT.
>>
>> I wonder, can w
Fixed, Thanks
Nick Dokos writes:
> ... and a typo on line 24 of README.org: just->jump.
>
> Nick
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmo
Hi,
The ":noweb yes" header argument will expand noweb references during
both tangling and weaving. I've added another noweb header argument
"tangle" which will expand noweb header arguments during tangling but
not during weaving(export), so replacing ":noweb yes" with ":noweb
tangle" in your exa
Hi Nick,
Thanks for noticing these points, I've pushed up fixes for both.
-- Eric
Nick Dokos writes:
> Eric Schulte wrote:
>
>> A test framework based on ert [1] is now included in the testing
>> directory of the org-mode repository. Directions for use are included
&
This issue should now be fixed.
Best -- Eric
Michael Brand writes:
>>> * [[http://www.example.com][example]]
>
> There is an other issue with this, let me name it issue2: It is not yet
> possible to link to such a heading with something like e. g.
>
> [[*%5b%5bhttp://www.example.com%5d%5bexampl
Hi Robert,
Currently the only way I know of inhibiting the export of the original
table, is to move it to an un-exporting subtree. This can be done using
the COMMENT header keyword by moving the table to a new subtree and
pressing C-c ; which runs org-toggle-comment in that subtree.
Best -- Eric
Ian Barton writes:
> Scott Jaderholm writes:
>
>> http://jaderholm.com/color-themes/color-theme-colorful-obsolescence.el
>> http://jaderholm.com/color-themes/color-theme-active.el
>> http://jaderholm.com/color-themes/color-theme-wombat.el
>>
>> Please link to don't copy so that as I make changes
Fixed, Thanks -- Eric
Achim Gratz writes:
> This commit produces a warning from the byte compiler on Emacs 23.1:
>
> In org-babel-expand-body:python:
> ob-python.el:60:29:Warning: reference to free variable
> `org-src-preserve-indentation'
> Wrote /home/gratz/lisp/org-mode/lisp/ob-python.elc
The following inhibits the insertion of blank lines on tangling.
(setq org-babel-tangle-pad-newline nil)
Best -- Eric
Sébastien Vauban writes:
> Hello,
>
> I just tried this:
>
> Creating the following =.reg= file:
>
> #+begin_src sh :tangle org-protocol-setup.reg
> REGEDIT4
>
> [HKEY_CLASSE
Ian Barton writes:
> Hi Eric,
>
> There is a file in worg called org-color-themes.org, which contains
> your colour theme (railscast). However, it's not referenced by any of
> the other worg pages, so you couldn't find it if you didn't know it
> existed! There is a short bit on org-appearance.pgp
Dan Davison writes:
> Worg could do with some reorganization. It is not at all easy to find
> stuff in there (at least, using a web browser).
I agree there is certainly room for improvement here. Maybe this sort
of re-organization should be considered along with the new CSS changes.
[...]
> T
John Hendy writes:
> Great topic. I agree. This will be quite the overhaul! Perhaps we should
> propose some type of organizing scheme? By level of usage (beg,
> intermediate, adv?), by functional use (notes, todos, exporting, math,
> babel?), etc.? Just some ideas. If one's going to reorganize,
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>>> [...] empty first line that's always inserted at the beginning of the file.
>>> What should I do to get rid of that first *empty* line?
>>
>> The following inhibits the inserti
Ah,
Thanks for pointing this out, this was actually a small issue in the
shell specific body expansion (it looks like Dan and I have both fixed
this in the last 5 minutes), it should now be fixed and strapped down
with a unit test.
Best -- Eric
Sébastien Vauban writes:
> Hi Eric,
>
&
Hi Ezequiel,
I haven't touched the blorgit code for probably over a year. That said
I have been using blorgit locally without problem.
Although the error you pasted doesn't raise any immediate flags for me I
can give my boilerplate question of "did you install the git
submodules"? If not, then
Hi Seb,
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
[...]
>> and strapped down with a unit test.
>
> Would you have a bit of time (I don't know exactly what's required), could you
> give information about how you'll write this u
Hi Seb,
I fully agree with your point, I believe I've just pushed up a fix for
this issue. This commit includes a short function with a long name
`ob-tangle/no-excessive-id-insertion-on-tangle' in test-ob-tangle.el.
Best -- Eric
Sébastien Vauban writes:
> Hi Eric,
>
> &
Hi Seb,
Since this old testing file is obsolete I've just deleted it. Thanks to
git it can always be resurrected later as the basis for a modern
org-html test suite.
Best -- Eric
Sébastien Vauban writes:
> #+TITLE: Old-Org-HTML-hides-Org-HTML.txt
> #+DATE: 2010-10-15
> #+LANGUAGE: e
Tested and Fixed. Thanks -- Eric
Sébastien Vauban writes:
> Hi Eric and Dan,
>
> * Getting messages from stderr
>
> #+begin_src sh
> ls NoSuchFileOrDirectory.txt
> #+end_src
>
> results in
>
> : ls: cannot access NoSuchFileOrDirectory.txt: No such file or directory
>
> in *Org-Babel Error Outpu
Sébastien Vauban writes:
[...]
>
> I don't have in mind full fontification like we now have in Org. No: *just the
> basic yellow background*, so that code blocks are outstanding in any mail,
> exactly *like it is now* but for the "cut here" markers (or "v+/v-").
>
While we're at it, why not go a
Hi Manuel,
The following works for me, it creates an index of all files in the same
directory as the Org-mode file.
--8<---cut here---start->8---
* index
Create an index automatically with an elisp code block.
#+begin_src emacs-lisp :exports results :results
using a
> similar approach?
>
> Thanks,
>
> Pere
>
> Al 15/10/10 19:07, En/na Eric Schulte ha escrit:
>> Hi Manuel,
>>
>> The following works for me, it creates an index of all files in the same
>> directory as the Org-mode file.
>>
>> --
Hi Tom,
See the "Evaluating code blocks" section of the manual for information
on how to pass header arguments to #+call: lines
http://orgmode.org/manual/Evaluating-code-blocks.html#Evaluating-code-blocks
something like
#+lob: elispgantt(table=gantttest) :results latex
should work
Cheers -
Yes,
The snippets used by the starter kit are available in their own git
repository at http://github.com/eschulte/yasnippet-org-mode
Best -- Eric
also, any suggestions or contributions are welcome
Rainer M Krug writes:
> On Tue, Apr 20, 2010 at 4:48 PM, Eric Schulte wrote:
>
>&g
Hi Rainer,
Rainer M Krug writes:
> Hi
>
> I just discovered one of the mysteries I experienced with org: the appearing
> ID properties.
Yes, I think this is caused by a recent change in the org-store-link
function which is called during tangling.
>
> They are caused by the back-linking of cod
This looks like a bug, the export of lob lines needs to be better about
recognizing if it is inside of a protected environment. Thanks for
pointing this out.
In the mean time the following syntax should work...
: #+lob: elispgantt(table=gantttesttable) :results output latex
Best -- Eric
BTW: Do
e
jar file could be downloaded and run directly without having to worry
about installing the entire ruby stack locally.
Best -- Eric
Michaël Parienti writes:
> Hi,
>
> On Thu, 14 Oct 2010 16:52:05 -0600
> "Eric Schulte" wrote:
>
>> If not, then run
>>
user code, and can already reduce the
amount of code in ob-org.el and org-mime.el.
>From e51017e4d7051aad31384a470f0a695dca0d6716 Mon Sep 17 00:00:00 2001
From: Eric Schulte
Date: Sun, 17 Oct 2010 15:17:13 -0600
Subject: [PATCH] org-export-string -- exports a string of org-mode markup text
* lis
gt;> #+source: load-local-lob
>> #+begin_src emacs-lisp :exports code
>> (org-babel-lob-ingest "~/org/local-lob.org")
>> #+end_src
>
> If this is off the mark, and the code should go in the main Library,
> then I'd want to check with Eric F. first abou
Applied Thanks -- Eric
"Thomas S. Dye" writes:
> Changes in HEAD
> Modified doc/org.texi
> diff --git a/doc/org.texi b/doc/org.texi
> index bd22ce9..84df413 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -456,6 +456,7 @@ Using header arguments
> * Buffer-wide header arguments:: Se
Hi,
I've tried to export your file and I had no problems. I believe the
problem you describe may be fixed in a recent (the last month or so)
patch to Org-mode. Could you try checking out the latest development
version of Org-mode and let me know if the problem persists?
http://orgmode.org/worg/
r attached example file with
org-confirm-babel-evaluate set to both nil and to true, in both cases it
worked for me without problem. Are you on a windows box (another one of
my go-to potential culprits)?
Best -- Eric
suvayu ali writes:
> Hi Eric,
>
> On 18 October 2010 18:15,
Suvayu Ali writes:
> Hi Eric,
>
> On Monday 18 October 2010 07:20 PM, Eric Schulte wrote:
>> Hmm,
>>
>> Are you sure that the version of Org-mode loaded in Emacs is the very
>> same version? What output do you get when you run the org-version
>> co
Suvayu Ali writes:
>
> On restarting Emacs and calling org-version, I get "Org-mode version
> 7.01trans". There shouldn't be any mixed files after all this. The
> problem still persists. Does that mean I am doing the installation
> wrong?
>
Yes, I believe that until you see the parenthesized por
1 - 100 of 3086 matches
Mail list logo