Re: Force previews to update
On Wed, Mar 07, 2018 at 09:21:02PM +, racoon wrote: > A cross reference to an enumerate number or a description label. I see. Indeed I haven't used those types of previews so I have not come across this issue. Scott signature.asc Description: PGP signature
Re: Force previews to update
On 07.03.2018 19:55, Scott Kostyshak wrote: On Wed, Mar 07, 2018 at 06:53:32PM +, racoon wrote: I think the (instant) preview function (Insert > Preview) is really nice. In particular for the readability of references in a text. However, I noticed that I rarely use it. I think this has to do with the fact that LyX does not automatically update those when their content changes. What is a specific example of a content change that you're thinking of? A cross reference to an enumerate number or a description label. Daniel
Re: Problem with lyx-archiv (zip)
Am 06.03.2018 um 15:40 schrieb a...@andreashegenbart.de: -Ursprüngliche Nachricht- Von: lyx-users@lists.lyx.orgIm Auftrag von Kornel Benko Gesendet: Dienstag, 6. März 2018 12:56 An: lyx-users@lists.lyx.org Betreff: Re: Problem with lyx-archiv (zip) Am Dienstag, 6. März 2018 12:27:09 CET schrieb a...@andreashegenbart.de: How can I define the system-dir? You have it set. To set different (say e.g. new_sys_dir) systemdir you have to use command-line argumets. $ lyx -sysdir new_sys_dir You´ll find attached two pdf-files: "Converter" and "Systemverzeichnis" Does this help along? Andreas Not really. We need the output of the python-command and of the configure output, which you may find in ~/AppData/Roaming/Lyx2.3/configure.log. Kornel You´ll find it attached Best Andreas In Andreas log file it is apparently this (>>)which causes the error: DEBUG: Add to RC: \Format lyxzip zip "LyX Archive (zip)" "" "" "" "document,menu=export" "" DEBUG: Add to RC: >> *\converter lyx lyxzip "python -tt $$s/scripts/lyxpak.py $$r/$$f" ""* I found in the internet only this one, which is 5 years old and before the export archiving was introduced: https://tex.stackexchange.com/questions/72913/lyx-export-suitable-for-journal-publication Any idea what is missing (Lyx 3.0 under windows) Wolfgang
Re: Force previews to update
On Wed, Mar 07, 2018 at 06:53:32PM +, racoon wrote: > I think the (instant) preview function (Insert > Preview) is really nice. In > particular for the readability of references in a text. However, I noticed > that I rarely use it. I think this has to do with the fact that LyX does not > automatically update those when their content changes. What is a specific example of a content change that you're thinking of? Scott signature.asc Description: PGP signature
Force previews to update
I think the (instant) preview function (Insert > Preview) is really nice. In particular for the readability of references in a text. However, I noticed that I rarely use it. I think this has to do with the fact that LyX does not automatically update those when their content changes. And I see why to have this done automatically is a bit tricky. I guess LyX would have to compare the current preview with a newly created preview when the document changes which in turn takes too much resources? However, the next best thing would probably be a function to update all previews, maybe Document > Update > Instant Previews or so? There is no such thing if I see it correctly. Daniel
Re: Windows users: can you test the 2.3.0 installer?
Am 07.03.2018 um 17:06 schrieb Emile Lunardon: I certainly did not update manually Miktex during the bundle3 installation. Read again my messages, You wrote "To test this new installation program, I let the Miktex update run. I have no idea what has been updated, but what's for sure is that the compilations with LyX don't work anymore now ! " This is what I don't understand. How could you decide to let the update run on your own? I realize now that you installed LyX 2.3.0 the first time using version 1 of the LyX installer. This can explain the problems you saw. I tested this now but cannot reproduce. Could you please maybe do me the favor and - uninstall LyX and MiKTeX _completely_ - reinstall LyX using the 2.3.0 RC1/ installer (if you still have it on your PC) - install LyX 2.3.0 over it using the version 3 installer. I finally manage later to recover a working Miktex via the installation of a new package. This what i also don't understand. if MiKTeX is broken, you can try whatever you want. Updates cannot be installed and a package installation doesn't repair MiKTeX. There must have happened something else. Because when a package update succeeds and you can use LyX afterwards, then it could only happen that the package file name database was incomplete. However, I cannot reproduce this. Meanwhile MiKTeX released 3 important bugfixes to its package handling system. I hope that they are available tomorrow for all users. regards Uwe
Re: Windows users: can you test the 2.3.0 installer?
Am 07.03.2018 um 15:43 schrieb Scott Kostyshak: No problem, everything is fine now. All you have to do is to install LyX using version 3 of the installer. I might have misunderstood something, but I think it is exactly version 3 of the installer that caused Emile's problems. He manually updated MiKTeX and that breaks it (as I explained due to a bug in MiKTeX). Installing version 3 of the installer will fix this. I asked him to test this since I am too very curious if this works. Emile, what is the result? regards Uwe
Re: Windows users: can you test the 2.3.0 installer?
On Mon, Mar 05, 2018 at 10:08:33AM +, Uwe Stöhr wrote: > Am 05.03.2018 um 10:57 schrieb Emile Lunardon: > > > This time, the usual way of repairing Miktex by an upgrade didn't work: > > So the things are going reallv worse ! > > No problem, everything is fine now. All you have to do is to install LyX > using version 3 of the installer. I might have misunderstood something, but I think it is exactly version 3 of the installer that caused Emile's problems. Scott signature.asc Description: PGP signature