Re: C++ "good practices" regarding constifying a function parameter?

Op 6 aug. 2016 11:26 schreef "Abdelrazak Younes" : > > Hi Scott, > > Too late already but my 2 cents below :-) > > > On 27/07/2016 02:54, Scott Kostyshak wrote: >> >> The attached patch constifies a function parameter. My question is >> whether this patch causes more pain to other

Re: [LyX/master] Fix display of branch buttons and tooltips.

On Sat, Jul 30, 2016 at 4:58 AM, Richard Heck wrote: > commit cbbae06c9bb735759a611bad483d3a1c01d3aed7 > Author: Richard Heck > Date: Fri Jul 29 22:58:03 2016 -0400 > > Fix display of branch buttons and tooltips. [..] > - if (isOpen(bv)) > - return heading; Hi

Re: [RFC] Staging Branches and Trac

Op 16 apr. 2016 21:50 schreef "Richard Heck" : > > > As Scott pointed out, my previous suggestions for how fixes committed to > the staging branches should be handled in trac was silly. We can't reuse > "fixedinmaster" for 2.3-staging. I'm also not sure that we want to > introduce

Re: Staging Branches [REVISED]

> > We should already be on 2.2 and not on master, which is the future: 2.3 > Yes, that was also my proposal. However, people appear to be afraid to not have the 2.2.0 tag in master. But note that if the 2.2-branch in this scenario is merged back into master after the release, it is equivalent

Re: master is locked for 2.2.0rc1 preparation

On Wed, Apr 13, 2016 at 11:20 AM, Pavel Sanda wrote: > Scott Kostyshak wrote: >> B) Branch 2.2.x from master and continue "unstable" development on >> master. >> >> To me it does not feel right that the commits in-between 2.2.0rc1 and >> 2.2.0 final would not *necessarily* be in

Re: master is locked for 2.2.0rc1 preparation

Op 12 apr. 2016 22:07 schreef "Vincent van Ravesteijn" <v...@lyx.org>: > > > Op 12 apr. 2016 21:29 schreef "Jean-Marc Lasgouttes" <lasgout...@lyx.org>: > > > > > Le 12/04/16 18:45, Scott Kostyshak a écrit : > > > >> So in th

Re: master is locked for 2.2.0rc1 preparation

Op 12 apr. 2016 21:29 schreef "Jean-Marc Lasgouttes" : > > Le 12/04/16 18:45, Scott Kostyshak a écrit : > >> So in the commit history of master we will not see the final 2.2.0 >> release (e.g. fde16219 for 2.1.0)? >> >> Have we done this before in this way? > > > No Vincent did

Re: [LyX/master] Fix 480937a103708a651/lyxgit. See also #9740.

On Fri, Nov 13, 2015 at 11:35 AM, Guenter Milde wrote: > On 2015-11-12, Kornel Benko wrote: >> Am Donnerstag, 12. November 2015 um 16:18:12, schrieb Guenter Milde > >>> As a proof of concept, I also changed lib/doc/el/Intro.lyx to use >>> DejaVu as non-TeX font. A similar

Re: [PATCH] Bug #9854 "Dataloss after git merge with change tracking"

On Thu, Nov 12, 2015 at 8:12 PM, Georg Baum <georg.b...@post.rwth-aachen.de> wrote: > Vincent van Ravesteijn wrote: > >> I doubt whether it is a good thing to start fiddling with the document >> when we read in a corrupt file. >> >> Version control systems can

Re: [PATCH] Bug #9854 "Dataloss after git merge with change tracking"

On Thu, Nov 12, 2015 at 4:41 PM, Jean-Marc Lasgouttes wrote: > Le 11/11/2015 23:12, Guillaume Munch a écrit : >> >> Dear list, >> >> >> The patch below fixes bug #9854. () >> Find more details in the commit log. >> >> I have two questions:

Re: We now include both png and svgz?

On Wed, Nov 11, 2015 at 1:02 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > Le 10/11/2015 10:02, Vincent van Ravesteijn a écrit : >> >> At the moment you cannot use LyX with Qt4 because it cannot read svgz >> files, and the code is not correctly falling back to

Re: We now include both png and svgz?

On Tue, Nov 10, 2015 at 4:13 AM, Scott Kostyshak wrote: > When experimenting with building the tar balls, I noticed a significant > difference in size between 2.2.0dev and 2.1.4. > > lyx-2.1.4.tar.gz is 20.8 MB > lyx-2.2.0dev.tar.gz is 24.8 MB > > A quick check seems to show

Re: Plan for the current testing situation

>> Ideally, I would like for commits that break tests to be on a separate git >> branch. Once the bugs exposed by a commit are fixed or the tests are fixed, or >> the .lyx files are fixed, then the branch could be merged to master. This >> allows us to presere a "0 failing tests" situation on the

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

> Democracy is not the point IMHO: The point is not to further delay the > release. Implementing a small and safe file format change where everybody > agrees that it is useful does not produce a significant delay. Discussing a > controversal change where no easy solution is in sight has the

Re: Two Shortcut Changes

Op 5 nov. 2015 21:48 schreef "Jean-Marc Lasgouttes" : > > Le 05/11/15 21:34, Richard Heck a écrit : > >>> I've used PSTricks extensively with LyX. Having a shortcut to ps >>> output has been very convenient. >> >> >> This seems like a case where you should set the default

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

On Fri, Nov 6, 2015 at 10:08 AM, Jean-Marc Lasgouttes wrote: > Le 06/11/2015 10:06, Stephan Witt a écrit : >> >> In this sense there is no need to reduce the likely-hood of merge >> conflicts >> with the state of change tracking. It's not a setting to toggle often, >> IMHO. >

Re: make lyxdist giving me an error

On Thu, Nov 5, 2015 at 9:57 AM, Scott Kostyshak wrote: > I have been reading up on the release process at various sources, > including http://wiki.lyx.org/Devel/ReleaseProcedure. > > The following command > ./autogen.sh && ./configure --enable-build-type=pre && make lyxdist >

Re: make lyxdist giving me an error

On Thu, Nov 5, 2015 at 10:31 AM, Vincent van Ravesteijn <v...@lyx.org> wrote: > On Thu, Nov 5, 2015 at 9:57 AM, Scott Kostyshak <skost...@lyx.org> wrote: >> I have been reading up on the release process at various sources, >> including http://wiki.lyx

Re: [ALPHA] Change Toggling Bug

Op 5 nov. 2015 22:44 schreef "Richard Heck" : > > On 11/05/2015 04:02 PM, Jean-Marc Lasgouttes wrote: >> >> Le 05/11/15 21:41, Richard Heck a écrit : >>> >>> Trivial fix: >> >> >> > case LFUN_CHANGES_TRACK: >> > buffer_.params().track_changes = >> >

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Op 6 nov. 2015 05:44 schreef "Pavel Sanda" : > > Guillaume Munch wrote: > > That "CT lock" feature, instead of imposing such a strict constraint > > (that could always be circumvented one way or the other...), could maybe > > display instead a message like "Pavel Sanda has requested

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Op 4-11-2015 om 21:06 schreef Georg Baum: Guillaume Munch wrote: Le 03/11/2015 21:16, Georg Baum a écrit : I don't think there is an easy solution, because it depends on the use case. For example, in our documentation workflows \tracking_changes needs to be the same for all users, so this

Re: [LyX/master] Document the export tests and other tests

On Thu, Nov 5, 2015 at 8:27 AM, Guenter Milde wrote: > On 2015-11-04, Georg Baum wrote: >> Guenter Milde wrote: > >>> On 2015-10-30, Georg Baum wrote: Kornel Benko wrote: > These directories are clearly not suitable for pure test files, so I'll need to add a new

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

On Thu, Nov 5, 2015 at 7:12 AM, Pavel Sanda <sa...@lyx.org> wrote: > Vincent van Ravesteijn wrote: >> > I consider it also document, not user, setting. It would cause confusions >> > if this setting is not transfered to my collaborators within the document. >> >

Re: [LyX/master] Math.lyx: replace tables by formal ones - final part 7/7

Op 4-11-2015 om 20:15 schreef Guenter Milde: On 2015-11-04, Kornel Benko wrote: [-- Type: text/plain, Encoding: quoted-printable --] Am Dienstag, 3. November 2015 um 00:23:47, schrieb Uwe Stöhr commit 279d0849460aac82c3adeac42d3f0e255274e7c8 Author: Uwe Stöhr

Re: Unit testing

> If there is no known advantage of gtest, I suggest using one of > boost::test or QTest, as these come from sources we already rely on. > The major advantage of "gtest" is that I only have to type "git push" and we have the framework up and running. A downside of boost::test is, according

Re: status update on the export tests

> In my view, suspension is orthogonal to reversion: > > - normal: we want the test to pass > revert: we want the test to fail You mean: revert is that "it is known to fail", but we haven't fixed it yet. > > - normal: run the test > suspend: skip the test temporarily > ignore: skip the

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

On Wed, Nov 4, 2015 at 1:50 AM, Guillaume Munch wrote: > Le 03/11/2015 21:16, Georg Baum a écrit : >> >> Guillaume Munch wrote: >> >>> >>> >>> I am bringing this to the list due to the timing, due to the fact that >>> it is a file format change,

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

On Wed, Nov 4, 2015 at 7:26 AM, Pavel Sanda wrote: > Guillaume Munch wrote: >> For \track_changes, I do not understand your rationale for making it a >> setting of the document. It is not locked on, so the user who edits the >> documentations has to know in any case that he should

Re: Unit testing

>> Any comments ? Shall I proceed to push this to master ? >> >> Vincent >> > > Having a unit test framework integrated is a very good idea! > > Why have you chosen gtest and not QTest? Does gtest has interesting > features which QTest does not have? I'm not very experienced with unit testing, so

Re: Unit testing

On Tue, Nov 3, 2015 at 2:28 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > Le 02/11/2015 21:36, Vincent van Ravesteijn a écrit : >> >> Dear all, >> >> I have prepared a unit test framework based on google-test (gtest). You >> can see the commits at

Unit testing

Dear all, I have prepared a unit test framework based on google-test (gtest). You can see the commits at http://git.lyx.org/?p=developers/vfr/lyx.git;a=shortlog;h=refs/heads/tests. It includes gtest-1.7.0 (permitted by the license). Unit testing can be enabled by running CMake with

Re: Upgrade to boost 1.59?

On Sun, Nov 1, 2015 at 4:51 PM, Scott Kostyshak <skost...@lyx.org> wrote: > On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote: >> Am 25.10.2015 um 06:19 schrieb Scott Kostyshak: >> >On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote: >&g

Re: Compiling LyX on Windows with more recent Visual Studio versions

Op 31-10-2015 om 14:44 schreef PhilipPirrip: On 10/31/2015 09:27 AM, PhilipPirrip wrote: Thanks, David. It did work with Qt 4.8.6 First thing I noticed, though, is that most icons are missing. Have to investigate. I remember seeing a similar issue here on the list recently. The errors

Re: Many tex2lyx failing now on master

Op 29-10-2015 om 18:33 schreef Kornel Benko: The problem was, that cmake accumulated messages from runtests.py. Now runtests.py is called for each file separately. Vincent, have you checked if that is OK to you? Kornel It indeed works much better. I just don't understand what the

Re: tests: file(TIMESTAMP ... ) requires CMake 2.8.11

On Wed, Oct 28, 2015 at 10:47 PM, Kornel Benko <kor...@lyx.org> wrote: > Am Mittwoch, 28. Oktober 2015 um 22:12:19, schrieb Vincent van Ravesteijn > <v...@lyx.org> >> Using CMake version 2.8.10, all tex2lyx tests fail due to the use of >> >> file( TI

Re: Many tex2lyx failing now on master

Op 28-10-2015 om 17:02 schreef Kornel Benko: It looks like the relevant code to set environment for tests added by add_test() command is in the cmake-sources at lest since february 2009. Searching the net, there are posts mentioning cmake2.6 with this feature. So I cannot imagine, why the

check_lstrings fails at Windows

The entries that are different from the test_lstrings reference file are for the inputs { ... 1.3754937356458394574047e17, 1.3754937356458394574047e18, 1.3754937356458394574047e19, 1.3754937356458394574047e20, ... 1e42 } and the outputs are: { ... 137549373564583950 1375493735645839400

tests: file(TIMESTAMP ... ) requires CMake 2.8.11

Using CMake version 2.8.10, all tex2lyx tests fail due to the use of file( TIMESTAMP .. ) in runtests.cmake. The TIMESTAMP command is available since CMake 2.8.11. Vincent

Re: Many tex2lyx failing now on master

> > It is only a bit > > annoying that I have to wait for a long time without getting any > > feedback on the progress. > > > > Vincent > > > > I don't feel guilty. I don't remember anyone saying anything about the 'env' command before. > > What do you mean with feedback about progress? > >

Re: [patch] update modernCV layout file

On Tue, Oct 27, 2015 at 12:56 AM, Uwe Stöhr wrote: > Am 26.10.2015 um 16:51 schrieb Stephan Witt: > >> You missed the "Change to the build-directory." part of Kornels advice. >> >> I think "D:\LyXGit\Master\lib\examples" isn't your build directory or at >> least it shouldn't be

Re: [patch] update modernCV layout file

> > The same is with updating the tex2lyx reference files. I asked on the list > but got not reply how I can do this: > http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg189509.html > Yes, sorry that it took me a few days to take up the issue. The others probably have a hard time debugging

Re: Many tex2lyx failing now on master

>> >> Well yes, there is no "env" command on Windows. > > Sorry, I did not knew about this. > >> This is used in both "src/tests/CMakeLists.txt" and >> "src/tex2lyx/CMakeLists.txt". > > I will look into this. Unfortunately the 'add_test()' command does hot have a > parameter to set the

Re: Many tex2lyx failing now on master

When I try to compile this file via the console or directly in MSVC I get always this error: Building Custom Rule D:/LyXGit/Master/src/tex2lyx/test/CMakeLists.txt CMake does not need to re-run because D:\LyXGit\Master\compile-result\src\tex2lyx\test\CMakeFiles\generate.stamp is up-to-date.

Re: [patch] update modernCV layout file

Op 26 okt. 2015 14:10 schreef "Uwe Stöhr" : > > Am 26.10.2015 um 06:31 schrieb Scott Kostyshak: > >>> I think it is safe enough to support 2 years old features and would >>> therefore like to put it in. >> >> >> Do we have any policy on this? What have we done in the past? > > >

Re: [LyX/master] colored-boxes.lyx: new example file for the tcolorbox.module

Op 25-10-2015 om 22:12 schreef Uwe Stöhr: Am 25.10.2015 um 11:08 schrieb Georg Baum: And if something is wrong with them, we should invest the time and improve our formatted references support, instead of fiddling with the premable. I set up www.lyx.org/trac/ticket/9817 for this issue. And

Re: Minimum compiler version

Op 24-10-2015 om 7:13 schreef Peter Kümmel: Am 23.10.2015 um 21:34 schrieb Vincent van Ravesteijn: support of MSVC2010. I think I don't need to tell Peter about MSVC support for C++11 (I guess he knows better than me). The message was really meant for you: if you introduce C++11 features

Re: back to LyX and therefore questions concerning LyX 2.2

Op 24 okt. 2015 20:42 schreef "Uwe Stöhr" : > > Am 23.10.2015 um 10:25 schrieb Jean-Marc Lasgouttes: > >> If you look closely, they are not closer than the vertival line over B_V >> is fromthe text. Seriously this is a much bigger problem > > > But it still doesn't look as good

Re: Upgrade to boost 1.59?

Op 23 okt. 2015 17:37 schreef "Jean-Marc Lasgouttes" : > > I think we should upgrade our local copy of boost to 1.59 before alpha (or at least before beta). > > Is the procedure documented somewhere? > > Also, what can we do to hide the warnings related to auto_ptr? If we are

Re: Minimum compiler version

Op 23-10-2015 om 20:55 schreef Guillaume Munch: Le 23/10/2015 17:55, Peter Kümmel a écrit : I wonder to still see auto_ptr: https://travis-ci.org/syntheticpp/lyx Which old compiler you wanna support? Peter Dear Peter, See

Re: back to LyX and therefore questions concerning LyX 2.2

Op 23-10-2015 om 9:15 schreef Pavel Sanda: So back to Uwe's question, it would be good you announce at some point - features won't change ( except of bugfixing ) - translatable strings are not going to be changed (except obvious bugs/typos). and maybe give some hint when this might occur :)

Re: Minimum compiler version

Op 23-10-2015 om 21:22 schreef Guillaume Munch: Le 23/10/2015 20:16, Vincent van Ravesteijn a écrit : Op 23-10-2015 om 20:55 schreef Guillaume Munch: Le 23/10/2015 17:55, Peter Kümmel a écrit : I wonder to still see auto_ptr: https://travis-ci.org/syntheticpp/lyx Which old compiler you

Re: back to LyX and therefore questions concerning LyX 2.2

On Thu, Oct 22, 2015 at 7:13 AM, Scott Kostyshak wrote: > On Mon, Oct 19, 2015 at 04:33:43PM +0200, Uwe Stöhr wrote: >> Dear LyXers, >> >> I would like to have a beta release short after the feature-freeze. >> During the beta and RC-cycle the docs will be updated because this >>

Re: LyX's master is now uncompilable

Op 19-10-2015 om 23:36 schreef Guillaume Munch: Le 19/10/2015 21:59, Vincent van Ravesteijn a écrit : Op 19 okt. 2015 22:51 schreef "Guillaume Munch" <g...@lyx.org <mailto:g...@lyx.org>>: > > Le 19/10/2015 21:34, Georg Baum a écrit : >> >> >>

Re: LyX's master is now uncompilable

Op 20-10-2015 om 20:06 schreef Georg Baum: Guillaume Munch wrote: I'll let Vincent decide whether he wants to make this change. Sure, our messages crossed each other, I would not have suggested that if I knew that he had time to test. The compilation error could btw easily be fixed by moving

Re: When to court Qt 5.6?

Op 15 okt. 2015 08:37 schreef "Jean-Marc Lasgouttes" : > > Le 15/10/15 01:06, Scott Kostyshak a écrit : > >> LyX 2.2.0 and the following 2.2.x releases will still continue to work >> well with Qt 4.8.6 but will also support Qt 5.6, which brings some >> advantages most notably

Re: When to court Qt 5.6?

Op 20 okt. 2015 02:32 schreef "Uwe Stöhr" : > > Am 15.10.2015 um 01:18 schrieb Scott Kostyshak: > >> Uwe can you confirm that shipping our alpha with Qt 5.6 beta is >> feasible for you? > > > Hi Scott, > > I am open for anything. I think that i will need in any case some help

Re: When to court Qt 5.6?

Op 20 okt. 2015 20:35 schreef "Georg Baum" : > > Uwe Stöhr wrote: > > > Besides this I am still using MSVC 2010. I need to update to MSVC 2012 > > or newer and this is another challenge. I already tested MSVC 2012 with > > Qt 5.5 with success. Let's see what Qt 5.6

Re: Where is the script that posts to lyx-cvs?

On Mon, Oct 19, 2015 at 1:38 PM, Jean-Marc Lasgouttes wrote: > > The title says it all. I'd like to add some header in there that the lyx-cvs > list can use to allow the message, instead of restricting to subscribers. > > JMarc It is in a git hook in a script called

Re: LyX's master is now uncompilable

Op 19 okt. 2015 22:51 schreef "Guillaume Munch" : > > Le 19/10/2015 21:34, Georg Baum a écrit : >> >> >> The message on the list is related to commit e948caf6, which is supposed to >> fix exactly this issue. What I do not understand it why the fix does not >> work for your recent

Re: [LyX/master] cmake: Put updatetex2lyxtests in an appropriate folder

Op 19-10-2015 om 18:45 schreef Kornel Benko: Am Montag, 19. Oktober 2015 um 18:02:02, schrieb Vincent van Ravesteijn <v...@lyx.org> commit 92b7c5a92f21956f6da19c8ac783cd9132ca82b9 Author: Vincent van Ravesteijn <v...@lyx.org> Date: Mon Oct 19 17:50:59 2015 +0200

Re: LyX's master is now uncompilable

Op 19-10-2015 om 19:04 schreef Uwe Stöhr: Am 19.10.2015 um 18:26 schrieb Guillaume Munch: I fail to see a problem with this commit after reading it again. I would like to do some trial-and-error but not being able to reproduce makes it complicated. It is also not clear to me what triggers

Re: [LyX/master] chkconfig.ltx: add packages supported by LyX

Op 18-10-2015 om 15:21 schreef Uwe Stöhr: commit c246ca2d43663dbce3d3052b2ae9459b45bf4acc Author: Uwe Stöhr Date: Sun Oct 18 15:21:50 2015 +0200 chkconfig.ltx: add packages supported by LyX - also update Win installer package list (trimspaces is required by

Re: [LyX/master] Fix typo

On Tue, Oct 13, 2015 at 8:45 AM, Jean-Marc Lasgouttes wrote: > Le 13/10/15 02:08, Scott Kostyshak a écrit : >> >> On Mon, Oct 12, 2015 at 11:49:42AM +0200, Jean-Marc Lasgouttes wrote: >>> >>> Le 12/10/2015 11:16, Stephan Witt a écrit : Am 12.10.2015 um 11:04 schrieb

Re: [LyX/master] Comply with rule-of-three

Op 12-10-2015 om 4:17 schreef Scott Kostyshak: On Sun, Oct 11, 2015 at 11:20:15AM +0200, Georg Baum wrote: commit cea2d71e641e6a4023128a367d1cd5a593ed1706 Author: Georg Baum Date: Sun Oct 11 11:16:09 2015 +0200 Comply with rule-of-three The rule-of-three says

Re: When to court Qt 5.6?

Op 12 okt. 2015 15:14 schreef "Liviu Andronic" : > > On Mon, Oct 12, 2015 at 1:39 PM, Jean-Marc Lasgouttes > wrote: > > Le 12/10/2015 12:45, Liviu Andronic a écrit : > >> > >> True. :) What is the current minimum Qt 5.x requirement? > > > > > > I do not

Re: Failing tex2lyx tests

On Wed, May 20, 2015 at 12:24 AM, Uwe Stöhr uwesto...@web.de wrote: Am 19.05.2015 um 21:20 schrieb Georg Baum: unfortunately the tex2lyx test failures increased (see attachment). Are you aware that this wastes time of developers? Did you see the questions Scott ansd I asked about the failing

Re: Failing tex2lyx tests

On Wed, May 20, 2015 at 12:24 AM, Uwe Stöhr wrote: > Am 19.05.2015 um 21:20 schrieb Georg Baum: > >> unfortunately the tex2lyx test failures increased (see attachment). Are >> you >> aware that this wastes time of developers? Did you see the questions Scott >> ansd I asked about

New requirement: X11/Intrisic.h

Since commit ([52fee355/lyxgit]; Fix external middle-mouse pasting with Qt5/X11), I need X11/Intrinsic.h for which I had to install the package libxt-devel. Does this need a check in configure.ac ?, and/or a note in the RELEASE_NOTES ? Vincent

Re: [LyX/master] Make RELEASE-NOTES accessible from GUI (#8616)

On Tue, May 19, 2015 at 9:59 AM, Juergen Spitzmueller sp...@lyx.org wrote: commit 9f55ce9b04c1786c5bed52afc9028f287d28bb32 Author: Juergen Spitzmueller sp...@lyx.org Date: Tue May 19 09:57:52 2015 +0200 Make RELEASE-NOTES accessible from GUI (#8616) CMake people, please check if

Re: [LyX/master] Add Qt's Svg module to the list of used modules. This is required to allow the use of e.g. the QSvgRenderer class.

Stephan Witt schreef op 19-5-2015 om 22:48: commit 0933df00113ee2735699c13559ad3b6e7e9fd115 Author: Stephan Witt sw...@lyx.org Date: Tue May 19 08:11:01 2015 +0200 Add Qt's Svg module to the list of used modules. This is required to allow the use of e.g. the QSvgRenderer class. Is

New requirement: X11/Intrisic.h

Since commit ([52fee355/lyxgit]; "Fix external middle-mouse pasting with Qt5/X11"), I need X11/Intrinsic.h for which I had to install the package libxt-devel. Does this need a check in configure.ac ?, and/or a note in the RELEASE_NOTES ? Vincent

Re: [LyX/master] Make RELEASE-NOTES accessible from GUI (#8616)

On Tue, May 19, 2015 at 9:59 AM, Juergen Spitzmueller wrote: > commit 9f55ce9b04c1786c5bed52afc9028f287d28bb32 > Author: Juergen Spitzmueller > Date: Tue May 19 09:57:52 2015 +0200 > > Make RELEASE-NOTES accessible from GUI (#8616) > > CMake people, please

Re: [LyX/master] Add Qt's Svg module to the list of used modules. This is required to allow the use of e.g. the QSvgRenderer class.

Stephan Witt schreef op 19-5-2015 om 22:48: commit 0933df00113ee2735699c13559ad3b6e7e9fd115 Author: Stephan Witt Date: Tue May 19 08:11:01 2015 +0200 Add Qt's Svg module to the list of used modules. This is required to allow the use of e.g. the QSvgRenderer class. Is

Re: 2.2

Jean-Marc Lasgouttes schreef op 13-5-2015 om 10:42: Hi there, The ritual question: what is still needed for 2.2? I guess we are still waiting for some python 3.3 goodness from José, but what else? It seems to me that publishing a beta version soon is very desirable. Consider that for 2.1

Re: boost update?

Georg Baum schreef op 16-5-2015 om 10:19: Hi, I tested LyX with boost 1.58, and it compiles and runs fine. Shall I update the included boost? This would get rid of some compiler warnings, and since 2.2 will live for a while I guess it is good to start with a recent boost, since a boost update

Re: boost update?

Op 18 mei 2015 22:20 schreef Georg Baum georg.b...@post.rwth-aachen.de: Vincent van Ravesteijn wrote: Last time I tried (not so long ago), I hit a lot of new compiler errors, which I didn't know how to fix. Thank you for fixing those.. It was easy, it was only one: b596330093d. Maybe

Re: 2.2

Jean-Marc Lasgouttes schreef op 13-5-2015 om 10:42: Hi there, The ritual question: what is still needed for 2.2? I guess we are still waiting for some python 3.3 goodness from José, but what else? It seems to me that publishing a beta version soon is very desirable. Consider that for 2.1

Re: boost update?

Georg Baum schreef op 16-5-2015 om 10:19: Hi, I tested LyX with boost 1.58, and it compiles and runs fine. Shall I update the included boost? This would get rid of some compiler warnings, and since 2.2 will live for a while I guess it is good to start with a recent boost, since a boost update

Re: boost update?

Op 18 mei 2015 22:20 schreef "Georg Baum" <georg.b...@post.rwth-aachen.de>: > > Vincent van Ravesteijn wrote: > > > Last time I tried (not so long ago), I hit a lot of new compiler errors, > > which I didn't know how to fix. > > > > Thank you fo

Re: C++ question about const

Scott Kostyshak schreef op 22-4-2015 om 3:37: My question is in regards to the patch I propose for #6173: http://www.lyx.org/trac/attachment/ticket/6173/0001-Update-previews-when-going-to-a-bookmark-6173.patch I move the definition of cur up because I need it before the return. I then need to

Re: C++ question about const

Scott Kostyshak schreef op 22-4-2015 om 3:37: My question is in regards to the patch I propose for #6173: http://www.lyx.org/trac/attachment/ticket/6173/0001-Update-previews-when-going-to-a-bookmark-6173.patch I move the definition of cur up because I need it before the return. I then need to

Re: 2 dataloss warnings after merge of remote-tracking branch

On Tue, Jan 13, 2015 at 10:14 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 13/01/2015 01:22, Uwe Stöhr a écrit : My change allowed to set the line width to any value you like. As i had to set a default width I chose 0.5 because this is already a LaTeX default width (if I remember

Re: 2 dataloss warnings after merge of remote-tracking branch

On Tue, Jan 13, 2015 at 11:27 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 11/01/2015 11:53, Georg Baum a écrit : Because they are on by default in MSVC and off by default in gcc. You can get similar ones with gcc by calling it with -Wconversion (but that outputs many more). gcc

Re: 2 dataloss warnings after merge of remote-tracking branch

Another thing if we use C++11 mode is that auto_ptr is deprecated. Who knows what to do about that? I googled it for you: ;) Note: This class template is deprecated as of C++11. unique_ptr is a new facility with a similar functionality, but with improved security (no fake copy assignments),

Re: [LyX/master] Remove direct calls of exit()

Georg Baum schreef op 9-1-2015 om 21:44: commit ca6fba31fbc44e4b4ed6457b16f3f0d2ee28b7f0 Author: Georg Baum b...@lyx.org Date: Fri Jan 9 21:43:45 2015 +0100 Remove direct calls of exit() This is a preparation for using QCoreApplication. @@ -1047,9 +1048,11 @@ int main(int

Re: 2 dataloss warnings after merge of remote-tracking branch

On Tue, Jan 13, 2015 at 10:14 AM, Jean-Marc Lasgouttes wrote: > Le 13/01/2015 01:22, Uwe Stöhr a écrit : >> >> My change allowed to set the line width to any value you like. As i had >> to set a default width I chose 0.5 because this is already a LaTeX >> default width (if I

Re: 2 dataloss warnings after merge of remote-tracking branch

On Tue, Jan 13, 2015 at 11:27 AM, Jean-Marc Lasgouttes wrote: > Le 11/01/2015 11:53, Georg Baum a écrit : >> >> Because they are on by default in MSVC and off by default in gcc. You can >> get similar ones with gcc by calling it with -Wconversion (but that >> outputs >> many

Re: 2 dataloss warnings after merge of remote-tracking branch

> > Another thing if we use C++11 mode is that auto_ptr is deprecated. Who knows > what to do about that? > I googled it for you: ;) "Note: This class template is deprecated as of C++11. unique_ptr is a new facility with a similar functionality, but with improved security (no fake copy

Re: [LyX/master] Remove direct calls of exit()

Georg Baum schreef op 9-1-2015 om 21:44: commit ca6fba31fbc44e4b4ed6457b16f3f0d2ee28b7f0 Author: Georg Baum Date: Fri Jan 9 21:43:45 2015 +0100 Remove direct calls of exit() This is a preparation for using QCoreApplication. @@ -1047,9 +1048,11 @@ int

Re: current master uncompilable under Windows

On Fri, Jan 9, 2015 at 11:19 AM, Kornel Benko kor...@lyx.org wrote: Am Donnerstag, 8. Januar 2015 um 20:08:35, schrieb Georg Baum georg.b...@post.rwth-aachen.de Vincent van Ravesteijn wrote: On Thu, Jan 8, 2015 at 10:13 AM, Kornel Benko kor...@lyx.org wrote: Am Mittwoch, 7. Januar 2015 um

Re: current master uncompilable under Windows

On Fri, Jan 9, 2015 at 11:19 AM, Kornel Benko <kor...@lyx.org> wrote: > Am Donnerstag, 8. Januar 2015 um 20:08:35, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> >> Vincent van Ravesteijn wrote: >> >> > On Thu, Jan 8, 2015 at 10:13 AM, Kornel Benko &l

Re: current master uncompilable under Windows

On Thu, Jan 8, 2015 at 10:13 AM, Kornel Benko kor...@lyx.org wrote: Am Mittwoch, 7. Januar 2015 um 21:32:25, schrieb Jean-Marc Lasgouttes lasgout...@lyx.org Le 07/01/2015 02:41, Uwe Stöhr a écrit : compiling current master I get 2 compilation errors: This looks like a missing dependency in

Re: 2.2 (was: Re: Retina support)

On Tue, Jan 6, 2015 at 7:58 PM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 04/01/2015 15:00, Stephan Witt a écrit : Is it possible to make a 2.2 release in a foreseeable future? As far as I am concerned, I'd just like to land the scroll-reloaded branch ASAP. It will not improve any

Re: current master uncompilable under Windows

On Thu, Jan 8, 2015 at 10:13 AM, Kornel Benko wrote: > Am Mittwoch, 7. Januar 2015 um 21:32:25, schrieb Jean-Marc Lasgouttes > >> Le 07/01/2015 02:41, Uwe Stöhr a écrit : >> > compiling current master I get 2 compilation errors: >> >> This looks like a

Re: 2.2 (was: Re: Retina support)

On Tue, Jan 6, 2015 at 7:58 PM, Jean-Marc Lasgouttes wrote: > Le 04/01/2015 15:00, Stephan Witt a écrit : >> >> Is it possible to make a 2.2 release in a foreseeable future? > > > As far as I am concerned, I'd just like to land the scroll-reloaded branch > ASAP. It will not

Install package texlive-esint-type1

Hi all, To compile the User's guide, I had to manually install the package texlive-esint-type1. Shouldn't this be installed automatically when the lyx package is installed ? I'm now at OpenSuse. Do other distros do install this package ? How can we inform the distros that this package is

[PATCH] str-metrics: Prevent clipping of chars with negative bearing

JMarc, The following fixes the clipping of characters with negative bearing, like the f, at the end of a sentence. This happens when part of the word is selected. To reproduce: 1. Start a new document 2. Type af 3. Select 'a' 4. Observe that the right part of the 'f' is clipped away. This patch

[PATCH] str-metrics: Prevent clipping of chars with negative bearing

JMarc, The following fixes the clipping of characters with negative bearing, like the "f", at the end of a sentence. This happens when part of the word is selected. To reproduce: 1. Start a new document 2. Type "af" 3. Select 'a' 4. Observe that the right part of the 'f' is clipped away. This

Install package texlive-esint-type1

Hi all, To compile the User's guide, I had to manually install the package "texlive-esint-type1". Shouldn't this be installed automatically when the lyx package is installed ? I'm now at OpenSuse. Do other distros do install this package ? How can we inform the distros that this package is

Compilation with Autotools and Qt5

Hi all, Apparently we need to append the following arguments to configure to be able to compile with qt5 and autotools (already discussed in https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg185551.html): configure --enable-qt5 CPPFLAGS=-fPIC --disable-concept-checks Should we make

  1   2   3   4   5   6   7   8   9   10   >