On Fri, Apr 08, 2022 at 10:50:19PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 8 Apr 2022 15:53:31 +0200
> > From: Tomas Kalibera
> >
> > Would this be an acceptable fix? (turn OSTYPE to uppercase when setting
> > MSYSTEM)
> >
> > MSYSTEM=$(echo $OSTYPE | tr [a-z] [A-Z]) uname | $EGREP -iv
> From: Gavin Smith
> Date: Fri, 8 Apr 2022 15:12:19 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> On Fri, Apr 08, 2022 at 03:53:31PM +0200, Tomas Kalibera wrote:
> >
> > On 4/8/22 15:31, Gavin Smith wrote:
> > > On Fri, Apr 08, 2022 at 03:15:01PM +0200, Tomas Kalibera wrote:
> > > > > Wha
> Date: Fri, 8 Apr 2022 15:53:31 +0200
> From: Tomas Kalibera
>
> Would this be an acceptable fix? (turn OSTYPE to uppercase when setting
> MSYSTEM)
>
> MSYSTEM=$(echo $OSTYPE | tr [a-z] [A-Z]) uname | $EGREP -iv
> 'cygwin|msys' >/dev/null; then
>
> It was suggested by Markus Mützel in a
> From: Gavin Smith
> Date: Fri, 8 Apr 2022 14:31:32 +0100
> Cc: Eli Zaretskii , bug-texinfo@gnu.org
>
> > It works with Msys2 and cygwin for me, but breaks with MSYSTEM, where
>
> What is MSYSTEM? Is this the original msys?
>
> > $ uname
> > MINGW32_NT-6.2
> >
> > $ MSYSTEM=$OSTYPE uname
> >
> From: Gavin Smith
> Date: Fri, 8 Apr 2022 13:56:31 +0100
> Cc: Tomas Kalibera , bug-texinfo@gnu.org
>
> What happens if we don't set MSYSTEM at all?
Then you cannot distinguish between MSYS and MinGW, because 'uname'
will return a value that doesn't tell which one is it. So you have a
problem
On 4/8/22 18:30, Gavin Smith wrote:
On Fri, Apr 08, 2022 at 06:07:01PM +0200, Tomas Kalibera wrote:
Works for me on all those 3 systems (just needed to add \ at the end of the
line after "/dev/null "). And checking OSTYPE against "msys" is a common
pattern in Msys2 patches, so I assume it is c
On Fri, Apr 08, 2022 at 06:07:01PM +0200, Tomas Kalibera wrote:
> Works for me on all those 3 systems (just needed to add \ at the end of the
> line after "/dev/null "). And checking OSTYPE against "msys" is a common
> pattern in Msys2 patches, so I assume it is correct for Msys2.
Commited in df78
On 4/8/22 17:25, Gavin Smith wrote:
On Fri, Apr 08, 2022 at 04:30:12PM +0200, Tomas Kalibera wrote:
I am not sure what is the correct name of it. I executed
C:\MinGW\msys\1.0\msys.bat to get the shell.
It uses : as path separator.
Have you found that running texi2dvi fails in such an environ
On Fri, Apr 08, 2022 at 04:30:12PM +0200, Tomas Kalibera wrote:
> I am not sure what is the correct name of it. I executed
> C:\MinGW\msys\1.0\msys.bat to get the shell.
> It uses : as path separator.
>
> > Have you found that running texi2dvi fails in such an environment, with
> > my patch above?
On 4/8/22 16:12, Gavin Smith wrote:
On Fri, Apr 08, 2022 at 03:53:31PM +0200, Tomas Kalibera wrote:
On 4/8/22 15:31, Gavin Smith wrote:
On Fri, Apr 08, 2022 at 03:15:01PM +0200, Tomas Kalibera wrote:
What happens if we don't set MSYSTEM at all?
diff --git a/util/texi2dvi b/util/texi2dvi
ind
On Fri, Apr 08, 2022 at 03:53:31PM +0200, Tomas Kalibera wrote:
>
> On 4/8/22 15:31, Gavin Smith wrote:
> > On Fri, Apr 08, 2022 at 03:15:01PM +0200, Tomas Kalibera wrote:
> > > > What happens if we don't set MSYSTEM at all?
> > > >
> > > > diff --git a/util/texi2dvi b/util/texi2dvi
> > > > index
On 4/8/22 15:31, Gavin Smith wrote:
On Fri, Apr 08, 2022 at 03:15:01PM +0200, Tomas Kalibera wrote:
What happens if we don't set MSYSTEM at all?
diff --git a/util/texi2dvi b/util/texi2dvi
index 1f42b41907..c506bbad37 100755
--- a/util/texi2dvi
+++ b/util/texi2dvi
@@ -85,7 +85,7 @@ IFS="$space
On Fri, Apr 08, 2022 at 03:15:01PM +0200, Tomas Kalibera wrote:
> > What happens if we don't set MSYSTEM at all?
> >
> > diff --git a/util/texi2dvi b/util/texi2dvi
> > index 1f42b41907..c506bbad37 100755
> > --- a/util/texi2dvi
> > +++ b/util/texi2dvi
> > @@ -85,7 +85,7 @@ IFS="$space$tab$newline"
On 4/8/22 14:56, Gavin Smith wrote:
On Wed, Apr 06, 2022 at 05:24:01PM +0300, Eli Zaretskii wrote:
Date: Wed, 6 Apr 2022 14:39:30 +0200
From: Tomas Kalibera
texi2dvi on Msys2 doesn't find tex, because it incorrectly detects ";"
as path separator (it is ":").
The problem is in the following
On Wed, Apr 06, 2022 at 05:24:01PM +0300, Eli Zaretskii wrote:
> > Date: Wed, 6 Apr 2022 14:39:30 +0200
> > From: Tomas Kalibera
> >
> > texi2dvi on Msys2 doesn't find tex, because it incorrectly detects ";"
> > as path separator (it is ":").
> >
> > The problem is in the following code. With M
> Date: Wed, 6 Apr 2022 14:39:30 +0200
> From: Tomas Kalibera
>
> texi2dvi on Msys2 doesn't find tex, because it incorrectly detects ";"
> as path separator (it is ":").
>
> The problem is in the following code. With Msys2, OSTYPE is "msys", but
> MSYSTEM is upper-case "MSYS" and uname needs i
Hello,
texi2dvi on Msys2 doesn't find tex, because it incorrectly detects ";"
as path separator (it is ":").
The problem is in the following code. With Msys2, OSTYPE is "msys", but
MSYSTEM is upper-case "MSYS" and uname needs it that way:
# In the case of Msys, uname returns a value derived
On Sun, Mar 20, 2022 at 10:22:32AM +0100, Wybo Dekker wrote:
> On line 464:
>
> ldta_result="$ldata_result \"$dir\""
>
> ldata should probably be ldta
Thank you for the report. The bug was probably introduced by me
when I added prefixes to the variable names.
There is a comment above the l
On line 464:
ldta_result="$ldata_result \"$dir\""
ldata should probably be ldta
--
Wybo Dekker
Deilsedijk 60
NL-4158 CH Deil
The Netherlands
m: +31 6 3033 3955
> the current texi2dvi ... no longer handles TEXINPUTS values
> correctly which contain braces.
>
> I've made the change below, and installed the current texi2dvi in
> TeX Live (all platforms). Let me know if problems persist (wouldn't
> surprise me).
It works for me, thanks.
Wer
the current texi2dvi ... no longer handles TEXINPUTS values
correctly which contain braces.
I've made the change below, and installed the current texi2dvi in TeX
Live (all platforms). Let me know if problems persist (wouldn't
surprise me).
Thanks,
karl
--- texi2dvi.~1.132.~ 2008-07-
Folks,
the current texi2dvi (both version 1.122 which is part of the current
TeXLive repository and 1.132 which is part of the current texinfo
repository) no longer handles TEXINPUTS values correctly which contain
braces. For example, version 1.34 (part of texinfo 4.8) did.
My shell is bash 3.
Hi Eli,
On Wed, May 25, 2005 at 09:30:57PM +0300, Eli Zaretskii wrote:
> > I don't have Cygwin nor DJGPP, nor any sense for responsibility. ;-)
>
> Does this mean that you won't mind checking-in changes disregarding
> any possible effects on the DJGPP port? I hope not.
absolutely not!
The jok
> Date: Wed, 25 May 2005 11:18:18 +0200
> From: Stepan Kasal <[EMAIL PROTECTED]>
> Cc: cygwin@cygwin.com, [EMAIL PROTECTED], bug-texinfo@gnu.org
>
> I don't have Cygwin nor DJGPP, nor any sense for responsibility. ;-)
Does this mean that you won't mind checking-in changes disregarding
any possib
> 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
_
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
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
-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.)
>
30 matches
Mail list logo
