Re: [LyX/master] Fix the implementation of new libertine package
Am Samstag, den 03.03.2018, 08:29 +0100 schrieb Jürgen Spitzmüller: > Am Freitag, den 02.03.2018, 12:18 +0100 schrieb Juergen Spitzmueller: > > commit 905516fd706a90148a458f9936c565cbe5fcfcff > > Author: Juergen Spitzmueller > > Date: Fri Mar 2 12:17:33 2018 +0100 > > > > Fix the implementation of new libertine package > > > > Needs to go to 2.3.1-staging > > Jürgen Richard, did you see this? Jürgen signature.asc Description: This is a digitally signed message part
Re: Solution: Summary for the Win installer problem
On 03/05/2018 07:33 PM, Uwe Stöhr wrote: > Am 05.03.2018 um 23:46 schrieb Richard Heck: > >> Uwe, even if LyX will not work without the updated installation, we >> CANNOT update the user's LaTeX installation without asking for >> permission---which means giving them the option to cancel the entire >> install. Otherwise, we can break things, as in the thread Scott posted. > > What? So I should deliver a LyX installer leading to a broken LaTeX > that can only be fixed by reinstalling MiKTeX? That cannot be the goal! The proposal is to *abort* the LyX installation, if the user does not want to update. You can explain in a dialog that LyX will not work otherwise. But you cannot screw with their system without their permission. Really. The obvious thing here is to ask about this before doing anything else. Do not touch ANYTHING until you have permission to proceed. > I don't get your point. What is the problem of updating a package > handling system? The point is that we do not affect people's systems without permission. Otherwise, we get reports like https://latex.org/forum/viewtopic.php?f=19&t=30919 which is unacceptable. > Under Linux you also have to do this if you want to be able to obtain > packages in future. > In this case it is even worse, whenever you you decide to update > packages by yourself and invoke MiKTeX's update manually you break > your package handling system. So also LyX 2.2.3 users can get a broken > system even without installing LyX. But the consequence is that they > then cannot user LyX anymore. This sounds like a MiKTeX bug that we do not need to make worse. Frankly, I find the whole Windows packaging system deeply worrying. We do not do anything like this on OSX---package some TeX distribution with our own code---and I am not sure you understand the way Linux works. For one thing, there is no single way Linux works, since all of this is highly dependent upon the distribution. And note: If some Linux distro messes this up, then WE do not get blamed for it, because WE do not release those packages. As Scott said some time ago, it is very strange indeed if LyX's basic functionality breaks because of a change in some external program's package-handling mechanism. LyX should not be that entwined with external programs. Richard
Re: Solution: Summary for the Win installer problem
Am 05.03.2018 um 23:46 schrieb Richard Heck: Uwe, even if LyX will not work without the updated installation, we CANNOT update the user's LaTeX installation without asking for permission---which means giving them the option to cancel the entire install. Otherwise, we can break things, as in the thread Scott posted. What? So I should deliver a LyX installer leading to a broken LaTeX that can only be fixed by reinstalling MiKTeX? That cannot be the goal! Moreover, if users are really forced to reinstall MiKTeX they loose all personal settings, packages etc. So what is preferable, a system that keeps all your personal settings, packages and that works of a broken system where you loose all personal settings? I don't get your point. What is the problem of updating a package handling system? Under Linux you also have to do this if you want to be able to obtain packages in future. In this case it is even worse, whenever you you decide to update packages by yourself and invoke MiKTeX's update manually you break your package handling system. So also LyX 2.2.3 users can get a broken system even without installing LyX. But the consequence is that they then cannot user LyX anymore. regards Uwe
Re: Solution: Summary for the Win installer problem
On 03/05/2018 03:18 PM, racoon wrote: > On 05.03.2018 20:16, Uwe Stöhr wrote: >> Am 05.03.2018 um 19:37 schrieb racoon: >> >>> However, it does not give the user a choice on whether to update >>> MiKTeX or not. >> >> Yes, that is correct and I explained now in several mails why and >> that there is no other option. > > Sorry, I have a bit of a hard time following the discussion. > > Why is forcing the user to make a choice between going ahead with the > setup and cancelling no option? Uwe, even if LyX will not work without the updated installation, we CANNOT update the user's LaTeX installation without asking for permission---which means giving them the option to cancel the entire install. Otherwise, we can break things, as in the thread Scott posted. Richard
Re: [LyX/master] tex2lyx: support biblatex
On 03/05/2018 07:03 AM, Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: >> I thought 2.3.1 was supposed to be either for urgent stuff or just be >> merged with 2.3.2. No I do not know... > My understanding was similar, i.e. 2.3.2-staging will be actually merged > into 2.3.1 if there is no immediate 2.3.1 release fixing some urgent > problem... Yes. rh
Re: [LyX/master] tex2lyx: support biblatex
On 03/05/2018 03:37 AM, Jürgen Spitzmüller wrote: > Am Montag, den 05.03.2018, 09:32 +0100 schrieb Jean-Marc Lasgouttes: >> I thought 2.3.1 was supposed to be either for urgent stuff or just >> be >> merged with 2.3.2. No I do not know... > I thought, since 2.3.1-staging does not contains really urgent stuff, > that 2.3.1 is released with urgent fixes (but without staging) if > urgent issues arise, and else with 2.3.1 staging. My thought was: urgent stuff and super-duper-safe stuff to 2.3.1-staging, in case we need an emergency release. This one looks a bit more extensive. I'd say 2.3.2-staging for now. rh
Re: [LyX/master] tex2lyx: support qualified citation lists (biblatex)
On 03/04/2018 02:14 PM, Jürgen Spitzmüller wrote: > Am Sonntag, den 04.03.2018, 20:12 +0100 schrieb Juergen Spitzmueller: >> commit 0915e814814ab26732b6dd13fc1740cfbf64b5b4 >> Author: Juergen Spitzmueller >> Date: Sun Mar 4 20:12:27 2018 +0100 >> >> tex2lyx: support qualified citation lists (biblatex) > This one's rather 2.3.2 stuff. OK. r
Re: [LyX/master] tex2lyx: refsection and bibbysection support (biblatex)
On 03/04/2018 11:31 AM, Jürgen Spitzmüller wrote: > Am Sonntag, den 04.03.2018, 17:30 +0100 schrieb Juergen Spitzmueller: >> commit 1a3dbbf07ad837a685af93bf3d1d1a784e0d27ae >> Author: Juergen Spitzmueller >> Date: Sun Mar 4 17:29:59 2018 +0100 >> >> tex2lyx: refsection and bibbysection support (biblatex) > Candidate for 2.3.1. OK. rh
Re: [LyX/master] tex2lyx: consider options passed via \PassOptionsToPackage
On 03/04/2018 10:50 AM, Jürgen Spitzmüller wrote: > Am Sonntag, den 04.03.2018, 16:48 +0100 schrieb Juergen Spitzmueller: >> commit 476401a76f8bdb3dd2c2a482b2088f00dbe501d9 >> Author: Juergen Spitzmueller >> Date: Sun Mar 4 16:45:37 2018 +0100 >> >> tex2lyx: consider options passed via \PassOptionsToPackage > Candidate for 2.3.1. OK. rh
Re: Solution: Summary for the Win installer problem
On 05.03.2018 20:16, Uwe Stöhr wrote: Am 05.03.2018 um 19:37 schrieb racoon: However, it does not give the user a choice on whether to update MiKTeX or not. Yes, that is correct and I explained now in several mails why and that there is no other option. Sorry, I have a bit of a hard time following the discussion. Why is forcing the user to make a choice between going ahead with the setup and cancelling no option? Feel free to just ignore my question if you have answered that as well before. Also, I noticed that the MiKTeX Package Manager opens up for some reason and stays open. I am not sure why that is happening. This is another bug in MiKTeX I mentioned. There will therefore be a sentence I the announcement text. However, I just see that MiKTeX released a new installer as promised. This bug will then be fixed. Sorry, I must have missed that, too. Daniel
Re: Solution: Summary for the Win installer problem
Am 05.03.2018 um 19:37 schrieb racoon: However, it does not give the user a choice on whether to update MiKTeX or not. Yes, that is correct and I explained now in several mails why and that there is no other option. Also, I noticed that the MiKTeX Package Manager opens up for some reason and stays open. I am not sure why that is happening. This is another bug in MiKTeX I mentioned. There will therefore be a sentence I the announcement text. However, I just see that MiKTeX released a new installer as promised. This bug will then be fixed. @Scott, I have no time today but will provide a new installer tomorrow. regards Uwe
Re: Solution: Summary for the Win installer problem
On 05.03.2018 19:37, racoon wrote: On 04.03.2018 19:36, Uwe Stöhr wrote: Am 04.03.2018 um 16:19 schrieb Uwe Stöhr: Good news: There will be a new MiKTeX installer soon and the MiKTeX maintainer proposed a workaround for the main bug. I cannot promise that I will find time today to check if this will work for all cases. OK, I could check it and it works. The new installer can be found here: http://ftp.lyx.de/LyXWinInstaller/LyX2.3.0/ Now the users is not bothered at all. Everything that needs to be done is done by the installer silently. I would nevertheless wait with the announcement because the MiKTeX developer promised to make a release just for us soon. If it will be available by Tuesday, I will create a new installer, if not, let's release LyX 2.3.0 with the installer version 3 I linked above. Thanks Uwe. I have tried the installer. However, it does not give the user a choice on whether to update MiKTeX or not. One is only told that MiKTeX must be updated and can only click "OK". I guess it would be preferable to let the user choose to at least update or cancel the whole installation. But maybe that is hard to implement since the message comes up only after parts of LyX are already installed? But maybe one could inform the user at an earlier stage where she then has to click "Next" or so? Also, I noticed that the MiKTeX Package Manager opens up for some reason and stays open. I am not sure why that is happening. And the installation also worked without an active internet connection.
Re: Solution: Summary for the Win installer problem
On 04.03.2018 19:36, Uwe Stöhr wrote: Am 04.03.2018 um 16:19 schrieb Uwe Stöhr: Good news: There will be a new MiKTeX installer soon and the MiKTeX maintainer proposed a workaround for the main bug. I cannot promise that I will find time today to check if this will work for all cases. OK, I could check it and it works. The new installer can be found here: http://ftp.lyx.de/LyXWinInstaller/LyX2.3.0/ Now the users is not bothered at all. Everything that needs to be done is done by the installer silently. I would nevertheless wait with the announcement because the MiKTeX developer promised to make a release just for us soon. If it will be available by Tuesday, I will create a new installer, if not, let's release LyX 2.3.0 with the installer version 3 I linked above. Thanks Uwe. I have tried the installer. However, it does not give the user a choice on whether to update MiKTeX or not. One is only told that MiKTeX must be updated and can only click "OK". I guess it would be preferable to let the user choose to at least update or cancel the whole installation. But maybe that is hard to implement since the message comes up only after parts of LyX are already installed? But maybe one could inform the user at an earlier stage where she then has to click "Next" or so? Also, I noticed that the MiKTeX Package Manager opens up for some reason and stays open. I am not sure why that is happening. Daniel
Re: Update on 2.3.0 situation and Windows-specific issues
On Sun, Mar 4, 2018 at 8:50 AM, Scott Kostyshak wrote: > On Sat, Mar 03, 2018 at 11:46:53PM +, Uwe Stöhr wrote: > > Am 03.03.2018 um 21:26 schrieb Scott Kostyshak: > > > > >- If you have a problem compiling the document Help > User Guide > after > > > installation, consider uninstalling LyX and MiKTeX, and then using > > > the LyX *bundle* installer, which will automatically reinstall > > > MiKTeX. > > > > Please replace this point by the text I just sent in my mail with the > > solution. > > OK, here is the Windows-specific part, after taking your and Joel's > suggestions into account: > > --- > The following statements are specific to Windows users: > - If you installed a pre-release of LyX 2.3.0, you should uninstall that > version before installing this newer release. > - If you have a virus scanner installed and LyX cannot find "latex.exe", > as a first step just close the installer and rerun it. > Minor suggested wording change to clarify (based on my understanding): from: virus scanner installed and LyX cannot find to: virus scanner installed and the LyX installer cannot find At least, the way I read the step, the installer is the component not finding the latex.exe executable, not the LyX executable itself post-install (at which point, one couldn't "just close the installer" because it would have completed already). Sorry for the late-breaking suggestion. - Joel
Re: [LyX/master] tex2lyx: support biblatex
Jean-Marc Lasgouttes wrote: > I thought 2.3.1 was supposed to be either for urgent stuff or just be > merged with 2.3.2. No I do not know... My understanding was similar, i.e. 2.3.2-staging will be actually merged into 2.3.1 if there is no immediate 2.3.1 release fixing some urgent problem... Pavel
Re: Solution: Summary for the Win installer problem
Le 04/03/2018 à 22:23, Uwe Stöhr a écrit : We need to install packages (hyphenation, language support, tipa, math, etc.) because we cannot know what features will be used by the user. This can only be done if the user has a working package handling system. As user I expect a working software and not that certain features don't work for reasons I don't understand. We cannot bother users with the system behind LyX. I understand the goal, but I have reservations about the means. If I have a working installation from last year, I see no reason why it would not still be a working installation this year, except for LyX insistence to "fix" it behind my back. Can we at least give a possibility for users not to be spoonfed if they do not want to? JMarc
Re: [LyX/master] tex2lyx: support biblatex
Am Montag, den 05.03.2018, 09:32 +0100 schrieb Jean-Marc Lasgouttes: > I thought 2.3.1 was supposed to be either for urgent stuff or just > be > merged with 2.3.2. No I do not know... I thought, since 2.3.1-staging does not contains really urgent stuff, that 2.3.1 is released with urgent fixes (but without staging) if urgent issues arise, and else with 2.3.1 staging. I also understood that 2.3.2 staging is stuff for later anyway (at least I would prefer so for the commits I pushed there). So either 2.3.1 > urgent fixes 2.3.2 > 2.3.1-staging and fixes committed to 2.3.x directly 2.3.3 > 2.3.2-staging and fixes committed to 2.3.x directly or (if no urgent issues arise) 2.3.1 > 2.3.1-staging and fixes committed to 2.3.x directly 2.3.2 > 2.3.2-staging and fixes committed to 2.3.x directly But I might have misunderstood the idea. > Do as you prefer. I do whatever the maintainer commands. Jürgen > JMarc signature.asc Description: This is a digitally signed message part
Re: [LyX/master] tex2lyx: support biblatex
Le 05/03/2018 à 07:48, Jürgen Spitzmüller a écrit : Am Sonntag, den 04.03.2018, 21:02 +0100 schrieb Jean-Marc Lasgouttes: Why not 2.3.1? Jürgen It is supposed to be for urgent matters. But 2.3.1-staging contains many non-urgent matters already. I think it tex2lyx support for the most anticipated new feature of 2.3.x is important enough. I thought 2.3.1 was supposed to be either for urgent stuff or just be merged with 2.3.2. No I do not know... Do as you prefer. JMarc
Re: tex2lyx no longer compilable because of too many nested ifs
Am Sonntag, den 04.03.2018, 21:51 +0100 schrieb Uwe Stöhr: > tex2lyx in master is no longer compilable with MSVC. The reason is > that > we have now too many else if clauses in text.cpp: Should be fixed. >D:\LyXGit\Master\src\tex2lyx\text.cpp(5269): fatal error C1061: > compiler limit: blocks nested too deeply > [D:\LyXGit\Master\compile-2015\src\tex2lyx\tex2lyx.vcxproj] > > This is a known limitation: > https://msdn.microsoft.com/en-us//library/dcda4f64.aspx > and Georg spent in the past some time to reduce the ifs. Rather than that, I got rid of the "else if" clauses altogether. We can as well continue in the loop if a condition is met. Now there shouldn't be any limitation anymore (if MSVC doesn't limit the number of if's also). Jürgen signature.asc Description: This is a digitally signed message part
