Re: Strategies for locating errors

2015-05-08 Thread Will Furnass
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

2015-05-08 Thread Will Furnass
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

2015-05-08 Thread Will Furnass
> 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

2015-05-07 Thread Georg Baum
Will Furnass wrote: On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de 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

Re: Strategies for locating errors

2015-05-07 Thread Georg Baum
Will Furnass wrote: On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de 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

Re: Strategies for locating errors

2015-05-07 Thread Georg Baum
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

Re: Strategies for locating errors

2015-05-05 Thread Rainer M Krug
Will Furnass wrfurna...@sheffield.ac.uk writes: On 05/05/15 12:47, Nikos Alexandris wrote: * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]: How do others locate compilation errors in large multi-file documents? snip Something like binary search: split in two halfs,

Re: Strategies for locating errors

2015-05-05 Thread Nikos Alexandris
* Will Furnass wrfurna...@sheffield.ac.uk [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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
On 05/05/15 12:47, Nikos Alexandris wrote: * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]: How do others locate compilation errors in large multi-file documents? snip Something like binary search: split in two halfs, try to find out which half does not compile.

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
On 05/05/15 13:27, Rainer M Krug wrote: Will Furnass wrfurna...@sheffield.ac.uk 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

Re: Strategies for locating errors

2015-05-05 Thread Gordon Cooper
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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Re: Strategies for locating errors

2015-05-05 Thread Wolfgang Engelmann
Am 05.05.2015 um 15:18 schrieb Will Furnass: On 05/05/15 13:27, Rainer M Krug wrote: Will Furnass wrfurna...@sheffield.ac.uk 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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de 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

Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
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

Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
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

Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Re: Strategies for locating errors

2015-05-05 Thread Nikos Alexandris
* Will Furnass wrfurna...@sheffield.ac.uk [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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
On 05/05/15 12:47, Nikos Alexandris wrote: * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]: How do others locate compilation errors in large multi-file documents? snip Something like binary search: split in two halfs, try to find out which half does not compile.

Re: Strategies for locating errors

2015-05-05 Thread Rainer M Krug
Will Furnass wrfurna...@sheffield.ac.uk writes: On 05/05/15 12:47, Nikos Alexandris wrote: * Will Furnass wrfurna...@sheffield.ac.uk [2015-05-05 11:51:56 +0100]: How do others locate compilation errors in large multi-file documents? snip Something like binary search: split in two halfs,

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
On 05/05/15 13:27, Rainer M Krug wrote: Will Furnass wrfurna...@sheffield.ac.uk 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

Re: Strategies for locating errors

2015-05-05 Thread Wolfgang Engelmann
Am 05.05.2015 um 15:18 schrieb Will Furnass: On 05/05/15 13:27, Rainer M Krug wrote: Will Furnass wrfurna...@sheffield.ac.uk 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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
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

Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
On 5 May 2015 at 21:38, Georg Baum georg.b...@post.rwth-aachen.de 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

Re: Strategies for locating errors

2015-05-05 Thread Gordon Cooper
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

Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Re: Strategies for locating errors

2015-05-05 Thread Nikos Alexandris
* 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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Re: Strategies for locating errors

2015-05-05 Thread Rainer M Krug
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":

Re: Strategies for locating errors

2015-05-05 Thread 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 >>

Re: Strategies for locating errors

2015-05-05 Thread Wolfgang Engelmann
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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
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

Re: Strategies for locating errors

2015-05-05 Thread Georg Baum
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

Re: Strategies for locating errors

2015-05-05 Thread Will Furnass
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

Re: Strategies for locating errors

2015-05-05 Thread Gordon Cooper
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