Unknown InsetLayout tag

Daniel xracoonx at gmx.de
Sun Feb 23 17:57:43 UTC 2020


On 2020-02-23 18:03, Jean-Marc Lasgouttes wrote:
> Le 23/02/2020 à 17:10, Daniel a écrit :
>>> LyX: Unknown InsetLayout tag [around line 34 of file 
>>> /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmpr0000gp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout 
>>> current token: 'Require' context: '']
>>> LyX: Unknown InsetLayout tag [around line 35 of file 
>>> /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmpr0000gp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout 
>>> current token: 'refstyle' context: '']
>>> LyX: Unknown InsetLayout tag [around line 43 of file 
>>> /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmpr0000gp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout 
>>> current token: 'Require' context: '']
>> [...]
>>
>> Okay, found the problem. I used "Require" instead "Requires" in a 
>> custom module. I guess it would be helpful for LyX to list the 
>> original filename and not only the temporary converted one in order to 
>> easier find problems?
> 
> I am not sure it is easy, unless layout2layout adds comments like what 
> the C preprocessor does:
> #file: xxx.layout
> #line: 123
> 
> I think it would be very complicated to get right, unless we manage to 
> automatize it.
> 
> JMarc

I see.

I was also wondering why LyX does complain straight away if I include a 
module with faulty content. The same holds for local layouts. Why does 
LyX say it's valid when I use unknown inset tags?

Daniel



More information about the lyx-users mailing list