texinfo configure bug
Thomas: I found a bug in the texinfo configure script, causing the test for for library with termcap variables always to fail. Here's a patch. --Paul Vojta cut here --- utils/texinfo/configure.ac.orig 2003-01-31 08:48:57.0 -0800 +++ utils/texinfo/configure.ac 2003-02-14 23:38:57.0 -0800 @@ -97,7 +97,7 @@ LIBS=$oldLIBS -l$termlib fi AC_TRY_LINK(, -#ifdef HAVE_NCURSES_TERMCAP_H +[#ifdef HAVE_NCURSES_TERMCAP_H #include ncurses/termcap.h #else #ifdef HAVE_TERMCAP_H @@ -116,7 +116,7 @@ UP++ PC++; return ospeed != 0; -, ac_cv_var_ospeed=$trylib; break) +], ac_cv_var_ospeed=$trylib; break) done LIBS=$oldLIBS ) --- utils/texinfo/configure.orig2003-01-31 08:49:25.0 -0800 +++ utils/texinfo/configure 2003-02-14 23:39:54.0 -0800 @@ -6405,7 +6405,12 @@ #endif #endif /* Make sure all variables actually exist. AIX 4.3 has ospeed but no BC. - --Andreas Ley [EMAIL PROTECTED] + --Andreas Ley [EMAIL PROTECTED], 24 Aug 2000. */ +BC++; +UP++ +PC++; +return ospeed != 0; + ; return 0; } @@ -6422,17 +6427,11 @@ ac_status=$? echo $as_me:$LINENO: \$? = $ac_status 5 (exit $ac_status); }; }; then - 24 Aug 2000. */ -BC++; -UP++ -PC++; -return ospeed != 0; - + ac_cv_var_ospeed=$trylib; break else echo $as_me: failed program was: 5 sed 's/^/| /' conftest.$ac_ext 5 -ac_cv_var_ospeed=$trylib; break fi rm -f conftest.$ac_objext conftest$ac_exeext conftest.$ac_ext done
Re: texinfo configure bug
Date: Sun, 16 Feb 2003 01:37:09 +0100 From: Thomas Esser [EMAIL PROTECTED] Subject: Re: texinfo configure bug To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] I found a bug in the texinfo configure script, causing the test for for library with termcap variables always to fail. Here's a patch. I don't get it. How can this work without ; after UP++ ? I guess I missed that one. --Paul
Re: mpost problem
Date: 05 Feb 2003 23:52:26 +0100
From: Olaf Weber [EMAIL PROTECTED]
To: Thomas Esser [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: mpost problem
Thomas Esser writes:
A better fix was suggested by Olaf Weber:
--- orig/texk/web2c/mpware/makempx.in Fri Oct 26 15:22:46 2001
+++ texk/web2c/mpware/makempx.inTue Feb 4 18:31:57 2003
@@ -15,7 +15,7 @@
: ${MPTOTEX=mpto -tex}
: ${MPTOTR=mpto -troff}
: ${NEWER=newer}
-: ${TEX=tex}
+: ${TEX=tex --parse-first-line}
: ${TROFF='eqn -d\$\$ | troff -Tpost'}
# convert relative path to absolute in $MAKEMPX_BINDIR:
By the way, I don't think quotes are required there, but do test so
they can be added if necessary.
They're needed on Solaris 2.6.
--Paul Vojta
Re: texmfsrc LICENSE
Date: Sat, 1 Feb 2003 21:24:37 +0100 From: Thomas Esser [EMAIL PROTECTED] Subject: Re: texmfsrc LICENSE To: [EMAIL PROTECTED], [EMAIL PROTECTED] BTW: I wonder if anybody has successfully compiled and/or tested rc2. I did not get much feetback yet... It compiles and works under Debian Linux --Paul Vojta
Re: 20030112 breaks dvips -o |lpr
Date: Thu, 16 Jan 2003 22:39:18 +0100 From: =?ISO-8859-1?Q?Giuseppe_Ghib=F2?= [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: 20030112 breaks dvips -o |lpr [and for special backtick, only allow a common set of commands at a fixed path, e.g. convert from ImageMagick] For format conversions, I prefer the approach used by xdvi: Instead of backtick, just put the file name there, and have the application recognize the format and run the appropriate converter. For example, in xdvi, if a \special refers to a file whose name ends in .Z or .gz or .bz2, and if the file begins with the right magic number, then xdvi will automatically run uncompress -c, gunzip -c, or bunzip2 -c (respectively) on the file. Regarding o |rm -rf / in config files, I would suggest that the behavior depend on the config file. For example, a config file in . would be regarded as unclean, and o |command in such a config file would be rejected, but a config file in /usr/local/texmf/dvips/config would be regarded as clean and dvips would allow o |command in such a location. --Paul Vojta
Re: Stack size limit?
Date: Thu, 12 Sep 2002 11:41:30 +0200 (MEST) From: David Kastrup [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Stack size limit? There are always ways to do weired things and to bring the system down unless you set up limits that make the system unusable. I don't think that adding such a system dependency is worth the trouble. Well, I would consider it worth the trouble in cases where this may affect system stability. If TeX can bring down the operating system, then it's a bug in the O/S, not in TeX. --Paul Vojta, [EMAIL PROTECTED]
Re: [PATCH]: cross building teTeX-src-beta-20020530 for Cygwin
To: [EMAIL PROTECTED] Subject: [PATCH]: cross building teTeX-src-beta-20020530 for Cygwin From: Jan Nieuwenhuizen [EMAIL PROTECTED] Date: Wed, 17 Jul 2002 14:57:54 +0200 Hi, I'm the (new) Cygwin maintainer for teTeX, and as such had to make some additions and fixes for cross building teTeX. Recently, I have made similar fixes to Guile. To cross build teTeX, it is assumed that you first compile and install teTeX natively. [snip] Attached is the raw patch ... Just a few comments specific to xdvik: The test XDVI_SYS_STREAMS already checks for stropts.h, so I don't see why the following diffs are needed: In texk/xdvik/configure.in -- -AC_CHECK_HEADERS(netdb.h sys/bsdtypes.h X11/Xosdefs.h sys/fcntl.h) +AC_CHECK_HEADERS(netdb.h stropts.h sys/bsdtypes.h X11/Xosdefs.h sys/fcntl.h) In texk/xdvik/events.c -- -#if HAVE_STREAMS +#if HAVE_STROPTS_H --Paul Vojta, [EMAIL PROTECTED]
Re: finally: new texmf tarball (beta-20011128)
Date: Thu, 29 Nov 2001 18:00:23 +0100 From: Thomas Esser [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: finally: new texmf tarball (beta-20011128) Hi, Yesterday I have uploaded a new texmf tarball which is quite up-to-date I think (please let me know about any outdated/wrong stuff in it). I noticed three files with weird permissions (646). Probably they don't belong: [texmf/]fonts/source/public/*.log --Paul Vojta, [EMAIL PROTECTED]
Re: finally: new teTeX pretest (20011103)
Date: Sat, 3 Nov 2001 23:55:18 +0100
From: Thomas Esser [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: finally: new teTeX pretest (20011103)
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Hi,
I am pleased to announce a new teTeX pretest release.
Thomas:
I have a request for dvips. Could you please incorporate the following patch
(which applies almost-cleanly to the latest sources)? It sets the environment
variables PRINTER and LPDEST when piping output to another program, so that
config files can have more commonality.
--Paul Vojta, [EMAIL PROTECTED]
cut here
diff -ur dvipsk.orig/dvips.1 dvipsk/dvips.1
--- dvips.1 Mon Sep 13 14:36:51 1999
+++ dvipsk/dvips.1 Mon Sep 13 14:37:03 1999
@@ -243,6 +243,16 @@
thus, specifying
.I !lpr
as the output file will automatically queue the file for printing.
+When running subprograms,
+.B dvips
+sets the
+.I PRINTER
+and
+.I LPDEST
+environment variables to the printer name (if available), so no
+.I -P
+option is needed for
+.IR lpr .
This option also disables the automatic reading of the
.I PRINTER
environment variable, and turns off the automatic sending of control D
diff -ur dvipsk.orig/dvips.c dvipsk/dvips.c
--- dvips.c Mon Sep 13 14:36:51 1999
+++ dvipsk/dvips.c Mon Sep 13 14:37:03 1999
@@ -964,10 +964,12 @@
if (*p == 0 argv[i+1])
p = argv[++i] ;
printer = p ;
+ xputenv(PRINTER, printer);
+ xputenv(LPDEST, printer);
noenv = 1 ;
if (!getdefaults()) {
/* If no config file, default the output name. */
-oname = concat (| lpr -P, printer);
+oname = | lpr;
}
npapsiz = opapsiz ;
while (npapsiz npapsiz-next)
@@ -1045,6 +1047,7 @@
strcpy(nextstring, p) ;
strcat(nextstring, .cfg) ;
#else
+ xputenv(LPDEST, p);
strcpy(nextstring, config.) ;
strcat(nextstring, p) ;
#endif
diff -ur dvipsk.orig/dvips.texi dvipsk/dvips.texi
--- dvips.texi Mon Sep 13 14:36:51 1999
+++ dvipsk/dvips.texi Mon Sep 13 14:37:03 1999
@@ -922,7 +922,9 @@
the output file will automatically queue the file for printing as
usual. (The MS-DOS version will print to the local printer device
@file{PRN} when @var{name} is @samp{|lpr} and a program by that name
-cannot be found.)
+cannot be found.) Under Unix, dvips will set the environment variables
+@code{PRINTER} and @code{LPDEST} to the printer name, so no @samp{-P}
+option is needed for @samp{lpr}.
@samp{-o} disables the automatic reading of the @code{PRINTER}
environment variable, and turns off the automatic sending of control-D.
@@ -1416,8 +1418,11 @@
In the file @file{config.foo}, a setting like this is probably
appropriate:
@example
-o |lpr -Pfoo
+o |lpr
@end example
+Under Unix, dvips will set the environment variables
+@code{PRINTER} and @code{LPDEST} to the printer name, so no @samp{-P}
+option is needed for @samp{lpr}.
The MS-DOS version will emulate spooling to @code{lpr} by printing to
the local printer device @file{PRN} if it doesn't find an executable
program by that name in the current directory or along the @code{PATH}.
Re: A new release teTeX+pdfTeX for Mac OS X
On Tue, Aug 07, 2001 at 08:47:55AM +0200, Sherlock Holmes wrote: (I hope my messages get through on the mailing lists I'm currently not subscribed to as I'm away for a couple of weeks) Made it (to tetex-pretest, at least). [snip] ftp://ftp.nluug.nl/comp/macosx/tex-gs/teTeX.dmg ftp://ftp.nluug.nl/pub/comp/macosx/tex-gs/teTeX.dmg -- Paul Vojta, [EMAIL PROTECTED]
Re: dvi{select,concat} (was: sourceforge for texk?)
Date: Wed, 6 Jun 2001 09:52:33 -0700 (PDT) From: Pierre MacKay [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [tex-k] sourceforge for texk? [snip] While I have your ear, I have been looking for the most recent version of the old dviselect and dviconcat originally developed by Chris Torek at the University of Maryland. If they have disappeared, as they seem to have, what takes their place? They are a lot more convenient than trying to muck around with postscript files directly. The most recent I'm aware of is CTAN:dviware/dvibook. --Paul Vojta, [EMAIL PROTECTED]
Re: xdvi's buttons are missing
Date: Mon, 2 Oct 2000 09:29:00 +0200 (MET DST) From: Thomas Esser [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: xdvi's buttons are missing One warning (error?) was displayed, though: ./xdvint_line: No such file or directory In what context? Hm... What do you mean by context? Hardware/software configuration? What I meant was, did this occur during ./configure, during make, or while running, and what was printed out just before and just after? (Not that it matters anymore; see below.) Is this different from what you were reporting earlier? No. I just wwanted tgive you the information that "x" keystroke or "+expert" does not cure the problem. OK. Date: Mon, 2 Oct 2000 10:01:10 +0200 (MET DST) From: Thomas Esser [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: xdvi-22.29 button problem: I have had a closer look at the button problem of xdvik and concluded the following: - the problem is caused by compiling against the XFree86-3.X headers and running against the shared libs of XFree86-4.01 - there is no difference between plain xdvi or xdvik regarding this bug (even though I have claimed that only xdvi works ok with XFree86-4.01 in an earlier message. That was wrong.) Thomas In that case, I think the advice is not to compile against the 3.X headers if you want to run it with the 4.0 shared libraries. Headers should be compatible with libraries, and I don't see any way around this. --Paul
Re: xdvi's buttons are missing
Date: Sun, 1 Oct 2000 09:36:02 +0200 (MET DST) From: Thomas Esser [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: xdvi's buttons are missing Have you tried -- plain (non-k) xdvi? I just did (for xdvi-22.29): ./configure --with-tetex make TEXMFMAIN=/usr/local/teTeX/share/texmf TEXMFCNF=/usr/local/teTeX/share/texmf/web2c ./xdvi /tmp/small2e and the buttens were not missing. One warning (error?) was displayed, though: ./xdvint_line: No such file or directory In what context? xdvi +expert the 'x' keystroke No buttons with xdvik. Or, more precise, the place for the buttinlist is there, but it is empty. Is this different from what you were reporting earlier? --Paul Vojta, [EMAIL PROTECTED]
Re: xdvi's buttons are missing
Date: Fri, 29 Sep 2000 20:14:53 +0200 (MET DST) From: Thomas Esser [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Nicolai Langfeldt [EMAIL PROTECTED], Paul Vojta [EMAIL PROTECTED] Subject: Re: xdvi's buttons are missing [Added xdvi + xdvik maintainers to Cc:] I have "updated" my system to RedHat 7.0, and now my xdvi does not have any of the buttons (Quit and friends). I can confirm that. It even happens for me if I recompile xdvi. Running xdvi against the XFree-4.01 shared libs shows this problem. Running the same binary arainst the XFree-3.?? libraries works ok. Have you tried -- plain (non-k) xdvi? xdvi +expert the 'x' keystroke What happens in each of the above cases? --Paul Vojta, [EMAIL PROTECTED]
Re: omega 1.11 (was: PStricks)
Date: Tue, 9 May 2000 07:14:07 +0200 (MET DST) From: Thomas Esser [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: PSTricks Well, omega-1.11 arrived on CTAN (ctan.tug.org, to be exact) on 2 February 2000. Is there any reason it did not appear in tetex-2305? I think that you are wrong. $ ls -l FILES.byname -rw-r--r-- 1 te users 4289960 Mar 28 00:26 FILES.byname $ grep 2000/03/27 FILES.byname 2000/03/27 | 12957 | FILES.last07days 2000/03/27 | 539583 | support/pmx/pmx-unix-2.20.tar.gz 2000/03/27 | 831118 | support/pmx/pmx220.sit.hqx $ grep omega.*.tar.gz FILES.byname 1997/11/03 |6065916 | systems/omega/omega.tar.gz 1997/11/01 |1112264 | systems/omega/omega_texmf.tar.gz 1999/07/07 |1409842 | systems/unix/teTeX/1.0/distrib/goodies/omega.tar.gz 1998/03/28 |2237604 | systems/web2c/dvik-omega-1.0.tar.gz 1998/03/14 | 252068 | systems/web2c/omegadoc-1.5.tar.gz 1998/03/28 |1050214 | systems/web2c/omegalib-1.5.tar.gz 1998/03/28 | 442070 | systems/web2c/web2c-7.2-omega-1.5.tar.gz This is on my local ctan mirror which I update by a DAT tape from time to time. Sure, I'll look at the new omega release, but I don't think that it was on CTAN in February. I was unable to connect to ftp.dante.de (it seems to be down at the moment), but look at this: _tashkent% ftp ftp.tex.ac.uk Connected to ftp.tex.ac.uk. 220 ftp.tex.ac.uk FTP server (Version wu-2.6.0(6) Mon Apr 10 09:59:05 BST 2000) ready. Name (ftp.tex.ac.uk:vojta): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 230-Welcome, archive user! 230- ... 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp cd tex-archive/systems/omega 250-Please read the file README 250- it was last modified on Mon Jan 31 02:28:00 2000 - 99 days ago 250 CWD command successful. ftp dir 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. total 1948 -rw-rw-r-- 1 ctan TeX 140 Nov 2 1997 .zipped -rw-r--r-- 1 ctan staff4665 Jan 31 02:28 README drwxr-sr-x 4 ctan staff4096 Apr 7 05:39 linux -rw-r--r-- 1 ctan staff 257437 Mar 30 1999 omega-doc-1.8.tar.gz -rw-r--r-- 1 ctan staff 1151397 Mar 17 1999 omega-lib-1.8.tar.gz -rw-r--r-- 1 ctan staff4385 Feb 2 12:45 omega.sty drwxr-sr-x 2 ctan staff4096 Apr 7 05:39 thai -rw-r--r-- 1 ctan staff 46373 Feb 6 03:03 torture.tex -rw-r--r-- 1 ctan staff 10448 Feb 2 12:48 uni2cuni.ocp -rw-r--r-- 1 ctan staff4818 Feb 2 12:47 uni2cuni.otp -rw-r--r-- 1 ctan staff 470398 Feb 2 12:45 web2c-7.3-omega-1.11.tar.gz 226 Transfer complete. --Paul Vojta, [EMAIL PROTECTED]
Re: PSTricks
Date: Mon, 8 May 2000 10:11:04 +0200 (MET DST) From: Thomas Esser [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: PSTricks PS: when working on teTeX, I always check for new stuff that arrived on CTAN. So, unless I have some updated package in a teTeX release, there is no need for telling me that some new software has arrived on CTAN... Well, omega-1.11 arrived on CTAN (ctan.tug.org, to be exact) on 2 February 2000. Is there any reason it did not appear in tetex-2305? --Paul Vojta, [EMAIL PROTECTED]
