Re: Layout Style: Display as Uppercase?

[Joel Kulesza]

On Wed, Dec 7, 2016 at 3:42 PM, Scott Kostyshak  wrote:

> On Wed, Dec 07, 2016 at 02:32:00PM -0700, Joel Kulesza wrote:
> > Colleagues:
> >
> > Is there a way to adjust the Font of a Style in a .layout to display as
> > UPPERCASE in LyX?
> >
> > I cannot see a way to do this in Help -> Customization --- have I
> > overlooked something?
> >
> > I am trying to get LyX to match the appearance of an associated .cls file
> > which converts all \section{...} entries to uppercase in the document.
>
> The feature does not currently exist. I have come across the same issue
> in the past. I think that there are conceptual issues and it is not
> clear we want to implement it. See the ticket here:
> http://www.lyx.org/trac/ticket/9489
> If you can respond to the concern there then maybe it would be
> reconsidered.


Thank you for confirming that the ability is absent and for pointing me to
that ticket.  Indeed, I understand the point raised that representing
non-uppercase text as uppercase would be misleading.  It would go against
WYSIWYM.  However, one might approach WYSIWYM from two directions: that of
the user and that of the publisher.  I believe the ticket to be written
from the perspective of the user and his/her interaction with LyX (if they
mean for uppercase, they should use/see it).

In my case, I'm trying to make a .layout such that a user can work within
LyX and use a publisher-provided class file.  The publisher-defined style
for \section is uppercase.  As such, all I'm looking for is the ability for
the .layout/LyX to interpret \section as uppercase and display it as such
regardless of the user's preference because that is what the publisher
means.  That will, hopefully, also (a) save the user a bit of time to not
have to capitalize the \section and (b) eliminate confusion/inconsistency
between LyX and what is produced as camera-ready (which is non-negotiable).

To avoid the "loss of information" cited in the ticket, I would propose
converting the case to uppercase as the section heading is typed so that
any subsequent copy/paste would be uppercase.  One might also disable the
relevant Edit -> Text Style entries for so-flagged layout styles.

Two asides:

   1. What is the prevailing opinion on the Edit -> Text Style submenu?  I
   would really like to see the lowercase/uppercase/capitalize options move
   into the Text style dialog (accessible from the Edit -> Text Style ->
   Customize entry).  This would seem to logically collect text
   manipulation/appearance operations.
   2. What is the functional difference between Text style -> Misc -> Noun
   vs. Text style -> Shape -> Small caps?  Looking at the LaTeX source with
   both, they appear to do the same thing.  Am I overlooking something or
   thinking too LaTeX-centric?

Thanks,
Joel

Re: TODO notes (double entries) in LyX 2.2.2 on Windows 10

[Richard Heck]

On 12/07/2016 08:14 PM, Cris Fuhrman wrote:
> My first email had an attachment of a lyx file (perhaps it didn't go
> through?)
>
> Anyway, it's definitely a bug in TODO notes... I even think I found
> the bug in the source
> at https://github.com/henrikmidtiby/todonotes/issues/22 (see my comment).

So it looks as if this is a bug in the LaTeX package, then, not in LyX?

Richard


>
> On Wed, Dec 7, 2016 at 6:43 PM, Richard Heck  > wrote:
>
> On 12/01/2016 11:14 AM, Cris Fuhrman wrote:
>> I've recently noticed an odd behavior of TODO Notes in LyX 2.2.2.
>> I enabled the fancyline option, and I saw I was getting two
>> lines. Upon further debugging (using author= and size=\tiny), I
>> can prove that it's actually generating two TODO notes at the
>> same place. Here's a screen grab:
>>
>> Inline image 1
>> I'm attaching the minimal example (used in LyX 2.2.2 under
>> Windows 10). I updated my MikTeX yesterday to see if it would go
>> away, but no luck. It's reproducible on BOTH my Windows 10
>> machines with LyX.
>>
>> I searched for todonotes modules (as I used it before prior to
>> LyX 2.2 before it was part of the distribution), but I couldn't
>> find anything in my LyX path directories that looked like a
>> duplicate. I'm not sure how this is happening.
>>
>> When I paste the LaTeX source from LyX (pasted below) into a
>> TeXstudio document, it works perfectly, so I don't think it's my
>> TeX installation.
>
> That's pretty strange. Can you post an example file?
>
> Richard
>
>

Re: TODO notes (double entries) in LyX 2.2.2 on Windows 10

[Cris Fuhrman]

My first email had an attachment of a lyx file (perhaps it didn't go
through?)

Anyway, it's definitely a bug in TODO notes... I even think I found the bug
in the source at https://github.com/henrikmidtiby/todonotes/issues/22 (see
my comment).

On Wed, Dec 7, 2016 at 6:43 PM, Richard Heck  wrote:

> On 12/01/2016 11:14 AM, Cris Fuhrman wrote:
>
> I've recently noticed an odd behavior of TODO Notes in LyX 2.2.2. I
> enabled the fancyline option, and I saw I was getting two lines. Upon
> further debugging (using author= and size=\tiny), I can prove that it's
> actually generating two TODO notes at the same place. Here's a screen grab:
>
> [image: Inline image 1]
> I'm attaching the minimal example (used in LyX 2.2.2 under Windows 10). I
> updated my MikTeX yesterday to see if it would go away, but no luck. It's
> reproducible on BOTH my Windows 10 machines with LyX.
>
> I searched for todonotes modules (as I used it before prior to LyX 2.2
> before it was part of the distribution), but I couldn't find anything in my
> LyX path directories that looked like a duplicate. I'm not sure how this is
> happening.
>
> When I paste the LaTeX source from LyX (pasted below) into a TeXstudio
> document, it works perfectly, so I don't think it's my TeX installation.
>
>
> That's pretty strange. Can you post an example file?
>
> Richard
>
>

Re: TODO notes (double entries) in LyX 2.2.2 on Windows 10

[Richard Heck]

On 12/01/2016 11:14 AM, Cris Fuhrman wrote:
> I've recently noticed an odd behavior of TODO Notes in LyX 2.2.2. I
> enabled the fancyline option, and I saw I was getting two lines. Upon
> further debugging (using author= and size=\tiny), I can prove that
> it's actually generating two TODO notes at the same place. Here's a
> screen grab:
>
> Inline image 1
> I'm attaching the minimal example (used in LyX 2.2.2 under Windows
> 10). I updated my MikTeX yesterday to see if it would go away, but no
> luck. It's reproducible on BOTH my Windows 10 machines with LyX.
>
> I searched for todonotes modules (as I used it before prior to LyX 2.2
> before it was part of the distribution), but I couldn't find anything
> in my LyX path directories that looked like a duplicate. I'm not sure
> how this is happening.
>
> When I paste the LaTeX source from LyX (pasted below) into a TeXstudio
> document, it works perfectly, so I don't think it's my TeX installation.

That's pretty strange. Can you post an example file?

Richard

Re: Layout Style: Display as Uppercase?

[Scott Kostyshak]

On Wed, Dec 07, 2016 at 02:32:00PM -0700, Joel Kulesza wrote:
> Colleagues:
> 
> Is there a way to adjust the Font of a Style in a .layout to display as
> UPPERCASE in LyX?
> 
> I cannot see a way to do this in Help -> Customization --- have I
> overlooked something?
> 
> I am trying to get LyX to match the appearance of an associated .cls file
> which converts all \section{...} entries to uppercase in the document.

The feature does not currently exist. I have come across the same issue
in the past. I think that there are conceptual issues and it is not
clear we want to implement it. See the ticket here:
http://www.lyx.org/trac/ticket/9489
If you can respond to the concern there then maybe it would be
reconsidered.

Scott


signature.asc
Description: PGP signature

Re: SIGSEGV crahsed

[Scott Kostyshak]

On Wed, Dec 07, 2016 at 06:51:18PM +0100, Patrick Dupre wrote:

> > Thanks for the backtrace, but I don't think it's useful as is. Are you
> > familiar with gdb by chance?
> not too much!

OK, well it is easy to tell you what to do in gdb. The other issue is we
have to make sure you have debug symbols. Are LyX's debug symbols
available in a separate package that you can install on Fedora? For
example, on Ubuntu they are in the package lyx-dbg.

> > What is your OS?
> fedora 24
> > Have you compiled LyX?
> No

OK. We can still probably debug the problem without it.

> lyx-2.2.2-1.fc24.x86_64
> > What LyX version are you using?
> > When exactly does the crash occur (right after you click "open")?
> I had a recent file loaded,
> than I open recent file which have been edited with lyx 2.2.2
> #LyX 2.1 created this file. For more info see http://www.lyx.org/
> \lyxformat 474
> it was edited for the last file in october 2015
> 
> Now, if I do the opposite:
> First open the old file and then the recent one, there is not crash.

I see. And can you reproduce only if you open from the recent files?
What if you navigate manually from the File > Open dialog?

> > Are you able to reproduce it? e.g. if you try to open (in
> > the same way) the same document that caused the crash does it crash
> > again?
> 
> Probably, at least it happen 2 times the way. However, in the mean time, I 
> edited the recent file (2.2.2)

OK good. If you can't reproduce, then it is hard to debug.

Scott


signature.asc
Description: PGP signature

Layout Style: Display as Uppercase?

[Joel Kulesza]

Colleagues:

Is there a way to adjust the Font of a Style in a .layout to display as
UPPERCASE in LyX?

I cannot see a way to do this in Help -> Customization --- have I
overlooked something?

I am trying to get LyX to match the appearance of an associated .cls file
which converts all \section{...} entries to uppercase in the document.

Thank you,
Joel

Re: SIGSEGV crahsed

[Patrick Dupre]

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Wednesday, December 07, 2016 at 6:35 PM
> From: "Scott Kostyshak" 
> To: lyx-users@lists.lyx.org
> Subject: Re: SIGSEGV crahsed
>
> On Wed, Dec 07, 2016 at 11:14:24AM +0100, Patrick Dupre wrote:
> > Hello,
> > 
> > I still have issue with lyx: crashes.
> 
> My memory is horrible. Are you referencing another thread?
Yes,
But it is the first for a while (6 months ?), at least the first one with 
lyx 2.2.2
> > It typical happen when I have a recent document opened and that I
> > want to open an older document (typically 1 year!)
> 
> Thanks for the backtrace, but I don't think it's useful as is. Are you
> familiar with gdb by chance?
not too much!
> What is your OS?
fedora 24
> Have you compiled LyX?
No
lyx-2.2.2-1.fc24.x86_64
> What LyX version are you using?
> When exactly does the crash occur (right after you click "open")?
I had a recent file loaded,
than I open recent file which have been edited with lyx 2.2.2
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
it was edited for the last file in october 2015

Now, if I do the opposite:
First open the old file and then the recent one, there is not crash.


> Are you able to reproduce it? e.g. if you try to open (in
> the same way) the same document that caused the crash does it crash
> again?

Probably, at least it happen 2 times the way. However, in the mean time, I 
edited the recent file (2.2.2)
> Sorry for the frustration. It's not fun when a program consistently
> crashes while you are doing work. Hopefully we can figure out what's
> going on.

I had the same problem, a while ago, but again, it did happen for the 1st time
with 2.2.2

> Scott
>

Re: SIGSEGV crahsed

[Scott Kostyshak]

On Wed, Dec 07, 2016 at 11:14:24AM +0100, Patrick Dupre wrote:
> Hello,
> 
> I still have issue with lyx: crashes.

My memory is horrible. Are you referencing another thread?

> It typical happen when I have a recent document opened and that I
> want to open an older document (typically 1 year!)

Thanks for the backtrace, but I don't think it's useful as is. Are you
familiar with gdb by chance?
What is your OS?
Have you compiled LyX?
What LyX version are you using?
When exactly does the crash occur (right after you click "open")?
Are you able to reproduce it? e.g. if you try to open (in
the same way) the same document that caused the crash does it crash
again?

Sorry for the frustration. It's not fun when a program consistently
crashes while you are doing work. Hopefully we can figure out what's
going on.

Scott


signature.asc
Description: PGP signature

Re: Rolling lists in Beamer

[Jürgen Spitzmüller]

2016-12-07 16:37 GMT+01:00 Rudi Gaelzer :

> I see.  Anyhoo, it's good to learn about all possibilities.
> Thanks again.
>
> Since we're talking about beamer and you seem a proficient user, another
> tweak
> I've been struggling to implement is a better control on the positioning of
> objects such as figures or boxes that will remain fixed at a given position
> whereas the remaining of the slide wraps around it.
>
> I've obtained a partial success with the wrap figure float, which call the
> wrapfig pack, but I don't really have a total control on the positioning
> (since it's a "float" after all) and the outcome is less than satisfactory.
>
> Some people report success using the cutwin package, others recommend
> pgf-tkiz
> for figures and/or textpos for boxes.  I still haven't come around finding
> time to test all possibilities, though. Do you have any suggestion on this
> regard?
>

I usually use the picture environment (and \put) to position stuff.

Jürgen

Re: Rolling lists in Beamer

[Rudi Gaelzer]

I see.  Anyhoo, it's good to learn about all possibilities.
Thanks again.

Since we're talking about beamer and you seem a proficient user, another tweak 
I've been struggling to implement is a better control on the positioning of 
objects such as figures or boxes that will remain fixed at a given position 
whereas the remaining of the slide wraps around it.

I've obtained a partial success with the wrap figure float, which call the 
wrapfig pack, but I don't really have a total control on the positioning 
(since it's a "float" after all) and the outcome is less than satisfactory.

Some people report success using the cutwin package, others recommend pgf-tkiz 
for figures and/or textpos for boxes.  I still haven't come around finding 
time to test all possibilities, though. Do you have any suggestion on this 
regard?

On quarta-feira, 7 de dezembro de 2016 15:56:28 BRST Jürgen Spitzmüller wrote:
> 2016-12-07 15:16 GMT+01:00 Rudi Gaelzer :
> > The "clever" implementation is IMHO the most elegant solution, but there
> > are
> > some subtle differences in the rolling behavior.  The most evident is that
> > with the "clever" rolling list, one has to continue changing slides until
> > the
> > only item remaining is the last.  Do you know if there's some "cleverer"
> > way
> > to avoid that?
> 
> Yes, but it is not as "clever" anymore. See attachment.
> 
> Jürgen

-- 
Rudi Gaelzer
Institute of Physics
Federal University of Rio Grande do Sul
BRAZIL
Registered linux user # 153741

Re: Rolling lists in Beamer

[Jürgen Spitzmüller]

2016-12-07 15:16 GMT+01:00 Rudi Gaelzer :

> The "clever" implementation is IMHO the most elegant solution, but there
> are
> some subtle differences in the rolling behavior.  The most evident is that
> with the "clever" rolling list, one has to continue changing slides until
> the
> only item remaining is the last.  Do you know if there's some "cleverer"
> way
> to avoid that?


Yes, but it is not as "clever" anymore. See attachment.

Jürgen


roll_list6.lyx
Description: application/lyx

Re: Rolling lists in Beamer

[Rudi Gaelzer]

Hi Jürgen.
Thank you for your reply.
Your improved rolling list solution is what I was looking for.  I was trying 
to implement the same result using Edit -> Text Style -> Only, but in this 
case the result is different. 

Your "clever" rolling list solution is the implementation of the other 
suggestion from the site.  That one I was able to implement exactly as you 
did.

What I was really interested in were rolling lists that contain nested lists 
with items that themselves are supposed to appear only in certain slides.
I was able to implement that result inserting the "only@" clause in the item 
overlay specification for those particular nested items.  See the attached 
file with my tweaks.

The "clever" implementation is IMHO the most elegant solution, but there are 
some subtle differences in the rolling behavior.  The most evident is that 
with the "clever" rolling list, one has to continue changing slides until the 
only item remaining is the last.  Do you know if there's some "cleverer" way 
to avoid that?

Anyway, thanks again.
As I learn new things about the beamer class the more impressed I become with 
its flexibility.


On quarta-feira, 7 de dezembro de 2016 12:41:44 BRST Jürgen Spitzmüller wrote:
> 2016-12-07 12:19 GMT+01:00 Rudi Gaelzer :
> > Has anyone implemented with Lyx-Beamer any of the "rolling lists"
> > discussed
> > here(?):
> > http://tex.stackexchange.com/questions/69609/rolling-> > 
> > bullet-points-in-beamer
> > 
> > I can implement the first example, but with heavy ERTing (see attached).
> > I'm just wondering if anyone has a more elegant implementation...
> 
> See attachement for two possible solutions.
> 
> Jürgen
> 
> > --
> > Rudi Gaelzer
> > Institute of Physics
> > Federal University of Rio Grande do Sul
> > BRAZIL
> > Registered linux user # 153741

-- 
Rudi Gaelzer
Institute of Physics
Federal University of Rio Grande do Sul
BRAZIL
Registered linux user # 153741

roll_list5.lyx
Description: application/lyx

Re: Rolling lists in Beamer

[Jürgen Spitzmüller]

2016-12-07 12:19 GMT+01:00 Rudi Gaelzer :

> Has anyone implemented with Lyx-Beamer any of the "rolling lists" discussed
> here(?):
> http://tex.stackexchange.com/questions/69609/rolling-
> bullet-points-in-beamer
>
> I can implement the first example, but with heavy ERTing (see attached).
> I'm just wondering if anyone has a more elegant implementation...
>


See attachement for two possible solutions.

Jürgen


> --
> Rudi Gaelzer
> Institute of Physics
> Federal University of Rio Grande do Sul
> BRAZIL
> Registered linux user # 153741


roll_list2.lyx
Description: application/lyx

Rolling lists in Beamer

[Rudi Gaelzer]

Has anyone implemented with Lyx-Beamer any of the "rolling lists" discussed 
here(?):
http://tex.stackexchange.com/questions/69609/rolling-bullet-points-in-beamer

I can implement the first example, but with heavy ERTing (see attached).
I'm just wondering if anyone has a more elegant implementation...
-- 
Rudi Gaelzer
Institute of Physics
Federal University of Rio Grande do Sul
BRAZIL
Registered linux user # 153741

roll_list.lyx
Description: application/lyx

SIGSEGV crahsed

[Patrick Dupre]

Hello,

I still have issue with lyx: crashes.

It typical happen when I have a recent document opened and that I
want to open an older document (typically 1 year!)

(  1) lyx: lyx(+0x58ffbf) [0x560f8491dfbf]
(  2) lyx: lyx(+0x5f227e) [0x560f8498027e]
(  3) lyx: lyx(+0x58ec70) [0x560f8491cc70]
(  4) lyx: lyx(+0x2684a8) [0x560f845f64a8]
(  5) /lib64/libc.so.6: /lib64/libc.so.6(+0x347e0) [0x7f54ca7677e0]
(  6) lyx: lyx(+0x326310) [0x560f846b4310]
(  7) lyx: lyx(+0x327cdc) [0x560f846b5cdc]
(  8) lyx: lyx(+0x328508) [0x560f846b6508]
(  9) lyx: lyx(+0x5681c3) [0x560f848f61c3]
( 10) lyx: lyx(+0x4a3fa2) [0x560f84831fa2]
( 11) lyx: lyx(+0x327a9f) [0x560f846b5a9f]
( 12) lyx: lyx(+0x36fd08) [0x560f846fdd08]
( 13) lyx: lyx(+0x5e8cd4) [0x560f84976cd4]
( 14) lyx: lyx(+0x5e5041) [0x560f84973041]
( 15) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, void**)
( 16) /lib64/libQt5Widgets.so.5: QTabWidget::currentChanged(int)
( 17) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x315007) 
[0x7f54cc248007]
( 18) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, void**)
( 19) /lib64/libQt5Widgets.so.5: QTabBar::currentChanged(int)
( 20) /lib64/libQt5Widgets.so.5: QTabBar::setCurrentIndex(int)
( 21) lyx: lyx(+0x5e51c7) [0x560f849731c7]
( 22) lyx: lyx(+0x5bf967) [0x560f8494d967]
( 23) lyx: lyx(+0x5c34ef) [0x560f849514ef]
( 24) lyx: lyx(+0x5c36e8) [0x560f849516e8]
( 25) lyx: lyx(+0x5c539e) [0x560f8495339e]
( 26) lyx: lyx(+0x59efed) [0x560f8492cfed]
( 27) lyx: lyx(+0x5965fa) [0x560f849245fa]
( 28) lyx: lyx(+0x620e7d) [0x560f849aee7d]
( 29) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, void**)
( 30) /lib64/libQt5Widgets.so.5: QAction::triggered(bool)
( 31) /lib64/libQt5Widgets.so.5: QAction::activate(QAction::ActionEvent)
( 32) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2e131a) 
[0x7f54cc21431a]
( 33) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2e753c) 
[0x7f54cc21a53c]
( 34) /lib64/libQt5Widgets.so.5: QMenu::mouseReleaseEvent(QMouseEvent*)
( 35) /lib64/libQt5Widgets.so.5: QWidget::event(QEvent*)
( 36) /lib64/libQt5Widgets.so.5: QMenu::event(QEvent*)
( 37) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
( 38) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
( 39) lyx: lyx(+0x5a10fc) [0x560f8492f0fc]
( 40) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
QEvent*)
( 41) /lib64/libQt5Widgets.so.5: QApplicationPrivate::sendMouseEvent(QWidget*, 
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool)
( 42) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bd8f8) 
[0x7f54cc0f08f8]
( 43) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bfc73) 
[0x7f54cc0f2c73]
( 44) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
( 45) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
( 46) lyx: lyx(+0x5a10fc) [0x560f8492f0fc]
( 47) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
QEvent*)
( 48) /lib64/libQt5Gui.so.5: 
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
( 49) /lib64/libQt5Gui.so.5: 
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
( 50) /lib64/libQt5Gui.so.5: 
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
( 51) /lib64/libQt5XcbQpa.so.5: /lib64/libQt5XcbQpa.so.5(+0x71600) 
[0x7f54bbc0e600]
( 52) /lib64/libglib-2.0.so.0: 
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x15a) [0x7f54ccca16ba]
( 53) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x49a70) 
[0x7f54ccca1a70]
( 54) /lib64/libglib-2.0.so.0: 
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f54ccca1b1c]
( 55) /lib64/libQt5Core.so.5: 
QEventDispatcherGlib::processEvents(QFlags)
( 56) /lib64/libQt5Core.so.5: 
QEventLoop::exec(QFlags)
( 57) /lib64/libQt5Core.so.5: QCoreApplication::exec()
( 58) lyx: lyx(+0x27088d) [0x560f845fe88d]
( 59) lyx: lyx(+0x11cdf1) [0x560f844aadf1]
( 60) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xf1) 
[0x7f54ca753731]
( 61) lyx: lyx(+0x125aa9) [0x560f844b3aa9]


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===