Re: Windows: release with Qt 5.5.1 or 5.6?

Am 13. Januar 2016 01:46:35 MEZ, schrieb Scott Kostyshak : >On Wed, Jan 13, 2016 at 01:31:59AM +0100, Peter Kümmel wrote: >> Am 13. Januar 2016 00:32:11 MEZ, schrieb Scott Kostyshak >: >> >Dear all, >> > >> >There is a question of whether we should release our

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 13. Januar 2016 05:27:22 MEZ, schrieb "Peter Kümmel" : >Am 13. Januar 2016 05:19:09 MEZ, schrieb "Peter Kümmel" >: >> It is a warning only committed from me today to fix a linker error. >>>You tried it with msvc 2010? And it worked? >>> >>>Yes. I

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 13. Januar 2016 05:19:09 MEZ, schrieb "Peter Kümmel" : > >>> It is a warning only committed from me today to fix a linker error. >>You tried it with msvc 2010? And it worked? >> >>Yes. I can now compile with MSVC 2010 and Qt 5.5.1. The compilation of > >>Zlib and friends

Re: Basic test of alpha1 tar

Jean-Marc Lasgouttes wrote: > Le 11/01/2016 10:59, Pavel Sanda a écrit : >> Jean-Marc Lasgouttes wrote: >>> I reproduce the svg you sent for 2.2, since it is not so large either :) >> >> More important is - can you reproduce the behaviour? It's pretty clear on my >> machine without trying any

Re: Basic test of alpha1 tar

Le 12/01/2016 10:15, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: More important is - can you reproduce the behaviour? It's pretty clear on my machine without trying any special conditions, just high repeat rate of the keyboard is needed. I only tried 2.2, so I did not really compare. I

Re: make distcheck: cannot remove '../../po/lyx.pot'

Le 12/01/2016 03:51, Scott Kostyshak a écrit : I wonder if the difference in behavior is due to: http://lists.gnu.org/archive/html/automake/2012-07/msg00023.html That thread is linked to on the main page: https://www.gnu.org/software/automake/ It is interesting but I fail to see how this

Re: why Babel with dvi3 (LuTeX)?

Scott Kostyshak wrote: > I strongly agree with Georg as for the good unit tests that we have. But > for our export tests and specifically our export tests known to be > unreliable, I understand Günter's objection that it could be just a lot > of wasted time. I should clarify that a prerequisite

Re: User pref parameters

Guillaume Munch wrote: > I am not convinced by the naming vcs_simplify_format but maybe there are > other suggestions? What about save_transient_properties or save_state ? I am fine with save_transient_properties as well. P

Re: Questions for Uwe once you are back

The cache needs to be deleted (as you discovered already). I'll push a script which deletes the complete build dir, cleanest way. For now I also need the info about Qt 5. What is the expected build target for beta1? My time is limited and I have to focus on one Qt version. I installed Qt

MinGW: development/cmake/mingw.bat

Hi Uwe, could you try development/cmake/mingw.bat. Call it from any path. The script creates the build folder "compile-mingw". Only requirement is that msvc2010-deps is on the same level as the lyx source dir (and the C:\Qt installation) After the build there is a LYX_INSTALLED dir with the

Re: Basic test of alpha1 tar

Jean-Marc Lasgouttes wrote: > Le 12/01/2016 10:15, Pavel Sanda a écrit : >> Jean-Marc Lasgouttes wrote: More important is - can you reproduce the behaviour? It's pretty clear on my machine without trying any special conditions, just high repeat rate of the keyboard is

Re: User pref parameters

Pavel Sanda wrote: > Guillaume Munch wrote: >> I am not convinced by the naming vcs_simplify_format but maybe there are >> other suggestions? What about save_transient_properties or save_state ? > > I am fine with save_transient_properties as well. P me too (and I do not like

Re: Questions for Uwe once you are back

Uwe Stöhr wrote: > Am 11.01.2016 um 21:22 schrieb Georg Baum: > >> I don't know whether he got them from you or directly from the original >> download pages, but this does not matter. What matters is that you get a >> consistent build and eliminate possible errors if you use these sources >> (by

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 12.01.2016 um 00:37 schrieb Uwe Stöhr: I did this now as I wrote in the Questions for Uwe once you are back thread. I had to delete CMake's cache first and re-run it from scratch. The 3rd party programs are compiled (with 134 warnings) but I don't get a DLL. Is this the plan - not to rely

Compilation fails with Mac OS 10.7 (autotools)

After boost has been moved to 3rdparty, I notice that linking fails on Mac OS 10.7. Stephan, is it the same as what you see? Can it be a config.h problem? JMarc Making all in . g++ -g -O2 -fno-omit-frame-pointer -framework AppKit -framework ApplicationServices

Re: Compilation fails with Mac OS 10.7 (autotools)

Am 12.01.2016 um 22:24 schrieb Jean-Marc Lasgouttes : > > > After boost has been moved to 3rdparty, I notice that linking fails on Mac OS > 10.7. > > Stephan, is it the same as what you see? Can it be a config.h problem? I had this with cmake build when external boost

Re: beta release

On Tue, Jan 12, 2016 at 10:45:53PM +0100, Enrico Forestieri wrote: > On Mon, Jan 11, 2016 at 07:30:30PM -0500, Scott Kostyshak wrote: > > > > I looked at the thread (actually it timed out for me but I could search > > the MID and found it on mail-archive here [1]). From what I see, there > > is

Re: beta release

On Tue, Jan 12, 2016 at 04:51:34PM -0500, Scott Kostyshak wrote: > On Tue, Jan 12, 2016 at 10:45:53PM +0100, Enrico Forestieri wrote: > > > > I hope both of you are not serious. > > I was completely serious. I did not follow the issue and did not want to > invest the time when I know there were

ctests and default output

Dear Kornel, in order to optimize the autotests, I tried setting the default output of the dedicated test sample TableErrorIfSlovakTextInserted.lyx to "dvi". (Rationale: the error is an incompatiblity of Babel Czech/Slovak with some table code. It does not show up with Polyglossia - no need for

Re: beta release

On Mon, Jan 11, 2016 at 07:30:30PM -0500, Scott Kostyshak wrote: > > I looked at the thread (actually it timed out for me but I could search > the MID and found it on mail-archive here [1]). From what I see, there > is no response to that message. Eh, you got a bronze contract service and that

Re: beta release

On Tue, Jan 12, 2016 at 11:06:25PM +0100, Enrico Forestieri wrote: > On Tue, Jan 12, 2016 at 04:51:34PM -0500, Scott Kostyshak wrote: > > On Tue, Jan 12, 2016 at 10:45:53PM +0100, Enrico Forestieri wrote: > > > > > > I hope both of you are not serious. > > > > I was completely serious. I did not

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 12.01.2016 um 00:37 schrieb Uwe Stöhr: I had to delete CMake's cache first and re-run it from scratch. The 3rd party programs are compiled (with 134 warnings) but I don't get a DLL. Is this the plan - not to rely anymore on DLLs? Yes, no Dlls any more (only the Qt related ones). thanks

Re: Questions for Uwe once you are back

For now I also need the info about Qt 5. What is the expected build target for beta1? My time is limited and I have to focus on one Qt version. I installed Qt 5.6 beta for mingw and mingw itself. Is this the way I should go? Yes, that would be great! It looks like the paths will also not

Re: User pref parameters

On Tue, Jan 12, 2016 at 05:18:40PM +, Guillaume Munch wrote: > Le 12/01/2016 02:23, Pavel Sanda a écrit : > >Guillaume Munch wrote: > Scott, do you sum up all these messages as a "+1", as you say? After a quick look, I do think there is a +1. Scott signature.asc Description: PGP signature

Re: beta release

On Tue, Jan 12, 2016 at 05:30:14PM +, Guillaume Munch wrote: > Le 12/01/2016 00:30, Scott Kostyshak a écrit : > >On Mon, Jan 11, 2016 at 06:28:02PM +, Guillaume Munch wrote: > >>Le 09/01/2016 00:15, Scott Kostyshak a écrit : > >>> > >>>Does any one view an issue as a beta blocker? > >> >

Re: beta release

On Tue, Jan 12, 2016 at 08:46:04PM +, Guillaume Munch wrote: > >>Also, what is this timeout issue? Some people do not get new messages sent > >>to old threads? > > > >I don't understand. Did I bring up the timeout issue? Which quoted text > >are you referring to? > > below > > >>>I looked

Re: beta release

On Tue, Jan 12, 2016 at 03:28:28PM -0500, Scott Kostyshak wrote: > > I think this should be done before release. Does it mean that I have to make > > it a beta blocker? > > No. In my opinion, a beta blocker is something that falls into one of > the following categories: > > (1) a fix for a bug

Re: beta release

Le 12/01/2016 20:28, Scott Kostyshak a écrit : Can anyone +1 this issue as a beta blocker? I did not follow the discussion closely. I think this should be done before release. Does it mean that I have to make it a beta blocker? No. In my opinion, a beta blocker is something that falls into

Re: User pref parameters

Le 12/01/2016 19:36, Georg Baum a écrit : Pavel Sanda wrote: Guillaume Munch wrote: I am not convinced by the naming vcs_simplify_format but maybe there are other suggestions? What about save_transient_properties or save_state ? I am fine with save_transient_properties as well. P me too

Re: make distcheck: cannot remove '../../po/lyx.pot'

Am Dienstag, 12. Januar 2016 um 14:47:35, schrieb Jean-Marc Lasgouttes > Le 12/01/2016 03:51, Scott Kostyshak a écrit : > > I wonder if the difference in behavior is due to: > > http://lists.gnu.org/archive/html/automake/2012-07/msg00023.html > > > > That thread is linked to

Re: beta release

Le 12/01/2016 22:06, Enrico Forestieri a écrit : On Tue, Jan 12, 2016 at 04:51:34PM -0500, Scott Kostyshak wrote: On Tue, Jan 12, 2016 at 10:45:53PM +0100, Enrico Forestieri wrote: I hope both of you are not serious. I was completely serious. I did not follow the issue and did not want to

Re: ctests and default output

Am Dienstag, 12. Januar 2016 um 22:07:59, schrieb Guenter Milde > Dear Kornel, > > in order to optimize the autotests, I tried setting the default output of > the dedicated test sample TableErrorIfSlovakTextInserted.lyx to "dvi". > > (Rationale: the error is an

Re: "Splitting of consecutive environments has been reworked and enhanced"

On Mon, Jan 11, 2016 at 03:04:33AM +, Guillaume Munch wrote: > > Dear Enrico, > > > Thank you for the recent patches that took into account some of my remarks. > > I have been using master a lot recently and I noticed another issue > which annoyed me: In 2.1, the behaviour when typing

Re: Questions for Uwe once you are back

Am 12.01.2016 um 19:43 schrieb Georg Baum: For now I also need the info about Qt 5. What is the expected build target for beta1? My time is limited and I have to focus on one Qt version. I installed Qt 5.6 beta for mingw and mingw itself. Is this the way I should go? That depends whether you

Re: Questions for Uwe once you are back

Am 12.01.2016 um 11:23 schrieb Peter Kümmel: For now I also need the info about Qt 5. What is the expected build target for beta1? My time is limited and I have to focus on one Qt version. I installed Qt 5.6 beta for mingw and mingw itself. Is this the way I should go? Yes, that would be

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 13.01.2016 um 01:38 schrieb Peter Kümmel: It is a warning only committed from me today to fix a linker error. You tried it with msvc 2010? And it worked? Yes. I can now compile with MSVC 2010 and Qt 5.5.1. The compilation of Zlib and friends works here also with MSVC2013. regards Uwe

Re: "Splitting of consecutive environments has been reworked and enhanced"

On 01/12/2016 06:53 PM, Enrico Forestieri wrote: > On Tue, Jan 12, 2016 at 11:49:54PM +0100, Enrico Forestieri wrote: >> On Mon, Jan 11, 2016 at 03:04:33AM +, Guillaume Munch wrote: >> >>> For the symbol itself, my suggestion was a very elongated version of ⌟, >>> meant to recall the plain

Re: Windows: release with Qt 5.5.1 or 5.6?

On 01/12/2016 06:32 PM, Scott Kostyshak wrote: > Dear all, > > There is a question of whether we should release our binary for Windows > compiled against Qt 5.5.1 or 5.6.0. > > My opinion is that we should release it with 5.5.1, unless there is a > known, significant issue that affects LyX for

Windows: release with Qt 5.5.1 or 5.6?

Dear all, There is a question of whether we should release our binary for Windows compiled against Qt 5.5.1 or 5.6.0. My opinion is that we should release it with 5.5.1, unless there is a known, significant issue that affects LyX for 5.5.1 *on Windows* and that would be solved with 5.6.0. There

Re: Questions for Uwe once you are back

On Wed, Jan 13, 2016 at 12:21:52AM +0100, Uwe Stöhr wrote: > For Qt 5.6 I will use MinGW and not MSVC. Since both are new programs to me > I think it makes sense to release beta1 with 5.5 if possible if Scott > agrees. I do agree with 5.5.1. I just started a new thread for this:

Re: Questions for Uwe once you are back

Am 12.01.2016 um 00:55 schrieb Kornel Benko: * for hunspell_include_dir I get this path: D:/LyXGit/Master/3rdparty/hunspell/1.3.3/src * for iconv_include_dir I get this path: D:/LyXGit/Master/compile-2010/libiconv/include This seems wrong to me. I expect that in both cases the files from

Re: "Splitting of consecutive environments has been reworked and enhanced"

Le 12/01/2016 22:49, Enrico Forestieri a écrit : On Mon, Jan 11, 2016 at 03:04:33AM +, Guillaume Munch wrote: Dear Enrico, Thank you for the recent patches that took into account some of my remarks. I have been using master a lot recently and I noticed another issue which annoyed me: In

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 12. Januar 2016 20:24:38 MEZ, schrieb Georg Baum : >Am 12.01.2016 um 00:37 schrieb Uwe Stöhr: >> I did this now as I wrote in the >> Questions for Uwe once you are back >> thread. >> I had to delete CMake's cache first and re-run it from scratch. The >> 3rd

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 12.01.2016 um 11:16 schrieb Peter Kümmel: Yes, no Dlls any more (only the Qt related ones). OK. However I get now man times this warning: D:\LyXGit\Master\compile-2010\zconf.h(10): warning C4005: 'Z_PREFIX': Makro-Neudefinition [D:\LyXGit\Master\compile-2010\src\LyX.vcxproj]

Re: Questions for Uwe once you are back

Am 13. Januar 2016 00:21:52 MEZ, schrieb "Uwe Stöhr" : >Am 12.01.2016 um 19:43 schrieb Georg Baum: > >>> For now I also need the info about Qt 5. What is the expected build >>> target for beta1? My time is limited and I have to focus on one Qt >>> version. I installed Qt 5.6 beta

Re: compilation problems with Qt 5.5.1 and MSVC 2010

Am 13. Januar 2016 01:18:12 MEZ, schrieb "Uwe Stöhr" : >Am 12.01.2016 um 11:16 schrieb Peter Kümmel: > >> Yes, no Dlls any more (only the Qt related ones). > >OK. > >However I get now man times this warning: > >D:\LyXGit\Master\compile-2010\zconf.h(10): warning C4005: 'Z_PREFIX':

Re: Windows: release with Qt 5.5.1 or 5.6?

On Tue, Jan 12, 2016 at 06:32:11PM -0500, Scott Kostyshak wrote: > Dear all, > > There is a question of whether we should release our binary for Windows > compiled against Qt 5.5.1 or 5.6.0. > > My opinion is that we should release it with 5.5.1, unless there is a > known, significant issue that

Re: "Splitting of consecutive environments has been reworked and enhanced"

On Tue, Jan 12, 2016 at 11:49:54PM +0100, Enrico Forestieri wrote: > On Mon, Jan 11, 2016 at 03:04:33AM +, Guillaume Munch wrote: > > > For the symbol itself, my suggestion was a very elongated version of ⌟, > > meant to recall the plain separator inset. But, a character that > > would match

Re: Questions for Uwe once you are back

My time is limited and I have to focus onone Qt >>> version. I installed Qt 5.6 beta for mingw and mingw itself. Is this >the way I should go? >> >> Yes, that would be great! > >Hi Peter, > >OK, I will try this. Since I never used MinGW I expect some obstacles >and will contact you. OK? Sure!

Re: Windows: release with Qt 5.5.1 or 5.6?

Am 13. Januar 2016 00:32:11 MEZ, schrieb Scott Kostyshak : >Dear all, > >There is a question of whether we should release our binary for Windows >compiled against Qt 5.5.1 or 5.6.0. > It is not very complicated to switch between these two versions. So just let see how the

Re: Windows: release with Qt 5.5.1 or 5.6?

On Wed, Jan 13, 2016 at 01:31:59AM +0100, Peter Kümmel wrote: > Am 13. Januar 2016 00:32:11 MEZ, schrieb Scott Kostyshak : > >Dear all, > > > >There is a question of whether we should release our binary for Windows > >compiled against Qt 5.5.1 or 5.6.0. > > > > It is not very

Re: [patch] Display the correct horizontal alignment in AMS environments

Le 11/01/2016 21:41, Georg Baum a écrit : Guillaume Munch wrote: I replace stored alignment and spacing values with computed values, only in the case of specific grids under discussion (Eqnarray, AMS...). Thus, defaultColAlign() can still make sense in the future for grids that rely on stored

Re: User pref parameters

Le 12/01/2016 02:23, Pavel Sanda a écrit : Guillaume Munch wrote: I understand this idea of "freezing" the setting, in order to set a custom value on opening. The current approach I have in mind is to read and save to a per-user-per-document (cursor-location-like) setting when

Re: #9794: inset-modify tabular commands are incorrectly disabled

Le 12/01/2016 01:42, Pavel Sanda a écrit : Guillaume Munch wrote: Actually yes I am documenting a new rule, but it isn't mine. The new rule requires a LFUN format increment and a LyX format increment Do you have by chance link to LFUN format increment discussion at hand? (I have no clue what

Re: beta release

Le 12/01/2016 00:30, Scott Kostyshak a écrit : On Mon, Jan 11, 2016 at 06:28:02PM +, Guillaume Munch wrote: Le 09/01/2016 00:15, Scott Kostyshak a écrit : Does any one view an issue as a beta blocker? The situation with the parbreak separator is not good and I would see changing its