bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texi2dvi texinfo 4.5 path_sep bugs


From: Karl Berry
Subject: Re: texi2dvi texinfo 4.5 path_sep bugs
Date: Fri, 4 Apr 2003 20:11:41 -0500

    The following from texi2dvi is wrong on cygwin (since COMSPEC will be
    set, even though the path_sep is ':').

Can you suggest a way to distinguish the cases?  Sorry, I've never used
cygwin.

    The following hardwires path_sep as ':'

A patch follows if you'd like to try it.

Thanks for the report.

karl


*** texi2dvi.~1.15.~    Tue Feb 18 06:28:09 2003
--- texi2dvi    Fri Apr  4 17:03:43 2003
***************
*** 366,378 ****
    INDEXSTYLE="$common$INDEXSTYLE_orig"
  
    # Convert relative paths to absolute paths, so we can run in another
!   # directory (e.g., in --clean mode, or during the macro-support
!   # detection.)
    #
    # Empty path components are meaningful to tex.  We rewrite them
    # as `EMPTY' so they don't get lost when we split on $path_sep.
!    TEXINPUTS=`echo $TEXINPUTS  |sed 
's/^:/EMPTY:/;s/:$/:EMPTY/;s/::/:EMPTY:/g'`
!   INDEXSTYLE=`echo $INDEXSTYLE |sed 
's/^:/EMPTY:/;s/:$/:EMPTY/;s/::/:EMPTY:/g'`
    save_IFS=$IFS
    IFS=$path_sep
    set x $TEXINPUTS; shift
--- 366,381 ----
    INDEXSTYLE="$common$INDEXSTYLE_orig"
  
    # Convert relative paths to absolute paths, so we can run in another
!   # directory (e.g., in --clean mode, or during the macro-support detection.)
    #
    # Empty path components are meaningful to tex.  We rewrite them
    # as `EMPTY' so they don't get lost when we split on $path_sep.
!   # Hopefully no one will have an actual directory named EMPTY.
!   replace_empty="-e 's/^$path_sep/EMPTY$path_sep/g' \
!                  -e 's/$path_sep\$/${path_sep}EMPTY/g' \
!                  -e 's/$path_sep$path_sep/${path_sep}EMPTY:/g'"
!    TEXINPUTS=`echo $TEXINPUTS  | eval sed $replace_empty`
!   INDEXSTYLE=`echo $INDEXSTYLE | eval sed $replace_empty`
    save_IFS=$IFS
    IFS=$path_sep
    set x $TEXINPUTS; shift




reply via email to

[Prev in Thread] Current Thread [Next in Thread]