Re: elsarticle
Am Mittwoch, 5. September 2018 17:56:26 CEST schrieb Jean-Marc Lasgouttes
:
> Le 04/09/2018 à 14:03, Kornel Benko a écrit :
> > Am Dienstag, 4. September 2018 12:35:52 CEST schrieb Jürgen Spitzmüller
> > :
> >> 2018-09-03 18:11 GMT+02:00 Kornel Benko :
> >>
> >>> Ah, yes, I forgot. So, since they don't respond, we don't care?
> >>>
> >>
> >> We could insist. Try to fix the problem ourselves in the cls and provide
> >> them with a patch. Ask for help on stackexchange ...
> >>
> >> Jürgen
> >>
> >
> > This is not so trivial. They use the created .aux file for infos about
> > counter too. But on the first run, this file does not exist. Rerunning
> > the compilation makes everything work.
> > If there only would have been the message 'Rerun latex' in the log-file :(
>
> What if we added something like
>
> AddToPreamble
>\IfFileExists{\jobname.aux}{}{\message{Re-run LaTeX to get counters
> right}}
> End
>
> Note that I did not try any of it and there are certainly several error
> in this code, but the idea should work, I think.
>
> JMarc
Unfortunately it does not help. (I already tried something like this with
AddToPreamble
\IfFileExists{\jobname.aux}{\message{}}{\message{^^JLaTeX Warning:
Value of counters on page 1 undefined^^J}}
EndPreamble
in elsarticle.layout)
The problem is, that the .aux file already exists at the moment of running
latex, because it is created by
bibtex.
If I use
\message{^^JLaTeX Warning: Value of counters on page 1 undefined^^J}
unconditionally instead, it works, but I don't like it.
Kornel
signature.asc
Description: This is a digitally signed message part.
Re: elsarticle
> > Why do you push _me_ to represent your position towards stackexchange? > Is it because I reported it? > If you don't want to do that, don't do it. In any case, I don't have time ATM to look after this problem. But it is certainly an upstream problem. Jürgen >
Re: Imagemagick might be banned from postscipt/pdf conversion soon on your distro too
Jürgen Spitzmüller wrote: > Am Sonntag, den 02.09.2018, 23:27 +0200 schrieb Pavel Sanda: > > These are pacthes for the vulns reported on Aug 21, but as the > > original report says: > > Yes, but it indicates that Artifex care and reacts swiftly. So no need > to declare ghostscript death (yet). I agree, we could just mention this problem in the 2.3.1 release news. Pavel
Re: elsarticle
Le 04/09/2018 à 14:03, Kornel Benko a écrit :
Am Dienstag, 4. September 2018 12:35:52 CEST schrieb Jürgen Spitzmüller
:
2018-09-03 18:11 GMT+02:00 Kornel Benko :
Ah, yes, I forgot. So, since they don't respond, we don't care?
We could insist. Try to fix the problem ourselves in the cls and provide
them with a patch. Ask for help on stackexchange ...
Jürgen
This is not so trivial. They use the created .aux file for infos about
counter too. But on the first run, this file does not exist. Rerunning
the compilation makes everything work.
If there only would have been the message 'Rerun latex' in the log-file :(
What if we added something like
AddToPreamble
\IfFileExists{\jobname.aux}{}{\message{Re-run LaTeX to get counters
right}}
End
Note that I did not try any of it and there are certainly several error
in this code, but the idea should work, I think.
JMarc
Re: For non-math operators, disable change limits or use \mathop?
Le 03/09/2018 à 21:56, Scott Kostyshak a écrit : On Mon, Sep 03, 2018 at 06:04:42PM +0200, Jean-Marc Lasgouttes wrote: Le 30/08/2018 à 06:52, Scott Kostyshak a écrit : The \limits command only works for math operators, but we enable MATH_LIMITS whenever there are limits. This leads to an error if the limits are not on a math operator. See the attached error.lyx. We can use \mathop to convert to a math operator, and then there is no error. See no_error.lyx. An alternative would be to just disable MATH_LIMITS if the symbol is not a math operator. Please try what I just pushed to master at 7b7ed64a0e76. Tested and works well! Thanks. Actually it did not work with under/overbrace. Fixed now. JMarc
Re: 2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"
Le 05/09/2018 à 14:25, Kornel Benko a écrit : 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 >>"#$&'`<<). What does "pwd" return? JMarc
Re: 2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"
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 signature.asc Description: This is a digitally signed message part.
2.3.1-1 compilation error on ubuntu 18.04.1 LTS "unsafe absolute working directory name"
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 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
Workaround for: WARNING: updating LaTeX or LyX under Windows will currently break LaTeX installation
As of today the update servers are working again. However, one needs a workaround because the buggy DLL of MiKTeX prevents the updates from being applied. it seems that the bug affects all users of Windows 7 while Win 10 is not affected. For the affected users there is a workaround but you need admin permissions and some knowledge: - open a Windows console as admin (type in "cmd" in the Windows Start field, and right-click on it to run it with admin privileges) - execute these 2 commands subsequently: initexmf --admin --update-fndb and initexmf --admin --mklinks --force - close the Windows console - now start the MiKTeX console - choose there to restart with admin privileges - check for updates and if there are any apply them From my point of view I see no other option than to provide a new LyX for Windows installer that repairs broken system by executing these commands in the background after LyX was installed. This way users with problems can just run the Win installer again and get a working LyX back in a minute without the need to know about console commands etc. @developers: Maybe now you see that the Win installer must do more and forcing a MiKTeX update is necessary as you can see in this case. We cannot say "not our fault". Yes, LyX is not to blame but what matters is if users can use LyX. In my case I wanted to write an urgent letter with LyX but could not use it and had to use LibreOffice instead. regards Uwe
Re: elsarticle
Am Mittwoch, 5. September 2018 08:25:57 CEST schrieb Jürgen Spitzmüller : > > Ask on stackexchange. > > Jürgen Please, don't make me crazy. The compilation needs a second run due to missing .aux file. You are convinced, that this behaviour is a class error. Why do you push _me_ to represent your position towards stackexchange? Is it because I reported it? We already have plenty of cases, where some missing file (.deb, .idx, .aux) needs a rerun. And we respect it. What is here so different, that we have to insist on a correction? Kornel signature.asc Description: This is a digitally signed message part.
