Re: Beamer, standard overlay specification, references Problem
Am 22.02.20 um 20:22 schrieb Paul A. Rubin:
On 2/22/20 11:09 AM, Wolfgang Engelmann wrote:
If I use in beamer a frame with standard overlay specification and
references, instead of the second reference the first one is shown
again. Taking out the standard overlay specification is a remedy. If I
need to use the standard overlay specification, is there a way to
circumvent this?
Look at the TEST.lyx and export to pdf > the error occurs
put the standard overlay specification in a note or take it off > no
error
I use LyX Version 2.3.4
(Sonntag, 12. Januar 2020)
Systemverzeichnis: /usr/share/lyx/
Benutzerverzeichnis: ~/.lyx/
Qt-Version (Laufzeit): 5.12.5
Qt-Version (bei Erstellung): 5.12.5
Wolfgang
I tried to compile this and set a new indoor record for "cannot
determine the size of a missing graphic" errors. Can you cut this down
to a minimal example that shows the problem?
Paul
I am awful sorry that I have sent indecently not the almost minimal file
I had prepared, but somehow the original file slipped in.
Wolfgang
Test.lyx
Description: application/lyx
% Encoding: UTF-8
@Article{Min2004,
author = {Min, H. and Johnson, C. H. and Golden, S. S.},
journal = {J Biol Rhythms},
title = {Phase determination of circadian gene expression in \emph{{S}ynechococcus elongatus} {PCC} 7942},
year= {2004},
pages = {103--112},
volume = {19},
owner = {wolfgang},
}
@Article{Smith2006,
author = {Smith, R. M. and Williams, S. B.},
journal = {Proc Natl Acad Sci U S A},
title = {Circadian rhythms in gene transcription imparted by chromosome compaction in the cyanobacterium \emph{{S}ynechococcus eleongatus}},
year= {2006},
pages = {8564--8569},
volume = {103},
owner = {wolfgang},
}
@Comment{jabref-meta: databaseType:bibtex;}
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unknown InsetLayout tag
On 2020-02-23 23:19, Richard Kimberly Heck wrote: On 2/23/20 12:57 PM, Daniel wrote: 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_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/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? If I put Format 66 Requires TEST into local layout, it validates. If I switch to "Require", it does not. With modules, LyX is complaining, above, as it tries to load them. I'm not sure how it could do so any sooner. Riki Ah, I see. My case was actually different: InsetLayout Flex:Test Require refstyle End Which validates and only complains rather silently in the message pane on generating the output. Daniel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unknown InsetLayout tag
On 2/23/20 12:57 PM, Daniel wrote: > 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_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/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? If I put Format 66 Requires TEST into local layout, it validates. If I switch to "Require", it does not. With modules, LyX is complaining, above, as it tries to load them. I'm not sure how it could do so any sooner. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unknown InsetLayout tag
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_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/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 -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unknown InsetLayout tag
Le 23/02/2020 à 17:10, Daniel a écrit : LyX: Unknown InsetLayout tag [around line 34 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/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 -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unknown InsetLayout tag
On 2020-02-23 16:12, Daniel wrote: Hi, When I typeset lyx document to a pdf, I get the messages below. Does anyone know what the problem might be? Daniel --- below --- LyX: Unknown InsetLayout tag [around line 34 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/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? Daniel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Unknown InsetLayout tag
Hi, When I typeset lyx document to a pdf, I get the messages below. Does anyone know what the problem might be? Daniel --- below --- LyX: Unknown InsetLayout tag [around line 34 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 44 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'varioref' context: ''] LyX: Unknown InsetLayout tag [around line 52 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 52 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 53 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertf24781.layout current token: 'varioref' context: ''] LyX: Unknown InsetLayout tag [around line 34 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 44 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'varioref' context: ''] LyX: Unknown InsetLayout tag [around line 52 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 52 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 53 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertp24781.layout current token: 'varioref' context: ''] LyX: Unknown InsetLayout tag [around line 34 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 43 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 44 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'varioref' context: ''] LyX: Unknown InsetLayout tag [around line 52 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 52 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'refstyle' context: ''] LyX: Unknown InsetLayout tag [around line 53 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertm24781.layout current token: 'varioref' context: ''] LyX: Unknown InsetLayout tag [around line 34 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertw24781.layout current token: 'Require' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file /var/folders/vd/k0bkrvfd4pddpgsj8_s9tmprgp/T/lyx_tmpdir.ZmaXjBB24781/convertw24781.layout current token:
Re: how to use parselog flag
Le 23/02/2020 à 05:26, Amra, Nasir a écrit : Hello, I am trying to debug why a converter does not work in lyx 2.3.3 (using miktex 2.9 on windows 7) , but I am able to run the script in a windows command window (cmd.exe). How do I set parselog flag in the converter and where would I find the log file? Is it just placing “parselog” in the flag option or “parselog=TRUE” or something else? What I am trying to resolve is why the MS Word converter: pandoc -s --filter pandoc-citeproc --csl vancouver-superscript.csl -f latex -o $$o -t docx $$i gives me a “ lyx – can not convert file” error message. Moreover, I am able to run the script above in a windows command line (cmd.exe) successfully. Any help would be much appreciated. As far as I remember, parselog is used for converters which return errors with line numbers (chktex or literate programming) this transforms these logs in a form that LyX can read). In your case the best bet is to read the Message Pane. Aren't there enough error messages there? JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: how to use parselog flag
On Sun, Feb 23, 2020 at 04:26:29AM +, Amra, Nasir wrote: > Hello, >I am trying to debug why a converter does not work in lyx 2.3.3 (using > miktex 2.9 on windows 7) , but I am able to run the script in a windows > command window (cmd.exe). How do I set parselog flag in the converter and > where would I find the log file? Is it just placing "parselog" in the flag > option or "parselog=TRUE" or something else? > What I am trying to resolve is why the MS Word converter: > pandoc -s --filter pandoc-citeproc --csl vancouver-superscript.csl -f latex > -o $$o -t docx $$i > > gives me a " lyx - can not convert file" error message. Moreover, I am able > to run the script above in a windows command line (cmd.exe) successfully. > Any help would be much appreciated. Maybe you will get helpful output if when you start LyX on the command line you use "-dbg". For example: lyx -dbg any should give a lot of output. Perhaps there's a better flag to choose. Best, Scott signature.asc Description: PGP signature -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
how to use parselog flag
Hello, I am trying to debug why a converter does not work in lyx 2.3.3 (using miktex 2.9 on windows 7) , but I am able to run the script in a windows command window (cmd.exe). How do I set parselog flag in the converter and where would I find the log file? Is it just placing "parselog" in the flag option or "parselog=TRUE" or something else? What I am trying to resolve is why the MS Word converter: pandoc -s --filter pandoc-citeproc --csl vancouver-superscript.csl -f latex -o $$o -t docx $$i gives me a " lyx - can not convert file" error message. Moreover, I am able to run the script above in a windows command line (cmd.exe) successfully. Any help would be much appreciated. Cheers, Nasir -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
