On Thu, Mar 10, 2016 at 12:50:25AM +0100, Uwe Stöhr wrote:
> Am 09.03.2016 um 04:37 schrieb Scott Kostyshak:
>
> >8. What am I missing?
>
> - I need for Qt 5.6 this patch from Peter to be applied:
> https://github.com/syntheticpp/lyx/commit/2470fb442cb2b04a69b2030f28f1da60221556a7?diff=unified
P
On Wed, Mar 09, 2016 at 09:40:38PM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > Dear all,
> >
> > I think we are getting close to being able to release 2.2.0rc1. We have
> > not discussed whether to release a beta3 or move directly to rc1. If
> > others disagree with moving directly to
On Thu, Mar 10, 2016 at 03:29:08PM +, José Matos wrote:
> On Wednesday, March 09, 2016 03:33:47 PM José Matos wrote:
> > This is an easy task. The lyx2lyx code follows untested and it should be
> > correct (TM).
> >
> > From the original patch the changes to lib/lyx2lyx/lyx_2_1.py should be
On Wed, Mar 09, 2016 at 07:40:34PM +, Guenter Milde wrote:
> On 2016-03-09, Scott Kostyshak wrote:
>
> > [-- Type: text/plain, Encoding: quoted-printable --]
>
> > On Sat, Mar 05, 2016 at 09:36:43PM +, Guenter Milde wrote:
>
> >> After all, this is a know upstream bug, not a "real" LyX i
On Wed, Mar 09, 2016 at 09:07:14PM +0100, Jean-Marc Lasgouttes wrote:
> Actually the concept was :
> 1. Take a quick look at the relevant makefile
> 2. If it looks difficult to fix then
>2.1 pretend you don't have time for pointless stuff
> Else
>2.2 fix the bug and brag about it.
Nice ap
On Thu, Mar 10, 2016 at 10:49:11AM +0100, Jürgen Spitzmüller wrote:
> 2016-03-09 19:55 GMT+01:00 Scott Kostyshak :
>
> > More out of curiosity than practical concern, are the following two
> > statements correct?
> >
> > 1. This patch could cause some documents that compile on 2.1.x to not
> > com
Hi Eran,
On Wed, Mar 09, 2016 at 03:53:22PM -0700, Eran Kaplinsky wrote:
> The implementation of separators in this version is a little different and
> confusing. Frame separators that show up as lines in 2.1 appear as an
> unfamiliar character, but not as a separator in the paragraph style. In
>
On Thu, Mar 10, 2016 at 09:32:36PM +0100, Jean-Marc Lasgouttes wrote:
> Thanks. So it's me after all. I'll handle it.
It seems like a minor issue (that no one reported in 2 years of testing
on master), so if you think it's better to wait, then I think that would
be fine. Your call.
Scott
signat
Thanks. So it's me after all. I'll handle it.
JMarc
Le 10 mars 2016 21:20:04 GMT+01:00, Scott Kostyshak a écrit :
>On Thu, Mar 10, 2016 at 05:04:24PM +0100, Jean-Marc Lasgouttes wrote:
>> Le 07/03/2016 18:26, Scott Kostyshak a écrit :
>> >>Does this patch fix the problem for you? I had to add ex
On Thu, Mar 10, 2016 at 05:04:24PM +0100, Jean-Marc Lasgouttes wrote:
> Le 07/03/2016 18:26, Scott Kostyshak a écrit :
> >>Does this patch fix the problem for you? I had to add explicit tests for
> >>some inset codes, but that will be OK for now. The problem is that we allow
> >>putting the cursor
Le 07/03/2016 18:26, Scott Kostyshak a écrit :
Does this patch fix the problem for you? I had to add explicit tests for
some inset codes, but that will be OK for now. The problem is that we allow
putting the cursor on the row preceding display math, but not after a
newline inset. I plan to rewrit
On Wednesday, March 09, 2016 03:33:47 PM José Matos wrote:
> This is an easy task. The lyx2lyx code follows untested and it should be
> correct (TM).
>
> From the original patch the changes to lib/lyx2lyx/lyx_2_1.py should be
> dropped as we are not changing the format there but only in 2.2.
>
Le 09/03/2016 20:06, Scott Kostyshak a écrit :
It works now. Thank you.
It is in.
JMarc
2016-03-09 19:55 GMT+01:00 Scott Kostyshak :
> More out of curiosity than practical concern, are the following two
> statements correct?
>
> 1. This patch could cause some documents that compile on 2.1.x to not
> compile with 2.2.0, if they have a certain block of ERT or preamble
> code. I guess t
14 matches
Mail list logo
