default dir when save for first time is not cwd

[Scott Kostyshak]

Currently if you start a new document and save, the default directory in
the save dialog is the home directory. This is true even if I start lyx
from a different directory. I would prefer for the default directory to
be the current working directory.

Has this been discussed before?

Scott


signature.asc
Description: PGP signature

2.2.2-staging Merged to 2.2.x

[Richard Heck]

I have merged 2.2.2-staging into 2.2.x now, so all commits for stable 
should now go to 2.2.x.


Richard

Re: scrunched radio buttons on message pane

[Scott Kostyshak]

On Wed, Jun 15, 2016 at 08:13:54PM +, Paul A. Rubin wrote:
> Scott Kostyshak  lyx.org> writes:
> 
> > 
> > On Tue, Jun 14, 2016 at 06:19:27PM +, Paul A. Rubin wrote:
> > > Scott Kostyshak  lyx.org> writes:
> > > 
> > > > 
> > > > Does anyone else see that the radio buttons are cut-off on the message
> > > > pane?
> > > > 
> > > 
> > > FWIW, they're find with LyX 2.2.0 /Qt 4.8.6 on Linux Mint Rebecca.
> > > 
> > > Paul
> > 
> > I forgot to mention: when testing you should try to make the height of
> > the messages pane as small as possible. Does it allow you to go "too"
> > small?
> > 
> 
> Ah,yes. I have to scrunch the window to its absolute minimum height, at
> which point the tops and bottoms of the radio button circles are clipped.
> Even one mouse fart bigger than minimum and the circles are intact.

OK so it is the same then.

Scott

P.S. I just googled "mouse fart" to see if that is an original creation
of yours. I like it.


signature.asc
Description: PGP signature

Re: One official build system?

[Georg Baum]

Kornel Benko wrote:

> Am Dienstag, 14. Juni 2016 um 22:37:58, schrieb Georg Baum
> 
>> The icons and the regex files are indeed a serious problem. The icons
>> should be fixed now, this was simply a wrong style of using variables.
> 
> It does not look like that. Even after ./autogen.sh and configure.

For me the oxygen stuff was missing completely, but now I saw that you added 
some missing icons. Thanks.

>> I'll take
>> care for the regex files later, but what I do not understand is how the
>> official windows build could succeed without these files (because of
>> http://www.lyx.org/trac/ticket/9373). I fear that (again) the official
>> installers were produced from git and not from an unpacked .tar.gz. Or
>> bug 9373 is magically fixed and nobody noticed.
>> 
> 
> I do not understand either.

I fixed the boost packaging. Maybe the windows build did work depsite the 
missing files, at least one was definitely not used.

> Some files are distributed in automake, which we do not want I suppose
> development/lyxserver/perl/LyX-Client-0.01.tar.gz
> development/lyxserver/perl/LyX-Polite-0.01.tar.gz
> src/client/lyxclient.cpp (what is this?)

The last one must be a local file (not in git). You see why I want explicit 
lists? ;-)


Georg

Re: scrunched radio buttons on message pane

[Paul A . Rubin]

Scott Kostyshak  lyx.org> writes:

> 
> On Tue, Jun 14, 2016 at 06:19:27PM +, Paul A. Rubin wrote:
> > Scott Kostyshak  lyx.org> writes:
> > 
> > > 
> > > Does anyone else see that the radio buttons are cut-off on the message
> > > pane?
> > > 
> > 
> > FWIW, they're find with LyX 2.2.0 /Qt 4.8.6 on Linux Mint Rebecca.
> > 
> > Paul
> 
> I forgot to mention: when testing you should try to make the height of
> the messages pane as small as possible. Does it allow you to go "too"
> small?
> 

Ah,yes. I have to scrunch the window to its absolute minimum height, at
which point the tops and bottoms of the radio button circles are clipped.
Even one mouse fart bigger than minimum and the circles are intact.

Paul

Re: [LyX/2.2.x] Make latex highlighter colors compatible with dark theme

[Guillaume Munch]

Le 15/06/2016 20:21, Pavel Sanda a écrit :

uillaume Munch wrote:

commit 5c13007d925bf77cb9c5bc59fec49915653970af
Author: Guillaume Munch 
Date:   Tue Jun 14 21:45:47 2016 +0100

 Make latex highlighter colors compatible with dark theme

 Partial fix for #8325


status.22x entry? p



thanks

Re: [LyX/2.2.x] Make latex highlighter colors compatible with dark theme

[Pavel Sanda]

uillaume Munch wrote:
> commit 5c13007d925bf77cb9c5bc59fec49915653970af
> Author: Guillaume Munch 
> Date:   Tue Jun 14 21:45:47 2016 +0100
> 
> Make latex highlighter colors compatible with dark theme
> 
> Partial fix for #8325

status.22x entry? p

Re: lyx and dark color schemes

[Pavel Sanda]

Liviu Andronic wrote:
> The single most unreadable instance though is blue headings like in Beamer:
> http://i.imgur.com/zoSqWvX.png

Fuuny, I use the same colors but it never occurred to me that this is hard to 
read :)

What can be somewhat annoying is to use branches, because you can't set both
foreground and background. So if you share document with someone who uses
different color set, or even need to use lyx for quick on different machines
you find out that you have to be extra careful what color to pick so both
dark/light regimes work :)

Pavel

Re: lyx and dark color schemes

[Liviu Andronic]

On Wed, Jun 15, 2016 at 5:52 PM, Guillaume Munch  wrote:
> Le 15/06/2016 15:47, Liviu Andronic a écrit :
>>
>> On Wed, Jun 15, 2016 at 3:35 PM, Guillaume Munch  wrote:
>>>
>>> Le 14/06/2016 22:14, Cor Blom a écrit :


 Op 14-06-16 om 22:21 schreef Guillaume Munch:
>
>
> Le 14/06/2016 21:16, Cor Blom a écrit :
>>
>>
>> Op 14-06-16 om 22:09 schreef Guillaume Munch:
>>>
>>>
>>> Le 14/06/2016 18:44, Cor Blom a écrit :


 Hi,

 Recently I tried lyx with a dark color scheme (breeze-dark  under
 kde
 plasma 5). Ihe toolbar icons are problematic, but I know how to fix
 that
 (and the oxygen set is not that bad against a dark background). In
 general I'm happy about it. There is one issue. I don't know whether
 it's possible and I'm missing something, or not.

 Under de Documents > Settings, in the preamble part, blue is used
 for
 code. Against a dark background this is unreadable. Also in the code
 view panel, de latex commands are blue, which makes them
 unreadable. Is
 that color configurable somewhere? I've searched but can't find the
 solution.

 Thanks,

 Cor

>>>
>>> Hi,
>>>
>>> Can you compile master and test a patch I send you?
>>>
>>> Guillaume
>>>
>>>
>>
>> Yes I can.
>>
>> Cor
>>
>>
>

 Thanks! This is a huge improvement. I have now readable purple text
 against the dark background.

>>>
>>> Huh great but I did not intend to make it purple. Can I please have a
>>> screenshot?
>>>
>> Good choice of color for dark schemes. Works well here with
>> Mediterranean (Darkest).
>
>
> This is just (blue + text color)/2...
>
>>
>> I too get something that is (to my eyes) purplish, though I should
>> mention that I'm also running redshift. The color picker says
>> "#6060DF" (or in the whereabouts).
>
>

> Blue then. What about math? And errors (e.g. unencodable characters) ?
>
I the preamble math is fine. Same in the source. Errors are acceptable
(not sure how to trigger unencodable chars though).

Looks good:
http://i.imgur.com/OK2bQpV.png
http://i.imgur.com/m3FdURN.png
http://i.imgur.com/NQQQ9Jz.png

Thanks,
Liviu

Re: [PATCH] unique_ptr and some clean-up

[Pavel Sanda]

Guillaume Munch wrote:
> Le 14/06/2016 21:49, Georg Baum a écrit :
>> Guillaume Munch wrote:
>>
>>> What error is it?
>>
>> ../../src/MetricsInfo.cpp:61:4: error: type ???lyx::MetricsBase??? is not
>> a direct base of ???lyx::MetricsBase???
>
> Thanks for the clues. I was not even aware that delegate constructors
> was a C++11 feature. Master must compile again with 4.6 now.

It does. P

Re: Basic module reloaded (Was: scrunched radio buttons on message pane)

[Scott Kostyshak]

On Wed, Jun 15, 2016 at 01:39:01PM +0100, Jean-Pierre Chrétien wrote:
> Le 15/06/2016 09:13, Scott Kostyshak a écrit :
> > On Wed, Jun 15, 2016 at 09:48:03AM +0100, Jean-Pierre Chrétien wrote:
> 
> > > I've seen this once with 2.2.0, but I can't reproduce, maybe I left open 
> > > an
> > > instance of 2.1.5, I see now
> > > 
> > > ../TextClass.cpp (317): Reading module file: [layouts/basic.module]
> > > ../TextClass.cpp (330): Finished reading module file: 
> > > [layouts/basic.module]
> > > 
> > > when I select LyX initialisation tracking.
> > 
> > I'm not sure about the above. If you can find a way to reproduce it, it
> > would be good to know.
> 
> Can't reproduce now even with 2.1.5.
> But I get these lines
> 
> BufferParams.cpp (2220): setBaseClass: article
> ../TextClass.cpp (317): Reading module file: [layouts/basic.module]
> ../TextClass.cpp (330): Finished reading module file: [layouts/basic.module]
> 
> evety time I open the Document->Settings menu, and apparently, every time
> there is an automatic backup, both with 2.1.5 ans 2.2.0.
> 
> What is specific to this module ?
> 
> Recipe:
> * open LyX
> * select "Texclass file reading" in the message pane parameters
> * Open a new file
> * Select Document->Settings
> 
> Messages are both in the terminal and in the Output window of the message 
> pane.

I see. I can reproduce when checking the "Texclass file reading". I
think these messages are normal, but I don't know much about this stuff.
I'm guessing basic.module is loaded because it is the only one that is
being used. Maybe it is a special module that doesn't appear it the
modules in document settings.

Scott


signature.asc
Description: PGP signature

Re: lyx and dark color schemes

[Richard Heck]

On 06/15/2016 11:48 AM, José Abílio Matos wrote:

On Tuesday, June 14, 2016 9:21:38 PM WEST Guillaume Munch wrote:

latexhighlighter.diff

Could this go to lyx-2.2 as well. I have the same problem with the font
colours but not the panel icons.


OK by me.

Richard

Re: Difference between endnotes and foottoend modules

[Richard Heck]

On 06/15/2016 01:50 PM, Jean-Pierre Chrétien wrote:

Hello,

I'm not sure to have translated the description of these modules all 
right.

* foottoend makes all footnotes endnotes
* endnotes offers an extra inset to add endnotes in addition to plain 
footnotes


If this is right, I must amend my translation of the description of 
endnotes, which is unclear. Too late for 2.1, I will do it for 2.2.x.


Yes, that is right.

rh

Re: Basic module reloaded (Was: scrunched radio buttons on message pane)

[Richard Heck]

On 06/15/2016 01:39 PM, Jean-Pierre Chrétien wrote:

Le 15/06/2016 09:13, Scott Kostyshak a écrit :

On Wed, Jun 15, 2016 at 09:48:03AM +0100, Jean-Pierre Chrétien wrote:


I've seen this once with 2.2.0, but I can't reproduce, maybe I left 
open an

instance of 2.1.5, I see now

../TextClass.cpp (317): Reading module file: [layouts/basic.module]
../TextClass.cpp (330): Finished reading module file: 
[layouts/basic.module]


when I select LyX initialisation tracking.


I'm not sure about the above. If you can find a way to reproduce it, it
would be good to know.


Can't reproduce now even with 2.1.5.
But I get these lines

BufferParams.cpp (2220): setBaseClass: article
../TextClass.cpp (317): Reading module file: [layouts/basic.module]
../TextClass.cpp (330): Finished reading module file: 
[layouts/basic.module]


evety time I open the Document->Settings menu, and apparently, every 
time there is an automatic backup, both with 2.1.5 ans 2.2.0.


What is specific to this module ?


This is the module for the "basic" citation styles. It's normal for it 
to be read when the Document> Settings dialog is created. A copy of the 
BufferParams is created at that time.


Richard

Re: #10216: Lyx V2.2.0 Modules no working

[Richard Heck]

On 06/15/2016 10:37 AM, Robert Betz wrote:
I created a new file with Lyx using the standard article style.  I 
then included the module Customisable Lists (enumitem) using the 
Document->Settings->Modules. I am assuming that the

\usepackage{enumitem}
directive should be in this file.


The enumitem module has changed some since 2.1.x. The enumitem package 
will only be added to the preamble if you actually use some of the 
resources the module provides. Try e.g. putting an enumeration in your 
document.


Richard

Re: Support for more references by "plain label"

[Richard Heck]

On 06/15/2016 10:32 AM, racoon wrote:

Hi,

There are, for example, a number of refstyle commands that are (not 
yet) supported by LyX. Here are some examples: 
http://www.lyx.org/trac/ticket/10201.


I tried to build some of these with modules that use the already 
implemented commands but failed. Basically I tried to catch the 
command, like \ref{}, and read out it's internal label 
reference to recycle it with other commands. LaTeX seems not really to 
be build to do such things. It is also rather cumbersome.


So here is a suggestion to enhance the capabilities of LyX to be more 
easily extendable:


Add an (all purpose) reference format to the cross reference dialog 
that just adds the plain  to the code.


This way one could use the dialog and database of references with many 
other commands which could also be more easily turned into modules. 
Maybe there have to be two of those plain options: one with and one 
without prefixes ("enu:", "eq:", "sec:", etc)?


I guess the citation dialog could profit from a similar option as 
well. But I have not thought about details. This will make it possible 
to use more BibLaTeX commands with the citation dialog and database 
even though the commands lack direct support (at the moment).


Also this will enable support for commands that LyX will probably 
never directly support, for example because LyX is using another 
package by default.


In a way my suggestion seems obvious (to me now) so maybe this has 
been suggested before and probably I am overlooking something. Or is 
this functionality even already implemented somehow? My wild guess is 
that it is rather easy to implement.


Yes, it would be very easy indeed, though it would be a file format 
change, so can't be issued before 2.3.0. And it's a good idea, too, both 
for references and for citations.


An even better idea, in a way, would be to allow the reference types and 
the associated code to be defined dynamically, i.e., in a module.


Richard

Re: lyx and dark color schemes

[Guillaume Munch]

Le 15/06/2016 17:45, Liviu Andronic a écrit :

On Wed, Jun 15, 2016 at 5:52 PM, Guillaume Munch  wrote:

Le 15/06/2016 15:47, Liviu Andronic a écrit :


On Wed, Jun 15, 2016 at 3:35 PM, Guillaume Munch  wrote:


Le 14/06/2016 22:14, Cor Blom a écrit :



Op 14-06-16 om 22:21 schreef Guillaume Munch:



Le 14/06/2016 21:16, Cor Blom a écrit :



Op 14-06-16 om 22:09 schreef Guillaume Munch:



Le 14/06/2016 18:44, Cor Blom a écrit :



Hi,

Recently I tried lyx with a dark color scheme (breeze-dark  under
kde
plasma 5). Ihe toolbar icons are problematic, but I know how to fix
that
(and the oxygen set is not that bad against a dark background). In
general I'm happy about it. There is one issue. I don't know whether
it's possible and I'm missing something, or not.

Under de Documents > Settings, in the preamble part, blue is used
for
code. Against a dark background this is unreadable. Also in the code
view panel, de latex commands are blue, which makes them
unreadable. Is
that color configurable somewhere? I've searched but can't find the
solution.

Thanks,

Cor



Hi,

Can you compile master and test a patch I send you?

Guillaume




Yes I can.

Cor






Thanks! This is a huge improvement. I have now readable purple text
against the dark background.



Huh great but I did not intend to make it purple. Can I please have a
screenshot?


Good choice of color for dark schemes. Works well here with
Mediterranean (Darkest).



This is just (blue + text color)/2...



I too get something that is (to my eyes) purplish, though I should
mention that I'm also running redshift. The color picker says
"#6060DF" (or in the whereabouts).



Blue then. What about math? And errors (e.g. unencodable characters) ?


Math is OK. I usually just change colours manually in Prefs > Colors.
Same for notes, etc.

The single most unreadable instance though is blue headings like in Beamer:
http://i.imgur.com/zoSqWvX.png

Unfortunately there is no ready way to change this, as it would
require to redefine document classes where these things are hardcoded.

There is also an open ticket for these issues:
http://www.lyx.org/trac/ticket/8325

But I'm not sure there is an easy way to come up with defaults
suitable for both light and dark schemes...



Yes there is that issue as well. However here I meant math and errors in
e.g. the preamble and source view.

Re: lyx and dark color schemes

[Liviu Andronic]

On Wed, Jun 15, 2016 at 5:52 PM, Guillaume Munch  wrote:
> Le 15/06/2016 15:47, Liviu Andronic a écrit :
>>
>> On Wed, Jun 15, 2016 at 3:35 PM, Guillaume Munch  wrote:
>>>
>>> Le 14/06/2016 22:14, Cor Blom a écrit :


 Op 14-06-16 om 22:21 schreef Guillaume Munch:
>
>
> Le 14/06/2016 21:16, Cor Blom a écrit :
>>
>>
>> Op 14-06-16 om 22:09 schreef Guillaume Munch:
>>>
>>>
>>> Le 14/06/2016 18:44, Cor Blom a écrit :


 Hi,

 Recently I tried lyx with a dark color scheme (breeze-dark  under
 kde
 plasma 5). Ihe toolbar icons are problematic, but I know how to fix
 that
 (and the oxygen set is not that bad against a dark background). In
 general I'm happy about it. There is one issue. I don't know whether
 it's possible and I'm missing something, or not.

 Under de Documents > Settings, in the preamble part, blue is used
 for
 code. Against a dark background this is unreadable. Also in the code
 view panel, de latex commands are blue, which makes them
 unreadable. Is
 that color configurable somewhere? I've searched but can't find the
 solution.

 Thanks,

 Cor

>>>
>>> Hi,
>>>
>>> Can you compile master and test a patch I send you?
>>>
>>> Guillaume
>>>
>>>
>>
>> Yes I can.
>>
>> Cor
>>
>>
>

 Thanks! This is a huge improvement. I have now readable purple text
 against the dark background.

>>>
>>> Huh great but I did not intend to make it purple. Can I please have a
>>> screenshot?
>>>
>> Good choice of color for dark schemes. Works well here with
>> Mediterranean (Darkest).
>
>
> This is just (blue + text color)/2...
>
>>
>> I too get something that is (to my eyes) purplish, though I should
>> mention that I'm also running redshift. The color picker says
>> "#6060DF" (or in the whereabouts).
>
>
> Blue then. What about math? And errors (e.g. unencodable characters) ?
>
Math is OK. I usually just change colours manually in Prefs > Colors.
Same for notes, etc.

The single most unreadable instance though is blue headings like in Beamer:
http://i.imgur.com/zoSqWvX.png

Unfortunately there is no ready way to change this, as it would
require to redefine document classes where these things are hardcoded.

There is also an open ticket for these issues:
http://www.lyx.org/trac/ticket/8325

But I'm not sure there is an easy way to come up with defaults
suitable for both light and dark schemes...


Liviu

Re: lyx and dark color schemes

[Guillaume Munch]

Le 15/06/2016 15:47, Liviu Andronic a écrit :

On Wed, Jun 15, 2016 at 3:35 PM, Guillaume Munch  wrote:

Le 14/06/2016 22:14, Cor Blom a écrit :


Op 14-06-16 om 22:21 schreef Guillaume Munch:


Le 14/06/2016 21:16, Cor Blom a écrit :


Op 14-06-16 om 22:09 schreef Guillaume Munch:


Le 14/06/2016 18:44, Cor Blom a écrit :


Hi,

Recently I tried lyx with a dark color scheme (breeze-dark  under kde
plasma 5). Ihe toolbar icons are problematic, but I know how to fix
that
(and the oxygen set is not that bad against a dark background). In
general I'm happy about it. There is one issue. I don't know whether
it's possible and I'm missing something, or not.

Under de Documents > Settings, in the preamble part, blue is used for
code. Against a dark background this is unreadable. Also in the code
view panel, de latex commands are blue, which makes them
unreadable. Is
that color configurable somewhere? I've searched but can't find the
solution.

Thanks,

Cor



Hi,

Can you compile master and test a patch I send you?

Guillaume




Yes I can.

Cor






Thanks! This is a huge improvement. I have now readable purple text
against the dark background.



Huh great but I did not intend to make it purple. Can I please have a
screenshot?


Good choice of color for dark schemes. Works well here with
Mediterranean (Darkest).


This is just (blue + text color)/2...



I too get something that is (to my eyes) purplish, though I should
mention that I'm also running redshift. The color picker says
"#6060DF" (or in the whereabouts).


Blue then. What about math? And errors (e.g. unencodable characters) ?

Re: lyx and dark color schemes

[Cor Blom]

Op 15-06-16 om 16:47 schreef Liviu Andronic:

On Wed, Jun 15, 2016 at 3:35 PM, Guillaume Munch  wrote:

Le 14/06/2016 22:14, Cor Blom a écrit :


Op 14-06-16 om 22:21 schreef Guillaume Munch:


Le 14/06/2016 21:16, Cor Blom a écrit :


Op 14-06-16 om 22:09 schreef Guillaume Munch:


Le 14/06/2016 18:44, Cor Blom a écrit :


Hi,

Recently I tried lyx with a dark color scheme (breeze-dark  under kde
plasma 5). Ihe toolbar icons are problematic, but I know how to fix
that
(and the oxygen set is not that bad against a dark background). In
general I'm happy about it. There is one issue. I don't know whether
it's possible and I'm missing something, or not.

Under de Documents > Settings, in the preamble part, blue is used for
code. Against a dark background this is unreadable. Also in the code
view panel, de latex commands are blue, which makes them
unreadable. Is
that color configurable somewhere? I've searched but can't find the
solution.

Thanks,

Cor



Hi,

Can you compile master and test a patch I send you?

Guillaume




Yes I can.

Cor






Thanks! This is a huge improvement. I have now readable purple text
against the dark background.



Huh great but I did not intend to make it purple. Can I please have a
screenshot?


Good choice of color for dark schemes. Works well here with
Mediterranean (Darkest).

I too get something that is (to my eyes) purplish, though I should
mention that I'm also running redshift. The color picker says
"#6060DF" (or in the whereabouts).

Screen shot here:
http://i.imgur.com/b5gA51x.png

Regards,
Liviu






My colors are similar. See attached screenshot.

Regards,

Cor

Re: lyx and dark color schemes

[Liviu Andronic]

On Wed, Jun 15, 2016 at 3:35 PM, Guillaume Munch  wrote:
> Le 14/06/2016 22:14, Cor Blom a écrit :
>>
>> Op 14-06-16 om 22:21 schreef Guillaume Munch:
>>>
>>> Le 14/06/2016 21:16, Cor Blom a écrit :

 Op 14-06-16 om 22:09 schreef Guillaume Munch:
>
> Le 14/06/2016 18:44, Cor Blom a écrit :
>>
>> Hi,
>>
>> Recently I tried lyx with a dark color scheme (breeze-dark  under kde
>> plasma 5). Ihe toolbar icons are problematic, but I know how to fix
>> that
>> (and the oxygen set is not that bad against a dark background). In
>> general I'm happy about it. There is one issue. I don't know whether
>> it's possible and I'm missing something, or not.
>>
>> Under de Documents > Settings, in the preamble part, blue is used for
>> code. Against a dark background this is unreadable. Also in the code
>> view panel, de latex commands are blue, which makes them
>> unreadable. Is
>> that color configurable somewhere? I've searched but can't find the
>> solution.
>>
>> Thanks,
>>
>> Cor
>>
>
> Hi,
>
> Can you compile master and test a patch I send you?
>
> Guillaume
>
>

 Yes I can.

 Cor


>>>
>>
>> Thanks! This is a huge improvement. I have now readable purple text
>> against the dark background.
>>
>
> Huh great but I did not intend to make it purple. Can I please have a
> screenshot?
>
Good choice of color for dark schemes. Works well here with
Mediterranean (Darkest).

I too get something that is (to my eyes) purplish, though I should
mention that I'm also running redshift. The color picker says
"#6060DF" (or in the whereabouts).

Screen shot here:
http://i.imgur.com/b5gA51x.png

Regards,
Liviu


>

Re: [PATCH] unique_ptr and some clean-up

[Guillaume Munch]

Le 14/06/2016 21:49, Georg Baum a écrit :

Guillaume Munch wrote:


What error is it?


../../src/MetricsInfo.cpp:61:4: error: type ‘lyx::MetricsBase’ is not
a direct base of ‘lyx::MetricsBase’


Thanks for the clues. I was not even aware that delegate constructors
was a C++11 feature. Master must compile again with 4.6 now.




BTW, if it is possible to keep gcc 4.6 supported for a while with
little effort I am in favour of this as well, and I can do also some
testing or fixing if needed (this should improve my C++11 knowledge
as well). What we do have learnt from this exercise is that anything
older than gcc 4.6 does not make sense, so we should bump the current
requirement from 4.3 to 4.6.



I like Jean-Marc's suggestion that special adaptations for 4.6 should be
marked and removed later, so that weird workarounds like the one for
RefChanger do not stay forever. Then gcc 4.6 can be supported as long as
people are willing to put effort in it. Thanks for proposing your help
fixing.


Guillaume

Re: lyx and dark color schemes

[Guillaume Munch]

Le 14/06/2016 22:14, Cor Blom a écrit :

Op 14-06-16 om 22:21 schreef Guillaume Munch:

Le 14/06/2016 21:16, Cor Blom a écrit :

Op 14-06-16 om 22:09 schreef Guillaume Munch:

Le 14/06/2016 18:44, Cor Blom a écrit :

Hi,

Recently I tried lyx with a dark color scheme (breeze-dark  under kde
plasma 5). Ihe toolbar icons are problematic, but I know how to fix
that
(and the oxygen set is not that bad against a dark background). In
general I'm happy about it. There is one issue. I don't know whether
it's possible and I'm missing something, or not.

Under de Documents > Settings, in the preamble part, blue is used for
code. Against a dark background this is unreadable. Also in the code
view panel, de latex commands are blue, which makes them
unreadable. Is
that color configurable somewhere? I've searched but can't find the
solution.

Thanks,

Cor



Hi,

Can you compile master and test a patch I send you?

Guillaume




Yes I can.

Cor






Thanks! This is a huge improvement. I have now readable purple text
against the dark background.



Huh great but I did not intend to make it purple. Can I please have a
screenshot?

Difference between endnotes and foottoend modules

[Jean-Pierre Chrétien]

Hello,

I'm not sure to have translated the description of these modules all right.
* foottoend makes all footnotes endnotes
* endnotes offers an extra inset to add endnotes in addition to plain footnotes

If this is right, I must amend my translation of the description of endnotes, 
which is unclear. Too late for 2.1, I will do it for 2.2.x.


--
Jean-Pierre

Re: Basic module reloaded (Was: scrunched radio buttons on message pane)

[Jean-Pierre Chrétien]

Le 15/06/2016 09:13, Scott Kostyshak a écrit :

On Wed, Jun 15, 2016 at 09:48:03AM +0100, Jean-Pierre Chrétien wrote:



I've seen this once with 2.2.0, but I can't reproduce, maybe I left open an
instance of 2.1.5, I see now

../TextClass.cpp (317): Reading module file: [layouts/basic.module]
../TextClass.cpp (330): Finished reading module file: [layouts/basic.module]

when I select LyX initialisation tracking.


I'm not sure about the above. If you can find a way to reproduce it, it
would be good to know.


Can't reproduce now even with 2.1.5.
But I get these lines

BufferParams.cpp (2220): setBaseClass: article
../TextClass.cpp (317): Reading module file: [layouts/basic.module]
../TextClass.cpp (330): Finished reading module file: [layouts/basic.module]

evety time I open the Document->Settings menu, and apparently, every time there 
is an automatic backup, both with 2.1.5 ans 2.2.0.


What is specific to this module ?

Recipe:
* open LyX
* select "Texclass file reading" in the message pane parameters
* Open a new file
* Select Document->Settings

Messages are both in the terminal and in the Output window of the message pane.

--
Jean-Pierre

Re: lyx and dark color schemes

[José Abílio Matos]

On Tuesday, June 14, 2016 9:21:38 PM WEST Guillaume Munch wrote:
> latexhighlighter.diff

Could this go to lyx-2.2 as well. I have the same problem with the font 
colours but not the panel icons.

Regards,
-- 
José Abílio

Re: [LyX/master] Make lyx2lyx infrastructure python3 ready

[José Abílio Matos]

On Sunday, June 12, 2016 9:24:44 PM WEST Georg Baum wrote:
> commit 166420d02ccb073dc32ab5cd0bc466de54aa36bb
> Author: Georg Baum 
> Date:   Sun Jun 12 21:21:15 2016 +0200
> 
> Make lyx2lyx infrastructure python3 ready
> 
> The LyX class works now with python 3. Certain file format conversions
> may still fail (convert_multiencoding() is a hot candidate), but this will
> need to be fixed in the individual modules.

Well done Georg.

I own you a beer. :-)

Regards,
-- 
José Abílio

Re: #10216: Lyx V2.2.0 Modules no working

[Robert Betz]

I created a new file with Lyx using the standard article style.  I then 
included the module Customisable Lists (enumitem) using the 
Document->Settings->Modules. I am assuming that the
\usepackage{enumitem}
directive should be in this file.

The latex code produced is attached.




——

Regards,

Bob


PROFESSOR ROBERT BETZ
School of Electrical Engineering and Computer Science
Faculty of Engineering and Built Environment

T: +61 2 4921 6091
M: +61 419 249 948
F: +61 2 4921 6993
E: robert.b...@newcastle.edu.au

The University of Newcastle (UoN)
University Drive
Callaghan NSW 2308
Australia

CRICOS Provider 00109J

[width=]

[The University of Newcastle]

[width=]

[width=]

[Website]



[Blog]



[Facebook]



[Twitter]



[YouTube]

[width=]



[width=]

[width=]





On 14 June 2016 at 1:13:18 AM, LyX Ticket Tracker 
(t...@lyx.org) wrote:

#10216: Lyx V2.2.0 Modules no working
+-
Reporter: rebetz | Owner: rebate
Type: defect | Status: new
Priority: normal | Milestone: 2.2.1
Component: layout | Version: 2.2.0
Severity: normal | Resolution:
Keywords: |
+-
Changes (by rgheck):

* keywords: Modules Settings =>
* component: general => layout


Comment:

We would need to see the LyX file and the module, if it's a custom one.

--
Ticket URL: 
The LyX Project 
LyX -- The Document Processor


image041.jpg@01D1B120.E2608060
Description: image041.jpg@01D1B120.E2608060


image001.jpg@01D1BB33.06854AE0
Description: image001.jpg@01D1BB33.06854AE0


image002.jpg@01D1BB33.06854AE0
Description: image002.jpg@01D1BB33.06854AE0


image003.jpg@01D1BB33.06854AE0
Description: image003.jpg@01D1BB33.06854AE0


image004.jpg@01D1BB33.06854AE0
Description: image004.jpg@01D1BB33.06854AE0


image005.jpg@01D1BB33.06854AE0
Description: image005.jpg@01D1BB33.06854AE0


image006.jpg@01D1BB33.06854AE0
Description: image006.jpg@01D1BB33.06854AE0


image005.jpg@01D1BB33_1.06854AE0
Description: image005.jpg@01D1BB33_1.06854AE0


image007.jpg@01D1BB33.06854AE0
Description: image007.jpg@01D1BB33.06854AE0


image005.jpg@01D1BB33_2.06854AE0
Description: image005.jpg@01D1BB33_2.06854AE0


image008.jpg@01D1BB33.06854AE0
Description: image008.jpg@01D1BB33.06854AE0


image005.jpg@01D1BB33_3.06854AE0
Description: image005.jpg@01D1BB33_3.06854AE0


image009.jpg@01D1BB33.06854AE0
Description: image009.jpg@01D1BB33.06854AE0


image010.jpg@01D1BB33.06854AE0
Description: image010.jpg@01D1BB33.06854AE0


image011.jpg@01D1BB33.06854AE0
Description: image011.jpg@01D1BB33.06854AE0


image012.jpg@01D1BB33.06854AE0
Description: image012.jpg@01D1BB33.06854AE0


newfile1.tex
Description: newfile1.tex

Support for more references by "plain label"

[racoon]

Hi,

There are, for example, a number of refstyle commands that are (not yet) 
supported by LyX. Here are some examples: 
http://www.lyx.org/trac/ticket/10201.


I tried to build some of these with modules that use the already 
implemented commands but failed. Basically I tried to catch the command, 
like \ref{}, and read out it's internal label reference to 
recycle it with other commands. LaTeX seems not really to be build to do 
such things. It is also rather cumbersome.


So here is a suggestion to enhance the capabilities of LyX to be more 
easily extendable:


Add an (all purpose) reference format to the cross reference dialog that 
just adds the plain  to the code.


This way one could use the dialog and database of references with many 
other commands which could also be more easily turned into modules. 
Maybe there have to be two of those plain options: one with and one 
without prefixes ("enu:", "eq:", "sec:", etc)?


I guess the citation dialog could profit from a similar option as well. 
But I have not thought about details. This will make it possible to use 
more BibLaTeX commands with the citation dialog and database even though 
the commands lack direct support (at the moment).


Also this will enable support for commands that LyX will probably never 
directly support, for example because LyX is using another package by 
default.


In a way my suggestion seems obvious (to me now) so maybe this has been 
suggested before and probably I am overlooking something. Or is this 
functionality even already implemented somehow? My wild guess is that it 
is rather easy to implement.


Best,
Daniel

Re: One official build system?

[Kornel Benko]

Am Dienstag, 14. Juni 2016 um 22:37:58, schrieb Georg Baum 

> Kornel Benko wrote:
> 
> > The result is that cmake part misses
> > Makefile.in
> > automake misses
> > lib/fonts/*.sfd (11 files)
> > lib/images/ipa/*.svgz (30 files)
> > lib/images/oxygen/*.svgz (88 files)
> > src/mathed/InsetMathXYArrow.{cpp,h}
> > 3rdparty/boost/libs/regex/src/{icu,usinstances,wc_regex_traits}.cpp
> > 
> > There are also many files in cmake-tar which are only for tests and not
> > important. But the automake missed files are more than serious IMHO.
> 
> Not all missing files are a problem. InsetMathXYArrow is dead code and the 
> .sfd files are left out on purpose as well (only usable by font experts).
> 
> The icons and the regex files are indeed a serious problem. The icons should 
> be fixed now, this was simply a wrong style of using variables.

It does not look like that. Even after ./autogen.sh and configure.

> I'll take 
> care for the regex files later, but what I do not understand is how the 
> official windows build could succeed without these files (because of 
> http://www.lyx.org/trac/ticket/9373). I fear that (again) the official 
> installers were produced from git and not from an unpacked .tar.gz. Or bug 
> 9373 is magically fixed and nobody noticed.
> 

I do not understand either.

Extra missing in automake (apart from already mentioned)
development/cmake/modules/LyXDestinations.cmake
development/cmake/scripts/xmingw

development/Win32/packaging/installer/{Console.dll,FindProcDLL.dll,InetLoad.dll,include/EnvVarUpdate.nsh,
 \

information,Encodings.txt,TranslatedLanguages.nsh,Packages.txt,Readme.txt}
src/frontends/qt4/GuiGraphicsUi.h (dead code?)
src/frontends/qt4/liblyxqt4.cpp
src/{lyxcore,lyxinsets,lyxmathed}.cpp

Some files are distributed in automake, which we do not want I suppose
development/lyxserver/perl/LyX-Client-0.01.tar.gz
development/lyxserver/perl/LyX-Polite-0.01.tar.gz
src/client/lyxclient.cpp (what is this?)

> Georg

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: scrunched radio buttons on message pane

[Scott Kostyshak]

On Wed, Jun 15, 2016 at 09:48:03AM +0100, Jean-Pierre Chrétien wrote:
> Le 14/06/2016 07:52, Scott Kostyshak a écrit :
> > Does anyone else see that the radio buttons are cut-off on the message
> > pane?
> > 
> > Attached is a screenshot.
> 
> I do not undertand what you mean by "cut-off".
> Here both on 2.2.0 and 2.2.1dev, they seem to be ok

Thanks for checking.

> (but the initial
> vertical size of the pane is to small, I have to enjlatge it to see the
> buttons).

Sorry for being unclear. This is exactly the problem I'm trying to fix.
It is a minor issue because as you found out you can enlarge it
manually, and in fact it stays enlarged across sessions I think. But
nonetheless I find it annoying and it is nice to try to provide a
polished experience. Ideally, it should not be possible to reduce the
size of a widget too much.

> But while fiddling with the message pane with lyx-2.1.5 I see this in the 
> terminal :
> 
> 
> tex2lyx/../TextClass.cpp (317): Reading module file: [layouts/basic.module]
> tex2lyx/../Lexer.cpp (257): lyxlex: UNcompressed
> tex2lyx/../Lexer.cpp (336): Comment read: `35 \DeclareLyXModule{Default 
> (basic)}'
> tex2lyx/../Lexer.cpp (336): Comment read: `35 DescriptionBegin'
> tex2lyx/../Lexer.cpp (336): Comment read: `35   Use the basic citation
> capabilities provided by plain LaTeX.'
> tex2lyx/../Lexer.cpp (336): Comment read: `35 DescriptionEnd'
> tex2lyx/../Lexer.cpp (336): Comment read: `35 Excludes: jurabib | natbib'
> tex2lyx/../Lexer.cpp (336): Comment read: `35 Category: Citation engine'
> tex2lyx/../Lexer.cpp (336): Comment read: `35 Author: Julien Rioux 
> '
> tex2lyx/../Lexer.cpp (336): Comment read: `35 translatable bits'
> tex2lyx/../Lexer.cpp (336): Comment read: `35 macros'
> tex2lyx/../Lexer.cpp (336): Comment read: `35 cite styles'
> tex2lyx/../TextClass.cpp (330): Finished reading module file: 
> [layouts/basic.module]
> 
> 
> and a popup confirms a problem with the basic module (attached).
> 
> I've seen this once with 2.2.0, but I can't reproduce, maybe I left open an
> instance of 2.1.5, I see now
> 
> ../TextClass.cpp (317): Reading module file: [layouts/basic.module]
> ../TextClass.cpp (330): Finished reading module file: [layouts/basic.module]
> 
> when I select LyX initialisation tracking.

I'm not sure about the above. If you can find a way to reproduce it, it
would be good to know.

Scott


signature.asc
Description: PGP signature

Re: scrunched radio buttons on message pane

[Jean-Pierre Chrétien]

Le 14/06/2016 07:52, Scott Kostyshak a écrit :

Does anyone else see that the radio buttons are cut-off on the message
pane?

Attached is a screenshot.


I do not undertand what you mean by "cut-off".
Here both on 2.2.0 and 2.2.1dev, they seem to be ok (but the initial vertical 
size of the pane is to small, I have to enjlatge it to see the buttons).


But while fiddling with the message pane with lyx-2.1.5 I see this in the 
terminal :


tex2lyx/../TextClass.cpp (317): Reading module file: [layouts/basic.module]
tex2lyx/../Lexer.cpp (257): lyxlex: UNcompressed
tex2lyx/../Lexer.cpp (336): Comment read: `35 \DeclareLyXModule{Default 
(basic)}'
tex2lyx/../Lexer.cpp (336): Comment read: `35 DescriptionBegin'
tex2lyx/../Lexer.cpp (336): Comment read: `35   Use the basic citation 
capabilities provided by plain LaTeX.'

tex2lyx/../Lexer.cpp (336): Comment read: `35 DescriptionEnd'
tex2lyx/../Lexer.cpp (336): Comment read: `35 Excludes: jurabib | natbib'
tex2lyx/../Lexer.cpp (336): Comment read: `35 Category: Citation engine'
tex2lyx/../Lexer.cpp (336): Comment read: `35 Author: Julien Rioux 
'
tex2lyx/../Lexer.cpp (336): Comment read: `35 translatable bits'
tex2lyx/../Lexer.cpp (336): Comment read: `35 macros'
tex2lyx/../Lexer.cpp (336): Comment read: `35 cite styles'
tex2lyx/../TextClass.cpp (330): Finished reading module file: 
[layouts/basic.module]


and a popup confirms a problem with the basic module (attached).

I've seen this once with 2.2.0, but I can't reproduce, maybe I left open an 
instance of 2.1.5, I see now


../TextClass.cpp (317): Reading module file: [layouts/basic.module]
../TextClass.cpp (330): Finished reading module file: [layouts/basic.module]

when I select LyX initialisation tracking.

--
Jean-Pierre

Icons in menus

[racoon]

Hi,

I could not find a discussion on icons in menus. I tend to believe that 
they help locating entries when scanning over a menu entry. But maybe 
that's bogus. I think icons in menus are less popular on macOS [sic] 
than on Windows and Linux. I am just throwing this in.


There seems to be Qt support for icons in menus. I guess one could add 
those icons that are already available from the toolbar (depending on 
the choice of toolbar icons) and leave others blank. That could already 
increase the speed in the location of entries.


Maybe there could be an option to disable icons in menus for those who 
don't like them?


Daniel

Re: Tarballs for LyX 2.2.0 are on FTP

[Guillaume Munch]

Le 15/06/2016 00:51, Enrico Forestieri a écrit :

On Fri, Jun 10, 2016 at 10:20:32PM +0100, Guillaume Munch wrote:

As for lyx2lyx, I gave one example of a commit which explicitly said
that it would not be made round-trip, and another example where it had
to be fixed afterwards because a special case was not taken into
accountn because it is developped on a trial-and-error basis.


Yes, development should not be performed on a trial-and-error basis.
Thanks for the mud.



Enrico, actually I do not believe that lyx2lyx can be developed without
trial-and-error, because of how loosely defined the lyx file format is.
(And if it ever was properly defined, and the goal was to convert
between perfectly-given specification, then it would use surer tools
than python and regexps.) This is the reason why I do not find wise to
rely on lyx2lyx in the context of testing (not counting the
impossibility of perfect round-trip).

The commit I was referring to, I did not even look into its details to
see whether it was a mistake or not, because I had assumed that it is
part of the necessary process of writing lyx2lyx. In an earlier message
I have said that I picked your file format change as an example because,
to my knowledge, it was the most complex for 2.2.

I can now understand better your reaction on the bug tracker. But, don't
take things so personally! :)