Re: Seminar example document not expected to work with updated TeX Live
On Thu, Oct 29, 2020 at 06:07:28PM +, José Abílio Matos wrote:
> On Thursday, October 29, 2020 2:54:39 PM WET Scott Kostyshak wrote:
> > Should we just write a LyX note inside the .lyx file that if they get an
> > error they should export to .tex and put
> > \RequirePackage[2020-02-02]{latexrelease} as the first line?
> >
> > Scott
>
> That seems a sensible thing to do IMHO.
Thanks, José. I did that at 1aa4987b.
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: he/Tutorial LuaTeX: strange error in terminal
On Sat, Oct 24, 2020 at 12:54:56PM -0400, Scott Kostyshak wrote: > On Sat, Oct 24, 2020 at 01:03:58PM +0200, Kornel Benko wrote: > > Am Sat, 24 Oct 2020 01:16:54 -0400 > > schrieb Scott Kostyshak : > > > > > This document compiles for me on an older system (with TL19) but on a > > > new installation and updated TL20, I now get an error and in the > > > terminal I see the following: > > > > > > lualatex: ../../../texk/web2c/luatexdir/lang/texlang.c:986: > > > hnj_hyphenation: Assertion > > > `(((varmem[(wordstart)].hh.u.B1) & (1 << 0)) && > > > !((varmem[(wordstart)].hh.u.B1) & (1 << > > > 1) ) && !((varmem[(wordstart)].hh.u.B1) & (1 << 2) ))' failed. > > > support/Systemcall.cpp > > > (291): Systemcall: 'lualatex "Tutorial.tex"' finished with exit code -1 > > > Error: LaTeX > > > failed > > > > > > Can anyone reproduce the above on an updated TL20 system? > > > > > > Scott > > > > Same here. > > Thanks. Does anyone know where is the correct place to report this? I > would guess on the LuaTeX mailing list? I sent an email to the LuaTeX list. I'll report the result back here. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX 2.3.6
On Thu, Oct 29, 2020 at 09:09:24PM -0400, Richard Kimberly Heck wrote: > On 10/29/20 8:39 PM, Scott Kostyshak wrote: > > On Thu, Oct 29, 2020 at 06:03:58PM -0400, Richard Kimberly Heck wrote: > > > >> So: Anything anyone wants to get into > >> 2.3.6 before we freeze strings? > > Can I backport fe1cbc06 and 334552ad to 2.3.x? I think that Kornel and I > > are the only ones who use the cpack deb feature. > > Go ahead. Done at 012bca0b and 3611c09f. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX 2.3.6
On 10/29/20 8:39 PM, Scott Kostyshak wrote: > On Thu, Oct 29, 2020 at 06:03:58PM -0400, Richard Kimberly Heck wrote: > >> So: Anything anyone wants to get into >> 2.3.6 before we freeze strings? > Can I backport fe1cbc06 and 334552ad to 2.3.x? I think that Kornel and I > are the only ones who use the cpack deb feature. Go ahead. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX 2.3.6
On Thu, Oct 29, 2020 at 06:03:58PM -0400, Richard Kimberly Heck wrote: > So: Anything anyone wants to get into > 2.3.6 before we freeze strings? Can I backport fe1cbc06 and 334552ad to 2.3.x? I think that Kornel and I are the only ones who use the cpack deb feature. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Testing Release of 2.4.0 Development Branch
Hi, everyone, We are beginning the process of moving towards the next major release of LyX, which will be 2.4.0. Toward that end, we have prepared a 'testing' release. Please note that this is very much for testing. We do not necessarily recommend that anyone use it for daily work, although some of us do. (Be aware that you may have to deal with some bugs and that files edited with 2.4.x cannot be opened in 2.3.x without being exported to that format.) Both source code and binaries for Windows and OSX can be found here: http://ftp.lyx.org/ftp/pub/lyx/devel/lyx-2.4/ Binaries for various Linux distros may or may not be available from their associated repositories. (But, if you are on Linux, you should not have too much trouble compiling the source. If you need help, just ask.) We will greatly appreciate any reports on how well these packages work! You can post comments either to lyx-users or to lyx-devel. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
LyX 2.3.6
Hi, all, Now that the development testing release is all but out, it is probably also time to do another 2.3.x release. We have a few crash fixes, and the last release was in June. So: Anything anyone wants to get into 2.3.6 before we freeze strings? A couple bugs that have only been fixed in master are listed on the bug tracker. JMarc and Enrico, these are yours. Go ahead and commit if you think it is safe. Of course, the officially open 2.3.6 bugs can also be found there. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX Development Release Tarballs, Round 3
On Thursday, October 29, 2020 12:26:14 AM WET Richard Kimberly Heck wrote: > I wasn't officially releasing it as an alpha and won't announce it that > way. We had not, so far as I am aware, made any official determination > about that (although Pavel suggested it). So, for now, it'll be > announced as a 'testing release'. If all goes well with it, maybe we can > do a real alpha in November. > > Riki This is mostly a question of expectations but for me this is what an alpha release is. :-) I have resumed the builds for lyx-devel copr's: https://copr.fedorainfracloud.org/coprs/jamatos/lyx-devel/ There are builds for x86_64 and aarch64 (arm). The build are done for Red Hat Enterprise Linux, 7 and 8, and for Fedora 31-34 (34 == rawhide). The package is called lyx-devel because it uses the -devel suffix so there is no clash with the stable version. After this initial step, to adapt the spec file for the changed package name, all the other releases will be very easy because the changes are very localized. Best regards, -- José Abílio-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Seminar example document not expected to work with updated TeX Live
On Thursday, October 29, 2020 2:54:39 PM WET Scott Kostyshak wrote:
> Should we just write a LyX note inside the .lyx file that if they get an
> error they should export to .tex and put
> \RequirePackage[2020-02-02]{latexrelease} as the first line?
>
> Scott
That seems a sensible thing to do IMHO.
--
José Abílio--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: git pull hangs
I have killed all those stale connections. Hopefully that will help. (I will guess that the working IP for some reason had an open connection.) First and foremost: this solved it, and now it works. Thank you again! Now, the embarrassing part: from your logs we found out that the unique working ip was exiting from a different nat address 131.175.154.246 instead of 131.175.154.248) who didn't reach the maximum number of open sockets. Our fault for not spotting this from our side. The others (131.175.147.207 and 131.175.147.134) were likely due to me trying to connect from different classrooms in the campus. We have no idea about why you ended up with those stale connections. The only clue I have found is https://stackoverflow.com/questions/6400151/git-daemon-unable-to-allocate-any-listen-sockets-on-host-null-port-9418 : it seems to suggest using --init-timeout=x and --timeout=x with x reasonably small (say 10) launching the git daemon (don't know if you already have these options in place). At any rate: thank you again for dealing with this. Marco -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: git pull hangs
On 10/29/20 9:27 AM, Marco Morandini wrote: I have killed all those stale connections. Hopefully that will help. (I will guess that the working IP for some reason had an open connection.) First and foremost: this solved it, and now it works. Thank you again! Now, the embarrassing part: from your logs we found out that the unique working ip was exiting from a different nat address 131.175.154.246 instead of 131.175.154.248) who didn't reach the maximum number of open sockets. Our fault for not spotting this from our side. The others (131.175.147.207 and 131.175.147.134) were likely due to me trying to connect from different classrooms in the campus. Mystery solved! We have no idea about why you ended up with those stale connections. The only clue I have found is https://stackoverflow.com/questions/6400151/git-daemon-unable-to-allocate-any-listen-sockets-on-host-null-port-9418 : it seems to suggest using --init-timeout=x and --timeout=x with x reasonably small (say 10) launching the git daemon (don't know if you already have these options in place). I've added those, thanks for the pointer! I'll try to check now and again for stale connections and see if that helps. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Seminar example document not expected to work with updated TeX Live
Our seminar example fails with an updated TeX Live 2020 system. The
maintainer states the following:
it is a problem with the new hook management of the current latex.ltx
seminar is a quite old package and there is no reason to use it with a
new LaTeX format. It won't be fixed, so the usual way is to use the
package latexrealease to get the old hook management.
The workaround is to add \RequirePackage[2020-02-02]{latexrelease} as
the first line of the .tex file.
What should we do regarding the example file for LyX? My opinion is that
we should still ship it since there are many TeX systems that are not
updated and even for updated systems the workaround is easy.
Should we just write a LyX note inside the .lyx file that if they get an
error they should export to .tex and put
\RequirePackage[2020-02-02]{latexrelease} as the first line?
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Seminar example fails on updated TL20
On Wed, Oct 28, 2020 at 05:16:06PM -0400, Scott Kostyshak wrote:
> On Sat, Oct 24, 2020 at 05:17:29PM -0400, Scott Kostyshak wrote:
> > On Sat, Oct 24, 2020 at 09:05:36PM +0100, José Abílio Matos wrote:
> > > On Saturday, October 24, 2020 5:57:50 PM WEST Scott Kostyshak wrote:
> > > > Thanks. Not sure where to report it since it looks like the 'seminar'
> > > > package hasn't been updated for a while so it's likely from an update to
> > > > a different package. I'll try to make an MWE and figure out which
> > > > package change caused the failure.
> > > >
> > > > Scott
> > >
> > > It works for me on Fedora 33, the first lines of the latex log says:
> > >
> > > This is pdfTeX, Version 3.14159265-2.6-1.40.21 (TeX Live 2020) (preloaded
> > > format=pdflatex 2020.10.14) 24 OCT 2020 21:01
> > >
> > >
> > > I am not sure if all the packages are updated in Fedora so it could be
> > > one of
> > > them...
> >
> > Thanks for checking José. After I make a minimal example (not sure when
> > I will get to this), I might see if you can post your LaTeX log for the
> > minimal example so we can look at package version differences.
>
> To reproduce the error I only need to use the seminar class. I sent an
> email to the maintainer. I'll report back when I hear from him. Note
> that a temporary workaround is to add the following to the .tex file as
> the first line:
>
> \RequirePackage[2020-02-02]{latexrelease}
>
> Perhaps it's a similar issue as reported here:
>
> https://github.com/tweh/menukeys/issues/59
The package maintainer says the issue will not be fixed. I'll start a new
thread with what we should do in LyX.
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Seminar example fails on updated TL20
On Thu, Oct 29, 2020 at 01:29:11PM +0200, Dr Eberhard Lisse wrote:
> Scott,
>
> please let me have a MWE, as I reported the menukeys issue (under the
> subject line "Changes to LaTeX" here.
I believe it suffices to just load the menukeys package. In case that
doesn't do it, here is a somewhat larger MWE that I am sure reproduced
the error for me:
\documentclass[english]{article}
\usepackage{lmodern}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{babel}
\usepackage{menukeys}
\begin{document}
\capslockmac{}
\end{document}
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Update Additional.lyx
On Thu, Oct 29, 2020 at 07:44:59AM +0200, Yuriy Skalko wrote: > Hello, > > After reviewing recent Russian translation of Additional.lyx manual, I've > done some updates to English version. Please go on. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Patches
On Thu, Oct 29, 2020 at 08:47:23AM +0200, Yuriy Skalko wrote: > Next 3 patches. Looks good. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Seminar example fails on updated TL20
Scott,
please let me have a MWE, as I reported the menukeys issue (under the
subject line "Changes to LaTeX" here.
el
On 28/10/2020 23:16, Scott Kostyshak wrote:
[...]
> To reproduce the error I only need to use the seminar class. I sent an
> email to the maintainer. I'll report back when I hear from him. Note
> that a temporary workaround is to add the following to the .tex file as
> the first line:
>
> \RequirePackage[2020-02-02]{latexrelease}
>
> Perhaps it's a similar issue as reported here:
>
> https://github.com/tweh/menukeys/issues/59
>
> Scott
>
>
--
If you want to email me, replace nospam with el
signature.asc
Description: OpenPGP digital signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX Development Release Tarballs, Round 3
Le 29/10/2020 à 01:26, Richard Kimberly Heck a écrit : On 10/28/20 8:15 PM, Jean-Pierre wrote: Le 26 octobre 2020 21:57:09 Richard Kimberly Heck a écrit : OK, so, another set of tarballs is at http://ftp.lyx.org/ftp/pub/lyx/devel/lyx-2.4/. Please let me know if that these are good to go (hopefully). Hello Riki Signature OK this time. Up to now, I just ran configure, and I see that the version name is lyx-2.4.0dev, that is the same as the one I retrieve with git to check master. Would not it read lyx-2.4.0alpha ? I wasn't officially releasing it as an alpha and won't announce it that way. We had not, so far as I am aware, made any official determination about that (although Pavel suggested it). So, for now, it'll be announced as a 'testing release'. If all goes well with it, maybe we can do a real alpha in November. OK. BTW, compilation worked all right with this conf : Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=development std-regex warnings assertions stdlib-debug callback-printing use-hunspell Bundled libraries:boost hunspell mythes C++ Compiler:g++ (8.3.0) C++ Compiler flags: -Wall -Wextra -fPIC -g -O -std=c++14 -Wno-deprecated-copy C++ Compiler user flags: Linker flags: -rdynamic Linker user flags: Qt Frontend: Qt version: 5.11.3 Packaging: posix LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx-2.4.0dev on Debian buster. UserGuide compiles fine. -- Jean-Pierre -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Patches
Next 3 patches.
Yuriy
From 37944992bf356680f8910d384df37ac3fb998339 Mon Sep 17 00:00:00 2001
From: Yuriy Skalko
Date: Mon, 26 Oct 2020 20:16:28 +0200
Subject: [PATCH 1/5] Move HullType functions declared in InsetMath.h into
InsetMath.cpp
---
src/mathed/InsetMath.cpp | 42
src/mathed/InsetMathHull.cpp | 42
2 files changed, 42 insertions(+), 42 deletions(-)
diff --git a/src/mathed/InsetMath.cpp b/src/mathed/InsetMath.cpp
index 1adeec10a8..33a9a4e6b4 100644
--- a/src/mathed/InsetMath.cpp
+++ b/src/mathed/InsetMath.cpp
@@ -30,6 +30,48 @@ using namespace std;
namespace lyx {
+HullType hullType(docstring const & s)
+{
+ if (s == "none") return hullNone;
+ if (s == "simple")return hullSimple;
+ if (s == "equation") return hullEquation;
+ if (s == "eqnarray") return hullEqnArray;
+ if (s == "align") return hullAlign;
+ if (s == "alignat") return hullAlignAt;
+ if (s == "xalignat") return hullXAlignAt;
+ if (s == "xxalignat") return hullXXAlignAt;
+ if (s == "multline") return hullMultline;
+ if (s == "gather")return hullGather;
+ if (s == "flalign") return hullFlAlign;
+ if (s == "regexp")return hullRegexp;
+ lyxerr << "unknown hull type '" << to_utf8(s) << "'" << endl;
+ return hullUnknown;
+}
+
+
+docstring hullName(HullType type)
+{
+ switch (type) {
+ case hullNone: return from_ascii("none");
+ case hullSimple: return from_ascii("simple");
+ case hullEquation: return from_ascii("equation");
+ case hullEqnArray: return from_ascii("eqnarray");
+ case hullAlign: return from_ascii("align");
+ case hullAlignAt:return from_ascii("alignat");
+ case hullXAlignAt: return from_ascii("xalignat");
+ case hullXXAlignAt: return from_ascii("xxalignat");
+ case hullMultline: return from_ascii("multline");
+ case hullGather: return from_ascii("gather");
+ case hullFlAlign:return from_ascii("flalign");
+ case hullRegexp: return from_ascii("regexp");
+ case hullUnknown:
+ lyxerr << "unknown hull type" << endl;
+ break;
+ }
+ return from_ascii("none");
+}
+
+
docstring InsetMath::name() const
{
return from_utf8("Unknown");
diff --git a/src/mathed/InsetMathHull.cpp b/src/mathed/InsetMathHull.cpp
index 4125bf6ee5..43f49584af 100644
--- a/src/mathed/InsetMathHull.cpp
+++ b/src/mathed/InsetMathHull.cpp
@@ -147,51 +147,9 @@ namespace {
os << "}\n";
}
-
} // namespace
-HullType hullType(docstring const & s)
-{
- if (s == "none") return hullNone;
- if (s == "simple")return hullSimple;
- if (s == "equation") return hullEquation;
- if (s == "eqnarray") return hullEqnArray;
- if (s == "align") return hullAlign;
- if (s == "alignat") return hullAlignAt;
- if (s == "xalignat") return hullXAlignAt;
- if (s == "xxalignat") return hullXXAlignAt;
- if (s == "multline") return hullMultline;
- if (s == "gather")return hullGather;
- if (s == "flalign") return hullFlAlign;
- if (s == "regexp")return hullRegexp;
- lyxerr << "unknown hull type '" << to_utf8(s) << "'" << endl;
- return hullUnknown;
-}
-
-
-docstring hullName(HullType type)
-{
- switch (type) {
- case hullNone: return from_ascii("none");
- case hullSimple: return from_ascii("simple");
- case hullEquation: return from_ascii("equation");
- case hullEqnArray: return from_ascii("eqnarray");
- case hullAlign: return from_ascii("align");
- case hullAlignAt:return from_ascii("alignat");
- case hullXAlignAt: return from_ascii("xalignat");
- case hullXXAlignAt: return from_ascii("xxalignat");
- case hullMultline: return from_ascii("multline");
- case hullGather: return from_ascii("gather");
- case hullFlAlign:return from_ascii("flalign");
- case hullRegexp: return from_ascii("regexp");
- case hullUnknown:
- lyxerr << "unknown hull type" << endl;
- break;
- }
- return from_ascii("none");
-}
-
static InsetLabel * dummy_pointer = 0;
InsetMathHull::InsetMathHull(Buffer * buf)
--
2.28.0.windows.1
From a1521094703b8c88ba383a79bdb86df863cc66d9 Mon Sep 17 00:00:00 2001
From: Yuriy Skalko
Date: Tue, 27 Oct 2020 11:20:27 +0200
Subject: [PATCH 2/5] Use nullptr
---
src/insets/Inset.h | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/insets/Inset.h b/src/insets/Inset.h
index 2fec7023a6..bf165d91c5 100644
--- a/src/insets/Inset.h
+++ b/src/insets/Inset.h
@@ -135,33 +135,33 @@ public:
virtual bool isLabeled() const { return false; }
///
