On Fri, Feb 16, 2018 at 09:43:54PM +, Jean-Marc Lasgouttes wrote:
> Le 16/02/2018 à 22:24, Scott Kostyshak a écrit :
> > To reproduce,
> >
> > 1. Insert an ERT
> > 2. Type <<"hello">> inside the ERT (include the " quotation marks)
> > 3. Select all inside the ERT so all contents inside the ERT
Le 16/02/2018 à 13:14, Jean-Pierre Chrétien a écrit :
Le 16/02/2018 à 10:29, Sam Lewis a écrit :
In a beamer frame, two boxes (minipages, drop shadow) are place in columns
next to each other. Everything works fine, except in the first frame one of
the boxes including text is always red.
The
Le 16/02/2018 à 22:24, Scott Kostyshak a écrit :
To reproduce,
1. Insert an ERT
2. Type <<"hello">> inside the ERT (include the " quotation marks)
3. Select all inside the ERT so all contents inside the ERT are
selected, but the inset as a whole is not selected.
4. cut
5. paste
Note that y
To reproduce,
1. Insert an ERT
2. Type <<"hello">> inside the ERT (include the " quotation marks)
3. Select all inside the ERT so all contents inside the ERT are
selected, but the inset as a whole is not selected.
4. cut
5. paste
I get an "Uncodable content" regression. I don't know if this is
2018-02-16 18:05 GMT+01:00 Richard Heck :
> On 02/14/2018 01:21 PM, Jürgen Spitzmüller wrote:
> > Am Mittwoch, den 14.02.2018, 12:50 -0500 schrieb Richard Heck:
> >> I wonder if what we really need to do here is add the 'unknown' cite
> >> engine the way we do unknown layouts. Otherwise, if, say,
On Fri, Feb 16, 2018 at 03:27:30PM +, Kornel Benko wrote:
> > >> Is there a chance, to test the lyx2lyx output with LyX 2.2, 2.1 and
> > >> maybe
> > >> even 1.6?
> > >
> > > I don't think so. Remember, we only test with executables just created.
> >
> > This is a pity. We should, at t
On 02/14/2018 01:21 PM, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 14.02.2018, 12:50 -0500 schrieb Richard Heck:
>> I wonder if what we really need to do here is add the 'unknown' cite
>> engine the way we do unknown layouts. Otherwise, if, say, the font is
>> modified in Document>Settings, then
If you make any commits to the staging branches, please update the
status.23x file. Sorry to have forgotten to create it and to issue that
reminder earlier.
Richard
Am Freitag, 16. Februar 2018 09:32:39 CET schrieb Guenter Milde
:
> On 2018-02-15, Kornel Benko wrote:
> > Am Mittwoch, 14. Februar 2018 17:26:47 CET schrieb Guenter Milde
> >
> >> We found and fixed some problems with the new test.
> >> However, there are still problems that go undetected:
> >>
On 02/15/2018 03:48 PM, Pavel Sanda wrote:
> commit 25741ca5bd2ff4c7eb55de0fabfa41bbf476c77e
> Author: Pavel Sanda
> Date: Thu Feb 15 21:48:23 2018 +0100
>
> Oops, asInsetGrpahics is new to master.
It would be fine to copy that into 2.3.2-staging.
Richard
Le 16/02/2018 à 10:29, Sam Lewis a écrit :
Hi,
This is a persistent irregularity with beamer when using CambridgeUS theme that
I noticed since 2.2.x. Currently I'm using 2.3.0dev.
In a beamer frame, two boxes (minipages, drop shadow) are place in columns next
to each other. Everything works
Thanks for your swift reply Baris!
I'll do some further testing on my site. I'm using TexLive
Cheers!Sam
On Friday, 16 February 2018, 17:36, Baris Erkus
wrote:
#yiv7916278218 #yiv7916278218 -- _filtered #yiv7916278218
{font-family:Helvetica;panose-1:2 11 5 4 2 2 2 2 2 4;} _filtered #
On 2018-02-15, Kornel Benko wrote:
> Am Mittwoch, 14. Februar 2018 17:26:47 CET schrieb Guenter Milde
>> We found and fixed some problems with the new test.
>> However, there are still problems that go undetected:
>> * We currently do not test, whether a backported file can be opened by the
>>
Hi,
This is a persistent irregularity with beamer when using CambridgeUS theme that
I noticed since 2.2.x. Currently I'm using 2.3.0dev.
In a beamer frame, two boxes (minipages, drop shadow) are place in columns next
to each other. Everything works fine, except in the first frame one of the
bo
14 matches
Mail list logo
