> Date: Tue, 24 May 2005 13:35:38 -0400
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED], cygwin@cygwin.com, bug-texinfo@gnu.org
>
> if { test -x "$dir/$1" && test -f "$dir/$1"; } ||
>{ test -x "$dir/$1.exe" && test -f "$dir/$1.exe"; }; then
>
> This seems sensible. I c
Hello,
On Tue, May 24, 2005 at 01:35:38PM -0400, Karl Berry wrote:
> if { test -x "$dir/$1" && test -f "$dir/$1"; } ||
>{ test -x "$dir/$1.exe" && test -f "$dir/$1.exe"; }; then
>
> Stepan, do you have an objection to it?
OK, this will be the cleanest solution, after all.
I commited
if { test -x "$dir/$1" && test -f "$dir/$1"; } ||
{ test -x "$dir/$1.exe" && test -f "$dir/$1.exe"; }; then
This seems sensible. I can't actually test it, since I don't have
either Cygwin or DJPP, but at least it is symmetric.
Stepan, do you have an objection to it?
Thanks,
k
--
Uns
Hi,
On Tue, May 24, 2005 at 06:32:58AM -0600, Eric Blake wrote:
> Now, if both tex and tex.exe exist, but tex is not executable,
> then you just failed to find tex.exe on cygwin.
OK. But later on, command "tex" is called.
If both tex and tex.exe exist in the same directory in path, what does
bas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Stepan Kasal on 5/24/2005 6:22 AM:
> So my job was to fix the comment. Well, I actually replaced the code
> together with the comments, to get something which is easier to explain.
> (Actually, my code is close to what Autoconf does.)
>
Hello,
On Thu, Feb 10, 2005 at 08:43:49PM -0500, Karl Berry wrote:
> Back on this thread about texi2dvi and cygwin from a couple weeks ago.
Back, after 3 1/2 month. This thread is immortal!
You added the comment:
# But on cygwin, test -x foo will not find foo.exe.
This is not true. te
Back on this thread about texi2dvi and cygwin from a couple weeks ago.
2) On cygwin, if both $dir/tex.exe exists and a directory $dir/tex/ exist,
this function misses the existence of tex.exe.
I don't see why the presence of $dir/tex would affect things.
tex.exe would never be found on cy
> Date: Tue, 25 Jan 2005 11:55:24 +0100
> From: Stepan Kasal <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], bug-texinfo@gnu.org,
> [EMAIL PROTECTED], [EMAIL PROTECTED], cygwin@cygwin.com
>
> > > Another way to fix the problem is to adopt the solution used by autoconf:
> >
Hi,
On Mon, Jan 24, 2005 at 09:58:16PM +0200, Eli Zaretskii wrote:
> > AC_SUBST(TESTF, "test -f")
> > testfile=conf$$.exe
> > touch $testfile
> > if test -x $testfile; then
> > test -f $testfile || TESTF=:
> > fi
> > rm -f $testfile
this code was full of silly
> Date: Mon, 24 Jan 2005 09:34:21 +0100
> From: Stepan Kasal <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], bug-texinfo@gnu.org, [EMAIL PROTECTED], [EMAIL
> PROTECTED],
> cygwin@cygwin.com
>
> Fix the problem exactly as reported:
> the configure script tests for the problem:
>
> AC_SUB
Hi,
On Sun, Jan 23, 2005 at 08:15:32PM -0500, Karl Berry wrote:
> Regarding texi2dvi and cygwin, please see if the new version (below) works.
> for dir in $PATH; do
> # use test -x rather than test -f for DJGPP, where test -x checks
> # for .exe. But test -x will also return true for d
Greetings,
Regarding texi2dvi and cygwin, please see if the new version (below) works.
(Akim, I'm cc-ing you since you've worked so much on texi2dvi, not to
mention autoconf, that I figured you might spot problems.)
Thanks,
karl
#! /bin/sh
# texi2dvi --- produce DVI (or PDF) files from Texinfo
> Date: Tue, 18 Jan 2005 06:29:08 -0700
> From: Eric Blake <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], cygwin@cygwin.com
>
> This was sent to a cygwin list, but is more properly a texinfo problem in
> the texi2dvi script (version 4.7). $COMSPEC has meaning in djgpp and
> perhaps mingw, but is ju
Subject: Fw: bug in texi2dvi, and hack patch
Thanks very much for the report and various fixes. I'll fix it one way
or another.
Regards,
karl
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Document
This was sent to a cygwin list, but is more properly a texinfo problem in
the texi2dvi script (version 4.7). $COMSPEC has meaning in djgpp and
perhaps mingw, but is just a worthless environment variable when inherited
into cygwin. Instead of using $COMSPEC for determining the path
separator, you
15 matches
Mail list logo
