On 8/20/2010 11:43 AM, Christopher Faylor wrote:
> On Fri, Aug 20, 2010 at 08:00:14AM -0400, Steve Holden wrote:
>> On 8/20/2010 7:53 AM, Steve Holden wrote:
>>> On 8/20/2010 5:29 AM, Reuben Thomas wrote:
On Thu 25 May 2006, Karl Berry wrote:
> This line in fmtutil.cnf indicates the p
On Fri, Aug 20, 2010 at 10:14:29AM -0400, Steve Holden wrote:
>I'd like to take this opportunity to say how much I personally
>appreciate the availability of Cygwin - I use it daily, and it makes
>the computing experience on Windows far more bearable and productive
>than it otherwise would be. I'l
On Fri, Aug 20, 2010 at 08:00:14AM -0400, Steve Holden wrote:
>On 8/20/2010 7:53 AM, Steve Holden wrote:
>> On 8/20/2010 5:29 AM, Reuben Thomas wrote:
>>> On Thu 25 May 2006, Karl Berry wrote:
>>>
This line in fmtutil.cnf indicates the problem:
etex pdfetex lang
On 8/20/2010 9:22 AM, Eric Blake wrote:
> On 08/20/2010 06:00 AM, Steve Holden wrote:
>>
>> My intention was to highlight the fact that issues will (eventually) be
>> re-raised thanks to the phenomenal group memory of this list. But of
>> course the issue might have had attention (or at least been
On 08/20/2010 06:00 AM, Steve Holden wrote:
>
> My intention was to highlight the fact that issues will (eventually) be
> re-raised thanks to the phenomenal group memory of this list. But of
> course the issue might have had attention (or at least been resolved as
> "wontfix" with appropriate disc
On 8/20/2010 7:53 AM, Steve Holden wrote:
> On 8/20/2010 5:29 AM, Reuben Thomas wrote:
>> On Thu 25 May 2006, Karl Berry wrote:
>>
>>> This line in fmtutil.cnf indicates the problem:
>>>
>>> etexpdfetex language.def
>>> -translate-file=cp227.tcx *etex.ini
>>>
>>> Either
On 8/20/2010 5:29 AM, Reuben Thomas wrote:
> On Thu 25 May 2006, Karl Berry wrote:
>
>> This line in fmtutil.cnf indicates the problem:
>>
>> etex pdfetex language.def-translate-file=cp227.tcx
>> *etex.ini
>>
>> Either (1) the second word should be changed to "etex", or
>> (2)
On Thu 25 May 2006, Karl Berry wrote:
> This line in fmtutil.cnf indicates the problem:
>
> etex pdfetex language.def-translate-file=cp227.tcx
> *etex.ini
>
> Either (1) the second word should be changed to "etex", or
> (2) it should be arranged for "etex" in invoke pdfetex i
i.e., the patch that Ralf Wildenhues previously sent out is correct
Ok, I applied the change to system.h, so that NULL_DEVICE will be
/dev/null under Cygwin. Makes sense.
Ralf's texi2dvi changes are clearly not generally applicable. E.g., Eli
has spent a lot of time making Texinfo (and ever
On Sun, May 28, 2006 at 12:13:03PM -0500, Karl Berry wrote:
>>On Sun, May 28, 2006 at 12:35:53PM -0400, Christopher Faylor wrote:
>>i.e., the patch that Ralf Wildenhues previously sent out is correct
>>(which shouldn't be too surprising since it came from the texinfo
>>release). There should be no
> Date: Sun, 28 May 2006 12:13:03 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED]
>
> Ralf's texi2dvi changes are clearly not generally applicable. E.g., Eli
> has spent a lot of time making Texinfo (and everything else) work under
> DJGPP. I can't just blow that away.
Th
On Sun, May 28, 2006 at 12:35:53PM -0400, Christopher Faylor wrote:
>i.e., the patch that Ralf Wildenhues previously sent out is correct
>(which shouldn't be too surprising since it came from the texinfo
>release).
^
cygwin
(I bet I'll regret not making that clear)
cgf
--
Unsubscribe info:
I forgot to cc bug-texinfo on this, so let me do that and expand on
things a little.
On Sun, May 28, 2006 at 11:43:19AM -0400, Christopher Faylor wrote:
>On Sat, May 27, 2006 at 02:09:58PM -0500, Karl Berry wrote:
>Content-Description: message body text
>>the script needs to initialize IFS
>>
On Sat, May 27, 2006 at 02:09:58PM -0500, Karl Berry wrote:
Content-Description: message body text
>the script needs to initialize IFS
>
>Ok, I put in the initialization. Thanks for the report & explanation.
>
>- I don't know about the NULL_DEVICE and the path_sep setting changes
>
>I don'
the script needs to initialize IFS
Ok, I put in the initialization. Thanks for the report & explanation.
- I don't know about the NULL_DEVICE and the path_sep setting changes
I don't either, I just do what I'm told :). Whatever the Cygwin folks
say should be done in the Cygwin part of
On Sat, May 27, 2006 at 10:05:20AM +0200, Ralf Wildenhues wrote:
>Hi Karl, Christopher,
>
>* Karl Berry wrote on Sat, May 27, 2006 at 01:21:16AM CEST:
>>
>> [Excluding cygwin, I doubt they care about this part.]
>
>Oh yes they will care especially about this part. ;-)
>
>> $ texindex ./main.a
Hi Karl, Christopher,
* Karl Berry wrote on Sat, May 27, 2006 at 01:21:16AM CEST:
>
> [Excluding cygwin, I doubt they care about this part.]
Oh yes they will care especially about this part. ;-)
> $ texindex ./main.au ./main.cp ./main.pg ./main.sb
> Segmentation fault (core dumped)
>
On Fri, May 26, 2006 at 09:33:12PM +, Eric Blake wrote:
>cgf wrote:
>
>> >0022FF88 61005EB3 (, , , )
>>
>> That's apparently a call to mktemp, although I can't tell what's causing
>> the problem.
>
>Well, looking at the source to the cygwin distribution of
cgf wrote:
> >0022FF88 61005EB3 (, , , )
>
> That's apparently a call to mktemp, although I can't tell what's causing
> the problem.
Well, looking at the source to the cygwin distribution of texinfo, it is
pretty obvious:
$ diff -u texindex.c.orig texindex.
On Fri, May 26, 2006 at 06:46:21AM +0200, Ralf Wildenhues wrote:
>$ cat texindex.exe.stackdump
>Exception: STATUS_ACCESS_VIOLATION at eip=6105440C
>
>eax=004A ebx=0003 ecx=0013 edx=02B9E8A9 esi=00405457 edi=0040544D
>
>ebp=0022EE08 esp=0022ED60 program=C:\cygwin\bin\texindex.exe, pid 2
Hi Karl,
* Karl Berry wrote on Fri, May 26, 2006 at 12:04:15AM CEST:
> This line in fmtutil.cnf indicates the problem:
>
> etex pdfetex language.def-translate-file=cp227.tcx
> *etex.ini
>
> Either (1) the second word should be changed to "etex", or
> (2) it should be arrang
This line in fmtutil.cnf indicates the problem:
etexpdfetex language.def-translate-file=cp227.tcx
*etex.ini
Either (1) the second word should be changed to "etex", or
(2) it should be arranged for "etex" in invoke pdfetex instead of etex.
E.g., make "etex" a link to pdfet
Hi Karl,
* Karl Berry wrote on Wed, May 24, 2006 at 10:03:39PM CEST:
>
> Ralf, what is the output if you run
> tex \\end
> etex \\end
> pdfetex \\end
See typescript, attached.
> This shows that texi2dvi is invoking etex.
> This shows that mktexfmt is invoking pdfetex to build etex.fmt.
>
Ok, you got me curious. How does TeX know what application wrote the file
if it's not "to do with" the contents of that file?
Sorry, I was referring to the one-line source file
\input texinfo @bye
As for the .fmt file, yes, it surely records whether tex, etex, pdfetex,
etc., was used t
Hi Dave,
* Dave Korn wrote on Tue, May 23, 2006 at 03:41:51PM CEST:
> On 23 May 2006 13:13, Ralf Wildenhues wrote:
>
> [ As per cygwin-L tradition, I am replying only to the lists; Ralf, if you see
> this and Karl does not, please feel free to forward it. ]
I'm sure Karl reads bug-texinfo; he ma
On 23 May 2006 13:13, Ralf Wildenhues wrote:
[ As per cygwin-L tradition, I am replying only to the lists; Ralf, if you see
this and Karl does not, please feel free to forward it. ]
> In the Automake testsuite, we're experiencing a bug with texi2dvi on
> Cygwin that looks like a problem with the
[ this is
http://lists.gnu.org/archive/html/bug-automake/2006-05/msg1.html aka
http://lists.gnu.org/archive/html/bug-texinfo/2006-05/msg00017.html
and the original report is
http://lists.gnu.org/archive/html/bug-automake/2006-04/msg00017.html
]
Hello Cygwin folks,
In the Automake testsuite, w
27 matches
Mail list logo
