Fwd: Re: 2 error in lyx 2.3

2017-06-02 Thread edu Gpl
After i upgrade from lyx 2.2.2 to 2.3 tcolorbox not work in the title of
chapter if i used it with arabic language, but work with english language.

Best regards
‏-- الرسالة المُعاد توجيهها --
من: "edu Gpl" 
التاريخ: ٠٢‏/٠٦‏/٢٠١٧ ٨:٤٢ م
الموضوع: Re: 2 error in lyx 2.3
إلى: "Richard Heck" 
‏نسخة إلى:

After i upgrade from lyx 2.2.2 to 2.3 tcolorbox not work in the title of
chapter if i used it with arabic language, but work with english language.

Best regards



بتاريخ ٠٢‏/٠٦‏/٢٠١٧ ٧:٠١ م، كتب "Richard Heck" :

> On 06/02/2017 12:45 AM, edu Gpl wrote:
> > thank you,
> > please what about 2nd problem, the code of chapter (in latex breamble
> > not worked).
>
> I don't have that email any longer. You'll have to repeat it.
>
> Richard
>
>


‏‏title_tcolorbox_ar - 2.3.lyx
Description: Binary data


‏‏title_tcolorbox_en - 2.3.lyx
Description: Binary data


Re: dash patch for stable

2017-06-02 Thread Enrico Forestieri
On Fri, Jun 02, 2017 at 07:30:34PM +, Guenter Milde wrote:
> 
> Note that the "ERT patch" is only for *stable*, i.e. 2.2.x.
> For 2.2, ERT is the only way to ensure full backwards compatibility.

A solution should have been thought and done before 2.2.0 was released.
Now it's too late.

-- 
Enrico


Re: dash patch for stable

2017-06-02 Thread Guenter Milde
On 2017-06-01, Enrico Forestieri wrote:
> On Thu, Jun 01, 2017 at 09:12:53PM +, Guenter Milde wrote:

>> On 2017-05-26, Scott Kostyshak wrote:
>> > On Fri, May 19, 2017 at 09:12:27AM -0400, Scott Kostyshak wrote:
>> >> Günter has written a lot about what to do regarding em- and en-dashes.
>> >> For more information, see:

>> >>   http://www.lyx.org/trac/ticket/10543

>> >> Does anyone else have feedback on what should be done on this for 2.3.0?

>> There is now a patch for stable attached to the ticket.
>> Thanks to Enrico for the inset code.

>> http://www.lyx.org/trac/raw-attachment/ticket/10543/0001-Keep-distinction-of-literal-dashes-vs-ligature-dashes-in-2-2.patch

>> OK to commit?

> Sorry, but I am opposed to this patch. You really mean to have all
> en/em-dashes become ERT!!!

So we have a conflict:

When I asked 

>> How important is backwards compatibility for documents generated with LyX
>> 2.1 or older?

>>a) no need to restore after it's broken by 2.2.
>>b) good but not required 
>>c) small changes tolerable as long as documents
>>   open and compile
>>d) 100% backwards compatibility whenever possible.

On 2017-05-31, Richard Heck wrote:

> I believe the rule is (d).

The reasoning is, that it is most annoying, if existing documents show
different layout (line or page-breaks etc.) when compiled with a new LyX
version, as this can easily go unnoticed until it is too late (document
printed and submitted...).


Note that the "ERT patch" is only for *stable*, i.e. 2.2.x.
For 2.2, ERT is the only way to ensure full backwards compatibility.

I am fine if the decision is not to restore full backwards compatibility
in the last release in the 2.2 series. (Considering that in most cases
the damage is already done.)

I leave the decision to the release manager.

Günter





Re: cmake and make install

2017-06-02 Thread Cor Blom

Op 01-06-17 om 12:34 schreef Kornel Benko:

(the "%cmake"  macro inheritis all kind of openSUSE settings).

Which ones?

Expanded it becomes this:

find . -name CMakeLists.txt -exec sed -i -re
'/^[[:blank:]]*[sS][eE][tT][[:blank:]]*\([[:blank:]]*(CMAKE_BUILD_TYPE|CMAKE_COLOR_MAKEFILE|CMAKE_INSTALL_PREFIX|CMAKE_VERBOSE_MAKEFILE).*\)/{s/^/#IGNORE
/}' '{}' +

Outch. What went wrong if not using this command?
I AM interested.
Specifically
CMAKE_VERBOSE_MAKEFILE will be reset with -DLYX_QUIET=ON
CMAKE_INSTALL_PREFIX will be set on the commandline



If I don't use openSUSE's preconfigured settings for cmake but define 
them myself, the make install stage is running fine. Made me wonder why 
I didn't do that in the first place. Thanks for the help.


Will later look into other suggestions made.

Cor