Scott Kostyshak wrote:
> I'm still not sure what the implications of moving to CMake as our
> official build system are (I should have made this more clear in my
To start with: If you make tarball with autotools and cmake is there
difference between those two, do we get the same files/and their co
> The following email thread (3 years ago) suggests that we would like to
> move to one official build system in the long-run across all platforms,
> but that there were barriers to using CMake:
> http://marc.info/?i=kmrd28$e1k$1%20()%20ger%20!%20gmane%20!%20org
>
> Have those issues been resolved?
On 06/03/2016 04:28 PM, Scott Kostyshak wrote:
> On Fri, Jun 03, 2016 at 09:38:09PM +0200, Kornel Benko wrote:
>> Am Freitag, 3. Juni 2016 um 12:42:33, schrieb Richard Heck
>>> I guess maybe there is a question worth discussing here about how many
>>> of us understand cmake well enough to modify t
Le 03/06/2016 18:40, Richard Heck a écrit :
On 06/01/2016 04:46 PM, Jean-Marc Lasgouttes wrote:
Le 01/06/16 à 18:34, Richard Heck a écrit :
I hope to do the 2.1.5 release in a week or so. Once that's been done,
and if nothing really bad has appeared in the meanwhile, then we let's
merge 2.2.2-s
Le 03/06/16 à 22:30, Scott Kostyshak a écrit :
I have set it to "unspecified". Is it better?
Yes, in my opinion this is better.
I also tried to make the ticket keyword plugin work again, but the only
thing I managed to obtain is a link to our wiki page about keywords. I
do not know how to d
On Fri, Jun 03, 2016 at 02:07:35PM +0200, Jean-Marc Lasgouttes wrote:
> Le 02/06/2016 à 06:56, Scott Kostyshak a écrit :
> > Now the default milestone is blank, which is great. Can we also have the
> > version be blank by default? I think this would help, as discussed
> > before, so that we know if
On Fri, Jun 03, 2016 at 09:38:09PM +0200, Kornel Benko wrote:
> Am Freitag, 3. Juni 2016 um 12:42:33, schrieb Richard Heck
> > On 06/03/2016 11:37 AM, José Abílio Matos wrote:
> > > On Friday, June 3, 2016 1:16:04 AM WEST Scott Kostyshak wrote:
> > >> From what I understand, most developers on Lin
Le 03/06/16 à 18:42, Richard Heck a écrit :
Same here. I am used to autotools, so I use it.
I have reservations about cmake, but I would have some against autotools
if I was not used to it already. All I ask from cmake is that it does
the right think (i.e. what we advise people to do) by defa
On Fri, Jun 03, 2016 at 09:34:15AM -0600, Joel Kulesza wrote:
> On Fri, Jun 3, 2016 at 9:11 AM, Guillaume Munch wrote:
>
> >
> > What are the
> > advantages? What are the basic commands? How do you set up
> > out-of-directory builds?
> >
> >
> I am far from an expert; however, a self-contained an
Am Freitag, 3. Juni 2016 um 12:42:33, schrieb Richard Heck
> On 06/03/2016 11:37 AM, José Abílio Matos wrote:
> > On Friday, June 3, 2016 1:16:04 AM WEST Scott Kostyshak wrote:
> >> From what I understand, most developers on Linux use autotools. I can't
> >> tell if this is because that is what mo
Jean-Marc Lasgouttes wrote:
> Le 24/05/2016 23:37, Pavel Sanda a écrit :
I only tried 2.2, so I did not really compare. I do not have 2.0 here. I
can try to have a look at 2.1 vs 2.2 later.
>>>
>>> Please try, we should see whether the problem is reproducible at all...
>>
>> Since you wer
Kornel Benko wrote:
> > --- a/src/frontends/qt4/ui/FontUi.ui
> > +++ b/src/frontends/qt4/ui/FontUi.ui
> ...
> >
> > +
> > +
> > +
> > + Activate extensions such as character protusion and font
> > expansion via the microtype package
> > +
>
> Do you mean protrusion inst
On 06/03/2016 11:37 AM, José Abílio Matos wrote:
> On Friday, June 3, 2016 1:16:04 AM WEST Scott Kostyshak wrote:
>> From what I understand, most developers on Linux use autotools. I can't
>> tell if this is because that is what most developers have experience
>> with or if it is because autotools
On 06/01/2016 04:46 PM, Jean-Marc Lasgouttes wrote:
> Le 01/06/16 à 18:34, Richard Heck a écrit :
>> I hope to do the 2.1.5 release in a week or so. Once that's been done,
>> and if nothing really bad has appeared in the meanwhile, then we let's
>> merge 2.2.2-staging and move towards a 2.2.1 relea
Now that we have 2.2.0, here are some wishes for the future:
Enumeration style document setting
==
GUI for setting the numbering style, similiar to what we already have
for bullet lists. I.e. the default for the 4 levels are "1.", "(a)",
"i.", "A."
The gui would change that
On Friday, June 3, 2016 2:02:15 PM WEST Jean-Marc Lasgouttes wrote:
> I prefer the fixed schedule. We never know exactly when starting a
> release cycle what features will happen or not. But we can enforce when
> the release will happen.
+1
--
José Abílio
On Friday, June 3, 2016 1:16:04 AM WEST Scott Kostyshak wrote:
> From what I understand, most developers on Linux use autotools. I can't
> tell if this is because that is what most developers have experience
> with or if it is because autotools has other advantages.
>
> Scott
In my case I use aut
On Fri, Jun 3, 2016 at 9:11 AM, Guillaume Munch wrote:
>
> What are the
> advantages? What are the basic commands? How do you set up
> out-of-directory builds?
>
>
I am far from an expert; however, a self-contained and somewhat compact
application of CMake is available here:
https://github.com/jk
Le 03/06/2016 06:16, Scott Kostyshak a écrit :
Dear all,
The following email thread (3 years ago) suggests that we would like to
move to one official build system in the long-run across all platforms,
but that there were barriers to using CMake:
http://marc.info/?i=kmrd28$e1k$1%20()%20ger%20!%20
Le 02/06/2016 21:33, Georg Baum a écrit :
commit 8d255ced2a003b2b8262bf51d1b245ff0dee9dc3
Author: Georg Baum
Date: Thu Jun 2 22:31:27 2016 +0200
Do not duplicate jpg format
Some qt versions report both "jpeg" and "jpg" as loadable file extensions.
In this case the jpg format w
Le 03/06/2016 à 15:03, Liviu Andronic a écrit :
We already have nightly builds for Ubuntu Linux:
https://launchpad.net/~lyx-devel/+archive/ubuntu/daily
It's been running for couple of years (probably all through the 2.2
development cycle), though I'm not sure it's made much of an impact in
terms
On Fri, Jun 3, 2016 at 2:02 PM, Jean-Marc Lasgouttes wrote:
> Le 31/05/2016 à 22:26, Georg Baum a écrit :
>>
>> We need to decide: Either have a fixed schedule, and an unknown feature
>> set
>> of the next release, or a fixed feature set, and an unknown schedule. We
>> do
>> not have enough man po
Le 02/06/2016 à 06:56, Scott Kostyshak a écrit :
Now the default milestone is blank, which is great. Can we also have the
version be blank by default? I think this would help, as discussed
before, so that we know if there is a version specified the user likely
has that version. Currently the defa
Le 31/05/2016 à 22:26, Georg Baum a écrit :
We need to decide: Either have a fixed schedule, and an unknown feature set
of the next release, or a fixed feature set, and an unknown schedule. We do
not have enough man power for defining both a fixed feature set and a fixed
release schedule.
I pre
Le 03/06/2016 à 07:24, Scott Kostyshak a écrit :
Dear all,
Are we going to require C++11 starting with LyX 2.3.0? From what I
understand, this will make several things easier.
Hello Scott,
Yes, that's the plan.
JMarc
Am Freitag, 3. Juni 2016 um 07:49:08, schrieb Pavel Sanda
> commit ba2b86fa5d718c434521a7b9722e6ccd677864ad
> Author: Pavel Sanda
> Date: Thu Jun 2 22:40:21 2016 -0700
>
> Introduce basic support for microtype.sty.
>
> https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg192743
26 matches
Mail list logo
