Oh dear. As the person who originally suggested using texi2dvi, I feel a little bit responsible for all the trouble it has caused. I wouldn't have thought that such a widely used script would have a bug like this.
Anyway, one option would be to include a patched version of texi2dvi in the org distribution, at least until the bug has been fixed in the official version. It is just a shell script, and not a huge file, so it wouldn't be too bad. Another option would be to simply inspect the contents of texi2dvi and write equivalent code in Emacs Lisp, since the original idea was just to improve the routines in org-mode that run pdflatex and bibtex. Much of the code in texi2dvi is to do with texinfo files and is irrelevant to how it is being used in org-mode so this might not be as hard as it looks.
Finally, there are various LaTeX Makefiles available that attempt to build a LaTeX document with a single invocation, much like texi2dvi. They are generally a bit less sophisticated than texi2dvi and I don't think that it would be a good idea to use them directly because requiring make might be problematic on Windows. In any case, they might provide some helpful hints on how to automate LaTeX compiling. Here are links to three that I have tried:
I've had the most success with the third one, but that is essentially just a wrapper for texi2dvi anyway.
Matt Leifer
On 9 October 2010 16:27, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
On Oct 9, 2010, at 12:27 PM, Eric S Fraga wrote:
On Fri, 8 Oct 2010 21:06:24 -0700, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
[...]
I have filed a bug report on the Fedora bugzilla[1] pointing to all
the relevant discussions about this issue. Feel free to add to/edit
it. Thanks everyone for narrowing this down. :)
And this bug has already been reported (twice) to Debian, as it turns
out:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584191
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586134
No resolution in either bug stream although suggestions do include
[A-Za-z] and [[:alpha:]].
I have simply edited /usr/bin/texi2dvi (but need to do this on all of
my other systems) and hope that next time it is upgraded the bug will
have been fixed...
I am looking for a way out which will allow pdf compilation of Org
work out of the box, and still allow texi2dvi to be used where possible.
I have so far come up with two possible work-arounds and would
like to hear if one of them makes sense:
1. I could set the environment variable LC_ALL
for the duration of the texi2dvi command to some value
like C? That should fix the egrep call, but could
it have adverse effects on the pdflatex and bibtex runs or
any other stuff used in texi2dvi?
2. On startup, I could use
(if (= 0 (shell-command "echo foo | egrep \"[A-z]\""))
....
to check if there is a problem and in this case go for
manual pdflatex runs rather than using texi2dvi. THis might work,
but it would be a bit unpredictable what ends up being used,
and with no setup in Org you could get different sets of commands
on different machines.
Any ather ideas? Comments?
Thanks.
- Carsten
- Carsten
--
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D