On 3/31/2012 11:26 AM, Ken Brown wrote:
On 3/31/2012 6:28 AM, Jon TURNEY wrote:
On 30/03/2012 12:36, Jon TURNEY wrote:
On 29/03/2012 20:59, Ken Brown wrote:
On 3/29/2012 8:14 AM, Jon TURNEY wrote:
Not so good :-(. Thanks for testing it, anyway.
I found a rather bad crash bug I'd introduced
On Mon, Apr 2, 2012 at 6:04 AM, Ken Brown wrote:
This was apparently a cygwin1.dll problem. I've installed the 2012-04-01
cygwin1.dll
snapshot, and XWin.20120329-git-6d4583d53c249549.exe starts again. I've
resumed testing texworks.
I had a similar experience. I could not get xterms to
On 4/2/2012 8:04 AM, Ken Brown wrote:
On 3/31/2012 11:26 AM, Ken Brown wrote:
On 3/31/2012 6:28 AM, Jon TURNEY wrote:
On 30/03/2012 12:36, Jon TURNEY wrote:
On 29/03/2012 20:59, Ken Brown wrote:
On 3/29/2012 8:14 AM, Jon TURNEY wrote:
Not so good :-(. Thanks for testing it, anyway.
I
On 2012-04-02 16:14, Ken Brown wrote:
Much earlier in the thread I mentioned a warning QFileSystemWatcher:
failed to add paths: /home/kbrown. I've looked at the QtCore sources,
and that warning is generated by the function
QFileSystemWatcher::addPaths, in corelib/io/qfilesystemwatcher.cpp. If
On Sat, Mar 31, 2012 at 9:26 AM, Ken Brown wrote:
I wanted to do some further tests, but I thought I should install the latest
Cygwin snapshot (2012-03-30) first. With that Cygwin snapshot, the XWin
snapshot of 20120329 won't start.
It's not quite right here either. Xwin starts up OK, but I
On 01/04/2012 07:07, Jim Reisert AD1C wrote:
On Sat, Mar 31, 2012 at 9:26 AM, Ken Brown wrote:
I wanted to do some further tests, but I thought I should install the latest
Cygwin snapshot (2012-03-30) first. With that Cygwin snapshot, the XWin
snapshot of 20120329 won't start.
It's not
On 31/03/2012 11:28, Jon TURNEY wrote:
On 30/03/2012 12:36, Jon TURNEY wrote:
For me, the problem of texworks hanging only occurs very intermittently. It
seems to be blocked deep in QtCore, waiting for the spawned process to
terminate (which has already happened).
Attaching to the texworks
On 30/03/2012 12:36, Jon TURNEY wrote:
On 29/03/2012 20:59, Ken Brown wrote:
On 3/29/2012 8:14 AM, Jon TURNEY wrote:
Not so good :-(. Thanks for testing it, anyway.
I found a rather bad crash bug I'd introduced and fixed that, so you might
want to try today's snapshot [1], but I'm not
On 3/31/2012 6:28 AM, Jon TURNEY wrote:
On 30/03/2012 12:36, Jon TURNEY wrote:
On 29/03/2012 20:59, Ken Brown wrote:
On 3/29/2012 8:14 AM, Jon TURNEY wrote:
Not so good :-(. Thanks for testing it, anyway.
I found a rather bad crash bug I'd introduced and fixed that, so you might
want to
On 29/03/2012 20:59, Ken Brown wrote:
On 3/29/2012 8:14 AM, Jon TURNEY wrote:
Not so good :-(. Thanks for testing it, anyway.
I found a rather bad crash bug I'd introduced and fixed that, so you might
want to try today's snapshot [1], but I'm not confident that I fixed the
problem you saw,
On 28/03/2012 13:44, Ken Brown wrote:
On 3/28/2012 8:28 AM, Ken Brown wrote:
On 3/28/2012 7:16 AM, Jon TURNEY wrote:
I'm afraid I can't reproduce your issue, but looking at the backtrace
and the
somewhat intermittent nature of the fault, I think perhaps this crash is
caused by a race
On 3/29/2012 8:14 AM, Jon TURNEY wrote:
On 28/03/2012 13:44, Ken Brown wrote:
On 3/28/2012 8:28 AM, Ken Brown wrote:
On 3/28/2012 7:16 AM, Jon TURNEY wrote:
I'm afraid I can't reproduce your issue, but looking at the backtrace
and the
somewhat intermittent nature of the fault, I think perhaps
On 2012-03-29 14:59, Ken Brown wrote:
OK, I'm running it now and have attached gdb to it. The good news is
that I've been running it for a couple hours with no crash, and I've
used texworks and have opened many tex files and pdf files in it without
a problem. The bad news is that texworks
On 3/29/2012 4:20 PM, Yaakov (Cygwin/X) wrote:
On 2012-03-29 14:59, Ken Brown wrote:
OK, I'm running it now and have attached gdb to it. The good news is
that I've been running it for a couple hours with no crash, and I've
used texworks and have opened many tex files and pdf files in it without
On 2012-03-24 14:47, Ken Brown wrote:
1. Install texworks-0.4.3-1 from Cygwin Ports.
2. Create two tex files in your home directory, say test1.tex and
test2.tex. I don't know if the contents matter, but in my case both
files contain the following:
\documentclass{article}
\begin{document}
Hello
On 26/03/2012 21:32, Ken Brown wrote:
On 3/26/2012 4:06 PM, Jon TURNEY wrote:
On 26/03/2012 20:47, Ken Brown wrote:
On 3/24/2012 3:47 PM, Ken Brown wrote:
One further detail for anyone trying to reproduce this: I just tried it on
a
second computer, and my recipe didn't immediately produce
On 3/28/2012 7:16 AM, Jon TURNEY wrote:
On 26/03/2012 21:32, Ken Brown wrote:
On 3/26/2012 4:06 PM, Jon TURNEY wrote:
On 26/03/2012 20:47, Ken Brown wrote:
On 3/24/2012 3:47 PM, Ken Brown wrote:
One further detail for anyone trying to reproduce this: I just tried it on a
second computer,
On 3/24/2012 3:47 PM, Ken Brown wrote:
To reproduce:
1. Install texworks-0.4.3-1 from Cygwin Ports.
2. Create two tex files in your home directory, say test1.tex and
test2.tex. I don't know if the contents matter, but in my case both
files contain the following:
\documentclass{article}
On 26/03/2012 20:47, Ken Brown wrote:
On 3/24/2012 3:47 PM, Ken Brown wrote:
To reproduce:
1. Install texworks-0.4.3-1 from Cygwin Ports.
2. Create two tex files in your home directory, say test1.tex and
test2.tex. I don't know if the contents matter, but in my case both
files contain the
On 3/26/2012 4:06 PM, Jon TURNEY wrote:
On 26/03/2012 20:47, Ken Brown wrote:
On 3/24/2012 3:47 PM, Ken Brown wrote:
To reproduce:
1. Install texworks-0.4.3-1 from Cygwin Ports.
2. Create two tex files in your home directory, say test1.tex and
test2.tex. I don't know if the contents matter,
20 matches
Mail list logo
