citation style
Hello, a nice feature of recent lyx versions is that one can choose the type of citation by right-clicking on the citation. What I am missing here is, however, this type: authors et al. 2010 (no comma!) there is only authors et al., 2010 The first one is demanded by a Springer Publ style. Is this difficult to include in a later version of lyx and how can I achieve it at the time being (ERT?) Wolfgang
Re: copy and paste of latex insert
Le vendredi 03 octobre 2014 à 19:26 -0400, Scott Kostyshak a écrit : On Fri, Oct 3, 2014 at 4:05 PM, Scott Kostyshak skost...@lyx.org wrote: On Fri, Oct 3, 2014 at 2:40 PM, emile lunardon emile.lunar...@gmail.com wrote: LyX 2.1.2 has forgotten how to copy and paste a LaTeX insert properly. Only the text information is pasted ans the surrounding insert is missing. Thanks for the report. Can you please be more specific. 2.1.2 compared to what? 2.1.1? 2.0.8.1? What is a LaTeX insert? Do you mean an ERT box? Can you give specific instructions for how to reproduce? e.g. 1. Go to Insert TeX Code. 2. Write $\alpha$ in the ERT. 3. Select the box and copy it. 4... paste it (somewhere specific?) Sent to me from the user: The phénomena is observed with the recent LyX 2.1.2 compared to LyX 2.0.8.1 on Windows . The Latex insert is obtained by the command Ctrl+L and filled with some text. The copy and paste of the Latex insert is made in the usual way with a mouse selection followed by Ctrl+V. Thanks, Emile. Scott FWIW, I tried that on Linux Debian and I couldn't observe what Emile describes. The ERT box is copied and pasted in the same condition (open or closed) as it was originally. Windows issue? -- Daniel CLEMENT
Re: How To Turn Off Auto-fill in Table Cells?
Am Freitag 03 Oktober 2014, 11:21:10 schrieb Rich Shepard: On Fri, 3 Oct 2014, Jürgen Spitzmüller wrote: Not possible, AFAIK: http://www.lyx.org/trac/ticket/9207 Jürgen, That's too bad. Actually, it's possible. In Tools Preferences Edit Shortcuts, you can find the following command sequence bound to Tab: command-alternatives completion-accept;cell-forward;tab-insert;depth- increment;outline-in If you swap completion-accept and cell-forward, you should get the desired behavior. Something changed in version 2.1.x that took tab movement away from tables. Perhaps that change can be identified and reversed. This definition is 6 years old. Jürgen
Re: Failed compilation succeeds from command line: two problems
Am Freitag 03 Oktober 2014, 17:15:49 schrieb stefano franchi: Compilation from the command line succeeds, even though Luatex does indeed report the same error. However, it seems to be able to recover from it. So the first question is: how come LyX cannot recover from the error while lualatex can? Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. Second issue is the error itself. The full log of the command line compilation shows that the error is probably biblatex- or biber- related, as it occur in the bibliography. The context of the error is as follows: [494] Overfull \hbox (6.58478pt too wide) in paragraph at lines 309--309 [][][][][]\EU2/MinionPro(0)/m/n/10.95 (). “ Au-topoiesis, Adap-t iv-ity, Tele-ol-ogy, Agency”. In: \EU2/MinionPro(0)/m/it/10.95 Phe-nomenol- [] What looks suspicious here are the old style figures in the year (2005). Do you us old style figures in the bib file? Apart from that, we would need to see the whole log file. Jürgen
Re: citation style
Am Samstag 04 Oktober 2014, 08:01:14 schrieb Wolfgang Engelmann: Hello, a nice feature of recent lyx versions is that one can choose the type of citation by right-clicking on the citation. What I am missing here is, however, this type: authors et al. 2010 (no comma!) there is only authors et al., 2010 Works here. Pleae post a minimal example file. Jürgen
Re: Enumitem and IEEETran
On 2014-10-03, Anders Host-Madsen wrote: It seems enumitem and IEEETran.cls are not compatible. I found the following solution on the web. Insert \let\labelindent\relax BEFORE enuitem is included. That works. The issue is that in LyX, the latex preamble comes after enumitem is called. Any way to include the above statement before enumitem is called? A relatively easy hack would be to * copy the enumitem.module file from the LyX library (See HelpAbout LyX for the location at your machine) to the local LyX library (on Unix ~/.lyx/layouts/) and rename to, e.g., ieetranenumitem.module. * in this local file, change the first line like e.g. -#\DeclareLyXModule[enumitem.sty]{Customisable Lists (enumitem)} +#\DeclareLyXModule[enumitem.sty]{Customisable Lists (enumitem-ieeehack)} * and the preamble code AddToPreamble + \let\labelindent\relax \usepackage{enumitem} % customizable list environments \newlength{\lyxlabelwidth} % auxiliary length EndPreamble Then use the new enumitem-ieeehack module. (Remember, that the labelindent macro is now the one defined by enumitem and maybe strange things happen with label indentation in the ieee class.) (Also remember to update you local copy when a new version of the upstream enumitem.module is issued.) Günter
Re: Matching math font with TG Pagella
On 2014-10-03, Daniel CLEMENT wrote: Le vendredi 03 octobre 2014 à 08:58 +, Guenter Milde a écrit : On 2014-09-27, Daniel CLEMENT wrote: Hello, I like to use the TexGyre Pagella font in many documents, better that Palatino which lacks ligatures. However, Palatino triggers a nice matching font for maths, and I was never able to get it with TG Pagella, at least under LyX 2.0.6. Now that I've installed LyX 2.1.1, I wondered if perhaps it was easier to achieve, but I can't find how to do it in the new fonts settings dialog box. Do I have to add a package or something in the preamble? You may try the newpx package. http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/newpx.html Thanks a lot, that works beautifully. The newpxmath font is very nice. Just out of curiosity, and to check that I'm doing things properly: - I select TexGyge Pagella in LyX's fonts dialog; - but I can't choose newpxmath from there so I have to add \usepackage{newpxmath} to my document preamble. Is that correct? This is how I would do it. Alternatively, you could also load Palatino in the font dialogue and overwrite the text font with tgpagella in the preamble \usepackage{tgpagella} This would result in the standard mathpazo symbols and fonts for formulae and TG Pagella in the text. With XeTeX/LuaTeX, you can use unicode-math with the Asana-Math fonts for maths and the OpenType Pagella for text. Günter
Re: copy and paste of latex insert
I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). 2014-10-04 9:41 GMT+02:00 Daniel CLEMENT dcleme...@sfr.fr: Le vendredi 03 octobre 2014 à 19:26 -0400, Scott Kostyshak a écrit : On Fri, Oct 3, 2014 at 4:05 PM, Scott Kostyshak skost...@lyx.org wrote: On Fri, Oct 3, 2014 at 2:40 PM, emile lunardon emile.lunar...@gmail.com wrote: LyX 2.1.2 has forgotten how to copy and paste a LaTeX insert properly. Only the text information is pasted ans the surrounding insert is missing. Thanks for the report. Can you please be more specific. 2.1.2 compared to what? 2.1.1? 2.0.8.1? What is a LaTeX insert? Do you mean an ERT box? Can you give specific instructions for how to reproduce? e.g. 1. Go to Insert TeX Code. 2. Write $\alpha$ in the ERT. 3. Select the box and copy it. 4... paste it (somewhere specific?) Sent to me from the user: The phénomena is observed with the recent LyX 2.1.2 compared to LyX 2.0.8.1 on Windows . The Latex insert is obtained by the command Ctrl+L and filled with some text. The copy and paste of the Latex insert is made in the usual way with a mouse selection followed by Ctrl+V. Thanks, Emile. Scott FWIW, I tried that on Linux Debian and I couldn't observe what Emile describes. The ERT box is copied and pasted in the same condition (open or closed) as it was originally. Windows issue? -- Daniel CLEMENT
Re: Matching math font with TG Pagella
Guenter Milde wrote: This is how I would do it. Alternatively, you could also load Palatino in the font dialogue and overwrite the text font with tgpagella in the preamble \usepackage{tgpagella} This would result in the standard mathpazo symbols and fonts for formulae and TG Pagella in the text. With XeTeX/LuaTeX, you can use unicode-math with the Asana-Math fonts for maths and the OpenType Pagella for text. It would be pretty trivial to add support for newpxmath to LyX (although it involves a file format change). You can take this as a model: http://www.lyx.org/trac/changeset/a84a98b5/lyxgit/ Jürgen
Re: citation style
Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen
Re: citation style
I am awful sorry, I sent the wrong file. Wolfgang Am 04.10.2014 um 10:47 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen TestA.lyx Description: application/lyx
Re: citation style
This was indeed something which should not happen: to send the original file from which I had prepared the short one. It should at least not have gone to the list! There is no excuse, but the publisher wants the proof reading done in such a short time, that I was too nervous (and too old, by the way). Must donate to the LyX people... Wolfgang, full of shame Am 04.10.2014 um 11:08 schrieb Wolfgang Engelmann: I am awful sorry, I sent the wrong file. Wolfgang Am 04.10.2014 um 10:47 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen
Re: citation style
Wolfgang Engelmann wrote: I am awful sorry, I sent the wrong file. Wolfgang By default, natbib does not provide a citation command with author-year in parathesis and no comma between author and year. An workaround is to use the citation command with comma and pass the following to the preamble: \setcitestyle{aysep={}} This will remove the comma between author and year globally in the output. If you want the comma to be omitted in the LyX view as well, paste the following to Document Local Format, hit Validate and OK (you might need to restart to see the effect): CiteFormat authoryear !open ( !sep ; !close ) !citet %!startlink%%!abbrvauthor%%!endlink% %!open%%!textbefore%%!year%%!nextcitet% !citealt %!startlink%%!abbrvauthor% %!textbefore%%!year%%!endlink%%!nextcitealt% !citealp %!startlink%%!abbrvauthor% %!year%%!endlink%%!nextcitealp% !nextcitet {%next%[[%!close%%!sep% %!citet%]]} !nextcitealt {%next%[[%!sep% %!citealt%]]} !nextcitealp {%next%[[%!sep% %!citealp%]]} cite %!citet%%!textafter%%!close% citep %!open%%!textbefore%%!citealp%%!textafter%%!close% citealp %!textbefore%%!citealp%%!textafter% citeauthor %!startlink%%!abbrvauthor%%!endlink%%!nextauthor%%!textafter% citeyear %!startlink%%!year%%!endlink%%!nextyear%%!textafter% End HTH, Jürgen
Re: citation style
Thanks, Jürgen, for the workaround. Since this will remove the commata between author and year globally, I decided to leave is to the Publisher. I am not willing to wreck my nerves and spill my time for the shareholders. But I appreciated your help very much, Yours Wolfgang Am 04.10.2014 um 11:34 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: I am awful sorry, I sent the wrong file. Wolfgang By default, natbib does not provide a citation command with author-year in parathesis and no comma between author and year. An workaround is to use the citation command with comma and pass the following to the preamble: \setcitestyle{aysep={}} This will remove the comma between author and year globally in the output. If you want the comma to be omitted in the LyX view as well, paste the following to Document Local Format, hit Validate and OK (you might need to restart to see the effect): CiteFormat authoryear !open ( !sep ; !close ) !citet %!startlink%%!abbrvauthor%%!endlink% %!open%%!textbefore%%!year%%!nextcitet% !citealt %!startlink%%!abbrvauthor% %!textbefore%%!year%%!endlink%%!nextcitealt% !citealp %!startlink%%!abbrvauthor% %!year%%!endlink%%!nextcitealp% !nextcitet {%next%[[%!close%%!sep% %!citet%]]} !nextcitealt {%next%[[%!sep% %!citealt%]]} !nextcitealp {%next%[[%!sep% %!citealp%]]} cite %!citet%%!textafter%%!close% citep %!open%%!textbefore%%!citealp%%!textafter%%!close% citealp %!textbefore%%!citealp%%!textafter% citeauthor %!startlink%%!abbrvauthor%%!endlink%%!nextauthor%%!textafter% citeyear %!startlink%%!year%%!endlink%%!nextyear%%!textafter% End HTH, Jürgen
Re: How To Turn Off Auto-fill in Table Cells?
On Sat, 4 Oct 2014, Jürgen Spitzmüller wrote: Actually, it's possible. In Tools Preferences Edit Shortcuts, you can find the following command sequence bound to Tab: command-alternatives completion-accept;cell-forward;tab-insert;depth- increment;outline-in If you swap completion-accept and cell-forward, you should get the desired behavior. Jürgen, Thank you, I'll do that. Something changed in version 2.1.x that took tab movement away from tables. Perhaps that change can be identified and reversed. This definition is 6 years old. Interesting. I've not experienced this behavior before this one document. Much appreciated, Rich
Re: Failed compilation succeeds from command line: two problems
On Oct 4, 2014 9:54 AM, Jürgen Spitzmüller sp...@lyx.org wrote: stefano franchi wrote: Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. I understand that, but why is this? Why not? Sorry my message got truncated. What I meant to say was: Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. S. Jürgen
Re: Failed compilation succeeds from command line: two problems
On Oct 4, 2014 11:57 AM, stefano franchi stefano.fran...@gmail.com wrote: On Oct 4, 2014 9:54 AM, Jürgen Spitzmüller sp...@lyx.org wrote: stefano franchi wrote: Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. I understand that, but why is this? Why not? Sorry my message got truncated. What I meant to say was: Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. I meant from kile ! Damned autocorrect S. Jürgen
Re: Failed compilation succeeds from command line: two problems
On Sat, Oct 4, 2014 at 12:57 PM, stefano franchi stefano.fran...@gmail.com wrote: On Oct 4, 2014 9:54 AM, Jürgen Spitzmüller sp...@lyx.org wrote: stefano franchi wrote: Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. I understand that, but why is this? Why not? Sorry my message got truncated. What I meant to say was: Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. The answer to Why?, as Jürgen stated, is that it is important that the user knows that there is an error so that the error can be fixed as soon as possible. It would be irresponsible of LyX not to make sure you know that a command failed. You might think then that we could just issue a warning, but I don't think things are that simple (as a permanent LyX solution). For example, if a document is exported from LyX on the command line, the warning is shown but there is a non-zero exit code so such a user might not realize there is a problem. I understand your argument, Stefano. It is a reasonable one and also a common one. For example, if you have a deadline to meet and a certain error that you think might not even affect the output of the PDF (and even if there is a chance, you could proof check the PDF manually), you just want your PDF and don't have time to think about fixing a possibly minor error. However, I think this is a feature request and not a bug. You might want to open a trac ticket because this type of conversation comes up from time to time and is likely to come up very often in 2.2 if we start stopping compilation when BibTeX errors occur (see http://www.lyx.org/trac/ticket/2757). Input from your side of the debate is important since we don't have any developer currently defending that (popular) feature request and it is important to understand and try to accommodate all workflows. If you do open a feature request, please mention exactly how Kile handles the situation. It's very useful to compare LyX with other programs and in this case appears to strengthen your argument. Off topic, this is an example of why versioning is useful. I use git and whenever I come across such a complicated issue, I just look at the differences between my current revision and the last good revision. I hope you get this frustrating issue figured out soon. It certainly sounds annoying. Scott
Re: Failed compilation succeeds from command line: two problems
On 04/10/2014 3:23 PM, Scott Kostyshak wrote: I understand your argument, Stefano. It is a reasonable one and also a common one. For example, if you have a deadline to meet and a certain error that you think might not even affect the output of the PDF (and even if there is a chance, you could proof check the PDF manually), you just want your PDF and don't have time to think about fixing a possibly minor error. However, I think this is a feature request and not a bug. You might want to open a trac ticket because this type of conversation comes up from time to time and is likely to come up very often in 2.2 if we start stopping compilation when BibTeX errors occur (see http://www.lyx.org/trac/ticket/2757). Input from your side of the debate is important since we don't have any developer currently defending that (popular) feature request and it is important to understand and try to accommodate all workflows. FWIW I also think we should have a compilation mode which keeps going as far as possible. Of course, it would be a opt-in setting (could be a dialog asking to continue in the GUI and a --force option on the command line). Cheers, Julien
Re: copy and paste of latex insert
On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien
Re: copy and paste of latex insert
You are right, the same phenomena occurs on Windows with Math inserts ! 2014-10-04 21:59 GMT+02:00 Julien Rioux jri...@lyx.org: On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien
Re: copy and paste of latex insert
On 5/10/2014 9:21 a.m., emile lunardon wrote: You are right, the same phenomena occurs on Windows with Math inserts ! 2014-10-04 21:59 GMT+02:00 Julien Rioux jri...@lyx.org mailto:jri...@lyx.org: On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien FWIW, I'm using Windows 7 LyX 2.1.2 and have just awoken from hibernation. Copy paste of ERT insets math insets proceeds as it should, both inset contents, in both a new document and a large existing one. I sometimes find that after restarting LyX, or even restarting Windows, various anomalous behaviours vanish. Andrew --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
citation style
Hello, a nice feature of recent lyx versions is that one can choose the type of citation by right-clicking on the citation. What I am missing here is, however, this type: authors et al. 2010 (no comma!) there is only authors et al., 2010 The first one is demanded by a Springer Publ style. Is this difficult to include in a later version of lyx and how can I achieve it at the time being (ERT?) Wolfgang
Re: copy and paste of latex insert
Le vendredi 03 octobre 2014 à 19:26 -0400, Scott Kostyshak a écrit : On Fri, Oct 3, 2014 at 4:05 PM, Scott Kostyshak skost...@lyx.org wrote: On Fri, Oct 3, 2014 at 2:40 PM, emile lunardon emile.lunar...@gmail.com wrote: LyX 2.1.2 has forgotten how to copy and paste a LaTeX insert properly. Only the text information is pasted ans the surrounding insert is missing. Thanks for the report. Can you please be more specific. 2.1.2 compared to what? 2.1.1? 2.0.8.1? What is a LaTeX insert? Do you mean an ERT box? Can you give specific instructions for how to reproduce? e.g. 1. Go to Insert TeX Code. 2. Write $\alpha$ in the ERT. 3. Select the box and copy it. 4... paste it (somewhere specific?) Sent to me from the user: The phénomena is observed with the recent LyX 2.1.2 compared to LyX 2.0.8.1 on Windows . The Latex insert is obtained by the command Ctrl+L and filled with some text. The copy and paste of the Latex insert is made in the usual way with a mouse selection followed by Ctrl+V. Thanks, Emile. Scott FWIW, I tried that on Linux Debian and I couldn't observe what Emile describes. The ERT box is copied and pasted in the same condition (open or closed) as it was originally. Windows issue? -- Daniel CLEMENT
Re: How To Turn Off Auto-fill in Table Cells?
Am Freitag 03 Oktober 2014, 11:21:10 schrieb Rich Shepard: On Fri, 3 Oct 2014, Jürgen Spitzmüller wrote: Not possible, AFAIK: http://www.lyx.org/trac/ticket/9207 Jürgen, That's too bad. Actually, it's possible. In Tools Preferences Edit Shortcuts, you can find the following command sequence bound to Tab: command-alternatives completion-accept;cell-forward;tab-insert;depth- increment;outline-in If you swap completion-accept and cell-forward, you should get the desired behavior. Something changed in version 2.1.x that took tab movement away from tables. Perhaps that change can be identified and reversed. This definition is 6 years old. Jürgen
Re: Failed compilation succeeds from command line: two problems
Am Freitag 03 Oktober 2014, 17:15:49 schrieb stefano franchi: Compilation from the command line succeeds, even though Luatex does indeed report the same error. However, it seems to be able to recover from it. So the first question is: how come LyX cannot recover from the error while lualatex can? Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. Second issue is the error itself. The full log of the command line compilation shows that the error is probably biblatex- or biber- related, as it occur in the bibliography. The context of the error is as follows: [494] Overfull \hbox (6.58478pt too wide) in paragraph at lines 309--309 [][][][][]\EU2/MinionPro(0)/m/n/10.95 (). “ Au-topoiesis, Adap-t iv-ity, Tele-ol-ogy, Agency”. In: \EU2/MinionPro(0)/m/it/10.95 Phe-nomenol- [] What looks suspicious here are the old style figures in the year (2005). Do you us old style figures in the bib file? Apart from that, we would need to see the whole log file. Jürgen
Re: citation style
Am Samstag 04 Oktober 2014, 08:01:14 schrieb Wolfgang Engelmann: Hello, a nice feature of recent lyx versions is that one can choose the type of citation by right-clicking on the citation. What I am missing here is, however, this type: authors et al. 2010 (no comma!) there is only authors et al., 2010 Works here. Pleae post a minimal example file. Jürgen
Re: Enumitem and IEEETran
On 2014-10-03, Anders Host-Madsen wrote: It seems enumitem and IEEETran.cls are not compatible. I found the following solution on the web. Insert \let\labelindent\relax BEFORE enuitem is included. That works. The issue is that in LyX, the latex preamble comes after enumitem is called. Any way to include the above statement before enumitem is called? A relatively easy hack would be to * copy the enumitem.module file from the LyX library (See HelpAbout LyX for the location at your machine) to the local LyX library (on Unix ~/.lyx/layouts/) and rename to, e.g., ieetranenumitem.module. * in this local file, change the first line like e.g. -#\DeclareLyXModule[enumitem.sty]{Customisable Lists (enumitem)} +#\DeclareLyXModule[enumitem.sty]{Customisable Lists (enumitem-ieeehack)} * and the preamble code AddToPreamble + \let\labelindent\relax \usepackage{enumitem} % customizable list environments \newlength{\lyxlabelwidth} % auxiliary length EndPreamble Then use the new enumitem-ieeehack module. (Remember, that the labelindent macro is now the one defined by enumitem and maybe strange things happen with label indentation in the ieee class.) (Also remember to update you local copy when a new version of the upstream enumitem.module is issued.) Günter
Re: Matching math font with TG Pagella
On 2014-10-03, Daniel CLEMENT wrote: Le vendredi 03 octobre 2014 à 08:58 +, Guenter Milde a écrit : On 2014-09-27, Daniel CLEMENT wrote: Hello, I like to use the TexGyre Pagella font in many documents, better that Palatino which lacks ligatures. However, Palatino triggers a nice matching font for maths, and I was never able to get it with TG Pagella, at least under LyX 2.0.6. Now that I've installed LyX 2.1.1, I wondered if perhaps it was easier to achieve, but I can't find how to do it in the new fonts settings dialog box. Do I have to add a package or something in the preamble? You may try the newpx package. http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/newpx.html Thanks a lot, that works beautifully. The newpxmath font is very nice. Just out of curiosity, and to check that I'm doing things properly: - I select TexGyge Pagella in LyX's fonts dialog; - but I can't choose newpxmath from there so I have to add \usepackage{newpxmath} to my document preamble. Is that correct? This is how I would do it. Alternatively, you could also load Palatino in the font dialogue and overwrite the text font with tgpagella in the preamble \usepackage{tgpagella} This would result in the standard mathpazo symbols and fonts for formulae and TG Pagella in the text. With XeTeX/LuaTeX, you can use unicode-math with the Asana-Math fonts for maths and the OpenType Pagella for text. Günter
Re: copy and paste of latex insert
I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). 2014-10-04 9:41 GMT+02:00 Daniel CLEMENT dcleme...@sfr.fr: Le vendredi 03 octobre 2014 à 19:26 -0400, Scott Kostyshak a écrit : On Fri, Oct 3, 2014 at 4:05 PM, Scott Kostyshak skost...@lyx.org wrote: On Fri, Oct 3, 2014 at 2:40 PM, emile lunardon emile.lunar...@gmail.com wrote: LyX 2.1.2 has forgotten how to copy and paste a LaTeX insert properly. Only the text information is pasted ans the surrounding insert is missing. Thanks for the report. Can you please be more specific. 2.1.2 compared to what? 2.1.1? 2.0.8.1? What is a LaTeX insert? Do you mean an ERT box? Can you give specific instructions for how to reproduce? e.g. 1. Go to Insert TeX Code. 2. Write $\alpha$ in the ERT. 3. Select the box and copy it. 4... paste it (somewhere specific?) Sent to me from the user: The phénomena is observed with the recent LyX 2.1.2 compared to LyX 2.0.8.1 on Windows . The Latex insert is obtained by the command Ctrl+L and filled with some text. The copy and paste of the Latex insert is made in the usual way with a mouse selection followed by Ctrl+V. Thanks, Emile. Scott FWIW, I tried that on Linux Debian and I couldn't observe what Emile describes. The ERT box is copied and pasted in the same condition (open or closed) as it was originally. Windows issue? -- Daniel CLEMENT
Re: Matching math font with TG Pagella
Guenter Milde wrote: This is how I would do it. Alternatively, you could also load Palatino in the font dialogue and overwrite the text font with tgpagella in the preamble \usepackage{tgpagella} This would result in the standard mathpazo symbols and fonts for formulae and TG Pagella in the text. With XeTeX/LuaTeX, you can use unicode-math with the Asana-Math fonts for maths and the OpenType Pagella for text. It would be pretty trivial to add support for newpxmath to LyX (although it involves a file format change). You can take this as a model: http://www.lyx.org/trac/changeset/a84a98b5/lyxgit/ Jürgen
Re: citation style
Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen
Re: citation style
I am awful sorry, I sent the wrong file. Wolfgang Am 04.10.2014 um 10:47 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen TestA.lyx Description: application/lyx
Re: citation style
This was indeed something which should not happen: to send the original file from which I had prepared the short one. It should at least not have gone to the list! There is no excuse, but the publisher wants the proof reading done in such a short time, that I was too nervous (and too old, by the way). Must donate to the LyX people... Wolfgang, full of shame Am 04.10.2014 um 11:08 schrieb Wolfgang Engelmann: I am awful sorry, I sent the wrong file. Wolfgang Am 04.10.2014 um 10:47 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen
Re: citation style
Wolfgang Engelmann wrote: I am awful sorry, I sent the wrong file. Wolfgang By default, natbib does not provide a citation command with author-year in parathesis and no comma between author and year. An workaround is to use the citation command with comma and pass the following to the preamble: \setcitestyle{aysep={}} This will remove the comma between author and year globally in the output. If you want the comma to be omitted in the LyX view as well, paste the following to Document Local Format, hit Validate and OK (you might need to restart to see the effect): CiteFormat authoryear !open ( !sep ; !close ) !citet %!startlink%%!abbrvauthor%%!endlink% %!open%%!textbefore%%!year%%!nextcitet% !citealt %!startlink%%!abbrvauthor% %!textbefore%%!year%%!endlink%%!nextcitealt% !citealp %!startlink%%!abbrvauthor% %!year%%!endlink%%!nextcitealp% !nextcitet {%next%[[%!close%%!sep% %!citet%]]} !nextcitealt {%next%[[%!sep% %!citealt%]]} !nextcitealp {%next%[[%!sep% %!citealp%]]} cite %!citet%%!textafter%%!close% citep %!open%%!textbefore%%!citealp%%!textafter%%!close% citealp %!textbefore%%!citealp%%!textafter% citeauthor %!startlink%%!abbrvauthor%%!endlink%%!nextauthor%%!textafter% citeyear %!startlink%%!year%%!endlink%%!nextyear%%!textafter% End HTH, Jürgen
Re: citation style
Thanks, Jürgen, for the workaround. Since this will remove the commata between author and year globally, I decided to leave is to the Publisher. I am not willing to wreck my nerves and spill my time for the shareholders. But I appreciated your help very much, Yours Wolfgang Am 04.10.2014 um 11:34 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: I am awful sorry, I sent the wrong file. Wolfgang By default, natbib does not provide a citation command with author-year in parathesis and no comma between author and year. An workaround is to use the citation command with comma and pass the following to the preamble: \setcitestyle{aysep={}} This will remove the comma between author and year globally in the output. If you want the comma to be omitted in the LyX view as well, paste the following to Document Local Format, hit Validate and OK (you might need to restart to see the effect): CiteFormat authoryear !open ( !sep ; !close ) !citet %!startlink%%!abbrvauthor%%!endlink% %!open%%!textbefore%%!year%%!nextcitet% !citealt %!startlink%%!abbrvauthor% %!textbefore%%!year%%!endlink%%!nextcitealt% !citealp %!startlink%%!abbrvauthor% %!year%%!endlink%%!nextcitealp% !nextcitet {%next%[[%!close%%!sep% %!citet%]]} !nextcitealt {%next%[[%!sep% %!citealt%]]} !nextcitealp {%next%[[%!sep% %!citealp%]]} cite %!citet%%!textafter%%!close% citep %!open%%!textbefore%%!citealp%%!textafter%%!close% citealp %!textbefore%%!citealp%%!textafter% citeauthor %!startlink%%!abbrvauthor%%!endlink%%!nextauthor%%!textafter% citeyear %!startlink%%!year%%!endlink%%!nextyear%%!textafter% End HTH, Jürgen
Re: How To Turn Off Auto-fill in Table Cells?
On Sat, 4 Oct 2014, Jürgen Spitzmüller wrote: Actually, it's possible. In Tools Preferences Edit Shortcuts, you can find the following command sequence bound to Tab: command-alternatives completion-accept;cell-forward;tab-insert;depth- increment;outline-in If you swap completion-accept and cell-forward, you should get the desired behavior. Jürgen, Thank you, I'll do that. Something changed in version 2.1.x that took tab movement away from tables. Perhaps that change can be identified and reversed. This definition is 6 years old. Interesting. I've not experienced this behavior before this one document. Much appreciated, Rich
Re: Failed compilation succeeds from command line: two problems
On Oct 4, 2014 9:54 AM, Jürgen Spitzmüller sp...@lyx.org wrote: stefano franchi wrote: Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. I understand that, but why is this? Why not? Sorry my message got truncated. What I meant to say was: Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. S. Jürgen
Re: Failed compilation succeeds from command line: two problems
On Oct 4, 2014 11:57 AM, stefano franchi stefano.fran...@gmail.com wrote: On Oct 4, 2014 9:54 AM, Jürgen Spitzmüller sp...@lyx.org wrote: stefano franchi wrote: Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. I understand that, but why is this? Why not? Sorry my message got truncated. What I meant to say was: Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. I meant from kile ! Damned autocorrect S. Jürgen
Re: Failed compilation succeeds from command line: two problems
On Sat, Oct 4, 2014 at 12:57 PM, stefano franchi stefano.fran...@gmail.com wrote: On Oct 4, 2014 9:54 AM, Jürgen Spitzmüller sp...@lyx.org wrote: stefano franchi wrote: Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. I understand that, but why is this? Why not? Sorry my message got truncated. What I meant to say was: Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. The answer to Why?, as Jürgen stated, is that it is important that the user knows that there is an error so that the error can be fixed as soon as possible. It would be irresponsible of LyX not to make sure you know that a command failed. You might think then that we could just issue a warning, but I don't think things are that simple (as a permanent LyX solution). For example, if a document is exported from LyX on the command line, the warning is shown but there is a non-zero exit code so such a user might not realize there is a problem. I understand your argument, Stefano. It is a reasonable one and also a common one. For example, if you have a deadline to meet and a certain error that you think might not even affect the output of the PDF (and even if there is a chance, you could proof check the PDF manually), you just want your PDF and don't have time to think about fixing a possibly minor error. However, I think this is a feature request and not a bug. You might want to open a trac ticket because this type of conversation comes up from time to time and is likely to come up very often in 2.2 if we start stopping compilation when BibTeX errors occur (see http://www.lyx.org/trac/ticket/2757). Input from your side of the debate is important since we don't have any developer currently defending that (popular) feature request and it is important to understand and try to accommodate all workflows. If you do open a feature request, please mention exactly how Kile handles the situation. It's very useful to compare LyX with other programs and in this case appears to strengthen your argument. Off topic, this is an example of why versioning is useful. I use git and whenever I come across such a complicated issue, I just look at the differences between my current revision and the last good revision. I hope you get this frustrating issue figured out soon. It certainly sounds annoying. Scott
Re: Failed compilation succeeds from command line: two problems
On 04/10/2014 3:23 PM, Scott Kostyshak wrote: I understand your argument, Stefano. It is a reasonable one and also a common one. For example, if you have a deadline to meet and a certain error that you think might not even affect the output of the PDF (and even if there is a chance, you could proof check the PDF manually), you just want your PDF and don't have time to think about fixing a possibly minor error. However, I think this is a feature request and not a bug. You might want to open a trac ticket because this type of conversation comes up from time to time and is likely to come up very often in 2.2 if we start stopping compilation when BibTeX errors occur (see http://www.lyx.org/trac/ticket/2757). Input from your side of the debate is important since we don't have any developer currently defending that (popular) feature request and it is important to understand and try to accommodate all workflows. FWIW I also think we should have a compilation mode which keeps going as far as possible. Of course, it would be a opt-in setting (could be a dialog asking to continue in the GUI and a --force option on the command line). Cheers, Julien
Re: copy and paste of latex insert
On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien
Re: copy and paste of latex insert
You are right, the same phenomena occurs on Windows with Math inserts ! 2014-10-04 21:59 GMT+02:00 Julien Rioux jri...@lyx.org: On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien
Re: copy and paste of latex insert
On 5/10/2014 9:21 a.m., emile lunardon wrote: You are right, the same phenomena occurs on Windows with Math inserts ! 2014-10-04 21:59 GMT+02:00 Julien Rioux jri...@lyx.org mailto:jri...@lyx.org: On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien FWIW, I'm using Windows 7 LyX 2.1.2 and have just awoken from hibernation. Copy paste of ERT insets math insets proceeds as it should, both inset contents, in both a new document and a large existing one. I sometimes find that after restarting LyX, or even restarting Windows, various anomalous behaviours vanish. Andrew --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
citation style
Hello, a nice feature of recent lyx versions is that one can choose the type of citation by right-clicking on the citation. What I am missing here is, however, this type: authors et al. 2010 (no comma!) there is only authors et al., 2010 The first one is demanded by a Springer Publ style. Is this difficult to include in a later version of lyx and how can I achieve it at the time being (ERT?) Wolfgang
Re: copy and paste of latex insert
Le vendredi 03 octobre 2014 à 19:26 -0400, Scott Kostyshak a écrit : > On Fri, Oct 3, 2014 at 4:05 PM, Scott Kostyshakwrote: > > On Fri, Oct 3, 2014 at 2:40 PM, emile lunardon > > wrote: > >> LyX 2.1.2 has forgotten how to copy and paste a LaTeX insert properly. Only > >> the text information is pasted ans the surrounding insert is missing. > > > > Thanks for the report. > > > > Can you please be more specific. 2.1.2 compared to what? 2.1.1? 2.0.8.1? > > What is a LaTeX insert? Do you mean an ERT box? Can you give specific > > instructions for how to reproduce? e.g. 1. Go to Insert > TeX Code. 2. > > Write "$\alpha"$ in the ERT. 3. Select the box and copy it. 4... paste > > it (somewhere specific?) > > > > Sent to me from the user: > > The phénomena is observed with the recent LyX 2.1.2 compared to LyX > 2.0.8.1 on Windows . > > The Latex insert is obtained by the command Ctrl+L and filled with some text. > > The copy and paste of the Latex insert is made in the usual way with a > mouse selection followed by Ctrl+V. > > Thanks, Emile. > > Scott FWIW, I tried that on Linux Debian and I couldn't observe what Emile describes. The ERT box is copied and pasted in the same condition (open or closed) as it was originally. Windows issue? -- Daniel CLEMENT
Re: How To Turn Off Auto-fill in Table Cells?
Am Freitag 03 Oktober 2014, 11:21:10 schrieb Rich Shepard: > On Fri, 3 Oct 2014, Jürgen Spitzmüller wrote: > > Not possible, AFAIK: > > http://www.lyx.org/trac/ticket/9207 > > Jürgen, > >That's too bad. Actually, it's possible. In Tools > Preferences > Edit > Shortcuts, you can find the following command sequence bound to "Tab": "command-alternatives completion-accept;cell-forward;tab-insert;depth- increment;outline-in" If you swap completion-accept and cell-forward, you should get the desired behavior. >Something changed in version 2.1.x that took tab movement > away from tables. Perhaps that change can be identified and reversed. This definition is 6 years old. Jürgen
Re: Failed compilation succeeds from command line: two problems
Am Freitag 03 Oktober 2014, 17:15:49 schrieb stefano franchi: > Compilation from the command line succeeds, even though Luatex does indeed > report the same error. However, it seems to be able to recover from it. > So the first question is: how come LyX cannot recover from the error while > lualatex can? Both cannot. The command line simply allows you to ignore the error with whatever visible or invisible consequences this has. LyX does not let you get away with it. The error needs to be fixed anyway. > Second issue is the error itself. The full log of the command line > compilation shows that the error is probably biblatex- or biber- related, > as it occur in the bibliography. The context of the error is as follows: > > [494] > Overfull \hbox (6.58478pt too wide) in paragraph at lines 309--309 > [][][][][]\EU2/MinionPro(0)/m/n/10.95 (). “ Au-topoiesis, Adap-t > iv-ity, Tele-ol-ogy, Agency”. In: \EU2/MinionPro(0)/m/it/10.95 Phe-nomenol- > > [] What looks suspicious here are the old style figures in the year (2005). Do you us old style figures in the bib file? Apart from that, we would need to see the whole log file. Jürgen
Re: citation style
Am Samstag 04 Oktober 2014, 08:01:14 schrieb Wolfgang Engelmann: > Hello, > > a nice feature of recent lyx versions is that one can choose the type of > citation by right-clicking on the citation. What I am missing here is, > however, this type: > authors et al. 2010 (no comma!) > there is only > authors et al., 2010 Works here. Pleae post a minimal example file. Jürgen
Re: Enumitem and IEEETran
On 2014-10-03, Anders Host-Madsen wrote: > It seems enumitem and IEEETran.cls are not compatible. I > found the following solution on the web. Insert > \let\labelindent\relax > BEFORE enuitem is included. That works. The issue is > that in LyX, the latex preamble comes after enumitem > is called. Any way to include the above statement > before enumitem is called? A relatively easy hack would be to * copy the "enumitem.module" file from the LyX library (See Help>About LyX for the location at your machine) to the local LyX library (on Unix ~/.lyx/layouts/) and rename to, e.g., "ieetranenumitem.module". * in this local file, change the first line like e.g. -#\DeclareLyXModule[enumitem.sty]{Customisable Lists (enumitem)} +#\DeclareLyXModule[enumitem.sty]{Customisable Lists (enumitem-ieeehack)} * and the preamble code AddToPreamble + \let\labelindent\relax \usepackage{enumitem} % customizable list environments \newlength{\lyxlabelwidth} % auxiliary length EndPreamble Then use the new "enumitem-ieeehack" module. (Remember, that the "labelindent" macro is now the one defined by enumitem and maybe strange things happen with label indentation in the ieee class.) (Also remember to update you local copy when a new version of the upstream enumitem.module is issued.) Günter
Re: Matching math font with TG Pagella
On 2014-10-03, Daniel CLEMENT wrote: > Le vendredi 03 octobre 2014 à 08:58 +, Guenter Milde a écrit : >> On 2014-09-27, Daniel CLEMENT wrote: >> > Hello, >> > I like to use the TexGyre Pagella font in many documents, better that >> > Palatino which lacks ligatures. >> > However, Palatino triggers a nice matching font for maths, and I was >> > never able to get it with TG Pagella, at least under LyX 2.0.6. >> > Now that I've installed LyX 2.1.1, I wondered if perhaps it was easier >> > to achieve, but I can't find how to do it in the new fonts settings >> > dialog box. >> > Do I have to add a package or something in the preamble? >> You may try the newpx package. >> http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/newpx.html > Thanks a lot, that works beautifully. The newpxmath font is very nice. > Just out of curiosity, and to check that I'm doing things properly: > - I select TexGyge Pagella in LyX's fonts dialog; > - but I can't choose newpxmath from there so I have to add > \usepackage{newpxmath} > to my document preamble. > Is that correct? This is how I would do it. Alternatively, you could also load Palatino in the font dialogue and overwrite the text font with tgpagella in the preamble \usepackage{tgpagella} This would result in the standard "mathpazo" symbols and fonts for formulae and TG Pagella in the text. With XeTeX/LuaTeX, you can use "unicode-math" with the Asana-Math fonts for maths and the OpenType Pagella for text. Günter
Re: copy and paste of latex insert
I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). 2014-10-04 9:41 GMT+02:00 Daniel CLEMENT: > Le vendredi 03 octobre 2014 à 19:26 -0400, Scott Kostyshak a écrit : > > On Fri, Oct 3, 2014 at 4:05 PM, Scott Kostyshak > wrote: > > > On Fri, Oct 3, 2014 at 2:40 PM, emile lunardon < > emile.lunar...@gmail.com> wrote: > > >> LyX 2.1.2 has forgotten how to copy and paste a LaTeX insert > properly. Only > > >> the text information is pasted ans the surrounding insert is missing. > > > > > > Thanks for the report. > > > > > > Can you please be more specific. 2.1.2 compared to what? 2.1.1? > 2.0.8.1? > > > What is a LaTeX insert? Do you mean an ERT box? Can you give specific > > > instructions for how to reproduce? e.g. 1. Go to Insert > TeX Code. 2. > > > Write "$\alpha"$ in the ERT. 3. Select the box and copy it. 4... paste > > > it (somewhere specific?) > > > > > > > Sent to me from the user: > > > > The phénomena is observed with the recent LyX 2.1.2 compared to LyX > > 2.0.8.1 on Windows . > > > > The Latex insert is obtained by the command Ctrl+L and filled with some > text. > > > > The copy and paste of the Latex insert is made in the usual way with a > > mouse selection followed by Ctrl+V. > > > > Thanks, Emile. > > > > Scott > FWIW, I tried that on Linux Debian and I couldn't observe what Emile > describes. The ERT box is copied and pasted in the same condition (open > or closed) as it was originally. Windows issue? > -- > Daniel CLEMENT >
Re: Matching math font with TG Pagella
Guenter Milde wrote: > This is how I would do it. > > Alternatively, you could also load Palatino in the font dialogue > and overwrite the text font with tgpagella in the preamble > > \usepackage{tgpagella} > > This would result in the standard "mathpazo" symbols and fonts for formulae > and TG Pagella in the text. > > With XeTeX/LuaTeX, you can use "unicode-math" with the Asana-Math fonts for > maths and the OpenType Pagella for text. It would be pretty trivial to add support for newpxmath to LyX (although it involves a file format change). You can take this as a model: http://www.lyx.org/trac/changeset/a84a98b5/lyxgit/ Jürgen
Re: citation style
Wolfgang Engelmann wrote: > Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen
Re: citation style
I am awful sorry, I sent the wrong file. Wolfgang Am 04.10.2014 um 10:47 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen TestA.lyx Description: application/lyx
Re: citation style
This was indeed something which should not happen: to send the original file from which I had prepared the short one. It should at least not have gone to the list! There is no excuse, but the publisher wants the proof reading done in such a short time, that I was too nervous (and too old, by the way). Must donate to the LyX people... Wolfgang, full of shame Am 04.10.2014 um 11:08 schrieb Wolfgang Engelmann: I am awful sorry, I sent the wrong file. Wolfgang Am 04.10.2014 um 10:47 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: Here are the examples. Please send a _minimal_ example file. This one has over 60 pages, and I would need to delete a dozens of unavailable graphics first. http://wiki.lyx.org/FAQ/MinimalExample Jürgen
Re: citation style
Wolfgang Engelmann wrote: > I am awful sorry, I sent the wrong file. Wolfgang By default, natbib does not provide a citation command with author-year in parathesis and no comma between author and year. An workaround is to use the citation command with comma and pass the following to the preamble: \setcitestyle{aysep={}} This will remove the comma between author and year globally in the output. If you want the comma to be omitted in the LyX view as well, paste the following to Document > Local Format, hit "Validate" and "OK" (you might need to restart to see the effect): CiteFormat authoryear !open ( !sep ; !close ) !citet %!startlink%%!abbrvauthor%%!endlink% %!open%%!textbefore%%!year%%!nextcitet% !citealt %!startlink%%!abbrvauthor% %!textbefore%%!year%%!endlink%%!nextcitealt% !citealp %!startlink%%!abbrvauthor% %!year%%!endlink%%!nextcitealp% !nextcitet {%next%[[%!close%%!sep% %!citet%]]} !nextcitealt {%next%[[%!sep% %!citealt%]]} !nextcitealp {%next%[[%!sep% %!citealp%]]} cite %!citet%%!textafter%%!close% citep %!open%%!textbefore%%!citealp%%!textafter%%!close% citealp %!textbefore%%!citealp%%!textafter% citeauthor %!startlink%%!abbrvauthor%%!endlink%%!nextauthor%%!textafter% citeyear %!startlink%%!year%%!endlink%%!nextyear%%!textafter% End HTH, Jürgen
Re: citation style
Thanks, Jürgen, for the workaround. Since this will remove the commata between author and year globally, I decided to leave is to the Publisher. I am not willing to wreck my nerves and spill my time for the shareholders. But I appreciated your help very much, Yours Wolfgang Am 04.10.2014 um 11:34 schrieb Jürgen Spitzmüller: Wolfgang Engelmann wrote: I am awful sorry, I sent the wrong file. Wolfgang By default, natbib does not provide a citation command with author-year in parathesis and no comma between author and year. An workaround is to use the citation command with comma and pass the following to the preamble: \setcitestyle{aysep={}} This will remove the comma between author and year globally in the output. If you want the comma to be omitted in the LyX view as well, paste the following to Document > Local Format, hit "Validate" and "OK" (you might need to restart to see the effect): CiteFormat authoryear !open ( !sep ; !close ) !citet %!startlink%%!abbrvauthor%%!endlink% %!open%%!textbefore%%!year%%!nextcitet% !citealt %!startlink%%!abbrvauthor% %!textbefore%%!year%%!endlink%%!nextcitealt% !citealp %!startlink%%!abbrvauthor% %!year%%!endlink%%!nextcitealp% !nextcitet {%next%[[%!close%%!sep% %!citet%]]} !nextcitealt {%next%[[%!sep% %!citealt%]]} !nextcitealp {%next%[[%!sep% %!citealp%]]} cite %!citet%%!textafter%%!close% citep %!open%%!textbefore%%!citealp%%!textafter%%!close% citealp %!textbefore%%!citealp%%!textafter% citeauthor %!startlink%%!abbrvauthor%%!endlink%%!nextauthor%%!textafter% citeyear %!startlink%%!year%%!endlink%%!nextyear%%!textafter% End HTH, Jürgen
Re: How To Turn Off Auto-fill in Table Cells?
On Sat, 4 Oct 2014, Jürgen Spitzmüller wrote: Actually, it's possible. In Tools > Preferences > Edit > Shortcuts, you can find the following command sequence bound to "Tab": "command-alternatives completion-accept;cell-forward;tab-insert;depth- increment;outline-in" If you swap completion-accept and cell-forward, you should get the desired behavior. Jürgen, Thank you, I'll do that. Something changed in version 2.1.x that took tab movement away from tables. Perhaps that change can be identified and reversed. This definition is 6 years old. Interesting. I've not experienced this behavior before this one document. Much appreciated, Rich
Re: Failed compilation succeeds from command line: two problems
On Oct 4, 2014 9:54 AM, "Jürgen Spitzmüller"wrote: > > stefano franchi wrote: > > > Both cannot. The command line simply allows you to ignore the error with > > > whatever visible or invisible consequences this has. LyX does not let you > > > get > > > away with it. The error needs to be fixed anyway. > > > > I understand that, but why is this? > > Why not? Sorry my message got truncated. What I meant to say was: Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. S. > > Jürgen
Re: Failed compilation succeeds from command line: two problems
On Oct 4, 2014 11:57 AM, "stefano franchi"wrote: > > > On Oct 4, 2014 9:54 AM, "Jürgen Spitzmüller" wrote: > > > > stefano franchi wrote: > > > > Both cannot. The command line simply allows you to ignore the error with > > > > whatever visible or invisible consequences this has. LyX does not let you > > > > get > > > > away with it. The error needs to be fixed anyway. > > > > > > I understand that, but why is this? > > > > Why not? > > Sorry my message got truncated. What I meant to say was: > Why does LyX fail compilation when programs like kile are able to continue past the error? It does not seem to be a technical constraint but a conscious decision. > > I understand that the error will need to be fixed sooner or later. But in some tricky cases (like this one) the error may hard to find. Indeed I have already spent four hour bisecting my document and I haven't pinned it down yet. As I keep looking, my only choice to keep working on the content is to export to latex and compile from command line or form mile. Wouldn't it be better to emulate the latter behavior in LyX? Unless I'm wrong about the technical constraints, of course. I meant "from kile" ! Damned autocorrect > > S. > > > > > Jürgen
Re: Failed compilation succeeds from command line: two problems
On Sat, Oct 4, 2014 at 12:57 PM, stefano franchiwrote: > > On Oct 4, 2014 9:54 AM, "Jürgen Spitzmüller" wrote: >> >> stefano franchi wrote: >> > > Both cannot. The command line simply allows you to ignore the error >> > > with >> > > whatever visible or invisible consequences this has. LyX does not let >> > > you >> > > get >> > > away with it. The error needs to be fixed anyway. >> > >> > I understand that, but why is this? >> >> Why not? > > Sorry my message got truncated. What I meant to say was: > Why does LyX fail compilation when programs like kile are able to continue > past the error? It does not seem to be a technical constraint but a > conscious decision. > > I understand that the error will need to be fixed sooner or later. But in > some tricky cases (like this one) the error may hard to find. Indeed I have > already spent four hour bisecting my document and I haven't pinned it down > yet. As I keep looking, my only choice to keep working on the content is to > export to latex and compile from command line or form mile. Wouldn't it be > better to emulate the latter behavior in LyX? Unless I'm wrong about the > technical constraints, of course. The answer to "Why?", as Jürgen stated, is that it is important that the user knows that there is an error so that the error can be fixed as soon as possible. It would be irresponsible of LyX not to make sure you know that a command failed. You might think then that we could just issue a warning, but I don't think things are that simple (as a permanent LyX solution). For example, if a document is exported from LyX on the command line, the warning is shown but there is a non-zero exit code so such a user might not realize there is a problem. I understand your argument, Stefano. It is a reasonable one and also a common one. For example, if you have a deadline to meet and a certain error that you think might not even affect the output of the PDF (and even if there is a chance, you could proof check the PDF manually), you just want your PDF and don't have time to think about fixing a possibly minor error. However, I think this is a feature request and not a bug. You might want to open a trac ticket because this type of conversation comes up from time to time and is likely to come up very often in 2.2 if we start stopping compilation when BibTeX errors occur (see http://www.lyx.org/trac/ticket/2757). Input from your side of the debate is important since we don't have any developer currently defending that (popular) feature request and it is important to understand and try to accommodate all workflows. If you do open a feature request, please mention exactly how Kile handles the situation. It's very useful to compare LyX with other programs and in this case appears to strengthen your argument. Off topic, this is an example of why versioning is useful. I use git and whenever I come across such a complicated issue, I just look at the differences between my current revision and the last "good" revision. I hope you get this frustrating issue figured out soon. It certainly sounds annoying. Scott
Re: Failed compilation succeeds from command line: two problems
On 04/10/2014 3:23 PM, Scott Kostyshak wrote: I understand your argument, Stefano. It is a reasonable one and also a common one. For example, if you have a deadline to meet and a certain error that you think might not even affect the output of the PDF (and even if there is a chance, you could proof check the PDF manually), you just want your PDF and don't have time to think about fixing a possibly minor error. However, I think this is a feature request and not a bug. You might want to open a trac ticket because this type of conversation comes up from time to time and is likely to come up very often in 2.2 if we start stopping compilation when BibTeX errors occur (see http://www.lyx.org/trac/ticket/2757). Input from your side of the debate is important since we don't have any developer currently defending that (popular) feature request and it is important to understand and try to accommodate all workflows. FWIW I also think we should have a compilation mode which keeps going as far as possible. Of course, it would be a opt-in setting (could be a dialog asking to continue in the GUI and a --force option on the command line). Cheers, Julien
Re: copy and paste of latex insert
On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien
Re: copy and paste of latex insert
You are right, the same phenomena occurs on Windows with Math inserts ! 2014-10-04 21:59 GMT+02:00 Julien Rioux: > On 04/10/2014 4:35 AM, emile lunardon wrote: > >> I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 >> is not present on the same version of LyX compilled on Linux Mint LMDE >> (Debian based distribution). >> >> > I've seen similar strange behavior with copy/paste in LyX on Windows 7: > Copy-pasting insets inserts only the inner text, copy-pasting math would > paste the latex commands, etc. It seems to happen when I restart from > hibernation mode, but I never could narrow it down further to > reproduce it consistently. The earliest instance dates back to LyX 2.0.x > but I can't remember if it happened even before. > > -- > Julien > >
Re: copy and paste of latex insert
On 5/10/2014 9:21 a.m., emile lunardon wrote: You are right, the same phenomena occurs on Windows with Math inserts ! 2014-10-04 21:59 GMT+02:00 Julien Rioux>: On 04/10/2014 4:35 AM, emile lunardon wrote: I confirm that the bug I observed with LyX 2.1.2 running on Windows 8.1 is not present on the same version of LyX compilled on Linux Mint LMDE (Debian based distribution). I've seen similar strange behavior with copy/paste in LyX on Windows 7: Copy-pasting insets inserts only the inner text, copy-pasting math would paste the latex commands, etc. It seems to happen when I restart from hibernation mode, but I never could narrow it down further to reproduce it consistently. The earliest instance dates back to LyX 2.0.x but I can't remember if it happened even before. -- Julien FWIW, I'm using Windows 7 & LyX 2.1.2 and have just "awoken" from hibernation. Copy & paste of ERT insets & math insets proceeds as it should, both inset & contents, in both a new document and a large existing one. I sometimes find that after restarting LyX, or even restarting Windows, various anomalous behaviours vanish. Andrew --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com