Re: [Orgmode] #+source line in export

2010-09-20 Thread Bastien
"Thomas S. Dye" writes: > Would it be possible for this setting to be in effect when Worg > generates its files from the org-mode sources? The effect is pleasing > in some situations. .emacs.el on the orgmode.org server now set (setq org-export-latex-listings-w-names nil) If this is not co

Re: [Orgmode] #+source line in export

2010-09-20 Thread Thomas S. Dye
Aloha Bastien, Would it be possible for this setting to be in effect when Worg generates its files from the org-mode sources? The effect is pleasing in some situations. All the best, Tom On Sep 19, 2010, at 5:52 PM, Eric Schulte wrote: Hi Tom, The following should inhibit the exportat

Re: [Orgmode] #+source line in export

2010-09-20 Thread Thomas S. Dye
Thanks Eric, that is what I was looking for. All the best, Tom On Sep 19, 2010, at 5:52 PM, Eric Schulte wrote: 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 f

Re: [Orgmode] #+source line in export

2010-09-19 Thread Eric Schulte
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

[Orgmode] #+source line in export

2010-09-19 Thread Thomas S. Dye
Aloha all, Is there a way to control export of the #+source line? I've been looking for a way to turn it off, especially in LaTeX export where it yields something like this: get-from-github() $\equiv$ I find the output of \equiv distracting (perhaps it is meaningful in a way I don't u