[O] Re: Continuation of main section text after subsections

[Sébastien Vauban]

Hi,

Samuel Wales wrote:
> Perhaps we could have a tag like :noexport: except that it exports body. It
> does not export the header. Optionally, it would be replaced with a blank
> line.
>
> Then he can put headers anywhere he wants.
>
> Would this work for the OP's use case?

I really am not (yet?) convinced by the need -- as I don't really see how it
fits in LaTeX/HTML.

However, just to answer one detail point, would such a new tag globally exist,
it would have to be :ignoreheading: (it does already exist in Org-Beamer for
"anonym" columns).

Best regards,
  Seb

-- 
Sébastien Vauban

[O] hyperlink and gnus registry.

[Francis Moreau]

Hello all,

I use hyperlink to link some Gnus emails to my Org documents.

But somtimes, I move the emails inside Gnus, from one group to another one.

Is it possible to make the Org link still work in this case ?

I don't know if taht could help, but I'm using gnus registry.

Thanks
-- 
Francis

Re: [O] Re: Inline images export to HTML generates < and > rather than < and >

[Sean Whitton]

Hi Bernt,

On 27 Mar 2011 at 14:09Z, Bernt Hansen wrote:

> This works for me.  I think there was a bug like this in a recent
> release.  What version of org-mode are you using?

> Mine exports as follows

> * Test export
> [[file:img/avi.gif]]

> ...
> 
> 
> ...

> Maybe try upgrading to the latest development snapshot of org?

> I'm using Org-mode version 7.5 (release_7.5.115.g00134)

That seems to work, thanks.  I thought I was already on the latest git
snapshot (or pretty close) but apparently not.

Thanks for the welcome.

S

-- 
Sean Whitton / 
OpenPGP KeyID: 0x3B6D411B
http://seanwhitton.com/



pgpMrTpUNhUnx.pgp
Description: PGP signature

Re: [O] FAQ? (was: Continuation of main section text after subsections ?)

[Marcel van der Boom]

On ma 28-mrt-2011 00:00
Memnon Anon  wrote:

> Marcel van der Boom  writes:
> [...]
>> I've looked for documentation or customization options on this, but
>> haven't found any yet. What I have done so far is turn the
>> subheadings into lists or surround them by *bold markers*, which
>> helps a little.
> 
> Seems to me to be worth an entry in the FAQ, isn't it?
> 

Definitely, especially the part about what is considered a proper
outline according to org-mode. 

marcel

-- 
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV-- http://www.hsdev.com
So! web applications -- http://make-it-so.info
Cobra build  -- http://cobra.mrblog.nl

Re: [O] zotero (or mendeley) integration with org

[Stephen Eglen]

Dear all,

Thanks for the informative replies.  I gave zotero a short-test
yesterday,and in general liked what I found, although as it uses sql
databases, it is moves away from my preference for plain text files to
see everything in.   I appreciate that sql may scale better, but I don't
have huge databases.  I think I'll continue to watch how the zotero
standalone develops.  

In the meantime, it made me think a bit more about looking after pdf
collections.  I'll try out using org mode for annotating my pdfs, to see
how that works.


I had not seen recoll before, that certainly looks nice.

Will feedback to the list if I have anything useful to add.

Stephen

Re: [O] ASCII table export should use tabs?

[Eric S Fraga]

Samuel Wales  writes:

> I wonder if org should export ASCII tables using tabs.
>
> If I send to this list, I can be confident that everybody will know to
> display in a monospace font.  That is not true for non-technical
> audiences.  Yet I think there are times when I want to send ASCII
> instead of HTML.  At least, I am not confident that /I/ know that HTML
> will display correctly.
>
> Tabs are not a perfect solution, as they will break with long entries.
>  Still, you can read a broken table with tabs easier than a table
> displayed in a proportional font, which I believe most nontechnical
> people use.
>
> What do you think?
>
> Samuel

I don't think Tabs will work well because either the tab positions are
unknown (depending on how the document is being read) or the tab
positions, if fixed, will be less than optimal for any given table.

For most non-technical audiences, I would recommend exporting to either
HTML or PDF if you're worried about tables being formatted correctly.  I
don't send ascii formatted text from org to hardly anybody.  

If you're sending email, as much as I dislike HTML messages, I do send
the odd one using org-mime-org-buffer-htmlize if there is formatting
that is critical to the understanding of the document.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)

[O] TeX to MathML & org-odt ?

[Jambunathan K]

Any opinions on TeX to MathML converters (specifically those that are
amenable to be integrated within Orgmode/Emacs ).

I am asking this query mainly in the context of new org-odt exporter.

Most of the MathML software that I came across seems to be geared more
towards graphical rendering of a MathML text (in context of web or
standalone math apps).

What would be the recommended converter based on personal experience?

Jambunathan K.

-- 

[O] latex export settings in init files

[Chris Beard]

Hello,
I've tried to modify some default latex export settings based on info from here
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg07645.html

I basically add to the org-mode-hook to do:
(setq org-export-latex-classes (cons '("myarticle"
 "% BEGIN My Article Defaults
  \\documentclass[10pt,letterpaper]{article}

  
\\usepackage[letterpaper,includeheadfoot,top=0.5in,bottom=0.5in,left=0.75in,right=0.75in]{geometry};;
more settings after this...
)
   org-export-latex-classes))

This works if I evaluate it after I've been exporting to latex, but I
get an error whenever I start up emacs:

setq: Symbol's value as variable is void: org-export-latex-classes

I'm guessing there's some org-mode latex-export thing that I need to
load first, but I'm not very familiar with how to do this. Any advice?

Thank you
Chris

Re: [O] latex export settings in init files

[Eric S Fraga]

Chris Beard  writes:

> Hello,
> I've tried to modify some default latex export settings based on info from 
> here
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg07645.html
>
> I basically add to the org-mode-hook to do:
> (setq org-export-latex-classes (cons '("myarticle"
>  "% BEGIN My Article Defaults
>   \\documentclass[10pt,letterpaper]{article}
>
>   
> \\usepackage[letterpaper,includeheadfoot,top=0.5in,bottom=0.5in,left=0.75in,right=0.75in]{geometry};;
> more settings after this...
> )
>org-export-latex-classes))
>
> This works if I evaluate it after I've been exporting to latex, but I
> get an error whenever I start up emacs:
>
> setq: Symbol's value as variable is void: org-export-latex-classes
>
> I'm guessing there's some org-mode latex-export thing that I need to
> load first, but I'm not very familiar with how to do this. Any advice?
>
> Thank you
> Chris

I have:

--8<---cut here---start->8---
(require 'org-install)
(require 'org-exp)
(require 'org-atom)
(require 'org-exp-bibtex)
(require 'org-latex)
--8<---cut here---end--->8---

before any customisations.

By the way, for the types of customisation you are doing above
(obviously, I don't know what you have omitted), I find it easier to
define an org template that has the appropriate #+LaTeX_CLASS_OPTIONS
and #+LATEX_HEADER lines.
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)

[O] remember-other-frame with org-capture?

[Radosław Grzanka]

Hello,
  I was using function "remember-other-frame" on my windows box to 
quickly popup emacs with "remember" activated. I also used "defadvice 
remember-other-frame" that configured size of popup window.


Now I switched to org-capture as being more powerful in terms of 
templates but I cannot find out equivalent of that function.


Can somebody more enlighten in org and emacs show me how to get same 
functionality with "org-capture" package? I tried to write this function 
myself but all I can do in elisp is "monkey-see-monkey-do" stuff which 
did not work in this case.


Thanks,
  Radek.

Re: [O] latex export settings in init files

[Chris Malone]

Hi Chris,

I would try Eric's suggestion of making sure you have all the correct
"require" statements in your .emacs file.  If that doesn't work, make sure
you have a recent version of =org-mode= --- I've run into this problem in
the past, even with the appropriate "require"s, but with an old version of
=org-mode=.

Chris

On Mon, Mar 28, 2011 at 8:05 AM, Eric S Fraga  wrote:

> Chris Beard  writes:
>
> > Hello,
> > I've tried to modify some default latex export settings based on info
> from here
> > http://www.mail-archive.com/emacs-orgmode@gnu.org/msg07645.html
> >
> > I basically add to the org-mode-hook to do:
> > (setq org-export-latex-classes (cons '("myarticle"
> >  "% BEGIN My Article Defaults
> >   \\documentclass[10pt,letterpaper]{article}
> >
> >
> \\usepackage[letterpaper,includeheadfoot,top=0.5in,bottom=0.5in,left=0.75in,right=0.75in]{geometry};;
> > more settings after this...
> > )
> >org-export-latex-classes))
> >
> > This works if I evaluate it after I've been exporting to latex, but I
> > get an error whenever I start up emacs:
> >
> > setq: Symbol's value as variable is void: org-export-latex-classes
> >
> > I'm guessing there's some org-mode latex-export thing that I need to
> > load first, but I'm not very familiar with how to do this. Any advice?
> >
> > Thank you
> > Chris
>
> I have:
>
> --8<---cut here---start->8---
> (require 'org-install)
> (require 'org-exp)
> (require 'org-atom)
> (require 'org-exp-bibtex)
> (require 'org-latex)
> --8<---cut here---end--->8---
>
> before any customisations.
>
> By the way, for the types of customisation you are doing above
> (obviously, I don't know what you have omitted), I find it easier to
> define an org template that has the appropriate #+LaTeX_CLASS_OPTIONS
> and #+LATEX_HEADER lines.
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
> : using Org-mode version 7.5 (release_7.5.115.g00134.dirty)
>
>

Re: [O] Re: [babel] "Marker does not point anywhere" error?

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 25/03/11 14:38, Rainer M Krug wrote:
> On 25/03/11 14:22, Sébastien Vauban wrote:
>> Hi Rainer,
> 
>> Rainer M Krug wrote:
>>> On 25/03/11 13:50, Jambunathan K wrote:

 Can you do M-x toggle-debug-on-error and copy/paste what comes up in the
 backtrace buffer?
>>>
>>> Here it is:
>>>
>>> Debugger entered--Lisp error: (error "Marker does not point anywhere")
>>>   (...)
>>>   org-babel-execute-src-block-maybe()
>>>   org-babel-execute-maybe()
>>>   org-babel-execute-safely-maybe()
>>>   run-hook-with-args-until-success(org-babel-execute-safely-maybe)
>>>   org-ctrl-c-ctrl-c(nil)
>>>   call-interactively(org-ctrl-c-ctrl-c nil nil)
> 
>> Just to be sure: above, it refers to C-c C-c
> 
> Correct
> 
> 
 When I put my cursor into the block and want to execute it with C-c c I
 get usually at the first attempt a "Marker does not point anywhere"
 error, and when I, without moving the cursor, do C-c c again, the code
 is executed - it is not a serious problem, but a little bit irritating.
> 
>> Here to C-c c... What's the capital "i" you refer to?
> 
> Sorry C-c C-c(org-ctrl-c-ctrl-c). The "I" is me (I get usually ).
> 
> 
>> Can you explicit which keybinding you're using?
> 
> org-ctrl-c-ctrl-c

Any progress on this one or do you need any further info?

Rainer

> 
> 
> 
> Cheers,
> 
> Rainer
> 
> 
> 
>> Best regards,
>>   Seb
> 
> 
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Tel:+33 - (0)9 53 10 27 44
Cell:   +27 - (0)8 39 47 90 42
Fax (SA):   +27 - (0)8 65 16 27 82
Fax (D) :   +49 - (0)3 21 21 25 22 44
Fax (FR):   +33 - (0)9 58 10 27 44
email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2Qg2AACgkQoYgNqgF2egoVGwCfTw5vUr1sr1r5JYTJMBpaezfo
31wAn1yrRL/+b6qXi8/yVVAbwIDIVVhZ
=5xtx
-END PGP SIGNATURE-

Re: [O] zotero (or mendeley) integration with org

[brian powell]

It uses SQLite--Stephen: I'd consider myself a
plaintext-whenever-possible sort of dude too; but,
SQLite (used in ZOTERO) is a simple/short C program and its (last time
I checked) extremely simple--for example there is only "left outer
join".

SQLite "databases" are very easy to work with and are often 1 simple,
small, very portable file.

I was reading some article yesterday: SQLite was ranked #1 in the top
ten best/most useful software of all time.

I understand your concern; and, often an SQL database is overkill and
"NOSQL" seems in vogue right now--but SQLite is something you might
really like--you can manipulate SQLite databases easily, like
plaintext.

I just tried ZOTERO too--very impressive.  I'm a lot more used to
using BibTeX though--which is purely plaintext; but, BibTeX can be a
typing chore!

On Mon, Mar 28, 2011 at 5:14 AM, Stephen Eglen
 wrote:
> Dear all,
>
> Thanks for the informative replies.  I gave zotero a short-test
> yesterday,and in general liked what I found, although as it uses sql
> databases, it is moves away from my preference for plain text files to
> see everything in.   I appreciate that sql may scale better, but I don't
> have huge databases.  I think I'll continue to watch how the zotero
> standalone develops.

[O] Re: latex export settings in init files

[Sébastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> By the way, for the types of customisation you are doing above (obviously, I
> don't know what you have omitted), I find it easier to define an org
> template that has the appropriate #+LaTeX_CLASS_OPTIONS and #+LATEX_HEADER
> lines.

I guess that you mean it "if the number of custom LaTeX lines is < 5 or 10",
something like that.

Even in such a case, I would opt the OP for his own document class (or style
file), so that every custom is only made once, in one place. And, would he
recompile his Org doc later, he would benefit from all the updated features he
put in his class -- if nothing is contradictorily changed...

Your argument is maybe about being "easier". True. And false: after all,
what's a class or style file, everything you want except for the first few
lines, and the last one, no?

(not trying to say the opposite of you ;-) but give the OP another "sound of
clock" -- maybe you think as well at other points I'm missing here?)

Best regards,
  Seb

-- 
Sébastien Vauban

Re: [O] Continuation of main section text after subsections

[Nick Dokos]

Samuel Wales  wrote:

> Perhaps we could have a tag like :noexport: except that it exports
> body.  It does not export the header.  Optionally, it would be
> replaced with a blank line.
> 
> Then he can put headers anywhere he wants.
> 
> Would this work for the OP's use case?
> 

My reading of it was that he wanted that to be done as he is putting
down his thoughts into the pensieve - ...err... org file I mean - so doing
it in export is too late. But I'm not the OP so maybe I've read it
wrong.

Using an imaginary EBNF spec, here's what org (and LaTeX) provides:

 ::= [] ()*

i.e. "a tree is some optional text followed by 0 or more trees",
whereas I think he wants:

 ::= [] ( [text])*

I hope these are not grossly wrong, but please take them with
the appropriate grain of salt.

Nick

[O] [TaskJuggler][Poll] Support for the new effort durations?

[Christian Egli]

The Effort property previously had no unit attached. With release 7.5 of
orgmode you can now attach units to it such as 4h, 2d or 2m. The
taskjuggler exporter however doesn't support this feature yet. It
currently assumes that if is simply a number that we are talking about
days. If the format is something like 5:30 it assumes that the effort is
in hours:minutes. It has no support for other formats (weeks, months
which taskjuggler itself would support).

Now I suppose the exporter should honor the new effort durations that
were introduced in 7.5. This is not that hard to change. However this
would mean that existing orgmode files will be exported differently,
i.e. the change is not backwards compatible.

At the moment I do not know how to deal with this. Should I just move to
the new effort durations and ask the user to upgrade their orgmode files
or more specifically to upgrade their effort properties to the new
effort durations format?

Thoughts?

Thanks
Christian

-- 
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

Re: [O] Continuation of main section text after subsections

[Marcel van der Boom]

On zo 27-mrt-2011 18:07
Samuel Wales  wrote:

> Perhaps we could have a tag like :noexport: except that it exports
> body.  It does not export the header.  Optionally, it would be
> replaced with a blank line.
> 
> Then he can put headers anywhere he wants.
> 
> Would this work for the OP's use case?

As others have already mentioned, this would indeed not solve my
issue. Once I am ready for export/publishing I'm more or less settled
on the document structure. Except for some cases, where I mark blocks
with my /noexport/ tag, I would expect the same (logical) structure in
the published document as in the source org file.

marcel

-- 
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV-- http://www.hsdev.com
So! web applications -- http://make-it-so.info
Cobra build  -- http://cobra.mrblog.nl

Re: [O] Re: Continuation of main section text after subsections ?

[Marcel van der Boom]

On zo 27-mrt-2011 13:08
"Filippo A. Salustri"  wrote:

> I would humbly suggest that the real question is a design / use case
> question.  Is it reasonable to expect authors to stick to proper
> outline format throughout their drafting process?  If it is, then org
> is fine as is.  If it isn't, then there's a problem.

Very much agreed. I think that paragraph is the best summary so
far for the problem, stated in generic terms. 

marcel

PS
For what it is worth, I think the 'case of inline tasks' is exactly the
same problem as mine.

-- 
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV-- http://www.hsdev.com
So! web applications -- http://make-it-so.info
Cobra build  -- http://cobra.mrblog.nl

Re: [O] Re: latex export settings in init files

[Nick Dokos]

Sébastien Vauban  wrote:

> Hi Eric,
> 
> Eric S Fraga wrote:
> > By the way, for the types of customisation you are doing above (obviously, I
> > don't know what you have omitted), I find it easier to define an org
> > template that has the appropriate #+LaTeX_CLASS_OPTIONS and #+LATEX_HEADER
> > lines.
> 
> I guess that you mean it "if the number of custom LaTeX lines is < 5 or 10",
> something like that.
> 
> Even in such a case, I would opt the OP for his own document class (or style
> file), so that every custom is only made once, in one place. And, would he
> recompile his Org doc later, he would benefit from all the updated features he
> put in his class -- if nothing is contradictorily changed...
> 
> Your argument is maybe about being "easier". True. And false: after all,
> what's a class or style file, everything you want except for the first few
> lines, and the last one, no?
> 
> (not trying to say the opposite of you ;-) but give the OP another "sound of
> clock" -- maybe you think as well at other points I'm missing here?)
> 

It depends on the comfort level of the user with org vs LaTeX as
well. If s/he wants to touch LaTeX as little as possible, Eric's
solution (combined with an #+INCLUDE file perhaps) is quite general and
it is perhaps more versatile: adding a class to org-export-latex-classes
buries it in some emacs initialization file; IMO, that's harder to
change (and find when you need to change it)[fn:1] but it may be the
appropriate way to deal with a more rigid LaTeX class setup that you
*always* (for some value of "always") want to follow.

BTW, does #+INCLUDE incorporate a path mechanism? That would go some
way into making this choice a "really doesn't matter which way you
go".
 
Nick

Footnotes:

[fn:1] But I freely admit that my emacs init setup is rather baroque,
thereby making things like that more difficult than they really need to
be. I also am somewhat allergic to customize (particularly when the spec
is complicated - as it is for org-export-latex-classes: I go cross-eyed
when I look at the customize screen for it), so I tend to avoid it in
most situations.

[O] [PATCH] Prefer matching line beginnings in org-export-latex-special-chars

[Lawrence Mitchell]

* lisp/org-latex.el (org-export-latex-special-chars): Fix regexp for
`single' special characters and ellipsis.

Repeated special characters are exported differently depending on
their position in the buffer.  A "&&" string at the start of a line is
exported as "&\&" whereas in the middle of a line you get "\&\&".  The
former is incorrect.  Fix this by matching the beginning of a line
before a character.  While we're at it, amalgamate the regexps for the
different special characters.
---

Suvayu Ali wrote:
> Hi Orgers,

> I wanted to insert comments in the exported tex file for latex export.
> Is there an standard way to do that? I found normal '%text' gets
> exported as '\%text'. However I can export comments by putting
> '%%text', it gets exported as '%\%text'.

Although this feels like a potentially useful feature, I believe
it is a bug.  Doubled special characters are exported differently
depending on where they are on a line:

&& foo

=> &\& foo

whereas

foo &&

=> foo \&\&

This is because the regexp for finding special characters prefers
matching a character over the start of a line \\(.\\|^\\)\\(&\\)
will set (match-string 1) to & and (match-string 2) to & if &&
occurs at the start of a line, although the intention is that
(match-string 1) should be the empty line-start string and
(match-string 2) the first ampersand.  We can fix this by
changing the regexp to \\(^\\|.\\)\\(&\\) as in this patch.

Cheers,
Lawrence

 lisp/org-latex.el |8 +---
 1 files changed, 1 insertions(+), 7 deletions(-)

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 605795c..30f7b4a 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1684,13 +1684,7 @@ See the `org-export-latex.el' code for a complete 
conversion table."
  "\\(\\(?\\$\\)\\)"
  "\\([a-zA-Z0-9()]+\\|[ 
\t\n]\\|\\b\\|\\)\\(_\\|\\^\\)\\({[^{}]+}\\|[a-zA-Z0-9]+\\|[ 
\t\n]\\|[:punct:]\\|)\\|{[a-zA-Z0-9]+}\\|([a-zA-Z0-9]+)\\)"
  "\\(.\\|^\\)\\(\\)\\([ 
\t\n]\\|\\([&#%{}\"]\\|[a-zA-Z][a-zA-Z0-9]*\\)\\)"
- "\\(.\\|^\\)\\(&\\)"
- "\\(.\\|^\\)\\(#\\)"
- "\\(.\\|^\\)\\(%\\)"
- "\\(.\\|^\\)\\({\\)"
- "\\(.\\|^\\)\\(}\\)"
- "\\(.\\|^\\)\\(~\\)"
- "\\(.\\|^\\)\\(\\.\\.\\.\\)"
+ "\\(^\\|.\\)\\([&#%{}~]\\|\\.\\.\\.\\)"
  ;; (?\< . "\\textless{}")
  ;; (?\> . "\\textgreater{}")
  )))
-- 
1.7.4.rc2.18.gb20e9

Re: [O] Re: agenda view opening multiple buffers

[Carsten Dominik]

On 27.3.2011, at 20:55, Manish wrote:

> On Sun, Mar 27, 2011 at 8:21 PM, Julian Burgos wrote:
>> Thanks.  Using x is good enough for now.  I´ll explore also Michael´s
>> suggestions.  It would be good to have the agenda open in a buffer
>> without having all the agenda files opened too.
>> 
> 
> Following code should do what you want (I think).
> 
> #+begin_src emacs-lisp
> ;; function code copied from definition of org-agenda-exit
>  (add-hook 'org-finalize-agenda-hook
>(lambda ()
>  (interactive)
>  (org-release-buffers org-agenda-new-buffers)
>  (setq org-agenda-new-buffers nil)))
> #+end_src

This will make the agenda disfunctional.  Each line in the agenda contains a 
pointer to the entry the line was derived from, so remote editing etc will stop 
working.

Exiting with "x" is the much better solution.

HTH

- Carsten

> 
> HTH
> -- 
> Manish
> 
>> On Sun, Mar 27, 2011 at 2:21 PM, Michael Markert
>>  wrote:
>>> On 27 Mar 2011, Bernt Hansen wrote:
 Julian Burgos  writes:
 
> Dear list,
> 
> When asking for an agenda view (C-c a), org mode opens all files in
> the agenda list in individual buffers.  I keep lots of files in my
> list (one per project), so having all those buffers open each time I
> visit my agenda is pretty annoying.  Is there a way to make org mode
> not open each file in a buffer (or close the buffers after reading the
> file) when asking for an agenda view?
> Thanks,
> 
> Julian
 
 Hi Julian,
 
 I think 'e' in the agenda is supposed to exit the agenda and close
 automatically opened agenda files.
>>> 
>>> It's `x'. But I think Julian meant that the buffers should be closed
>>> automatically and not open at least as long as the agenda is shown.
>>> 
>>> For the original issue I think the following would help:
>>> #+begin_src emacs-lisp
>>> (defun project-agenda (&optional args keys restriction)
>>> (interactive)
>>> (let ((org-agenda-files '("~/project-file1"
>>>   "~/project-file2")))
>>>   (org-agenda args keys restriction)))
>>> #+end_src
>>> 
>>> Or pressing `<' in the prompt buffer, for more see (describe-function
>>> 'org-agenda)
>>> 
>>> Michael
>>> 
>> 
>> 
>> 
>> --
>> Julian Mariano Burgos
>> Hafrannsóknastofnunin/Marine Research Institute
>> Skúlagata 4, 121 Reykjavà k, Iceland
>> SÃ mi/Telephone : +354-5752037
>> Bréfsà mi/Telefax:  +354-5752001
>> Netfang/Email: jul...@hafro.is, jmbur...@uw.edu
>> 
>> 
> 

[O] Re: [babel] Calling source blocks with arguments

[Philipp Haselwarter]

Do you guys really just go and change all your variables in your
scripts?


-- 
Philipp Haselwarter

[O] [PATCH] Ensure org-export-handle-comments protects its insertions

[Lawrence Mitchell]

* lisp/org-exp.el (org-export-handle-comments): Add the org-protected
property to the replacement string.

Although org-export-handle-comments adds the org-protected property to
the matched string, the subsequent `replace-match' call to change the
comment character does not add this property to the entire format
string.  Fix this by propertizing the entirety of the newtext argument
to replace-match.
---
I think this change makes the actual implementation match the
intention of the code, we want the replacement comment character
to be protected as well, however, I'm not sure if this breaks the
usecases in ob-tangle and the like.

 lisp/org-exp.el |5 -
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index 3e84314..da2475e 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -1853,7 +1853,10 @@ When it is nil, all comments will be removed."
 (not (equal (char-before (match-end 1)) ?+)))
(progn (add-text-properties
(match-beginning 0) (match-end 0) '(org-protected t))
-  (replace-match (format commentsp (match-string 2)) t t))
+  (replace-match (propertize
+  (format commentsp (match-string 2))
+  'org-protected t)
+ t t))
  (goto-char (1+ pos))
  (replace-match "")
  (goto-char (max (point-min) (1- pos
-- 
1.7.4.rc2.18.gb20e9

Re: [O] Re: [babel] Calling source blocks with arguments

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 28/03/11 17:19, Philipp Haselwarter wrote:
> Do you guys really just go and change all your variables in your
> scripts?
> 
> 
No.

See org manual, section 14.5, "Evaluating code blocks"

#+function: () 

Rainer

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Tel:+33 - (0)9 53 10 27 44
Cell:   +27 - (0)8 39 47 90 42
Fax (SA):   +27 - (0)8 65 16 27 82
Fax (D) :   +49 - (0)3 21 21 25 22 44
Fax (FR):   +33 - (0)9 58 10 27 44
email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2QqOAACgkQoYgNqgF2egrlsQCfQnenn3xgg1GV2mTBveMV2n6R
AxEAmwWTVC154zWL3mI5GN8yzZVhOBzf
=/2tq
-END PGP SIGNATURE-

Re: [O] Re: latex export settings in init files

[Eric S Fraga]

Sébastien Vauban  writes:

> Hi Eric,
>
> Eric S Fraga wrote:
>> By the way, for the types of customisation you are doing above (obviously, I
>> don't know what you have omitted), I find it easier to define an org
>> template that has the appropriate #+LaTeX_CLASS_OPTIONS and #+LATEX_HEADER
>> lines.
>
> I guess that you mean it "if the number of custom LaTeX lines is < 5 or 10",
> something like that.
>
> Even in such a case, I would opt the OP for his own document class (or style
> file), so that every custom is only made once, in one place. And, would he
> recompile his Org doc later, he would benefit from all the updated features he
> put in his class -- if nothing is contradictorily changed...
>
> Your argument is maybe about being "easier". True. And false: after all,
> what's a class or style file, everything you want except for the first few
> lines, and the last one, no?
>
> (not trying to say the opposite of you ;-) but give the OP another "sound of
> clock" -- maybe you think as well at other points I'm missing here?)

And a very good thing this is as well, Sébastien!

I guess I should clarify the above, in any case: the example the OP gave
had very specific geometry values etc.  If this is tailored to a
specific journal or conference, for instance, I would prefer to have
these settings in the document as otherwise you end up with zillions of
entries in the org variable.

If, however, the customisation is more "qualitative" (for want of a
better word but essentially meaning the definitions appropriate for
different "classes" of documents), I agree completely with you.

In the end, I use a combination of both customisations: I have entries
for article, report, conference, ... and then customise specific values
in each document.

But the great thing is you can do it either way individually, or both
ways combined, and it will work!

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)

Re: [O] Re: [babel] Calling source blocks with arguments

[Eric S Fraga]

Philipp Haselwarter  writes:

> Do you guys really just go and change all your variables in your
> scripts?

I guess... but, in answer to your original question, I would simply pass
all arguments as one "org" variable (eg. :var cmdline="one two three")
and then have the shell script break these up as desired.  I know that's
not what you wanted, mind you... :(

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)

Re: [O] Bug: Recurring items NEVER show up in timeline unaccompanied

[Carsten Dominik]

On 24.3.2011, at 18:31, Mark S wrote:

> Hello Carsten et al,
> 
> --- On Thu, 3/24/11, Carsten Dominik  wrote:
> 
>> 1. Be satisfied with the way things are, just realize
>>   that repeaters only show up on the first date when
>>   the event happens for the first time.
> 
> This would mean that you could never *trust* the
> timeline when dealing with events more than a week or
> two out. You would always have that lingering worry
> that you forgot to bump one of the repeaters.
> 
>> 2. Use the agenda, restricted to a single file, for a
>>   time range you specify.  This has the advantage
>>   that also diary sexps will work properly - the
>>   timeline currently has no way to deal with these.
> 
> This would be great if there were a "sparse"
> agenda. There isn't a way to make the agenda not show
> empty days is there? As it is, if you make an agenda
> extending out a year, you will have to wade through
> several hundred lines worth of empty days.
> 
>> 3. Change the section of the timeline code that
>>   produces the list of interesting dates.
> 
> That seems like a good solution. Is it difficult?
> 
>> 4. Define a variable that will make the timeline
>>   always look at *every* date in the range covered
>>   by the file.  And live with the fact that
>>   constructing the view might take long.  Maybe it
>>   will not even to terribly long if you really use
>>   this view for single projects.  This would be easy
>>   to implement.
> 
> This would work too, I think. Creating an agenda that
> goes out one year only took about 3 seconds on my
> not-state-of-the-art machine. Presumably the timeline
> would be faster, since it wouldn't produce all the
> extra gap lines.
> 
> Actually, when I tried to make a year long agenda using
> v-y I spent just about as much getting past the "are
> you sure" screens as it took to build the agenda.
> 
> The ideal solution would be that the Timeline view
> would process dates exactly like the agenda, including
> multiple-files, but display them like the traditional
> timeline, with ranges of dates omitted.

This is already possible, by binding the variable
org-agenda-show-all-dates to nil around the call to make
the agenda (for examples using the options section of a
custom agenda command).  So the only missing piece for
your preferred solution is the determination of starting
dates and end date in  a useful and automatic way.  Maybe
I can take a look some time this week and see if 
there is a simple way to replace the time line with
something better.

- Carsten

> 
> Mark
> 

[O] Re: zotero (or mendeley) integration with org

[Erik Hetzner]

At Sat, 26 Mar 2011 15:47:44 +,
Stephen Eglen wrote:
> 
> There was a mail-thread lastyear about zotero and integration with org.
> Now that there is an alpha release of 'org-standalone' 
>   http://www.zotero.org/blog/2011/02/
> 
> has anyone looked at whether this helps integrate org and zotero?
> 
> I've not yet switched to a pdf manager (they're all stuffed into a
> folder, with a few subfolders, and the only meta-data is in the
> filename!), so I'd appreciate hearing what others to do to look after
> their pdfs.  Mendeley is a possibility too (although syncing between
> machines is a must, and Mendeley doesn't offer that yet.)

Hi Stephen,

Re. zotero-plain [1] & integration with Zotero standalone, it would
depend on what external interface Zotero standalone is presenting for
integration with external programs (e.g. the Chrome or Safari
extensions), which is not at all clear to me. zotero-plain currently
depends on mozrepl, which I do not think would distributed with Zotero
standalone.

However, with a few modifications it should be possible to get
zotero-plain to work with the zotero.org web API, which would provide
most of the benefits of Zotero standalone, although you would be
relying on a 3rd party service.

best, Erik

1. http://e6h.org/~egh/hg/zotero-plain/
Sent from my free software system .

Re: [O] TeX to MathML & org-odt ?

[Suvayu Ali]

On Mon, 28 Mar 2011 16:09:00 +0530
Jambunathan K  wrote:

> Any opinions on TeX to MathML converters (specifically those that are
> amenable to be integrated within Orgmode/Emacs ).

I am not sure whether this is what you are asking about but just in case
you are. I use ooolatex plugin with OOo (maybe we should start calling
it Libreoffice from now :) ).  It lets me specify custom latex headers
to choose packages and renders equations as scalable images. The
rendered images can then be re-edited by selecting them again. And as
far as I recall it stays editable across OOo installations as long as
the ooolatex plugin and latex are installed.

Since it uses latex, I am guessing on paper this could be made to work
with emacs? Hope this is what you wanted to know.

-- 
Suvayu

Open source is the future. It sets us free.

[O] [PATCH] Allow inactive timestamps in org-expiry (copy of lost patch)

[Marcel van der Boom]

Hi,

Attached is a patch to org-expiry.el in contrib/lisp to allow a
customization of the timestamps inserted by org-expiry for 'CREATED'
and 'EXPIRED' properties.

This patch is what is attached to the message displayed at [1]. I have
been using this patch for a while and it works fine. From searching it
looks like this patch was 'forgotten', but I may have overlooked
something.

If the patch was rejected, you can ignore me. If it was forgotten I'd
like to request to include it.

Thx,
marcel

[1] http://www.mail-archive.com/emacs-orgmode@gnu.org/msg20882.html 


-- 
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV-- http://www.hsdev.com
So! web applications -- http://make-it-so.info
Cobra build  -- http://cobra.mrblog.nl
diff --git a/contrib/lisp/org-expiry.el b/contrib/lisp/org-expiry.el
index 4a49399..930b921 100644
--- a/contrib/lisp/org-expiry.el
+++ b/contrib/lisp/org-expiry.el
@@ -81,6 +81,11 @@
   :tag "Org Expiry"
   :group 'org)
 
+(defcustom org-expiry-inactive-timestamps nil
+  "Insert inactive timestamps for the created and expired time properties"
+  :type 'boolean
+  :group 'org-expiry)
+
 (defcustom org-expiry-created-property-name "CREATED"
   "The name of the property for setting the creation date."
   :type 'string
@@ -283,21 +288,25 @@ to today's date.  With two `C-u' prefixes, prompt the user for to
 update the date."
   (interactive "P")
   (let* ((d (org-entry-get (point) org-expiry-created-property-name))
-	 d-time d-hour)
+	 d-time d-hour timestr)
 (when (or (null d) arg)
   ;; update if no date or non-nil prefix argument
   ;; FIXME Use `org-time-string-to-time' 
-  (setq d-time (if d (apply 'encode-time (org-parse-time-string d))
+  (setq d-time (if d (org-time-string-to-time d)
 		 (current-time)))
   (setq d-hour (format-time-string "%H:%M" d-time))
+  (setq timestr
+	;; two C-u prefixes will call org-read-date
+	(if (equal arg '(16))
+		(concat "<" (org-read-date
+			 nil nil nil nil d-time d-hour) ">")
+	  (format-time-string (cdr org-time-stamp-formats
+  ;; maybe transform to inactive timestamp
+  (if org-expiry-inactive-timestamps
+	  (setq timestr (concat "[" (substring timestr 1 -1) "]")))
   (save-excursion
 	(org-entry-put
-	 (point) org-expiry-created-property-name
-	 ;; two C-u prefixes will call org-read-date
-	 (if (equal arg '(16))
-	 (concat "<" (org-read-date
-			  nil nil nil nil d-time d-hour) ">")
-	   (format-time-string (cdr org-time-stamp-formats
+	 (point) org-expiry-created-property-name timestr)
 
 (defun org-expiry-insert-expiry (&optional today)
   "Insert a property with the expiry date.
@@ -306,15 +315,20 @@ and insert today's date."
   (interactive "P")
   (let* ((d (org-entry-get (point) org-expiry-expiry-property-name))
 	 d-time d-hour)
-(setq d-time (if d (apply 'encode-time (org-parse-time-string d))
+(setq d-time (if d (org-time-string-to-time d)
 		   (current-time)))
 (setq d-hour (format-time-string "%H:%M" d-time))
+(setq timestr (if today
+		  (format-time-string (cdr org-time-stamp-formats))
+		(concat "<" (org-read-date
+ nil nil nil nil d-time d-hour) ">")))
+;; maybe transform to inactive timestamp
+(if org-expiry-inactive-timestamps
+	(setq timestr (concat "[" (substring timestr 1 -1) "]")))
+ 
 (save-excursion
   (org-entry-put
-   (point) org-expiry-expiry-property-name
-   (if today (format-time-string (cdr org-time-stamp-formats))
-	 (concat "<" (org-read-date
-		  nil nil nil nil d-time d-hour) ">"))
+   (point) org-expiry-expiry-property-name timestr
 
 ;;; Functions to process expired entries:
 

[O] Re: lisp/org-clock.el: Add param :properties to list properties in clocktable

[Niels Giesen]

> Bernt Hansen  writes:

> Thanks for the example.  That helps a lot.  I think posting this to Worg
> would be very useful.

Hi Bernt, I will do so if/when these patches get accepted ;)



-- 
http://pft.github.com/

Re: [O] Re: agenda view opening multiple buffers

[Manish]

On Mon, Mar 28, 2011 at 8:48 PM, Carsten Dominik wrote:
>
> On 27.3.2011, at 20:55, Manish wrote:
>
>> On Sun, Mar 27, 2011 at 8:21 PM, Julian Burgos wrote:
>>> Thanks.  Using x is good enough for now.  I´ll explore also Michael´s
>>> suggestions.  It would be good to have the agenda open in a buffer
>>> without having all the agenda files opened too.
>>>
>>
>> Following code should do what you want (I think).
>>
>> #+begin_src emacs-lisp
>> ;; function code copied from definition of org-agenda-exit
>>  (add-hook 'org-finalize-agenda-hook
>>            (lambda ()
>>              (interactive)
>>              (org-release-buffers org-agenda-new-buffers)
>>              (setq org-agenda-new-buffers nil)))
>> #+end_src
>
> This will make the agenda disfunctional.  Each line in the agenda contains a 
> pointer to the entry the line was derived from, so remote editing etc will 
> stop working.
>
> Exiting with "x" is the much better solution.
>


Thanks for pointing that out.  Wouldn't "x" that close the agenda as
well along with the buffers?  OP said: " It would be good to have the
agenda open in a buffer without having all the agenda files opened
too."  May be a special custom agenda command that calls the above
lambda function at the end would work better by limiting the damaged
behaviour to just one command?

/manish

Re: [O] advice: how to export a list without exporting all entries

[Carsten Dominik]

On 24.3.2011, at 21:45, Eric S Fraga wrote:

> Carsten,
> 
> one question about your workflow.  I've actually implemented much of
> what you have suggested but I am having one problem:
> 
> Carsten Dominik  writes:
> 
> [...]
> 
>> 3. I am not using an ordered list for the action items.  Instead, I
>>   give them explicit numbers, in the sequence in which I am defining
>>   the actions.  I am using some custom code (see end of this mail) to
>>   create these actions with unique numbers.  Running
>>   `M-x org-maction-new-action' (this is `C-c n' in my setup) will
>>   insert a new action that looks like this:
>> 
>>   ** TODO Action #2: :#2:
> 
> This is fine except that #x tags don't work in latex export!

I have fixed the LaTeX exporter to take care of this issue.

- Carsten

Re: [O] Re: agenda view opening multiple buffers

[Carsten Dominik]

On 28.3.2011, at 20:30, Manish wrote:

> On Mon, Mar 28, 2011 at 8:48 PM, Carsten Dominik wrote:
>> 
>> On 27.3.2011, at 20:55, Manish wrote:
>> 
>>> On Sun, Mar 27, 2011 at 8:21 PM, Julian Burgos wrote:
 Thanks.  Using x is good enough for now.  I´ll explore also Michael´s
 suggestions.  It would be good to have the agenda open in a buffer
 without having all the agenda files opened too.
 
>>> 
>>> Following code should do what you want (I think).
>>> 
>>> #+begin_src emacs-lisp
>>> ;; function code copied from definition of org-agenda-exit
>>>  (add-hook 'org-finalize-agenda-hook
>>>(lambda ()
>>>  (interactive)
>>>  (org-release-buffers org-agenda-new-buffers)
>>>  (setq org-agenda-new-buffers nil)))
>>> #+end_src
>> 
>> This will make the agenda disfunctional.  Each line in the agenda contains a 
>> pointer to the entry the line was derived from, so remote editing etc will 
>> stop working.
>> 
>> Exiting with "x" is the much better solution.
>> 
> 
> 
> Thanks for pointing that out.  Wouldn't "x" that close the agenda as
> well along with the buffers?

Yes.

>  OP said: " It would be good to have the
> agenda open in a buffer without having all the agenda files opened
> too."  May be a special custom agenda command that calls the above
> lambda function at the end would work better by limiting the damaged
> behaviour to just one command?

No.  The agenda buffer needs the source buffers alive to function.

- Carsten

Re: [O] [PATCH] Allow inactive timestamps in org-expiry (copy of lost patch)

[Nick Dokos]

Marcel van der Boom  wrote:

> This patch is what is attached to the message displayed at [1]. I have
> been using this patch for a while and it works fine. From searching it
> looks like this patch was 'forgotten', but I may have overlooked
> something.
> 
> If the patch was rejected, you can ignore me. If it was forgotten I'd
> like to request to include it.
> 

I don't think it was rejected outright, it looks as if it was
inadvertently dropped. Probably part of the reason is that David sent
the patches as application/octet-stream so they never made it to
patchwork (was patchwork even running back in 2009? I don't remember
when it was set up.) The other part might be that it's a contrib package
so most people never get to use it, let alone complain about it. The third
part might be that it was Dec. 31, so people were out partying instead of
applying patches (unimaginable, I know :-) )

The patch is now in patchwork (under your name), so it will be addressed
at some point. One question: there was a second patch in the link you
provided - should that be resubmitted as well?

Nick

> 
> [1] http://www.mail-archive.com/emacs-orgmode@gnu.org/msg20882.html 
> 
> 

Re: [O] latex export settings in init files

[Aankhen]

Hi Chris,

On Mon, Mar 28, 2011 at 17:25, Chris Beard  wrote:
> Hello,
> I've tried to modify some default latex export settings based on info from 
> here
> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg07645.html
>
> I basically add to the org-mode-hook to do:
>
> [snip]
>
> This works if I evaluate it after I've been exporting to latex, but I
> get an error whenever I start up emacs:
>
> setq: Symbol's value as variable is void: org-export-latex-classes
>
> I'm guessing there's some org-mode latex-export thing that I need to
> load first, but I'm not very familiar with how to do this. Any advice?

An alternative to flat out ‘require’-ing everything is
‘eval-after-load’.  For example:

,
| (eval-after-load 'org-export-latex
|   '(progn
|  (add-to-list org-export-latex-classes '("myarticle" . "..."))
|
|  (setq org-export-latex-date-format "%Y %B %d"
|org-export-latex-custom-lang-environments '((python "listings")
`

I use this approach & autoloads almost universally in my init file,
following some advice I read.[1] It’s a trade-off between failing
early if you have errors and speeding up Emacs’s initialization.  It
can also be less than straightforward to understand…

Aankhen

[1]: http://a-nickels-worth.blogspot.com/2007/11/effective-emacs.html

Re: [O] [PATCH] Allow inactive timestamps in org-expiry (copy of lost patch)

[Marcel van der Boom]

On ma 28-mrt-2011 14:55
Nick Dokos  wrote:

> The patch is now in patchwork (under your name), so it will be
> addressed at some point. One question: there was a second patch in
> the link you provided - should that be resubmitted as well?

The patch I attached combined the two mentioned in the message into one
patch.

marcel
-- 
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV-- http://www.hsdev.com
So! web applications -- http://make-it-so.info
Cobra build  -- http://cobra.mrblog.nl

[O] 7th todo keyword bug

[Samuel Wales]

I have found another todo keyword bug of the same type as the other 6.

A headline with a word that is the same as a todo keyword but not in
upper case has different behavior.

Example:

  * test
* Question[]
  * test

Have QUESTION as a todo keyword.  Put point at the marked spot.  Press
TAB.  The headline will outdent instead of cycling visibility.  It
should cycle visibility as it does with other headlines.

Thanks.

Samuel

-- 
The Kafka Pandemic:
  
http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html
I support the Whittemore-Peterson Institute (WPI)
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.

[O] Re: zotero (or mendeley) integration with org

[Matt Lundin]

Stephen Eglen  writes:

> There was a mail-thread lastyear about zotero and integration with org.
> Now that there is an alpha release of 'org-standalone' 
>   http://www.zotero.org/blog/2011/02/
>
> has anyone looked at whether this helps integrate org and zotero?
>
> I've not yet switched to a pdf manager (they're all stuffed into a
> folder, with a few subfolders, and the only meta-data is in the
> filename!), so I'd appreciate hearing what others to do to look after
> their pdfs.  Mendeley is a possibility too (although syncing between
> machines is a must, and Mendeley doesn't offer that yet.)

One option is to manage metadata in org-mode itself, relying on
org-attach to store and preserve links to the pdf files. Bibtex source
blocks can used to store bibliographical data for each pdf.

I find the combination of emacs-w3m, google scholar, and org-mode to be
an easier and more transparent way to manage bibtex data than an
indirect route via Zotero or Mendeley. But I also prefer to edit all my
bibtex data by hand. :)

Recoll is great for indexing. I have a mess of spaghetti code I use to
pull recoll results into a temporary org outline. I can then open the
relevant files using org links. I'd be happy to share it if anyone is
interested.

Best,
Matt

[O] Bug: Numbering in TOC broken for HTML export [7.5 (release_7.5.132.gf04d4)]

[Bernt Hansen]

Hi Lawrence,

Numbering of the Table of Contents is broken in master for HTML export.
git bisect identifies the following commit as the cause of this regression.

--8<---cut here---start->8---
9f57b8e85d185fbf3f9788fd4099709d512dedd1 is the first bad commit
commit 9f57b8e85d185fbf3f9788fd4099709d512dedd1
Author: Lawrence Mitchell 
Date:   Wed Mar 23 14:38:18 2011 +

Allow mixed export of numbered and unnumbered sections in HTML

* lisp/org-html.el (org-export-as-html): Get local value of
org-export-with-section-numbers from the buffer's plist.  Deal
specially with the case the resulting value is an integer.
(org-html-level-start): New optional argument of the option plist used
instead of `org-export-with-section-numbers'.  Also deal specially
with the case that the value is an integer.

When `org-export-with-section-numbers' (or the buffer-local
:section-numbers option) is an integer, we now export the first NUM
levels of headings with numbers and lower-level headings without.

:04 04 d3f89726820ce5f8c97d6bc21f7c86c46575c203 
4e0888ace3fdcafc3385a173d86d9d893d646730 M  lisp
--8<---cut here---end--->8---

I noticed this while updating http://doc.norang.ca/org-mode.html and my
TOC turned into a plain unnumbered list.

Reverting this commit fixes the problem for me.

Emacs  : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
 of 2010-12-11 on raven, modified by Debian
Package: Org-mode version 7.5 (release_7.5.132.gf04d4)

The following org file should have the headings numbered and include a
numbered table of contents.

--8<---cut here---start->8---
#+TITLE: Numbered TOC test for HTML export
#+OPTIONS:   H:3 num:t toc:t

* Section One 
This is the text for section one.
* Section Two
This is the text for section two.
--8<---cut here---end--->8---

Regards,
-- 
Bernt

[O] Evaluating all #+calls in a buffer

[Nick Dokos]

I have a code block in a file and then a bunch of calls to it with
different parameters. Is there a way to do all the calls in one batch?
So far, I have tried C-c C-v C-b which seems to do only the code block,
but not the #+calls and I have tried setting :export results with a
subsequent C-c C-e h to export to HTML - neither of these seems to do
the job.

E.g I can C-c C-c individually on the calls in the following:

--8<---cut here---start->8---

* foo

#+srcname: foo
#+begin_src python :export results :results output :var a :var b
print a + b
#+end_src

#+results: foo

#+call: foo(a=2, b=3) :file five

#+results: foo(a=2, b=3)
[[file:five]]

#+call: foo(a=3, b=4) :file seven

#+results: foo(a=3, b=4)
[[file:seven]]

--8<---cut here---end--->8---

and I get the output files "five" and "seven". What I would like to
be able to do is to execute something in batch mode that will produce
the two files as a result:

  emacs --batch -l minimal.emacs.babel -f  foo.org

Is there such a ?

Thanks,
Nick