Re: New 2.3.1 Windows Installer for Testing
On 7/09/2018 5:37 a.m., Richard Kimberly Heck wrote: Here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Please let us know if this fixes the slowness bug from before. If so, we'll proceed to release. Riki I've installed this version and it solves the slowness problem with my test document. The kpsewhich.log is not being added to with operations (new paragraphs, selection + deletion, etc.) that were generating entries with the first installer. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
New 2.3.1 Windows Installer for Testing
Here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Please let us know if this fixes the slowness bug from before. If so, we'll proceed to release. Riki
LyX 2.3.1 Again
Hi, all, First, sorry to be slow dealing with the new tarballs, etc. I'm about to upload a new Windows installer for testing, and if that's OK then I'll upload new tarballs, etc, so we can build new binaries, etc. While we're waiting, it seems to me that it is now time to kill off the bundle installer. I was going to wait to do this until 2.3.2, but given the recent chaos with MiKTeX, I don't see how we can release such a thing. This will mean putting some language on the LyX website, similar to what's there for OSX, telling people that they will need to install a TeX distribution. Since this will be a new thing for some people, it'd be nice either there or elsewhere to try to provide some guidance, specifically about how to install TeXLive so as to end up with a functional installation for use with LyX. Are there any Windows users who could experiment with this and come up with some language for the website or wiki? Are there different 'types' of installation people can use? Is it possible for us somehow to create a list of packages that people can pass to TeXLive so those will be installed? The thing I most worry about is font definitions, actually. I personally find the error messages in those cases to be nearly unintelligible. Riki
Re: Question on osuosl.org hosting service(s)
Thanks, Pavel, to taking this responsiblity. On 09/06/2018 10:37 AM, Pavel Sanda wrote: > Hi OSU Open Source Lab, > > I'm one of developers of LyX, open source document processor (www.lyx.org). > Our services (web/bug tracker system/git server/wiki site) used to be kindly > hosted for the past decade by University of Bonn, but their virtualization > service will be unfortunately discontinued soon. > > We are currently looking for a new shelter for the project infrastructure > and because we know you already host bunch of other OS projects > we wanted to ask whether it would be possible to use your hosting > service. > > Our current services run in the virtual machine (we have complete > qcow2 image available) and include: > - web (www.lyx.org - apache + php) > - git server (git.lyx.org) which is accessed via ssh by developers > - bug tracker system (www.lyx.org/trac) > - wiki (wiki.lyx.org) > - svn server (svn.lyx.org) interfacing to some parts of web/wiki > > Apart from those: > > - mail conferences are currently maintained independently, but the host > already > suggested to use different service, which would provide more reliable > uptimes... > > - ftp infrastructure (ftp.lyx.org) and mirroring is maintained independently > and we currently do not need any help. > > > Are the specifics above compatible with your hosting policies? > We should be able to change some parts in case the big picture is > compatible... > > > Thanks for your attention, on the behalf of the LyX team, > > Pavel Sanda
Re: 2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"
It seems that the problem was due to an unintentional change in the name of the folder. It had nothing to do with LyX. Apologies and thanks for your replies! Micha On 05.09.2018 14:25, Kornel Benko wrote: Am Mittwoch, 5. September 2018 14:04:50 CEST schrieb Micha H. Werner : currently, compilation of LyX2.3.1-1 fails on Ubuntu 18.04.1 LTS. This is the complete output of ./configure: root@dell:/local/lyx# ./configure Why do you do this as root? And why in the source dir? configuring LyX version 2.3.0 checking for build type... release checking for version suffix... checking whether Qt5 is requested... no checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking target system type... x86_64-pc-linux-gnu checking what packaging should be used... posix checking whether to enable maintainer-specific portions of Makefiles... no checking whether make supports nested variables... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... configure: error: unsafe absolute working directory name According to configure, the directory name contains unsafe characters (one of >>"#$&'`<<). Kornel
Re: Cannot unshow label of conglomerate
2018-09-06 15:39 GMT+02:00 Daniel : > When I rename my style to InsetLayout Flex:Greyedout, then it does *not* > show as conglomerate. Is that what I should see? > No. See attached. > > And strange that one can toggle it with Ctrl+i but there is no way to > change it via any menu (context or not). > That's what I tried to explain in my previous post. Jürgen conglomerate_note.lyx Description: application/lyx
Re: Cannot unshow label of conglomerate
On 06/09/2018 15:18, Jürgen Spitzmüller wrote: 2018-09-06 12:34 GMT+02:00 Daniel: In the attached file I have turned a grayed out note into a conglomerate. However, I don't know hoe to unshow the label below it since there is no Show Label in the context menu. Also, there seems to be no Show Label menu entry in general for conglomerates. Is any of this on purpose or a bug? The conglomerate context menu is only taken up for Flex insets (yours takes to context-note menu, which does not have a toggle entry). If you rename your style to InsetLayout Flex:Greyedout, you'll se that. Shortcut Ctrl+i works with your definition as well, though. When I rename my style to InsetLayout Flex:Greyedout, then it does *not* show as conglomerate. Is that what I should see? And strange that one can toggle it with Ctrl+i but there is no way to change it via any menu (context or not).
Re: Cannot unshow label of conglomerate
2018-09-06 12:34 GMT+02:00 Daniel: > In the attached file I have turned a grayed out note into a conglomerate. > However, I don't know hoe to unshow the label below it since there is no > Show Label in the context menu. Also, there seems to be no Show Label menu > entry in general for conglomerates. Is any of this on purpose or a bug? > The conglomerate context menu is only taken up for Flex insets (yours takes to context-note menu, which does not have a toggle entry). If you rename your style to InsetLayout Flex:Greyedout, you'll se that. Shortcut Ctrl+i works with your definition as well, though. > > Best, > Daniel >
Cannot unshow label of conglomerate
In the attached file I have turned a grayed out note into a conglomerate. However, I don't know hoe to unshow the label below it since there is no Show Label in the context menu. Also, there seems to be no Show Label menu entry in general for conglomerates. Is any of this on purpose or a bug? Best, Daniel conglomerate_note.lyx Description: application/lyx
Re: elsarticle
Am Donnerstag, 6. September 2018 10:34:56 CEST schrieb Jürgen Spitzmüller
:
> 2018-09-05 19:27 GMT+02:00 Kornel Benko :
>
> > If I use
> > \message{^^JLaTeX Warning: Value of counters on page 1
> > undefined^^J}
> > unconditionally instead, it works, but I don't like it.
> >
>
> A workaround for the templates, until the class is fixed, is to put this to
> the preamble:
>
> % Workaround for a bug in elsarticle 3.0
>
> \Newlabel{t1}{1}
>
> \Newlabel{t2}{2}
>
> Jürgen
>
>
> >
> > Kornel
> >
Thanks Jürgen, I think we can wait one or two weeks.
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: Patch for bug in elsarticle.cls
On Thu, Sep 6, 2018 at 1:55 PM, Jürgen Spitzmüller wrote: > Dear colleagues > > Please find attached a patch that fixes an issue in recent elsarticle.cls > (3.0). The problem is that you forgot to check the existence of the > titlefootnote (tnote) label (\X@t) in \tnotemark (as opposed to the > other labels in other contexts, where you check with \elsRef). As a > consequence, you get a "missing number" LaTeX error on the first LaTeX run > (before the labels are written to the aux file). This is a problem with > editors that break compilations on LaTeX errors (such as LyX, which > currently cannot process elsarticle documents with title footnotes). > > Please consider this patch for the next release of the class. > > Dear Jürgen, Thank you for the patch. Next week we will release an updated version to CTAN. We will include this patch as well. thank you -- Rishi T. LaTeX Support at STMDOCS
Re: Patch for bug in elsarticle.cls
2018-09-06 10:48 GMT+02:00 Rishikesan Nair T : > Dear Jürgen, > > Thank you for the patch. Next week we will release an updated version to > CTAN. We will include this patch as well. > > thank you > Dear Rishi Excellent. Thanks for the swift reaction! Jürgen
Re: elsarticle
2018-09-05 19:27 GMT+02:00 Kornel Benko :
> If I use
> \message{^^JLaTeX Warning: Value of counters on page 1
> undefined^^J}
> unconditionally instead, it works, but I don't like it.
>
A workaround for the templates, until the class is fixed, is to put this to
the preamble:
% Workaround for a bug in elsarticle 3.0
\Newlabel{t1}{1}
\Newlabel{t2}{2}
Jürgen
>
> Kornel
>
>
>
>
Patch for bug in elsarticle.cls
Dear colleagues
Please find attached a patch that fixes an issue in recent elsarticle.cls
(3.0). The problem is that you forgot to check the existence of the
titlefootnote (tnote) label (\X@t) in \tnotemark (as opposed to the
other labels in other contexts, where you check with \elsRef). As a
consequence, you get a "missing number" LaTeX error on the first LaTeX run
(before the labels are written to the aux file). This is a problem with
editors that break compilations on LaTeX errors (such as LyX, which
currently cannot process elsarticle documents with title footnotes).
Please consider this patch for the next release of the class.
Thanks in advance,
Jürgen
--- /usr/local/texlive/2018/texmf-dist/tex/latex/elsarticle/elsarticle.cls
+++ /tmp/meld-tmpvss9c3st
@@ -123,7 +123,7 @@
\def\tnotemark[#1]{}
\else
\def\tnotemark[#1]{\@for\mytmark:=#1\do{%
- \expandafter\ifcase\csname X@\mytmark\endcsname\or$^{\star}$\or
+ \expandafter\ifcase\elsRef{\mytmark}\or$^{\star}$\or
$^{,\star\star}$\fi
}%
}
