Re: [Orgmode] Re: Bibtex and latex export

[Nick Dokos]

Eric S Fraga <address@hidden> wrote:

> On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz <address@hidden> wrote:
> > 
> > Hi Eric,
> > 
> > Eric S Fraga <address@hidden> writes:
> > > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
> > > | egrep: Invalid range end
> > > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.
> > 
> > Something somewhere tries to make a local path from an absolute one by
> > prepending "./", which fails (predictably).  Is the input readable at
> > the original path?  Not sure the error message from egrep has to do with
> > it or not, but it must be in any case one of the processes started by
> > texi2dvi (does not show up on my system, I only have calls to grep when
> > I trace it, but one of the sub-processes might still use it).  I think
> > texi2dvi also invokes shell scripts, so any funny configuration in the
> > environment, especially where path points to, could throw it off.
> 
> As far as I know, there is nothing out of the ordinary with my paths
> etc (please note that the /.../ above was an edit on my part to hide a
> rather long path).  Any hints as to what I can do to explore this
> would be most helpful.  How can I get a trace on what texi2dvi is
> doing?  (sh -v /usr/bin/texi2dvi?)
> 

There is an explicit egrep on line 1563 or thereabouts (my version
says

# texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
# $Id: texi2dvi,v 1.104 2007/09/10 00:36:30 karl Exp $

at the top of the file):


  # If the COMMAND_LINE_FILENAME is not absolute (e.g., --debug.tex),
  # prepend `./' in order to avoid that the tools take it as an option.
  echo "$command_line_filename" | $EGREP '^(/|[A-z]:/)' >&6 \
  || command_line_filename="./$command_line_filename"


The regular expression seems a bit weird (upper case A to lower case
z?), but I can't see off the top of my head how it gets tripped up.  For
tracing, try

   sh -x texi2dvi ....

Nick