Re: LyX 2.2.1 Tarballs
On 07/22/2016 11:28 PM, Scott Kostyshak wrote: > On Fri, Jul 22, 2016 at 11:17:09PM -0400, Richard Heck wrote: >> On 07/22/2016 02:02 PM, Pavel Sanda wrote: >>> Richard Heck wrote: Source tarballs for LyX 2.2.1 have been uploaded to ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/. Please prepare binaries. >>> works here. it would ease my packaging life >>> if we could stick to single naming conventions, >>> ie. having >>> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.1/ >>> and not >>> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/ >> Did Scott use lyx-2.2.0? I believe I had just 2.1.4 and 2.1.5. > I tried to copy what was done for 2.1.0 for this type of thing, but if > the 2.1.0 folder name was just "2.1.0" and for 2.2.0 I put "lyx-2.2.0" > then I made a mistake. I deleted all the old stuff, so who knows. rh
Re: LyX 2.2.1 Tarballs
On Fri, Jul 22, 2016 at 11:17:09PM -0400, Richard Heck wrote: > On 07/22/2016 02:02 PM, Pavel Sanda wrote: > > Richard Heck wrote: > >> Source tarballs for LyX 2.2.1 have been uploaded to > >> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/. Please prepare binaries. > > works here. it would ease my packaging life > > if we could stick to single naming conventions, > > ie. having > > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.1/ > > and not > > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/ > > Did Scott use lyx-2.2.0? I believe I had just 2.1.4 and 2.1.5. I tried to copy what was done for 2.1.0 for this type of thing, but if the 2.1.0 folder name was just "2.1.0" and for 2.2.0 I put "lyx-2.2.0" then I made a mistake. Scott signature.asc Description: PGP signature
LabelFont in arguments of insets
I downloaded and installed Uwe's windows 2.2.1 installer (which, I gather, may not be exactly the official 2.2.1). I can confirm that the assertion is no longer there that arose when using color in the LabelFont specification for an argument in a flex inset, which is good, but (at least with this version of LyX on windows 7) the color specification has no effect. Richard noticed that Series bold in the spec. also triggered an assertion. That no longer does so, and the bold *is* displayed, so it is only color for which there seems to be a problem. I've attached the same MWE as last time (with Series bold added to the LabelFont spec.). Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus MWE.lyx Description: application/lyx
Re: \Omega is not displayed correctly
On 07/22/2016 01:07 PM, Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: >> Le 22/07/2016 ? 00:10, Richard Heck a écrit : >>> On 07/21/2016 06:05 PM, Scott Kostyshak wrote: On Thu, Jul 21, 2016 at 04:29:32PM -0400, Richard Heck wrote: > But I can't access trac right now Same here. >>> I'm not sure what the problem is. CPU load is low. Bandwidth, possibly. >>> I think we are on a shared server, too, so who knows what others' loads >>> are like. >> Here is what top says. Doesn't it mean that we swap a lot? Where can I see >> the requests at a given point? > iotop if installed could give a hint. Seems better now, so a mystery. rh
Re: LyX 2.2.1 Tarballs
On 07/22/2016 02:02 PM, Pavel Sanda wrote: > Richard Heck wrote: >> Source tarballs for LyX 2.2.1 have been uploaded to >> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/. Please prepare binaries. > works here. it would ease my packaging life > if we could stick to single naming conventions, > ie. having > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.1/ > and not > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/ Did Scott use lyx-2.2.0? I believe I had just 2.1.4 and 2.1.5. Richard
Re: LyX 2.2.1 Tarballs
On 07/22/2016 08:57 PM, Uwe Stöhr wrote: > Am 21.07.2016 um 20:51 schrieb Richard Heck: > >> Source tarballs for LyX 2.2.1 have been uploaded to >> ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/. Please prepare binaries. > > The tarball is not compilable for me because of a CMake issue: > > [snip] I do not know anything about CMake. Hopefully, someone else can help with this. > Since I can compile the current 2.2.x branch without problems, I > included the lyx.exe to the installer that I compiled of current 2.2.x > branch (as I see the code is identic to the one when you prepared the > binary). > Here is the installer: > http://ftp.lyx.de/LyX%202.2.1/ > > Since I released installers with lyx.exe compiled from tagged branches > for years, I don't see why this should harm here. This is not ideal, but we shall proceed this way for the moment. Hopefully, we can get the CMake issue fixed and produce a new build. > (Btw., the tarball does not include the build5-2015.bat file because > this is missing in the makefile. Seems that I forgot to add it there.) We can add it to 2.2.x once that is open again. rh
Re: LyX 2.2.1 Tarballs
Am 21.07.2016 um 20:51 schrieb Richard Heck: Source tarballs for LyX 2.2.1 have been uploaded to ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/. Please prepare binaries. The tarball is not compilable for me because of a CMake issue: "D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj" (Standardziel) (1) -> (PostBuildEvent Ziel) -> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: The command "setlocal\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: "C:\Program Files\CMake\bin\cmake.exe" -DBUILD_TYPE=Release -P cmake_install.cmake\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmEnd\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmErrorLevel\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: exit /b %1\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmDone\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd\r [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :VCEnd" was terminated with code 1. [D:\LyXGit\LyX22\compile-2015\INSTALL.vcxproj] After 3 hours of fiddling around with this I gave up. It is a CMake issue that I don't understand. (I have admin privileges.) I can compile any other LyX branch I like using CMake 3.6.1 without any problems, I can also compile the tarball of 2.1.5 and 2.2.0 so there must be a bug in the 2.2.1 tarball. Since I can compile the current 2.2.x branch without problems, I included the lyx.exe to the installer that I compiled of current 2.2.x branch (as I see the code is identic to the one when you prepared the binary). Here is the installer: http://ftp.lyx.de/LyX%202.2.1/ Since I released installers with lyx.exe compiled from tagged branches for years, I don't see why this should harm here. I have now other things to do and cannot work on LyX. Sorry. I can give it another try on Sunday. (Btw., the tarball does not include the build5-2015.bat file because this is missing in the makefile. Seems that I forgot to add it there.) regards Uwe
Re: Instant previews only repainted if window active or mouse over
On Fri, Jul 22, 2016 at 10:10:02AM -0700, Pavel Sanda wrote: > Scott Kostyshak wrote: > > My guess is that it has been like this forever > > Correct, it also true for graphic insets, but as said very minor thing. Good to know. OK I will let it go. Scott signature.asc Description: PGP signature
Re: LyX 2.2.1 Tarballs
Richard Heck wrote: > Source tarballs for LyX 2.2.1 have been uploaded to > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/. Please prepare binaries. works here. it would ease my packaging life if we could stick to single naming conventions, ie. having ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.1/ and not ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/2.2.1/ Pavel
Re: Instant previews only repainted if window active or mouse over
Scott Kostyshak wrote: > My guess is that it has been like this forever Correct, it also true for graphic insets, but as said very minor thing. P
Re: \Omega is not displayed correctly
Jean-Marc Lasgouttes wrote: > Le 22/07/2016 ? 00:10, Richard Heck a écrit : >> On 07/21/2016 06:05 PM, Scott Kostyshak wrote: >>> On Thu, Jul 21, 2016 at 04:29:32PM -0400, Richard Heck wrote: But I can't access trac right now >>> Same here. >> >> I'm not sure what the problem is. CPU load is low. Bandwidth, possibly. >> I think we are on a shared server, too, so who knows what others' loads >> are like. > > Here is what top says. Doesn't it mean that we swap a lot? Where can I see > the requests at a given point? iotop if installed could give a hint. P
Re: Ticket #10304 : Instant Preview: Too much horizontal space
Jean-Marc Lasgouttes wrote: > I'd be interested to have input at this point. I think it's a good idea, it has been said more times that it's easy to overlook a missing whitespace around (preview) math insets, this should help. Pavel
Re: \Omega is not displayed correctly
Le 21/07/2016 à 21:00, L. Han a écrit : After update to 2.2.0, \Omega is not displayed correctly in Lyx. It looks like a bold \neg now. Hope it will be fixed soon. Thanks! It could be that the latest version of the fonts supplied with lyx are not properly installed. See http://www.lyx.org/trac/ticket/10161 esp. comment:7.
Re: Ticket #6570
On 22.07.2016 16:48, Jean-Marc Lasgouttes wrote:
Le 22/07/2016 à 15:13, racoon a écrit :
The next problem is of course that the pasting from the clipboard
on line 314:
{{{
pasteFromStack(cur, cur.buffer()->errorList("Paste"), 0);
}}}
Is there some stack on which one can put the selection and pasting it
later without using the clipboard?
This is the whole reason why this bug has not been fixed yet. We've bee
lazy to do this not-so-difficult temporary cut-stack.
Thanks! At least I got the problem then.
Daniel
Re: [LyX/2.2.x] Start preparations for 2.2.1.
Le 22/07/2016 à 14:31, Jean-Pierre Chrétien a écrit : Le 21/07/2016 19:30, Richard Heck a écrit : commit ad72f2b5544bbe42c575a3028f629c810fc0a409 Author: Richard Heck Date: Thu Jul 21 14:25:32 2016 -0400 Start preparations for 2.2.1. + +- New document parameter "Save transient properties" under Document Properties > + Format. (Output has been renamed into Format.) Disabling this option is made + to play nicer in collaborative settings. (bug 9841) Rather Document->Settings->Format, and "Output" has not been yet renamed to "Format". I guess we will have to live with this omission of mine :) Sorry. BTW, as a translator in French, I find the change from "Output" to "Format" (which was discussed in a previous thread) a bit awkward as I already translate "Layout" as "Format". Then one could translate Format into something else, though I have to admit that nothing else comes to mind. What about "Export" rather than "Format"? This covers all three items in the subwindow. It has the same issue as Output: "save transient properties" controls the source file, rather than an output file. (I have a similar issue with the "source panel": it should really be called "output panel". Calling it "source" is entirely inappropriate and propagates the false impression that LyX intends to be a LaTeX editor.) And for transient properties, "LyX save options" seems better to me that "LyX format". Makes sense. Speaking of save options, was there not a discussion about "save compressed" missing in the dialog? Thanks for the feedback. If nobody has a better idea for the name, then we can revert to Output. I'll be waiting for opinions. Guillaume
Re: Ticket #6570
Le 22/07/2016 à 15:13, racoon a écrit :
The next problem is of course that the pasting from the clipboard
on line 314:
{{{
pasteFromStack(cur, cur.buffer()->errorList("Paste"), 0);
}}}
Is there some stack on which one can put the selection and pasting it
later without using the clipboard?
This is the whole reason why this bug has not been fixed yet. We've bee
lazy to do this not-so-difficult temporary cut-stack.
JMarc
Re: Ticket #6570
On 22.07.2016 12:42, racoon wrote:
On Ticket #6570, http://www.lyx.org/trac/ticket/6570.
The culprit here seems to be in
`Text3.cpp`:
{{{
static bool doInsertInset(Cursor & cur, Text * text,
FuncRequest const & cmd, bool edit, bool pastesel)
{
...
bool gotsel = false;
if (cur.selection()) {
cutSelection(cur, false, pastesel);
cur.clearSelection();
gotsel = true;
}
text->insertInset(cur, inset);
...
}
}}}
Maybe there are similar passages elsewhere that need to be fixed.
Removing `cutSelection(cur, false, pastesel);` seems to solve the
problem about overwritten clipboards. But then the current clipboard is
inserted into the inset and the current selection is not removed.
(I started with adding `eraseSelection(cur);` instead but it's
undefined. How does one add the definition from `CutAndPaste.cpp`?)
Okay, found out about the definition but it did nit help since
`eraseSelection` seems not to work in this context. ("Can't erase...")
Instead `cutSelection(cur, false, false);` seems to erase the text
without pushing it to the clipboard.
The next problem is of course that the pasting from the clipboard
on line 314:
{{{
pasteFromStack(cur, cur.buffer()->errorList("Paste"), 0);
}}}
Is there some stack on which one can put the selection and pasting it
later without using the clipboard?
Daniel
Re: [LyX/2.2.x] Start preparations for 2.2.1.
Le 21/07/2016 19:30, Richard Heck a écrit : commit ad72f2b5544bbe42c575a3028f629c810fc0a409 Author: Richard Heck Date: Thu Jul 21 14:25:32 2016 -0400 Start preparations for 2.2.1. + +- New document parameter "Save transient properties" under Document Properties > + Format. (Output has been renamed into Format.) Disabling this option is made + to play nicer in collaborative settings. (bug 9841) Rather Document->Settings->Format, and "Output" has not been yet renamed to "Format". BTW, as a translator in French, I find the change from "Output" to "Format" (which was discussed in a previous thread) a bit awkward as I already translate "Layout" as "Format". What about "Export" rather than "Format"? This covers all three items in the subwindow. And for transient properties, "LyX save options" seems better to me that "LyX format". -- Jean-Pierre
Re: Compiling with Microsoft Visual C++
On 22.07.2016 11:53, racoon wrote: On 22.07.2016 11:03, racoon wrote: On 21.07.2016 16:40, Kornel Benko wrote: Am Donnerstag, 21. Juli 2016 um 16:32:14, schrieb racoon Okay, so what happens if I disable "LYX_INSTALL" then? Why don't you try? Because there may be people who tried and can share their experience and my computer is slow and it takes quite some time. Okay, disabling "LYX_INSTALL" and "LYX_NLS" seems to get rid of those compilations of .po and .gmo files which speeds up compilation (on my slow machine a lot). Maybe that should be mentioned somewhere? Okay, I was told now that compiling LYX instead of LYX_INSTALL should have the same effect. Haven't tried. But maybe mention that instead? Daniel
Ticket #6570
On Ticket #6570, http://www.lyx.org/trac/ticket/6570.
The culprit here seems to be in
`Text3.cpp`:
{{{
static bool doInsertInset(Cursor & cur, Text * text,
FuncRequest const & cmd, bool edit, bool pastesel)
{
...
bool gotsel = false;
if (cur.selection()) {
cutSelection(cur, false, pastesel);
cur.clearSelection();
gotsel = true;
}
text->insertInset(cur, inset);
...
}
}}}
Maybe there are similar passages elsewhere that need to be fixed.
Removing `cutSelection(cur, false, pastesel);` seems to solve the
problem about overwritten clipboards. But then the current clipboard is
inserted into the inset and the current selection is not removed.
(I started with adding `eraseSelection(cur);` instead but it's
undefined. How does one add the definition from `CutAndPaste.cpp`?)
But since this ticket is so old maybe it is very tricky to solve it? In
any case feel free to take over. My knowledge is probably too limited. :)
Daniel
Re: Compiling with Microsoft Visual C++
On 22.07.2016 11:03, racoon wrote: On 21.07.2016 16:40, Kornel Benko wrote: Am Donnerstag, 21. Juli 2016 um 16:32:14, schrieb racoon Okay, so what happens if I disable "LYX_INSTALL" then? Why don't you try? Because there may be people who tried and can share their experience and my computer is slow and it takes quite some time. Okay, disabling "LYX_INSTALL" and "LYX_NLS" seems to get rid of those compilations of .po and .gmo files which speeds up compilation (on my slow machine a lot). Maybe that should be mentioned somewhere? The only other effect I recognized was that a terminal runs in the background. No big deal I guess. Daniel
Re: Compiling with Microsoft Visual C++
On 21.07.2016 16:40, Kornel Benko wrote: Am Donnerstag, 21. Juli 2016 um 16:32:14, schrieb racoon Okay, so what happens if I disable "LYX_INSTALL" then? Why don't you try? Because there may be people who tried and can share their experience and my computer is slow and it takes quite some time. Daniel
Re: Ticket #10304 : Instant Preview: Too much horizontal space
Le 22/07/2016 à 05:48, Andrew Parsloe a écrit : This code was present at the introduction of the preview inset. I was thinking of http://www.lyx.org/trac/ticket/7522 (e.g. comment 11). My memory is that the spacing increased after that ticket. Yes. I do not plan to touch this code. JMarc
