all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matthew Leifer <msleifer@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Karl Berry: Re: Nick Dokos: texi2dvi egrep regexp
Date: Sat, 9 Oct 2010 17:28:35 +0100	[thread overview]
Message-ID: <AANLkTikGAAg0ObnzAystJBDp5bcZ+DqB20NC2Fv3v9nS@mail.gmail.com> (raw)
In-Reply-To: <3B502F70-93E5-485E-B4B9-4850A06B7925@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4026 bytes --]

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:

http://www.acoustics.hut.fi/u/mairas/UltimateLatexMakefile/
http://code.google.com/p/latex-makefile/
http://xpt.sourceforge.net/tools/latexmake/

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 <fatkasuvayu%2Blinux@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...
>>
>
> Hi everyone,
>
> 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
>>
>> _______________________________________________
>> 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-orgmode
>>
>
>
> _______________________________________________
> 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-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 5868 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
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-orgmode

  reply	other threads:[~2010-10-09 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 18:51 Karl Berry: Re: Nick Dokos: texi2dvi egrep regexp Nick Dokos
2010-10-09  4:06 ` suvayu ali
2010-10-09 10:27   ` Eric S Fraga
2010-10-09 15:27     ` Carsten Dominik
2010-10-09 16:28       ` Matthew Leifer [this message]
2010-10-09 16:42       ` Nick Dokos
2010-10-09 17:25         ` Thomas S. Dye
2010-10-10  7:05           ` Carsten Dominik
2010-10-10 16:37             ` Thomas S. Dye
2010-10-10 18:04         ` Eric S Fraga
2010-10-09 16:59       ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikGAAg0ObnzAystJBDp5bcZ+DqB20NC2Fv3v9nS@mail.gmail.com \
    --to=msleifer@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.