On Mon, Dec 7, 2009 at 4:47 PM, Peter Kümmel wrote:
> Am Montag, den 07.12.2009, 09:34 +0100 schrieb Abdelrazak Younes:
>> One "easy solution would
>> be to clone the to-be-compiled Buffer and starts the LateX export and
>> the compilation from a new thread.
>
> This would be the best approach. An
Am Montag, den 07.12.2009, 09:34 +0100 schrieb Abdelrazak Younes:
> > No problem, disabling the changes is simple. How does instant preview
> > work? What means 'instant' in this context? Does it use threads
> >
>
> No, instant preview was already using detached process. The only thing
> speci
Peter Kümmel wrote:
Am Sonntag, den 06.12.2009, 18:53 -0500 schrieb Ben M.:
On Sun, Dec 6, 2009 at 4:43 PM, Peter Kümmel wrote:
Before the patch LyX was single-threaded; means, processing an
user-event, like pressing a button, had to wait until all previewing
is done.
I never h
Am Sonntag, den 06.12.2009, 18:53 -0500 schrieb Ben M.:
> On Sun, Dec 6, 2009 at 4:43 PM, Peter Kümmel wrote:
> > Before the patch LyX was single-threaded; means, processing an
> > user-event, like pressing a button, had to wait until all previewing
> > is done.
>
> I never had to wait for "Insta
On Sun, Dec 6, 2009 at 4:43 PM, Peter Kümmel wrote:
> Before the patch LyX was single-threaded; means, processing an
> user-event, like pressing a button, had to wait until all previewing
> is done.
I never had to wait for "Instant Preview." Is that not classified as
a "user-event"?
>> I have n
Am Sonntag, den 06.12.2009, 12:38 -0500 schrieb Ben M.:
> > Just work as usual with the current version and see if something
> > strange happens. The are may possibilities of bugs, e.g. what happens
> > when you click several times on the preview button?
>
> Could you please summarize the expected
On Sun, Dec 6, 2009 at 1:48 PM, Abdelrazak Younes wrote:
> On 06/12/2009 18:28, Ben M. wrote:
>> I did as you suggested and made testing copies. Also, my documents
>> use the noamssymb.module from Ticket #5058, which doesn't have a
>> "Format" directive. This resulted in a conversion for each do
On 06/12/2009 18:28, Ben M. wrote:
On Sun, Dec 6, 2009 at 5:53 AM, Abdelrazak Younes wrote:
That difference may be due to lyx2lyx conversion. Please save your master
and child docs with trunk and try again.
I did as you suggested and made testing copies. Also, my documents
use the n
On Sun, Dec 6, 2009 at 5:53 AM, Abdelrazak Younes wrote:
> That difference may be due to lyx2lyx conversion. Please save your master
> and child docs with trunk and try again.
I did as you suggested and made testing copies. Also, my documents
use the noamssymb.module from Ticket #5058, which does
On 06/12/2009 01:05, Ben M. wrote:
On Sat, Dec 5, 2009 at 6:21 PM, Pavel Sanda wrote:
isn't it that lyx2lyx runs for 1.6 files - to convert them into 2.0 format
before loading?
saving files in 2.0 would solve it (beware you can't go easily back !:)
I'm happy for now. My files load
On 05/12/2009 20:56, Ben M. wrote:
On Fri, Dec 4, 2009 at 10:23 PM, Vincent van Ravesteijn wrote:
Ben M. schreef:
My computer essentially crashed after exhausting all 3GB of RAM
because of roughly 50 simultaneous latex/python processes to generate
instant previews. I'm all for multit
Ben M. wrote:
> On Sat, Dec 5, 2009 at 4:31 PM, Andre Poenitz wrote:
>> I'd use valgrind --tool=callgrind and kcachegrind for visualization.
>
> Currently I'm equipped for compiling LyX only under cygwin and win32.
> A brief Google search indicates that valgrind doesn't work on these
> platfor
Ben M. wrote:
>
> Back to the original topic... Peter, is there anything I can do to
> test out your patches?
>
Just work as usual with the current version and see if something
strange happens. The are may possibilities of bugs, e.g. what happens
when you click several times on the preview butt
On 12/05/2009 06:16 PM, Ben M. wrote:
2009/12/5 Richard Heck:
On 12/05/2009 05:47 PM, Vincent van Ravesteijn wrote:
We've updated the layout format from 11 (branch) to 19 now (trunk). Each
time when LyX reads a layout file, it converts it to format 19. This is
shown as the creation of
On Sat, Dec 5, 2009 at 6:21 PM, Pavel Sanda wrote:
> isn't it that lyx2lyx runs for 1.6 files - to convert them into 2.0 format
> before loading?
> saving files in 2.0 would solve it (beware you can't go easily back !:)
I'm happy for now. My files load in 8 seconds with 1.6 and 12 seconds
with
Ben M. wrote:
> On Fri, Dec 4, 2009 at 10:23 PM, Vincent van Ravesteijn wrote:
> > Ben M. schreef:
> >> My computer essentially crashed after exhausting all 3GB of RAM
> >> because of roughly 50 simultaneous latex/python processes to generate
> >> instant previews. I'm all for multithreading, but
2009/12/5 Richard Heck:
> On 12/05/2009 05:47 PM, Vincent van Ravesteijn wrote:
>> We've updated the layout format from 11 (branch) to 19 now (trunk). Each
>> time when LyX reads a layout file, it converts it to format 19. This is
>> shown as the creation of all those temporary files in your logfil
On 12/05/2009 05:47 PM, Vincent van Ravesteijn wrote:
But now I run into another problem. (This happened yesterday too.)
When I load my master document (containing 7 children), 1.6.x loads it
in 8 seconds, while trunk takes 45 seconds.
So I do:
lyx-16x -dbg files 2> mastertest-16x.txt
lyx-
But now I run into another problem. (This happened yesterday too.)
When I load my master document (containing 7 children), 1.6.x loads it
in 8 seconds, while trunk takes 45 seconds.
So I do:
lyx-16x -dbg files 2> mastertest-16x.txt
lyx-2 -dbg files 2> mastertest-2.txt
(see attached)
They
On Sat, Dec 5, 2009 at 4:31 PM, Andre Poenitz wrote:
> I'd use valgrind --tool=callgrind and kcachegrind for visualization.
Currently I'm equipped for compiling LyX only under cygwin and win32.
A brief Google search indicates that valgrind doesn't work on these
platforms. :(
My linux server
On Sat, Dec 05, 2009 at 02:56:28PM -0500, Ben M. wrote:
> [...]
> I'd be happy to profile it if someone can explain how. Is the best
> way to recompile with "-pg" and use gprof?
I'd use valgrind --tool=callgrind and kcachegrind for visualization.
Andre'
On Fri, Dec 4, 2009 at 10:23 PM, Vincent van Ravesteijn wrote:
> Ben M. schreef:
>> My computer essentially crashed after exhausting all 3GB of RAM
>> because of roughly 50 simultaneous latex/python processes to generate
>> instant previews. I'm all for multithreading, but this is a bit much!
>
>
Ben M. schreef:
Could you please try your big document with the actual trunk version of Lyx?
Has it become better with the recent changes?
After compiling in Cygwin, I noticed that my file took very long to
load. I tried with Win32 to see if things were faster. No. I soon
discovered wh
> Could you please try your big document with the actual trunk version of Lyx?
> Has it become better with the recent changes?
I only ever use branch, so I have no experience to compare with the
"recent changes."
After compiling in Cygwin, I noticed that my file took very long to
load. I tried
Original-Nachricht
> Datum: Wed, 2 Dec 2009 20:48:04 -0500
> Von: "Ben M."
> An: lyx-devel@lists.lyx.org
> Betreff: Exporting in a separate thread
> Each time I view/export a PDF, LyX freezes for several seconds while
> the document generates.
Ben M. wrote:
Each time I view/export a PDF, LyX freezes for several seconds while
the document generates. This is bug #412.
http://www.lyx.org/trac/ticket/412
Why doesn't LyX simply perform the export in a separate thread instead
of locking the UI?
I'm really surprised that this bug has rem
Each time I view/export a PDF, LyX freezes for several seconds while
the document generates. This is bug #412.
http://www.lyx.org/trac/ticket/412
Why doesn't LyX simply perform the export in a separate thread instead
of locking the UI?
I'm really surprised that this bug has remained open for 8
27 matches
Mail list logo
