Re: Fwd: Nomenclature in TOC different/unexpected in LyX2.1 vs Lyx2,2.2

2016-10-26 Thread Jürgen Spitzmüller
Am Mittwoch, den 26.10.2016, 13:13 +0200 schrieb Michael Berger: > Beat me - I do not recall how and why it got there but killing it > solved my problem: see snapshot. > Is this line of any use ever or may I scrap it for good? I think you can safely remove it since you already add this header to t

Re: Fwd: Nomenclature in TOC different/unexpected in LyX2.1 vs Lyx2,2.2

2016-10-26 Thread Michael Berger
On 10/26/2016 09:55 AM, Jürgen Spitzmüller wrote: Am Mittwoch, den 26.10.2016, 08:07 +0200 schrieb Michael Berger: Dear developers, I am forwarding my initial e-mail to you because I found that the behavior described is not specific to classicthesis. Other document classes (I checked Komascript

Re: Fwd: Nomenclature in TOC different/unexpected in LyX2.1 vs Lyx2,2.2

2016-10-26 Thread Michael Berger
On 10/26/2016 09:55 AM, Jürgen Spitzmüller wrote: Am Mittwoch, den 26.10.2016, 08:07 +0200 schrieb Michael Berger: Dear developers, I am forwarding my initial e-mail to you because I found that the behavior described is not specific to classicthesis. Other document classes (I checked Komascript

Re: Fwd: Nomenclature in TOC different/unexpected in LyX2.1 vs Lyx2,2.2

2016-10-26 Thread Jürgen Spitzmüller
Am Mittwoch, den 26.10.2016, 08:07 +0200 schrieb Michael Berger: > Dear developers, > I am forwarding my initial e-mail to you because I found that the > behavior described is not specific to classicthesis. > Other document classes (I checked Komascript Article and Article > Standard) show a simila

Fwd: Nomenclature in TOC different/unexpected in LyX2.1 vs Lyx2,2.2

2016-10-25 Thread Michael Berger
Dear developers, I am forwarding my initial e-mail to you because I found that the behavior described is not specific to classicthesis. Other document classes (I checked Komascript Article and Article Standard) show a similar behavior. That makes me believe it is a LyX 2.2.2 , 2.2.x etc. is