> 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
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
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 Use
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?
>
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 searc
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 (other
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 h
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
c
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 curso
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
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
* 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 temp
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 look
13 matches
Mail list logo
