On Friday, July 8, 2016 2:10:07 PM WEST Richard Heck wrote:
> Good, and thanks for fixing this.
>
> rh
Thank you. :-)
The change is in for 2.2.2 together with a change status and the bug close.
Regards,
--
José Abílio
On 07/08/2016 12:01 PM, José Abílio Matos wrote:
> On Thursday, July 7, 2016 4:05:15 PM WEST Richard Heck wrote:
>> Patch seems reasonable to me.
>>
>> Please commit to 2.2.x after 2.2.1 is released.
>>
>> Richard
> Thank you Richard. :-)
>
> Commited to master and I will do the same to 2.2.x after
On Thursday, July 7, 2016 4:05:15 PM WEST Richard Heck wrote:
> Patch seems reasonable to me.
>
> Please commit to 2.2.x after 2.2.1 is released.
>
> Richard
Thank you Richard. :-)
Commited to master and I will do the same to 2.2.x after 2.2.1 is out.
Regards,
--
José Abílio
Patch seems reasonable to me.
Please commit to 2.2.x after 2.2.1 is released.
Richard
On 07/07/2016 05:18 AM, José Abílio Matos wrote:
On Thursday, July 7, 2016 10:09:44 AM WEST Andrew Parsloe wrote:
Yes, changing > to -o results in an exported compressed file that 2.1.5
can read. Thanks fo
On Thursday, July 7, 2016 10:09:44 AM WEST Andrew Parsloe wrote:
>
> Yes, changing > to -o results in an exported compressed file that 2.1.5
> can read. Thanks for the help.
>
> Andrew
Thank you Andrew. I still blame windows for this but in any case to use the
option -o is the right thing to do
On 6/07/2016 9:14 p.m., José Abílio Matos wrote:
Could you try the following:
*) go to Tools->Preferences->File Handling->Converters
*) choose in the Converter Definition "LyX -> LyX 2.1.x"
*) change the converter from
"python -tt $$s/lyx2lyx/lyx2lyx -t 474 $$i > $$o"
to
"python -tt $$s
On Wednesday, July 6, 2016 10:31:45 AM WEST Andrew Parsloe wrote:
> LyX 2.1.5 has no trouble saving and reading its own compressed files.
That is good, I was being thoroughly in order to not to discart any
possibility.
> If I save a compressed file in 2.2.0, LyX 2.1.5 can read it. If I export
>
On 6/07/2016 2:16 a.m., José Abílio Matos wrote:
Could you, please, test the following (independent) tests:
1) take the compressed ".21.lyx" created with 2.2 use an
external program to decompress that file and see if lyx 2.1 opens that file?
2) use lyx 2.1 to create a compressed file, save i
On Tuesday, July 5, 2016 10:36:51 PM WEST Andrew Parsloe wrote:
> The problem is just with compressed files. Uncompressed they export
> fine, and can be read in 2.1.5. With the compressed file when I try to
> open it in 2.1.5 I get the message: ".21.lyx is not a
> readable LyX document." Perhaps
On 5/07/2016 8:40 p.m., José Abílio Matos wrote:
On Saturday, May 28, 2016 3:00:09 PM WEST Andrew Parsloe wrote:
I inadvertently tried exporting a compressed 2.2 file to 2.1.4. It was
not recognised by 2.1.4. When I try exporting an empty 2.2 compressed
file, it too isn't recognized by 2.1.4,
On Saturday, May 28, 2016 3:00:09 PM WEST Andrew Parsloe wrote:
> I inadvertently tried exporting a compressed 2.2 file to 2.1.4. It was
> not recognised by 2.1.4. When I try exporting an empty 2.2 compressed
> file, it too isn't recognized by 2.1.4, so clearly this is not an
> allowed mode of e
On Tue, Jul 05, 2016 at 10:12:52AM +1200, Andrew Parsloe wrote:
>
>
> On 4/07/2016 10:52 a.m., Scott Kostyshak wrote:
> > On Sat, May 28, 2016 at 03:00:09PM +1200, Andrew Parsloe wrote:
> > > I inadvertently tried exporting a compressed 2.2 file to 2.1.4. It was not
> > > recognised by 2.1.4. Whe
On 4/07/2016 10:52 a.m., Scott Kostyshak wrote:
On Sat, May 28, 2016 at 03:00:09PM +1200, Andrew Parsloe wrote:
I inadvertently tried exporting a compressed 2.2 file to 2.1.4. It was not
recognised by 2.1.4. When I try exporting an empty 2.2 compressed file, it
too isn't recognized by 2.1.4, s
On Sat, May 28, 2016 at 03:00:09PM +1200, Andrew Parsloe wrote:
> I inadvertently tried exporting a compressed 2.2 file to 2.1.4. It was not
> recognised by 2.1.4. When I try exporting an empty 2.2 compressed file, it
> too isn't recognized by 2.1.4, so clearly this is not an allowed mode of
> expo
14 matches
Mail list logo
