From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Karl Berry: Re: Nick Dokos: texi2dvi egrep regexp Date: Sat, 09 Oct 2010 12:42:41 -0400 Message-ID: <26025.1286642561@gamaville.dokosmarshall.org> References: <17038.1286563867@gamaville.dokosmarshall.org> <87sk0fk6eo.wl%ucecesf@ucl.ac.uk> <3B502F70-93E5-485E-B4B9-4850A06B7925@gmail.com> Reply-To: nicholas.dokos@hp.com Return-path: Received: from [140.186.70.92] (port=47560 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P4cVd-0003tN-Bj for emacs-orgmode@gnu.org; Sat, 09 Oct 2010 12:42:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P4cVc-0008O1-0c for emacs-orgmode@gnu.org; Sat, 09 Oct 2010 12:42:57 -0400 Received: from vms173015pub.verizon.net ([206.46.173.15]:59162) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P4cVb-0008Nf-TW for emacs-orgmode@gnu.org; Sat, 09 Oct 2010 12:42:55 -0400 Received: from gamaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173015.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LA10052L7R5ZKA0@vms173015.mailsrvcs.net> for emacs-orgmode@gnu.org; Sat, 09 Oct 2010 11:42:42 -0500 (CDT) In-reply-to: Message from Carsten Dominik of "Sat, 09 Oct 2010 17:27:23 +0200." <3B502F70-93E5-485E-B4B9-4850A06B7925@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Carsten Dominik wrote: > 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? > Yes, at least theoretically. I don't think anybody has gone down the path of investigating these effects. > 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. > The trouble with this is that you are checking on egrep which will give you a positive for egrep versions >= 2.6.x, but the fix to texi2dvi might have made that irrelevant. How about try texi2dvi except do Seb's thrice-repeated pdflatex (or whatever) call After everybody has updated to the latest texinfo, the exception code can be taken out. Alternatively, the texi2dvi method can be reverted: it was an idea that was worth trying, but it has caused more harm than good at this point - maybe it can be revisited in six months. > Any ather ideas? Comments? > Nick