Re: Performance regression in export to LaTeX?

Le 20/12/2021 à 12:16, Jürgen Spitzmüller a écrit : Am Montag, dem 20.12.2021 um 10:21 +0100 schrieb Jürgen Spitzmüller: Tried again and (once more) ended up at commit 26ea1e14966c092a7b87c75c19b83a369e79aeb8 Author: Juergen Spitzmueller Date:   Sun Apr 22 19:06:46 2018 +0200     Align

Re: Performance regression in export to LaTeX?

On Mon, Dec 20, 2021 at 12:41:03PM +0100, Kornel Benko wrote: > Am Mon, 20 Dec 2021 12:08:01 +0100 > schrieb Jürgen Spitzmüller : > > > Am Montag, dem 20.12.2021 um 11:19 +0100 schrieb Kornel Benko: > > > Same commit as originally found Scott :) > > > > Which is what the "once more" part

Re: Performance regression in export to LaTeX?

Am Mon, 20 Dec 2021 12:08:01 +0100 schrieb Jürgen Spitzmüller : > Am Montag, dem 20.12.2021 um 11:19 +0100 schrieb Kornel Benko: > > Same commit as originally found Scott :) > > Which is what the "once more" part referred to. I missed it. > > BTW, I am surprised by your time-values. Here the

Re: Performance regression in export to LaTeX?

Am Montag, dem 20.12.2021 um 10:21 +0100 schrieb Jürgen Spitzmüller: > Tried again and (once more) ended up at > > commit 26ea1e14966c092a7b87c75c19b83a369e79aeb8 > Author: Juergen Spitzmueller > Date:   Sun Apr 22 19:06:46 2018 +0200 > >     Align fontenc with document fonts > > I'll check if

Re: Performance regression in export to LaTeX?

Am Montag, dem 20.12.2021 um 11:19 +0100 schrieb Kornel Benko: > Same commit as originally found Scott :) Which is what the "once more" part referred to. > BTW, I am surprised by your time-values. Here the export took 1m 51 > secs before the last > commit, and now I see 57 secs for the export to

Re: Performance regression in export to LaTeX?

Am Mon, 20 Dec 2021 10:21:35 +0100 schrieb Jürgen Spitzmüller : > Am Sonntag, dem 19.12.2021 um 19:08 +0100 schrieb Jürgen Spitzmüller: > > > I can bisect as well. > > > > I gave up. > > Tried again and (once more) ended up at > > commit 26ea1e14966c092a7b87c75c19b83a369e79aeb8 > Author:

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 19:08 +0100 schrieb Jürgen Spitzmüller: > > I can bisect as well. > > I gave up. Tried again and (once more) ended up at commit 26ea1e14966c092a7b87c75c19b83a369e79aeb8 Author: Juergen Spitzmueller Date: Sun Apr 22 19:06:46 2018 +0200 Align fontenc with

Re: Performance regression in export to LaTeX?

Le 19/12/2021 à 15:45, Jürgen Spitzmüller a écrit : Am Sonntag, dem 19.12.2021 um 15:03 +0100 schrieb Jürgen Spitzmüller: So it's the cprotection checks that seem to cost time. Need to check whether this can be optimized. After 61b8afd893ec we're back at real0m19,685s user0m15,633s

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 19:21 + schrieb José Abílio Matos: > If this proves to be a problem we can speed lyx2lyx code (using > profiling to identify the bottlenecks). No, this doesn't seem to be involved. Jürgen signature.asc Description: This is a digitally signed message part --

Re: Performance regression in export to LaTeX?

On Sunday, 19 December 2021 17.15.19 WET Jürgen Spitzmüller wrote: > The first thing to check, since this is a 2.3.x file, is how much time > is taken by lyx2lyx. If this proves to be a problem we can speed lyx2lyx code (using profiling to identify the bottlenecks). -- José Abílio--

Re: Performance regression in export to LaTeX?

Le 19/12/2021 à 19:22, Scott Kostyshak a écrit : On Sun, Dec 19, 2021 at 07:08:56PM +0100, Jürgen Spitzmüller wrote: Am Sonntag, dem 19.12.2021 um 18:15 +0100 schrieb Jürgen Spitzmüller: I can bisect as well. I gave up. I'll give it a try. Might not be able to do it until tomorrow though.

Re: Performance regression in export to LaTeX?

On Sun, Dec 19, 2021 at 07:08:56PM +0100, Jürgen Spitzmüller wrote: > Am Sonntag, dem 19.12.2021 um 18:15 +0100 schrieb Jürgen Spitzmüller: > > I can bisect as well. > > I gave up. I'll give it a try. Might not be able to do it until tomorrow though. Scott signature.asc Description: PGP

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 18:15 +0100 schrieb Jürgen Spitzmüller: > I can bisect as well. I gave up. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 11:55 -0500 schrieb Scott Kostyshak: > I can try to do another bisect if there's interest. I'm just not sure > this is something even related to a use case. I guess the first thing > to check would be if indeed the issue only shows up with a very long > line. The

Re: Performance regression in export to LaTeX?

On Sun, Dec 19, 2021 at 05:39:16PM +0100, Jürgen Spitzmüller wrote: > Am Sonntag, dem 19.12.2021 um 11:37 -0500 schrieb Scott Kostyshak: > > Thanks for checking. Indeed I think my computer has some performance > > issues (especially with I/O, which I think is relevant in this case). > > > > And

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 11:37 -0500 schrieb Scott Kostyshak: > Thanks for checking. Indeed I think my computer has some performance > issues (especially with I/O, which I think is relevant in this case). > > And what do you get with 2.3.0? real0m1,108s user0m1,077s sys 0m0,031s

Re: Performance regression in export to LaTeX?

On Sun, Dec 19, 2021 at 05:29:07PM +0100, Jürgen Spitzmüller wrote: > Am Sonntag, dem 19.12.2021 um 17:24 +0100 schrieb Jürgen Spitzmüller: > > Though I am getting > > > > real0m5,935s > > user0m5,739s > > sys 0m0,066s > > > > With this on master (with -e pdflatex). > > (i.e.,

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 17:24 +0100 schrieb Jürgen Spitzmüller: > Though I am getting > > real 0m5,935s > user 0m5,739s > sys 0m0,066s > > With this on master (with -e pdflatex). (i.e., with your testfile) Jürgen signature.asc Description: This is a digitally signed message part

Re: Performance regression in export to LaTeX?

>   time mylyx 2.3.x -e pdflatex UserGuide.lyx > > The format "pdflatex" is the shortname for "LaTeX (pdflatex)", where > pdf2 is the shortname for "PDF (pdflatex)". i.e., I'm checking just > LyX's LaTeX export without compiling. You're right. Th

Re: Performance regression in export to LaTeX?

n master (with your recent fix), I get times like the following: real 0m44.676s user 0m44.575s sys 0m0.092s I'm still using the following command when testing: time mylyx 2.3.x -e pdflatex UserGuide.lyx The format "pdflatex" is the shortname for "LaTeX (pdflatex)",

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 15:03 +0100 schrieb Jürgen Spitzmüller: > So it's the cprotection checks that seem to cost time. Need to check > whether this can be optimized. After 61b8afd893ec we're back at real0m19,685s user0m15,633s sys 0m3,025s Which is still a bit slower than

Re: Performance regression in export to LaTeX?

Am Sonntag, dem 19.12.2021 um 11:45 +0100 schrieb Jürgen Spitzmüller: > I try to bisect myself. This leads to: commit b814c4fda732c8b5ee019692eb881c35b9335da6 Author: Juergen Spitzmueller Date: Sun Sep 20 08:45:42 2020 +0200 Fix unnecessary cprotect Note, however, that this is not

Re: Performance regression in export to LaTeX?

Am Samstag, dem 18.12.2021 um 13:26 -0500 schrieb Scott Kostyshak: > Thanks, Jean-Pierre. I wonder why you must export to pdf2. Using > "pdflatex" instead gives an error? Because -e takes a file format as argument, and the file format for pdflatex output is pdf2, not pdflatex. > > In any case,

Re: Performance regression in export to LaTeX?

On Sat, Dec 18, 2021 at 12:01:36PM +0100, Jean-Pierre Chrétien wrote: > Le 18/12/2021 à 03:23, Scott Kostyshak a écrit : > > If I do > > > >time lyx -e pdflatex UserGuide.lyx > > > > I get big differences in timings if I do the above with master versus > > with 2.3.0. I'm not sure these

Re: Performance regression in export to LaTeX?

Le 18/12/2021 à 03:23, Scott Kostyshak a écrit : If I do time lyx -e pdflatex UserGuide.lyx I get big differences in timings if I do the above with master versus with 2.3.0. I'm not sure these differences necessarily mean a regression. I've definitely compiled master with different compile

Performance regression in export to LaTeX?

If I do time lyx -e pdflatex UserGuide.lyx I get big differences in timings if I do the above with master versus with 2.3.0. I'm not sure these differences necessarily mean a regression. I've definitely compiled master with different compile flags. Does anyone else see differences when

Re: Math.lyx export to latex

On 2015-03-31, Kornel Benko wrote: What is a good name for the subdir? Similar to the behaviour of web browsers when downloading HTML+images, I'd name it document-name-without-extension-files/ i.e. for math.tex it would becomd math-files/ What do we do if it already exists? Add a number

Re: Math.lyx export to latex

On Wed, Apr 1, 2015 at 4:56 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Guenter Milde wrote: On 2015-03-31, Kornel Benko wrote: What is a good name for the subdir? Similar to the behaviour of web browsers when downloading HTML+images, I'd name it

Re: Math.lyx export to latex

anything. The most probable reason for this is that the current LaTeX export is not the first one that the user did from this document. Asking would be consistent with what is done already for the main document, adding a number is not really wanted, since several exports in a row would produce

Re: Math.lyx export to latex

On 2015-03-31, Kornel Benko wrote: > What is a good name for the subdir? Similar to the behaviour of web browsers when downloading HTML+images, I'd name it "-files/" i.e. for "math.tex" it would becomd "math-files/" > What do we do if it already exists? Add a number or ask. Günter

Re: Math.lyx export to latex

he fact that the directory does already exist does not mean anything. The most probable reason for this is that the current LaTeX export is not the first one that the user did from this document. Asking would be consistent with what is done already for the main document, adding a number is not really w

Re: Math.lyx export to latex

On Wed, Apr 1, 2015 at 4:56 PM, Georg Baum wrote: > Guenter Milde wrote: > >> On 2015-03-31, Kornel Benko wrote: >> >> >>> What is a good name for the subdir? >> >> Similar to the behaviour of web browsers when downloading HTML+images, I'd >> name it "-files/" i.e.

Re: Math.lyx export to latex

-source}/lib/doc/Math.lyx to a local directory, say ~/lyx/test/. This is not needed, but shows that the behaviour does not depend on the path of Math.lyx 2.) use your lyx from the build directory to open the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source

Re: Math.lyx export to latex

On Tue, Mar 31, 2015 at 09:04:41AM +0200, Kornel Benko wrote: Am Montag, 30. März 2015 um 20:26:04, schrieb Scott Kostyshak skost...@lyx.org It seems there is an enhancement that we can do. For example, we could have a user-friendly dialog about not having write permissions to the

Re: Math.lyx export to latex

Am Dienstag, 31. März 2015 um 11:02:45, schrieb Enrico Forestieri for...@lyx.org On Tue, Mar 31, 2015 at 09:04:41AM +0200, Kornel Benko wrote: Am Montag, 30. März 2015 um 20:26:04, schrieb Scott Kostyshak skost...@lyx.org It seems there is an enhancement that we can do. For example,

Re: Math.lyx export to latex

On Tue, Mar 31, 2015 at 5:36 AM, Kornel Benko kor...@lyx.org wrote: Am Dienstag, 31. März 2015 um 11:02:45, schrieb Enrico Forestieri for...@lyx.org On Tue, Mar 31, 2015 at 09:04:41AM +0200, Kornel Benko wrote: Am Montag, 30. März 2015 um 20:26:04, schrieb Scott Kostyshak skost...@lyx.org

Re: Math.lyx export to latex

Am Dienstag, 31. März 2015 um 10:31:18, schrieb Scott Kostyshak skost...@lyx.org On Tue, Mar 31, 2015 at 5:36 AM, Kornel Benko kor...@lyx.org wrote: Am Dienstag, 31. März 2015 um 11:02:45, schrieb Enrico Forestieri for...@lyx.org On Tue, Mar 31, 2015 at 09:04:41AM +0200, Kornel Benko

Re: Math.lyx export to latex

erve creation of files in lyx-source > >> > >> 1.) copy {lyx-source}/lib/doc/Math.lyx to a local directory, say > >> ~/lyx/test/. > >> This is not needed, but shows that the behaviour does not depend on > >> the path of Math.lyx > >&g

Re: Math.lyx export to latex

On Tue, Mar 31, 2015 at 09:04:41AM +0200, Kornel Benko wrote: > Am Montag, 30. März 2015 um 20:26:04, schrieb Scott Kostyshak > > > > It seems there is an enhancement that we can do. For example, we could > > have a user-friendly dialog about not having write permissions to

Re: Math.lyx export to latex

Am Dienstag, 31. März 2015 um 11:02:45, schrieb Enrico Forestieri > On Tue, Mar 31, 2015 at 09:04:41AM +0200, Kornel Benko wrote: > > Am Montag, 30. März 2015 um 20:26:04, schrieb Scott Kostyshak > > > > > > > It seems there is an enhancement that we can do.

Re: Math.lyx export to latex

On Tue, Mar 31, 2015 at 5:36 AM, Kornel Benko wrote: > Am Dienstag, 31. März 2015 um 11:02:45, schrieb Enrico Forestieri > >> On Tue, Mar 31, 2015 at 09:04:41AM +0200, Kornel Benko wrote: >> > Am Montag, 30. März 2015 um 20:26:04, schrieb Scott Kostyshak >> >

Re: Math.lyx export to latex

Am Dienstag, 31. März 2015 um 10:31:18, schrieb Scott Kostyshak > On Tue, Mar 31, 2015 at 5:36 AM, Kornel Benko wrote: > > Am Dienstag, 31. März 2015 um 11:02:45, schrieb Enrico Forestieri > > > >> On Tue, Mar 31, 2015 at 09:04:41AM +0200,

Re: Math.lyx export to latex

on the path of Math.lyx 2.) use your lyx from the build directory to open the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy-param.pdf Second scenario with installed lyx

Re: Math.lyx export to latex

on the path of Math.lyx 2.) use your lyx from the build directory to open the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy-param.pdf Second scenario with installed lyx. Make sure

Re: Math.lyx export to latex

to open the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy-param.pdf Are you sure that the correct file is opened? Maybe some black magic for special handling of our own docs goes

Re: Math.lyx export to latex

Kornel Benko wrote: Am Montag, 30. März 2015 um 22:23:38, schrieb Georg Baum georg.b...@post.rwth-aachen.de Unfortunately I don't have time to investigate now, but I'd guess that neither Exporter.cpp nor TempFile is the culprit. It is normal for the conversion process to use temporary files.

Re: Math.lyx export to latex

Am Montag, 30. März 2015 um 22:52:20, schrieb Georg Baum georg.b...@post.rwth-aachen.de Kornel Benko wrote: Am Montag, 30. März 2015 um 22:23:38, schrieb Georg Baum georg.b...@post.rwth-aachen.de Unfortunately I don't have time to investigate now, but I'd guess that neither

Re: Math.lyx export to latex

that the behaviour does not depend on the path of Math.lyx 2.) use your lyx from the build directory to open the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy-param.pdf Are you sure

Re: Math.lyx export to latex

of Math.lyx 2.) use your lyx from the build directory to open the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy-param.pdf I think this is the expected behavior. When you export

Re: Math.lyx export to latex

/. This is not needed, but shows that the behaviour does not depend on the path of Math.lyx 2.) use your lyx from the build directory to open the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy

Re: Math.lyx export to latex

ur does not depend on > the path of Math.lyx > 2.) use your lyx from the build directory to open the file > 3.) File->Export->LaTeX(LuaLaTeX) > > Now go to the lyx-source > # git status > > You see many untracked .pdf files like e.g. > lib/images/math

Re: Math.lyx export to latex

ieb Kornel Benko <kor...@lyx.org> > > This is a recipe to observe creation of files in lyx-source > > > > 1.) copy {lyx-source}/lib/doc/Math.lyx to a local directory, say > > ~/lyx/test/. > > This is not needed, but shows that the behaviour does not depend on > >

Re: Math.lyx export to latex

lyx from the build directory to open the file > 3.) File->Export->LaTeX(LuaLaTeX) > > Now go to the lyx-source > # git status > > You see many untracked .pdf files like e.g. > lib/images/math-macro-remove-greedy-param.pdf Are you sure that the correct file is opened? Maybe

Re: Math.lyx export to latex

test/. This is not needed, but shows that the behaviour does not > > depend on the path of Math.lyx > > 2.) use your lyx from the build directory to open the file > > 3.) File->Export->LaTeX(LuaLaTeX) > > > > Now go to the lyx-source > > # git status > &

Re: Math.lyx export to latex

Kornel Benko wrote: > Am Montag, 30. März 2015 um 22:23:38, schrieb Georg Baum > >> Unfortunately I don't have time to investigate now, but I'd guess that >> neither Exporter.cpp nor TempFile is the culprit. It is normal for the >> conversion process to use

Re: Math.lyx export to latex

Am Montag, 30. März 2015 um 22:52:20, schrieb Georg Baum > Kornel Benko wrote: > > > Am Montag, 30. März 2015 um 22:23:38, schrieb Georg Baum > > > >> Unfortunately I don't have time to investigate now, but I'd guess that > >>

Re: Math.lyx export to latex

s not depend on > the path of Math.lyx > 2.) use your lyx from the build directory to open the file > 3.) File->Export->LaTeX(LuaLaTeX) > > Now go to the lyx-source > # git status > > You see many untracked .pdf files like e.g. > lib/images/math-macro-remove-greedy-param.pdf

Re: Math.lyx export to latex

ocal directory, say ~/lyx/test/. >> This is not needed, but shows that the behaviour does not depend on >> the path of Math.lyx >> 2.) use your lyx from the build directory to open the file >> 3.) File->Export->LaTeX(LuaLaTeX) >> >> Now go to the lyx-source &

Math.lyx export to latex

the file 3.) File-Export-LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy-param.pdf Second scenario with installed lyx. Make sure, the lyx system dirs are not writeable by you 2.) open the file 3.) try the export

Math.lyx export to latex

the file 3.) File->Export->LaTeX(LuaLaTeX) Now go to the lyx-source # git status You see many untracked .pdf files like e.g. lib/images/math-macro-remove-greedy-param.pdf Second scenario with installed lyx. Make sure, the lyx system dirs are not writeable by you 2.) open the file 3

Re: Export to Latex and Overwriting Included Images

, it is impossible to export to latex(plain) without overwriting the existing EPS version with a new version (created by ghostscript). There is a warning at least, but still it means no export without data loss in the existing EPS file. The warning dialogue only allows overwrite, overwrite all

Re: Export to Latex and Overwriting Included Images

is included as image, it is impossible to export to latex(plain) without overwriting the existing EPS version with a new version (created by ghostscript). There is a warning at least, but still it means no export without data loss in the existing EPS file. The warning dialogue only allows

Re: no way to export as latex

abdelkader belahcene wrote: thanks for reply, I want to generate the latex file from the lyx file, this option existed in the previous release; file---export ---latex, like file--export---pdf , html and other This option does exist in 1.5.beta1. At least, it does in my copy. There are two

Re: no way to export as latex

abdelkader belahcene wrote: > thanks for reply, > I want to generate the latex file from the lyx file, this option > existed in the previous release; file--->export --->latex, like > file-->export--->pdf , html and other This option does exist in 1.5.beta1. At l

Re: [Fwd: export to latex]

On Fri, Oct 27, 2006 at 11:05:51AM +0200, Edwin Leuven wrote: sometime ago i wrote: Original Message Subject: export to latex Date: Tue, 02 May 2006 20:53:01 +0200 From: Edwin Leuven [EMAIL PROTECTED] To: LyX Developers lyx-devel@lists.lyx.org an old annoyance of mine

Re: [Fwd: export to latex]

Andre Poenitz schrieb: On Fri, Oct 27, 2006 at 11:05:51AM +0200, Edwin Leuven wrote: sometime ago i wrote: Original Message Subject: export to latex Date: Tue, 02 May 2006 20:53:01 +0200 From: Edwin Leuven [EMAIL PROTECTED] To: LyX Developers lyx-devel@lists.lyx.org

Re: [Fwd: export to latex]

On Fri, Oct 27, 2006 at 11:05:51AM +0200, Edwin Leuven wrote: > sometime ago i wrote: > > Original Message > Subject: export to latex > Date: Tue, 02 May 2006 20:53:01 +0200 > From: Edwin Leuven <[EMAIL PROTECTED]> > To: LyX Developers <lyx-de

Re: [Fwd: export to latex]

Andre Poenitz schrieb: > On Fri, Oct 27, 2006 at 11:05:51AM +0200, Edwin Leuven wrote: >> sometime ago i wrote: >> >> Original Message ---- >> Subject: export to latex >> Date: Tue, 02 May 2006 20:53:01 +0200 >> From: Edwin Leuven <[EMAIL PR

[Fwd: export to latex]

sometime ago i wrote: Original Message Subject: export to latex Date: Tue, 02 May 2006 20:53:01 +0200 From: Edwin Leuven [EMAIL PROTECTED] To: LyX Developers lyx-devel@lists.lyx.org an old annoyance of mine is the following: when exporting to latex, each cell of a table

Re: [Fwd: export to latex]

Edwin == Edwin Leuven [EMAIL PROTECTED] writes: Edwin sometime ago i wrote: Original Message Edwin Subject: export to latex Date: Tue, 02 May 2006 20:53:01 +0200 Edwin From: Edwin Leuven [EMAIL PROTECTED] To: LyX Developers Edwin lyx-devel@lists.lyx.org Edwin an old annoyance

Re: [Fwd: export to latex]

Jean-Marc Lasgouttes wrote: The patch is wrong. If you do not add a \n, you should not increase ret, which counts lines. thanks, update attached Other that that, I am not against such a patch. But of course, people who use large tables will not be happy either. It is a bit difficult to

Re: [Fwd: export to latex]

Edwin Leuven wrote: will commit soon... it's in

[Fwd: export to latex]

sometime ago i wrote: Original Message Subject: export to latex Date: Tue, 02 May 2006 20:53:01 +0200 From: Edwin Leuven <[EMAIL PROTECTED]> To: LyX Developers <lyx-devel@lists.lyx.org> an old annoyance of mine is the following: when exporting to latex, each cel

Re: [Fwd: export to latex]

>>>>> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes: Edwin> sometime ago i wrote: Original Message ---- Edwin> Subject: export to latex Date: Tue, 02 May 2006 20:53:01 +0200 Edwin> From: Edwin Leuven <[EMAIL PROTECTED]> To: LyX Deve

Re: [Fwd: export to latex]

Jean-Marc Lasgouttes wrote: The patch is wrong. If you do not add a \n, you should not increase "ret", which counts lines. thanks, update attached Other that that, I am not against such a patch. But of course, people who use large tables will not be happy either. It is a bit difficult to

Re: [Fwd: export to latex]

Edwin Leuven wrote: will commit soon... it's in

UTF-8 export to LaTeX works

Hi, I just committed a few fixes to get UTF-8 latex export working. Regards, Asger Index: bufferparams.C === --- bufferparams.C (revision 15381) +++ bufferparams.C (working copy) @@ -839,26 +839,32

UTF-8 export to LaTeX works

Hi, I just committed a few fixes to get UTF-8 latex export working. Regards, Asger Index: bufferparams.C === --- bufferparams.C (revision 15381) +++ bufferparams.C (working copy) @@ -839,26 +839,32

Re: 1.4.2svn crash with view-postscript/dvi (export to latex?)

Am Donnerstag, 25. Mai 2006 05:28 schrieb Bo Peng: if (lyx::support::rename(temp_file, new_file)) { temp_file = new_file; output_file = ChangeExtension(output_file, ext);

Re: 1.4.2svn crash with view->postscript/dvi (export to latex?)

Am Donnerstag, 25. Mai 2006 05:28 schrieb Bo Peng: > if (lyx::support::rename(temp_file, new_file)) { > temp_file = new_file; > output_file = ChangeExtension(output_file, ext); >

1.4.2svn crash with view-postscript/dvi (export to latex?)

Dear list, lyx 1.4.2 cvs crashes when I try to view a file with eps figure. Here is the gdb trace: Assertion triggered in void ExportData::addExternalFile(const std::string, const std::string, const std::string) by failing check lyx::support::AbsolutePath(sourceName) in file exporter.C:322

Re: 1.4.2svn crash with view-postscript/dvi (export to latex?)

The problem is at line 683, insetgraphics.C // source file is now full path /tmp/lyx_tmpdir20237FyBZGA/lyx_tmpbuf0/4_home_bpeng_simuPOP_doc_log_LDdecay.eps if (!runparams.nice GetExtension(temp_file) != ext) { // The LaTeX compiler will not be able to

1.4.2svn crash with view->postscript/dvi (export to latex?)

Dear list, lyx 1.4.2 cvs crashes when I try to view a file with eps figure. Here is the gdb trace: Assertion triggered in void ExportData::addExternalFile(const std::string&, const std::string&, const std::string&) by failing check "lyx::support::AbsolutePath(sourceName)" in file exporter.C:322

Re: 1.4.2svn crash with view->postscript/dvi (export to latex?)

The problem is at line 683, insetgraphics.C // source file is now full path /tmp/lyx_tmpdir20237FyBZGA/lyx_tmpbuf0/4_home_bpeng_simuPOP_doc_log_LDdecay.eps if (!runparams.nice && GetExtension(temp_file) != ext) { // The LaTeX compiler will not be able to

Re: export to latex

Edwin == Edwin Leuven [EMAIL PROTECTED] writes: Edwin an old annoyance of mine is the following: when exporting to Edwin latex, each cell of a table is on its own line. Edwin with the attached each row is on its own line which i find much Edwin better. What would be good is to insert a \n only

Re: export to latex

> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes: Edwin> an old annoyance of mine is the following: when exporting to Edwin> latex, each cell of a table is on its own line. Edwin> with the attached each row is on its own line which i find much Edwin> better. What would be good is to

export to latex

an old annoyance of mine is the following: when exporting to latex, each cell of a table is on its own line. with the attached each row is on its own line which i find much better. opinions (flames)? thanks, ed. Index: src/tabular.C

export to latex

an old annoyance of mine is the following: when exporting to latex, each cell of a table is on its own line. with the attached each row is on its own line which i find much better. opinions (flames)? thanks, ed. Index: src/tabular.C

diff between 'view postscript' and 'export to latex'

If I try to 'view postscript', I get some error. To see probably goes wrong, I dived into /tmp/lyx_tmpdir22544Ij6u7P/lyx_tmpbuf0 - I guess the directory where the temporary files are copied into. Running LaTeX there, I get the same error as from within lyx: ! Font U/AnnSton/xl/n/24.88=AnnSton at

diff between 'view postscript' and 'export to latex'

If I try to 'view postscript', I get some error. To see probably goes wrong, I dived into /tmp/lyx_tmpdir22544Ij6u7P/lyx_tmpbuf0 - I guess the directory where the temporary files are copied into. Running LaTeX there, I get the same error as from within lyx: ! Font U/AnnSton/xl/n/24.88=AnnSton at

Re: [Patch] RFQ: ParagraphList Rewrite (possible hidden bug in export to latex)

Hello, For those interested, here is a second version of the it_vector class. With former one an assertion is triggered whenever you try to export to latex. It seems that the at() method is used beyond the size() limit. I am really not sure but there is maybe a hidden bug somewhere

Re: [Patch] RFQ: ParagraphList Rewrite (possible hidden bug in export to latex)

Hello, For those interested, here is a second version of the it_vector class. With former one an assertion is triggered whenever you try to export to latex. It seems that the at() method is used beyond the size() limit. I am really not sure but there is maybe a hidden bug somewhere

LyX export to latex broken

This smacks of Boost.Filesystem breakage. qlyxcvs is a symbolic link pointing at ~/lyx/devel/build/src/lyx-qt $ qlyxcvs -e latex UserGuide_13x.lyx LyXTextClassList::Read: unable to find textclass file `'. Exiting. $ ~/lyx/devel/build/src/lyx-qt -e latex UserGuide_13x.lyx creating local macro

Re: LyX export to latex broken

Angus Leeming wrote: This smacks of Boost.Filesystem breakage. qlyxcvs is a symbolic link pointing at ~/lyx/devel/build/src/lyx-qt $ qlyxcvs -e latex UserGuide_13x.lyx LyXTextClassList::Read: unable to find textclass file `'. Exiting. This was my bad. I had a ~/lib/lyxrc.defaults file left

LyX export to latex broken

This smacks of Boost.Filesystem breakage. qlyxcvs is a symbolic link pointing at ~/lyx/devel/build/src/lyx-qt $ qlyxcvs -e latex UserGuide_13x.lyx LyXTextClassList::Read: unable to find textclass file `'. Exiting. $ ~/lyx/devel/build/src/lyx-qt -e latex UserGuide_13x.lyx creating local macro

Re: LyX export to latex broken

Angus Leeming wrote: > This smacks of Boost.Filesystem breakage. > qlyxcvs is a symbolic link pointing at ~/lyx/devel/build/src/lyx-qt > $ qlyxcvs -e latex UserGuide_13x.lyx > LyXTextClassList::Read: unable to find textclass file `'. Exiting. This was my bad. I had a ~/lib/lyxrc.defaults file

Re: command to export to latex ?

On Tue, Feb 19, 2002 at 07:43:30PM +0100, Toni Moreno Giménez wrote: I'm automatizing documentacion creation and web updating process, by using bash scripting ,from LyX based documents, but I need a command to export *.lyx to *.tex . without needed of use the LyX GUI. You can use -i and -e

Re: command to export to latex ?

On Tue, Feb 19, 2002 at 07:43:30PM +0100, Toni Moreno Giménez wrote: > I'm automatizing documentacion creation and web updating process, by using > bash scripting ,from LyX based documents, but I need a command to export > *.lyx to *.tex . without needed of use the LyX GUI. You can use -i and

command to export to latex ?

Hay , Im not subscribed to the list, please , send me directly to me, your answers , thanks. I'm automatizing documentacion creation and web updating process, by using bash scripting ,from LyX based documents, but I need a command to export *.lyx to *.tex . without needed of use the LyX GUI.

Re: command to export to latex ?

On 19 February 2002 21:43, Toni Moreno Giménez wrote: Hay , Im not subscribed to the list, please , send me directly to me, your answers , thanks. I'm automatizing documentacion creation and web updating process, by using bash scripting ,from LyX based documents, but I need a command to

  1   2   >