Re: Strategies for locating errors
> Will Furnass wrote: >> >> If would be great if LyX would switch to/open the child document >> containing the likely location of the error and move the cursor to that >> location. Ticket filed: http://www.lyx.org/trac/ticket/9539
Re: Strategies for locating errors
Will Furnass wrote: > On 5 May 2015 at 21:38, Georg Baum wrote: > >> >> If you select the error item in the error dialog then the corresponding >> LyX contents should should be selected in the main area as well. This is >> not always 100% correct, but usually the error cause is nearby. Does this >> not work in your case? >> > > Ah, I hadn't noticed that before! That works perfectly if the error is in > the master document but not if the error is in a child document (of which > I have quite a few). > > If would be great if LyX would switch to/open the child document > containing the likely location of the error and move the cursor to that > location. I agree. Please file an enhancement request at http://www.lyx.org/trac/wiki/BugTrackerHome. It should not be too difficult to implement, since LyX has all information which is needed (which file and which line number). I guess it was simply forgotten. Georg
Re: Strategies for locating errors
On 06/05/15 09:57, Will Furnass wrote: That works perfectly if the error is in the master document but not if the error is in a child document (of which I have quite a few). I have been having similar problems with errors, mainly relating to producing printable pdf versions of a Software User Manual that has fairly frequent updates and changes. This manual is a team effort written with Lyx with an on-line HTML version being the primary release format. The HTML does not show some Latex errors but they do appear when a pdf conversion is attempted, and my team task is to deal with the pdfs. Error reports give a line number, which has been difficult to translate into a location in the Lyx file. However, I'm now experimenting with the Latex Editor, Texmaker. It appears to happily present the Lyx files, all with line numbers. Perhaps this will help my error finding, we can but see. Gordon Tauranga New Zealand.
Re: Strategies for locating errors
On 5 May 2015 at 21:38, Georg Baum wrote: > > If you select the error item in the error dialog then the corresponding LyX > contents should should be selected in the main area as well. This is not > always 100% correct, but usually the error cause is nearby. Does this not > work in your case? > Ah, I hadn't noticed that before! That works perfectly if the error is in the master document but not if the error is in a child document (of which I have quite a few). If would be great if LyX would switch to/open the child document containing the likely location of the error and move the cursor to that location. Will
Re: Strategies for locating errors
Will Furnass wrote: > How do others locate compilation errors in large multi-file documents? > > I get a 'Missing } inserted' error for 'l.1052' when compiling but can't > relate that line number to the LyX source. I then try exporting to tex > using pdflatex into a temporary directory and search through all 16 tex > files looking for errors on or near line 1052. If you select the error item in the error dialog then the corresponding LyX contents should should be selected in the main area as well. This is not always 100% correct, but usually the error cause is nearby. Does this not work in your case? Georg
Re: Strategies for locating errors
Wolfgang Engelmann wrote: > That was the reason I was asking a while ago, whether the latex source > panel (under >view) could show the tex line number. But I was told it is > not possible under lyx. Why that? Of course it would only be possible if the panel is set to show the full source (otherwise the line number would be wrong), but in that case it should not be a problem. Georg
Re: Strategies for locating errors
On 05/05/15 15:06, Wolfgang Engelmann wrote: > That was the reason I was asking a while ago, whether the latex > source panel (under >view) could show the tex line number. But I was > told it is not possible under lyx. That would certainly be a step in the right direction. Given that we already have forward and backward search between LyX and a PDF viewer using SyncTeX then something similar for LyX to/from TeX should be feasible. Will
Re: Strategies for locating errors
Am 05.05.2015 um 15:18 schrieb Will Furnass: On 05/05/15 13:27, Rainer M Krug wrote: Will Furnass writes: could LyX be improved to make locating errors less manual though? For example, if a mapping was generated at compile time from LyX lines to TeX lines then buttons could be added to the compilation pane to move the cursor between the lines referenced in error messages. I am by no means a LaTeX expert -0 so I might be wrong, but - the LaTeX error messages are already quite cryptic, and the error you quote (Missing } inserted' error for 'l.1052') means that the missing "}" is inserted in this line - where it is actually missing and what is causing this does not even LaTeX know - so there is no chance that LyX will be able to tell you. True, but the line number associated with a LaTeX error is a useful clue when fault-finding and being able to quickly move the cursor to the corresponding line in LyX could make fixing broken documents much quicker in many situations. The compilation pane could display a caveat next to buttons for moving the cursor between error line numbers saying something like 'the root cause of this error may not lie at this location'. Will That was the reason I was asking a while ago, whether the latex source panel (under >view) could show the tex line number. But I was told it is not possible under lyx. Wolfgang
Re: Strategies for locating errors
On 05/05/15 13:27, Rainer M Krug wrote: > Will Furnass writes: >> >> could LyX be improved to make locating errors less manual >> though? For example, if a mapping was generated at compile time >> from LyX lines to TeX lines then buttons could be added to the >> compilation pane to move the cursor between the lines referenced >> in error messages. > > I am by no means a LaTeX expert -0 so I might be wrong, but - the > LaTeX error messages are already quite cryptic, and the error you > quote (Missing } inserted' error for 'l.1052') means that the > missing "}" is inserted in this line - where it is actually > missing and what is causing this does not even LaTeX know - so > there is no chance that LyX will be able to tell you. True, but the line number associated with a LaTeX error is a useful clue when fault-finding and being able to quickly move the cursor to the corresponding line in LyX could make fixing broken documents much quicker in many situations. The compilation pane could display a caveat next to buttons for moving the cursor between error line numbers saying something like 'the root cause of this error may not lie at this location'. Will
Re: Strategies for locating errors
Will Furnass writes: > On 05/05/15 12:47, Nikos Alexandris wrote: >> * Will Furnass [2015-05-05 11:51:56 +0100]: >> >>> How do others locate compilation errors in large multi-file documents? >>> > >> >> Something like "binary search": split in two halfs, try to find out >> which half does not compile. Then, again, repeat the same: split in >> half, identify the erroneous part. Sooner or later you'll nail the >> source of the error. > > A good idea, but could LyX be improved to make locating errors less > manual though? For example, if a mapping was generated at compile time > from LyX lines to TeX lines then buttons could be added to the > compilation pane to move the cursor between the lines referenced in > error messages. I am by no means a LaTeX expert -0 so I might be wrong, but - the LaTeX error messages are already quite cryptic, and the error you quote (Missing } inserted' error for 'l.1052') means that the missing "}" is inserted in this line - where it is actually missing and what is causing this does not even LaTeX know - so there is no chance that LyX will be able to tell you. Rainer > > Will > > > > > > -- Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 signature.asc Description: PGP signature
Re: Strategies for locating errors
On 05/05/15 12:47, Nikos Alexandris wrote: > * Will Furnass [2015-05-05 11:51:56 +0100]: > >> How do others locate compilation errors in large multi-file documents? >> > > Something like "binary search": split in two halfs, try to find out > which half does not compile. Then, again, repeat the same: split in > half, identify the erroneous part. Sooner or later you'll nail the > source of the error. A good idea, but could LyX be improved to make locating errors less manual though? For example, if a mapping was generated at compile time from LyX lines to TeX lines then buttons could be added to the compilation pane to move the cursor between the lines referenced in error messages. Will
Re: Strategies for locating errors
* Will Furnass [2015-05-05 11:51:56 +0100]: > How do others locate compilation errors in large multi-file documents? > > I get a 'Missing } inserted' error for 'l.1052' when compiling but can't > relate that line number to the LyX source. I then try exporting to tex > using pdflatex into a temporary directory and search through all 16 tex > files looking for errors on or near line 1052. > > An alternative approach would have been to comment the > 'includes'/'inputs' for various chapters of my thesis then try to > recompile but this partitioning approach would be slow given that it > currently takes ~5mins to compile my thesis. > > I'm sure I can find the cause of the error eventually; I was just > wondering if there were a neat way of identifying the location of > errors. At present pretty much everything in LyX is a joy and very > slick apart from locating the source of errors. > > FYI, yes I am using a little Evil Red Text (to use \resizebox within > table floats). Something like "binary search": split in two halfs, try to find out which half does not compile. Then, again, repeat the same: split in half, identify the erroneous part. Sooner or later you'll nail the source of the error. Cheers, Nikos