Re: Bleeding-edge LyX
Am 04.04.2016 um 12:24 schrieb Andrew Parsloe: On 4/04/2016 10:19 a.m., Andrew Parsloe wrote: On 4/04/2016 9:02 a.m., Scott Kostyshak wrote: On Mon, Apr 04, 2016 at 07:50:58AM +1200, Andrew Parsloe wrote: On 4/04/2016 5:38 a.m., Scott Kostyshak wrote: On Sun, Apr 03, 2016 at 10:14:18AM +1200, Andrew Parsloe wrote: On 3/04/2016 2:44 a.m., Peter Kümmel wrote: I've downloaded a more recent version, and the console window is absent, which is good. However, there is a problem with \lyxformat numbers. I see that a new document in bleeding-edge LyX is format 507. Documents in beta2 are 506 and are not converted. Looking at the messages pane (newfile1.lyx is a 506 document), Opening document D:\Documents\newfile1.lyx...Error: Document format failure C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx is not a readable LyX document. Are you able to open 2.1.x files? Scott I hadn't tried that, but I've just done so, and no, 2.1.x files result in the same error. (I've reverted to beta2 now.) I wonder if the problem is that your 2.2.0dev binary either cannot find lyx2lyx or is using a different lyx2lyx. Note that lyx and lyx2lyx are separate programs so the lyx program calls lyx2lyx (thus your PATH is important). Are you using this bleeding-edge LyX thing locally or did you install it? Scott Having unzipped the download, you are presented with two directories, one labelled bin and one Resources. As I understand it, you simply copy these on top of the installed LyX. It sounds somewhat hair-raising. My bumbling about (it took me a number of attempts to work out exactly what to do although the instructions seem clear enough in hindsight) may well have had side-effects, including corrupting PATH. At this point I'll simply wait for rc1. Andrew In fact I've had another go, and now the bleeding edge LyX can open documents from earlier versions of LyX. Help > About lists the date of the build as 3 April, QT Version 5.5.1. The citation dialogue which you were looking for a windows user's comments on (#10019, & which is why I undertook this exercise) looks good, as far as I can tell. The minimum height is a little less than in 2.1.4, the minimum width the same. It seems to stretch horizontally and vertically as I would expect. However, there are still problems with bleeding edge LyX and as you surmised, Scott, they do seem to centre around the path. The format of my custom modules is not updated to 60. I had to do that manually and the LyX icon in the task bar, when LyX is being used, is the windows default icon for a program. When I try to change the icon windows responds: Windows can't find the file %Program Files%\LyX 2.2\bin\lyx.exe. When I browse to C:\Program Files (x86)\LyX 2.2\bin\lyx.exe it tells me that "the file C:\Program Files (x86)\LyX 2.2\bin\lyx.exe" contains no icons. Whether this is the fault of b-e LyX or me, I don't know. The missing icon is a bug of b-e. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Bleeding-edge LyX
On 4/04/2016 10:19 a.m., Andrew Parsloe wrote: On 4/04/2016 9:02 a.m., Scott Kostyshak wrote: On Mon, Apr 04, 2016 at 07:50:58AM +1200, Andrew Parsloe wrote: On 4/04/2016 5:38 a.m., Scott Kostyshak wrote: On Sun, Apr 03, 2016 at 10:14:18AM +1200, Andrew Parsloe wrote: On 3/04/2016 2:44 a.m., Peter Kümmel wrote: I've downloaded a more recent version, and the console window is absent, which is good. However, there is a problem with \lyxformat numbers. I see that a new document in bleeding-edge LyX is format 507. Documents in beta2 are 506 and are not converted. Looking at the messages pane (newfile1.lyx is a 506 document), Opening document D:\Documents\newfile1.lyx...Error: Document format failure C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx is not a readable LyX document. Are you able to open 2.1.x files? Scott I hadn't tried that, but I've just done so, and no, 2.1.x files result in the same error. (I've reverted to beta2 now.) I wonder if the problem is that your 2.2.0dev binary either cannot find lyx2lyx or is using a different lyx2lyx. Note that lyx and lyx2lyx are separate programs so the lyx program calls lyx2lyx (thus your PATH is important). Are you using this bleeding-edge LyX thing locally or did you install it? Scott Having unzipped the download, you are presented with two directories, one labelled bin and one Resources. As I understand it, you simply copy these on top of the installed LyX. It sounds somewhat hair-raising. My bumbling about (it took me a number of attempts to work out exactly what to do although the instructions seem clear enough in hindsight) may well have had side-effects, including corrupting PATH. At this point I'll simply wait for rc1. Andrew In fact I've had another go, and now the bleeding edge LyX can open documents from earlier versions of LyX. Help > About lists the date of the build as 3 April, QT Version 5.5.1. The citation dialogue which you were looking for a windows user's comments on (#10019, & which is why I undertook this exercise) looks good, as far as I can tell. The minimum height is a little less than in 2.1.4, the minimum width the same. It seems to stretch horizontally and vertically as I would expect. However, there are still problems with bleeding edge LyX and as you surmised, Scott, they do seem to centre around the path. The format of my custom modules is not updated to 60. I had to do that manually and the LyX icon in the task bar, when LyX is being used, is the windows default icon for a program. When I try to change the icon windows responds: Windows can't find the file %Program Files%\LyX 2.2\bin\lyx.exe. When I browse to C:\Program Files (x86)\LyX 2.2\bin\lyx.exe it tells me that "the file C:\Program Files (x86)\LyX 2.2\bin\lyx.exe" contains no icons. Whether this is the fault of b-e LyX or me, I don't know. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Bleeding-edge LyX
On 4/04/2016 9:02 a.m., Scott Kostyshak wrote: On Mon, Apr 04, 2016 at 07:50:58AM +1200, Andrew Parsloe wrote: On 4/04/2016 5:38 a.m., Scott Kostyshak wrote: On Sun, Apr 03, 2016 at 10:14:18AM +1200, Andrew Parsloe wrote: On 3/04/2016 2:44 a.m., Peter Kümmel wrote: I've downloaded a more recent version, and the console window is absent, which is good. However, there is a problem with \lyxformat numbers. I see that a new document in bleeding-edge LyX is format 507. Documents in beta2 are 506 and are not converted. Looking at the messages pane (newfile1.lyx is a 506 document), Opening document D:\Documents\newfile1.lyx...Error: Document format failure C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx is not a readable LyX document. Are you able to open 2.1.x files? Scott I hadn't tried that, but I've just done so, and no, 2.1.x files result in the same error. (I've reverted to beta2 now.) I wonder if the problem is that your 2.2.0dev binary either cannot find lyx2lyx or is using a different lyx2lyx. Note that lyx and lyx2lyx are separate programs so the lyx program calls lyx2lyx (thus your PATH is important). Are you using this bleeding-edge LyX thing locally or did you install it? Scott Having unzipped the download, you are presented with two directories, one labelled bin and one Resources. As I understand it, you simply copy these on top of the installed LyX. It sounds somewhat hair-raising. My bumbling about (it took me a number of attempts to work out exactly what to do although the instructions seem clear enough in hindsight) may well have had side-effects, including corrupting PATH. At this point I'll simply wait for rc1. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Bleeding-edge LyX
On Mon, Apr 04, 2016 at 07:50:58AM +1200, Andrew Parsloe wrote: > On 4/04/2016 5:38 a.m., Scott Kostyshak wrote: > >On Sun, Apr 03, 2016 at 10:14:18AM +1200, Andrew Parsloe wrote: > >>On 3/04/2016 2:44 a.m., Peter Kümmel wrote: > >>I've downloaded a more recent version, and the console window is absent, > >>which is good. However, there is a problem with \lyxformat numbers. I see > >>that a new document in bleeding-edge LyX is format 507. Documents in beta2 > >>are 506 and are not converted. Looking at the messages pane (newfile1.lyx is > >>a 506 document), > >> > >>Opening document D:\Documents\newfile1.lyx...Error: Document format failure > >> > >> > >> > >>C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx > >>is not a readable LyX document. > >Are you able to open 2.1.x files? > > > >Scott > I hadn't tried that, but I've just done so, and no, 2.1.x files result in > the same error. (I've reverted to beta2 now.) I wonder if the problem is that your 2.2.0dev binary either cannot find lyx2lyx or is using a different lyx2lyx. Note that lyx and lyx2lyx are separate programs so the lyx program calls lyx2lyx (thus your PATH is important). Are you using this bleeding-edge LyX thing locally or did you install it? Scott signature.asc Description: PGP signature
Re: Bleeding-edge LyX
On 4/04/2016 5:38 a.m., Scott Kostyshak wrote: On Sun, Apr 03, 2016 at 10:14:18AM +1200, Andrew Parsloe wrote: On 3/04/2016 2:44 a.m., Peter Kümmel wrote: I've downloaded a more recent version, and the console window is absent, which is good. However, there is a problem with \lyxformat numbers. I see that a new document in bleeding-edge LyX is format 507. Documents in beta2 are 506 and are not converted. Looking at the messages pane (newfile1.lyx is a 506 document), Opening document D:\Documents\newfile1.lyx...Error: Document format failure C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx is not a readable LyX document. Are you able to open 2.1.x files? Scott I hadn't tried that, but I've just done so, and no, 2.1.x files result in the same error. (I've reverted to beta2 now.) Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Bleeding-edge LyX
On Sun, Apr 03, 2016 at 10:14:18AM +1200, Andrew Parsloe wrote: > On 3/04/2016 2:44 a.m., Peter Kümmel wrote: > I've downloaded a more recent version, and the console window is absent, > which is good. However, there is a problem with \lyxformat numbers. I see > that a new document in bleeding-edge LyX is format 507. Documents in beta2 > are 506 and are not converted. Looking at the messages pane (newfile1.lyx is > a 506 document), > > Opening document D:\Documents\newfile1.lyx...Error: Document format failure > > > > C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx > is not a readable LyX document. Are you able to open 2.1.x files? Scott signature.asc Description: PGP signature
Re: Bleeding-edge LyX
On 3/04/2016 2:44 a.m., Peter Kümmel wrote: Am 2. April 2016 11:26:06 MESZ, schrieb Andrew Parsloe <apars...@clear.net.nz>: Hullo Peter, I've tried twice now to get a working bleeding-edge LyX (on a windows 7 machine), since there have been occasions recently when it would have been helpful to have someone testing latest commits on a windows machine. Everything seems to function until I launch LyX. A console window opens, and then LyX is launched, but as you can see from the attachment, the console window displays three error messages, and remains open. Closing the console window closes LyX. With these errors present, I'm reluctant to do anything serious with the resulting LyX. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus Lyx gives a lot of warnings. I don't think these are critical. The console is enabled for bleeding edge build, maybe not a good idea. In a release the console is just disabled, so there is no differrence in the lyx functionality. I will disable the console for bleeding edge, too. Thanks for testing bleeding edge, I already was thinking about killing it. Peter I've downloaded a more recent version, and the console window is absent, which is good. However, there is a problem with \lyxformat numbers. I see that a new document in bleeding-edge LyX is format 507. Documents in beta2 are 506 and are not converted. Looking at the messages pane (newfile1.lyx is a 506 document), Opening document D:\Documents\newfile1.lyx...Error: Document format failure C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx is not a readable LyX document. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Bleeding-edge LyX
On Sat, Apr 02, 2016 at 10:42:55AM -0400, Richard Heck wrote: > They are probably in customized bind files, possibly in > user.bind. I'm not sure where these files are on Windows. I think Help > About will say. Scott signature.asc Description: PGP signature
Re: Bleeding-edge LyX
Am 2. April 2016 11:26:06 MESZ, schrieb Andrew Parsloe <apars...@clear.net.nz>: >Hullo Peter, >I've tried twice now to get a working bleeding-edge LyX (on a windows 7 > >machine), since there have been occasions recently when it would have >been helpful to have someone testing latest commits on a windows >machine. Everything seems to function until I launch LyX. A console >window opens, and then LyX is launched, but as you can see from the >attachment, the console window displays three error messages, and >remains open. Closing the console window closes LyX. With these errors >present, I'm reluctant to do anything serious with the resulting LyX. > >Andrew > > >--- >This email has been checked for viruses by Avast antivirus software. >https://www.avast.com/antivirus Lyx gives a lot of warnings. I don't think these are critical. The console is enabled for bleeding edge build, maybe not a good idea. In a release the console is just disabled, so there is no differrence in the lyx functionality. I will disable the console for bleeding edge, too. Thanks for testing bleeding edge, I already was thinking about killing it. Peter
Re: Bleeding-edge LyX
On 04/02/2016 05:26 AM, Andrew Parsloe wrote: > Hullo Peter, > I've tried twice now to get a working bleeding-edge LyX (on a windows > 7 machine), since there have been occasions recently when it would > have been helpful to have someone testing latest commits on a windows > machine. Everything seems to function until I launch LyX. A console > window opens, and then LyX is launched, but as you can see from the > attachment, the console window displays three error messages, and > remains open. Closing the console window closes LyX. With these errors > present, I'm reluctant to do anything serious with the resulting LyX. You probably have been getting these same errors for a very long time, but you just never saw them. The LyX functions mentioned were removed in LyX 2.0! They are probably in customized bind files, possibly in user.bind. I'm not sure where these files are on Windows. It should be safe to proceed. Richard
Bleeding-edge LyX
Hullo Peter, I've tried twice now to get a working bleeding-edge LyX (on a windows 7 machine), since there have been occasions recently when it would have been helpful to have someone testing latest commits on a windows machine. Everything seems to function until I launch LyX. A console window opens, and then LyX is launched, but as you can see from the attachment, the console window displays three error messages, and remains open. Closing the console window closes LyX. With these errors present, I'm reluctant to do anything serious with the resulting LyX. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
