Re: No Integrals?
On 4/26/19 5:17 PM, UD Kap wrote: Thank you all for your speedy responses. I suspect that Pavel has fingered it-- I don't see any LYX folder in the /usr/share/fonts folder. At least on Mint, there is no .../lyx folder there. The problem is on the Lyx screen-- the output looks OK. I installed from Liviu's ppa. Liviu's PPA has a package named fonts-lyx that will create a folder /usr/share/fonts/truetype (if it does not already exist) and then put a subfolder named 'lyx' under that. In /usr/share/fonts/truetype/lyx, you should find 11 TrueType font files (.ttf extension). If that's not there, you just need to install the fonts-lyx package from the PPA. It is likely, in addition, that my TexLive installation is at fault-- I installed TL from the Mint/Ubuntu repositories, rather than from the VERY CONFUSED Texlive site. The disappointing result is that tlmgr does not work right, or not at all. I get TeXLive from a different PPA: https://launchpad.net/~jonathonf/+archive/ubuntu/texlive. (He also has LyX distributions there, but I've been sticking with Liviu's PPA and have no regrets.) Paul
Re: Win 7 and LyX and MikTeX
On 25/04/2019 6:45 AM, Baris Erkus wrote: Hello, Is anybody using LyX+MikTeX+Win 7 without any problems? I have a computer where I can only install Win 7 and wondering if it will cause any problems. Thanks Baris I have a computer with this combination installed and I much prefer it to my current computer with LyX+MiKTeX+Win 10. Unfortunately the Win 7 machine showed signs of aging but I used it without problems for many years. Andrew
Re: No Integrals?
Thank you all for your speedy responses. I suspect that Pavel has fingered it-- I don't see any LYX folder in the /usr/share/fonts folder. The problem is on the Lyx screen-- the output looks OK. I installed from Liviu's ppa. It is likely, in addition, that my TexLive installation is at fault-- I installed TL from the Mint/Ubuntu repositories, rather than from the VERY CONFUSED Texlive site. The disappointing result is that tlmgr does not work right, or not at all. Yours, Ehud Kaplan On 4/26/19 9:46 AM, Guenter Milde wrote: On 2019-04-26, UD Kap wrote: I am sure I am doing something REALLY silly, but my Lyx (2.3.2, running under Linux Mint-XFCE) refuses to show integrals, pi, etc. Instead, it shows some other symbols (O with an accent for integral, bold letter P for \pi, etc.). Wrong font or wrong font encoding. Latex works fine-- if I use ERT in Lyx or Texworks without Lyx everything is correct, but not if I Insert an equation into Lyx. Is this on screen or in the output? Where did I screw up? Hard to tell without more info: * if it is on screen: what is your GUI font? * if it is in the output, give a minimal example (very samll lyx file that shows the problem). Also, try to export the example to LaTeX, look for differences between ERT and math-inset. Günter -- -- Ehud Kaplan, Ph.D. Visiting professor Dept. of Philosophy & History of Science Charles University, Prague & the National Institute of Mental Health, Topolová 748, Klecany Czechia --- Jules and Doris Stein Research to Prevent Blindness Professor Director, Center of Excellence for Computational & System neuroscience, The Friedman Brain Institute, MSSM Director, The laboratory of Visual & Computational Neuroscience Depts. of Neuroscience, Ophthalmology, Chemical & Structural Biology Icahn school of medicine at Mount Sinai One Gustave Levy Place New York, NY, 10029 USA
Re: Using new enumerate environment without ERT
On Fri, Apr 26, 2019 at 9:39 PM Paul A. Rubin wrote: > > > Suppose that I have created a new enumerate-like enumerate, say > > xenumerate. How can I use it from inside LyX without recourse to ERT? > > > A couple of possibilities come to mind. If you want to use the new > version exclusively (and not use good old "enumerate"), you could > redefine the enumerate environment itself. Assuming you want xenumerate > to coexist with enumerate, you can define a layout for it, either in the > Local Layout portion of the document settings (if you only want it for > one document) or in a module file installed in your local layouts directory. > > Guessing that you want the last one (i.e., add this along side regular > enumerations and make it available to any document that wants it), I > would suggest looking at /usr/share/lyx/layouts/stdlists.inc for > inspiration. (That's the Linux path; on other OSes, your path may > differ.) Look for the section that begins "Style Enumerate" and copy it > to your local module file (which will also need the proper header > stuff). Change the first line of the style to "Style Xenumerate" (or > whatever), change the LatexName entry to "xenumerate", and see if > anything else needs tweaking (quite possibly not). > > Help > Customization has lots of details about creating your own modules > and paragraph styles. Note that you will have to expressly include the > module in any document where you want to use the style. (You could hack > stdlists.inc itself, but then you would need to repeat the hack any time > an upgrade/reinstallation overwrote /usr/share/lyx/layouts.) Thanks, Paul, for your very valuable help! I am going now to ponder about your suggestions and choose the one that fits best my needs. Paul
Re: Using new enumerate environment without ERT
On 4/26/19 4:16 PM, Paul Smith wrote: Dear All, Suppose that I have created a new enumerate-like enumerate, say xenumerate. How can I use it from inside LyX without recourse to ERT? Thanks in advance, Paul A couple of possibilities come to mind. If you want to use the new version exclusively (and not use good old "enumerate"), you could redefine the enumerate environment itself. Assuming you want xenumerate to coexist with enumerate, you can define a layout for it, either in the Local Layout portion of the document settings (if you only want it for one document) or in a module file installed in your local layouts directory. Guessing that you want the last one (i.e., add this along side regular enumerations and make it available to any document that wants it), I would suggest looking at /usr/share/lyx/layouts/stdlists.inc for inspiration. (That's the Linux path; on other OSes, your path may differ.) Look for the section that begins "Style Enumerate" and copy it to your local module file (which will also need the proper header stuff). Change the first line of the style to "Style Xenumerate" (or whatever), change the LatexName entry to "xenumerate", and see if anything else needs tweaking (quite possibly not). Help > Customization has lots of details about creating your own modules and paragraph styles. Note that you will have to expressly include the module in any document where you want to use the style. (You could hack stdlists.inc itself, but then you would need to repeat the hack any time an upgrade/reinstallation overwrote /usr/share/lyx/layouts.) Paul (the original one)
Using new enumerate environment without ERT
Dear All, Suppose that I have created a new enumerate-like enumerate, say xenumerate. How can I use it from inside LyX without recourse to ERT? Thanks in advance, Paul
Re: No Integrals?
On 4/25/19 11:48 PM, UD Kap wrote: I am sure I am doing something REALLY silly, but my Lyx (2.3.2, running under Linux Mint-XFCE) refuses to show integrals, pi, etc. Instead, it shows some other symbols (O with an accent for integral, bold letter P for \pi, etc.). Latex works fine-- if I use ERT in Lyx or Texworks without Lyx everything is correct, but not if I Insert an equation into Lyx. Where did I screw up? Thanks-- Ehud Kaplan Did you compile it yourself, install from the Canonical repository, or install from Liviu's PPA (which I recommend; the Canonical repo tends to lag behind the current release)? If you installed from a repo, did you install the lyx-common and fonts-lyx packages as well as the lyx package? Paul
Re: Exporting ePub / XML: always SIGSEV
Dear Anders, thank you so much! I have now found a possibility to use ePub. It is still not perfect and up to now is not useful for publishing etc., but for private use it is fine. The following seems to work for me: export–LyXhtml (here LyX is not getting a SIGSEV) then I convert the XHTML-file in Calibre to ePub Calibre is really extremely useful… I think I will try a little bit around with LyX and Calibre in the next time, but for the moment this works for me. All best Jess Am 25. Apr. 2019, 21:53 +0200 schrieb Anders Ekberg : > On 25 Apr 2019, at 21:36, jezZiFeR wrote: > > > > Hello Anders, > > > > thanks a lot! This sounds good, but I do normally only use LyX and run into > > new problems. First I tried several possibilities to export to TeX is with > > also with »weitere Formate und Optionen« (more formats and options) – here > > it worked. In all other cases (file – export – LaTeX (plain) or export – > > export as – LaTeX (normal) or export – export as – LaTeX (XeTeX)) I have > > got a SIGSEV-signal again. > > > > Well, then I opened the TeX-file in TeXShop (I dont have TeX Studio). In > > the prefs there is no build, and I did not know ho to continue from here. > > Then I just tried: > > > > export – XML text > > > > This produced an XML-file. I do not know if the file would work, because I > > do not know how to continue from here. Did Could I also use calibre for > > converting from XML to ePub? > > > > Thanks, best > > Jess > > Looks like you have a problem with your installation. I would try to > reinstall (and if problems remain to a Tools > Reconfigure and open Terminal > and run sudo texhash). > Anyway, to your question: Calibre is free to download, so you can download it > and then add the xml-file to Calibre (Add book…) and then convert to EPUB > (Convert books…). If it works or not should depend on the status the > XML-file, but that is outside my knowledge (I was just happy when the recipe > I posted worked ;-) > > All the best! > Anders >
Re: install lyx2.3.2; was: Re: figure.pdf is not shown in document
On Fri, Apr 26, 2019 at 09:35:28AM +0200, Wolfgang Engelmann wrote: > I am not sure about the procedure to download lyx 2.3.2 from > > https://packages.debian.org/stable-backports/source/lyx > > Should I first download qtbase5-dev (>=5.6.0) from Other Packages > related to lyx and what does > > * build-depends > > * build-depends-indep > > mean? What else is recommended for downloading and is it done before > or after lyx download? I thought that we already solved this? https://www.mail-archive.com/lyx-users@lists.lyx.org/msg108958.html Pavel
Re: One more thing about LyX compile speed
On Fri, 26 Apr 2019 07:00:16 + Baris Erkus wrote: > On 25-Apr-19 2:55 PM, Steve Litt wrote: > > Hi all, > > > > My 377 page "Troubleshooting Techniques of the Successful > > Technologist", compiled from a shellscript that starts by adding > > customization material and ends by displaying the finished PDF, > > takes 18 seconds on my 16GB RAM, AMD A6-6400K APU with Radeon(tm) HD > > Graphics, dual core at 3.9Ghz. > > > > This document consists of one LyX file. I've always used one LyX > > file and never a master/children document setup. The reasons I > > never went master/children are: > > > > 1. At the >500 page docs I do, a single file compiles well and > > presents no problems with viewing or editing. > > > > 2. I don't split books between authors. > > > > 3. During the many years I've been on this list, I've seen a heck > > of a lot of people posting strange problems with master/children > > document setups. > > > > I don't know whether compiling single file would be significantly > > faster, significantly slower, or for practical purposes equal to > > master/children. But I imagine it would take about 1/2 hour to find > > out, simply by copying the master to a different filename, and then > > replacing each child reference with that child's LyX text. > > > > Doing it this way leaves the original master/children version > > untouched, so if there's no difference it can continue to be used. > > If the one-file method is significantly faster, a regression test > > and a few renames enable the one-file method to be used into the > > future, with the master/children as a backup. > > > > SteveT > > I wonder the content of the document. Do you have many equations, Zero. > figures, Ten or so. > cross-references, A few. Plus a very extensive index. > citations etc? I don't remember, but certainly less than ten. > Do you turn the instant > preview on? No. SteveT
Re: One more thing about LyX compile speed
On Thu, 25 Apr 2019 21:30:54 - (UTC) Guenter Milde wrote: > On 2019-04-25, Steve Litt wrote: > > Hi all, > > > My 377 page "Troubleshooting Techniques of the Successful > > Technologist", compiled from a shellscript that starts by adding > > customization material and ends by displaying the finished PDF, > > takes 18 seconds on my 16GB RAM, AMD A6-6400K APU with Radeon(tm) HD > > Graphics, dual core at 3.9Ghz. > > I suppose you don't use LuaTeX. No. It turns out that some time in the past, I changed my shellscript to do: lyx --export pdf4 $1.lyx A look into configure.py indicates that pdf4 means Xetex, and pdf5 means LuaTeX. So I changed between pdf4 and pdf5 a few times, and it takes about 15.5 seconds for pdf4, and 24 seconds for pdf5 (LuaTeX). My shellscript does more than just export from LyX. It first puts customer info into the LyX file itself, then it compiles LyX to PDF, then it checks the PDF metadata to make sure everything's OK, and then it displays the PDF file, finishing after I quit out of mupdf. SteveT
Re: Exporting ePub / XML: always SIGSEV
Dear Stephan, thank you, I continue finding workarounds, at least this now only happens if I try to export via »export as«. The other possibilities seem to work though. All best Jess Am 26. Apr. 2019, 10:52 +0200 schrieb Stephan Witt : > Am 26.04.2019 um 10:28 schrieb jezZiFeR : > > > > Dear Stephan, > > > > hm, now I have got a SIGSEV-signal again and could reproduce it every time > > I use the dialogue with »export as«, like this: > > > > file–export–export as > > > > I get the message, that there are no information to export to the chosen > > format: > > »Keine Informationen vorhanden, um das Format HTML zu exportieren.« > > and the SIGSEV-error-message. So this time I could send the stack trace, > > see below. > > Dear Jess, > > thank you for it. Of course it looks like garbage for mere mortal people. :) at least i could find the lyx–frontend–action–action in line 6… :) > > If I try to interpret it I can see in line (6) our code is involved the last > time before the crash. Here the method named lyx::frontend::Action::action is > called and this method does nearly nothing except calling some configured > method indirectly. A crash here means the internal memory structures of the > running LyX got corrupted at some point in time before. Unfortunately these > things happen unnoticed at the time the code to blame is executed. Probably > there is some memory passed back to the OS too early. > > So, I don’t have a solution for this crash. But it’s almost sure it’s > unrelated with the availability of the export function. > > Best regards, > Stephan > > > > > Thanks in advance, all best > > Jess > > > > > > > > — > > > > ( 1) 1 lyx 0x00010560d5d6 > > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > > : 1 lyx 0x00010560d5d6 > > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > > + 199 > > ( 2) 2 lyx 0x00010560d9e1 > > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > > : 2 lyx 0x00010560d9e1 > > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > > + 135 > > ( 3) 3 lyx 0x0001053a71ce _ZN3lyxL13error_handlerEi : 3 lyx > > 0x0001053a71ce _ZN3lyxL13error_handlerEi + 603 > > ( 4) 4 libsystem_platform.dylib 0x7fff5d488b3d _sigtramp : 4 > > libsystem_platform.dylib 0x7fff5d488b3d _sigtramp + 29 > > ( 5) 5 libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc : 5 > > libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc + 103 > > ( 6) 6 lyx 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv : 6 lyx > > 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv + 74 > > ( 7) 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : > > 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 > > ( 8) 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE > > : 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE + > > 263 > > ( 9) 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : > > 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 > > ( 10) 10 QtCore 0x000106781ac1 _ZN7QObject5eventEP6QEvent : 10 QtCore > > 0x000106781ac1 _ZN7QObject5eventEP6QEvent + 801 > > ( 11) 11 QtWidgets 0x000106bd7dfd > > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 11 QtWidgets > > 0x000106bd7dfd > > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 301 > > ( 12) 12 QtWidgets 0x000106bd9177 > > _ZN12QApplication6notifyEP7QObjectP6QEvent : 12 QtWidgets > > 0x000106bd9177 _ZN12QApplication6notifyEP7QObjectP6QEvent + 391 > > ( 13) 13 lyx 0x00010561cb6b > > _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 13 lyx > > 0x00010561cb6b > > _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent + 21 > > ( 14) 14 QtCore 0x000106757be4 > > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 14 QtCore > > 0x000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent > > + 164 > > ( 15) 15 QtCore 0x000106758d6b > > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData : > > 15 QtCore 0x000106758d6b > > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + > > 891 > > ( 16) 16 libqcocoa.dylib 0x00010926010e > > _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv : 16 > > libqcocoa.dylib 0x00010926010e > > _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv + 190 > > ( 17) 17 libqcocoa.dylib 0x0001092609d1 > > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv : 17 > > libqcocoa.dylib 0x0001092609d1 > > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv + 33 > > ( 18) 18 CoreFoundation 0x7fff3006d395 > >
Re: Exporting ePub / XML: always SIGSEV
Am 26.04.2019 um 10:28 schrieb jezZiFeR : > > Dear Stephan, > > hm, now I have got a SIGSEV-signal again and could reproduce it every time I > use the dialogue with »export as«, like this: > > file–export–export as > > I get the message, that there are no information to export to the chosen > format: > »Keine Informationen vorhanden, um das Format HTML zu exportieren.« > and the SIGSEV-error-message. So this time I could send the stack trace, see > below. Dear Jess, thank you for it. Of course it looks like garbage for mere mortal people. If I try to interpret it I can see in line (6) our code is involved the last time before the crash. Here the method named lyx::frontend::Action::action is called and this method does nearly nothing except calling some configured method indirectly. A crash here means the internal memory structures of the running LyX got corrupted at some point in time before. Unfortunately these things happen unnoticed at the time the code to blame is executed. Probably there is some memory passed back to the OS too early. So, I don’t have a solution for this crash. But it’s almost sure it’s unrelated with the availability of the export function. Best regards, Stephan > > Thanks in advance, all best > Jess > > > > — > > ( 1) 1 lyx 0x00010560d5d6 > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > : 1 lyx 0x00010560d5d6 > _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > + 199 > ( 2) 2 lyx 0x00010560d9e1 > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > : 2 lyx 0x00010560d9e1 > _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b > + 135 > ( 3) 3 lyx 0x0001053a71ce _ZN3lyxL13error_handlerEi : 3 lyx > 0x0001053a71ce _ZN3lyxL13error_handlerEi + 603 > ( 4) 4 libsystem_platform.dylib 0x7fff5d488b3d _sigtramp : 4 > libsystem_platform.dylib 0x7fff5d488b3d _sigtramp + 29 > ( 5) 5 libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc : 5 > libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc + 103 > ( 6) 6 lyx 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv : 6 lyx > 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv + 74 > ( 7) 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 7 > QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 > ( 8) 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE : > 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE + 263 > ( 9) 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 9 > QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 > ( 10) 10 QtCore 0x000106781ac1 _ZN7QObject5eventEP6QEvent : 10 QtCore > 0x000106781ac1 _ZN7QObject5eventEP6QEvent + 801 > ( 11) 11 QtWidgets 0x000106bd7dfd > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 11 QtWidgets > 0x000106bd7dfd _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent > + 301 > ( 12) 12 QtWidgets 0x000106bd9177 > _ZN12QApplication6notifyEP7QObjectP6QEvent : 12 QtWidgets 0x000106bd9177 > _ZN12QApplication6notifyEP7QObjectP6QEvent + 391 > ( 13) 13 lyx 0x00010561cb6b > _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 13 lyx > 0x00010561cb6b _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent > + 21 > ( 14) 14 QtCore 0x000106757be4 > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 14 QtCore > 0x000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + > 164 > ( 15) 15 QtCore 0x000106758d6b > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData : 15 > QtCore 0x000106758d6b > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + 891 > ( 16) 16 libqcocoa.dylib 0x00010926010e > _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv : 16 libqcocoa.dylib > 0x00010926010e _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv + > 190 > ( 17) 17 libqcocoa.dylib 0x0001092609d1 > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv : 17 > libqcocoa.dylib 0x0001092609d1 > _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv + 33 > ( 18) 18 CoreFoundation 0x7fff3006d395 > __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ : 18 > CoreFoundation 0x7fff3006d395 > __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 > ( 19) 19 CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 : 19 > CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 + 108 > ( 20) 20 CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 : 20 > CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 + 195 > ( 21) 21 CoreFoundation 0x7fff3005037a __CFRunLoopRun : 21 CoreFoundation > 0x7fff3005037a
Re: Quicker build
On 25/04/2019 16:12, Pavel Sanda wrote: On Sat, Apr 20, 2019 at 03:51:11PM +0200, Daniel wrote: I have already tried to only compile parts of it but there was not much difference. If you don't mind sharing it, you could take *one* part which takes lot of time, anonymize it little bit via buffer-anonymize lfun and show it to us, I am willing to have a look and test whether time on more decent machine actually helps or it's lyx speed problem. Pavel Thanks for the offer. I have already tested it on a pretty fast MacBook Pro. This brings the compilation time down from 5 minutes to 1.5. Still seems long for a chapter with 35 pages. Unfortunately, I cannot share the document currently, but I will come back to it. It might be also interesting in general what is causing this. I also tried to export the tex file but LyX did not produce code I managed to compile. Daniel
Re: Exporting ePub / XML: always SIGSEV
Dear Stephan, hm, now I have got a SIGSEV-signal again and could reproduce it every time I use the dialogue with »export as«, like this: file–export–export as I get the message, that there are no information to export to the chosen format: »Keine Informationen vorhanden, um das Format HTML zu exportieren.« and the SIGSEV-error-message. So this time I could send the stack trace, see below. Thanks in advance, all best Jess — ( 1) 1 lyx 0x00010560d5d6 _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b : 1 lyx 0x00010560d5d6 _ZN3lyx8frontend5Alert7doErrorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b + 199 ( 2) 2 lyx 0x00010560d9e1 _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b : 2 lyx 0x00010560d9e1 _ZN3lyx8frontend5Alert5errorERKNSt3__112basic_stringIwNS2_11char_traitsIwEENS2_9allocatorIwSA_b + 135 ( 3) 3 lyx 0x0001053a71ce _ZN3lyxL13error_handlerEi : 3 lyx 0x0001053a71ce _ZN3lyxL13error_handlerEi + 603 ( 4) 4 libsystem_platform.dylib 0x7fff5d488b3d _sigtramp : 4 libsystem_platform.dylib 0x7fff5d488b3d _sigtramp + 29 ( 5) 5 libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc : 5 libsystem_malloc.dylib 0x7fff5d44c807 malloc_zone_malloc + 103 ( 6) 6 lyx 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv : 6 lyx 0x0001055f60aa _ZN3lyx8frontend6Action6actionEv + 74 ( 7) 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 7 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 ( 8) 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE : 8 QtWidgets 0x000106bce457 _ZN7QAction8activateENS_11ActionEventE + 263 ( 9) 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv : 9 QtCore 0x000106789ab9 _ZN11QMetaObject8activateEP7QObjectiiPPv + 3113 ( 10) 10 QtCore 0x000106781ac1 _ZN7QObject5eventEP6QEvent : 10 QtCore 0x000106781ac1 _ZN7QObject5eventEP6QEvent + 801 ( 11) 11 QtWidgets 0x000106bd7dfd _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent : 11 QtWidgets 0x000106bd7dfd _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 301 ( 12) 12 QtWidgets 0x000106bd9177 _ZN12QApplication6notifyEP7QObjectP6QEvent : 12 QtWidgets 0x000106bd9177 _ZN12QApplication6notifyEP7QObjectP6QEvent + 391 ( 13) 13 lyx 0x00010561cb6b _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent : 13 lyx 0x00010561cb6b _ZN3lyx8frontend14GuiApplication6notifyEP7QObjectP6QEvent + 21 ( 14) 14 QtCore 0x000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent : 14 QtCore 0x000106757be4 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 164 ( 15) 15 QtCore 0x000106758d6b _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData : 15 QtCore 0x000106758d6b _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData + 891 ( 16) 16 libqcocoa.dylib 0x00010926010e _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv : 16 libqcocoa.dylib 0x00010926010e _ZN28QCocoaEventDispatcherPrivate19processPostedEventsEv + 190 ( 17) 17 libqcocoa.dylib 0x0001092609d1 _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv : 17 libqcocoa.dylib 0x0001092609d1 _ZN28QCocoaEventDispatcherPrivate26postedEventsSourceCallbackEPv + 33 ( 18) 18 CoreFoundation 0x7fff3006d395 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ : 18 CoreFoundation 0x7fff3006d395 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 ( 19) 19 CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 : 19 CoreFoundation 0x7fff3006d33b __CFRunLoopDoSource0 + 108 ( 20) 20 CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 : 20 CoreFoundation 0x7fff30050dd1 __CFRunLoopDoSources0 + 195 ( 21) 21 CoreFoundation 0x7fff3005037a __CFRunLoopRun : 21 CoreFoundation 0x7fff3005037a __CFRunLoopRun + 1219 ( 22) 22 CoreFoundation 0x7fff3004fc64 CFRunLoopRunSpecific : 22 CoreFoundation 0x7fff3004fc64 CFRunLoopRunSpecific + 463 ( 23) 23 HIToolbox 0x7fff2f2e6ab5 RunCurrentEventLoopInMode : 23 HIToolbox 0x7fff2f2e6ab5 RunCurrentEventLoopInMode + 293 ( 24) 24 HIToolbox 0x7fff2f2e66f4 ReceiveNextEventCommon : 24 HIToolbox 0x7fff2f2e66f4 ReceiveNextEventCommon + 371 ( 25) 25 HIToolbox 0x7fff2f2e6568 _BlockUntilNextEventMatchingListInModeWithFilter : 25 HIToolbox 0x7fff2f2e6568 _BlockUntilNextEventMatchingListInModeWithFilter + 64 ( 26) 26 AppKit 0x7fff2d5a1363 _DPSNextEvent : 26 AppKit 0x7fff2d5a1363 _DPSNextEvent + 997 ( 27) 27 AppKit 0x7fff2d5a0102 -[NSApplication: 27 AppKit 0x7fff2d5a0102 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362 ( 28) 28 AppKit 0x7fff2d59a165 -[NSApplication run] : 28 AppKit 0x7fff2d59a165 -[NSApplication run] + 699
Re: No Integrals?
On Fri, Apr 26, 2019 at 07:46:00AM -, Guenter Milde wrote: > On 2019-04-26, UD Kap wrote: > > I am sure I am doing something REALLY silly, but my Lyx (2.3.2, running > > under Linux Mint-XFCE) refuses to show integrals, pi, etc. > > Instead, it shows some other symbols (O with an accent for integral, > > bold letter P for \pi, etc.). > > Wrong font or wrong font encoding. More precisely, do you see some font files in /usr/share/fonts/truetype/lyx/ ? Pavel
Re: No Integrals?
On 2019-04-26, UD Kap wrote: > I am sure I am doing something REALLY silly, but my Lyx (2.3.2, running > under Linux Mint-XFCE) refuses to show integrals, pi, etc. > Instead, it shows some other symbols (O with an accent for integral, > bold letter P for \pi, etc.). Wrong font or wrong font encoding. > Latex works fine-- if I use ERT in Lyx > or Texworks without Lyx everything is correct, but not if I Insert an > equation into Lyx. Is this on screen or in the output? > Where did I screw up? Hard to tell without more info: * if it is on screen: what is your GUI font? * if it is in the output, give a minimal example (very samll lyx file that shows the problem). Also, try to export the example to LaTeX, look for differences between ERT and math-inset. Günter
install lyx2.3.2; was: Re: figure.pdf is not shown in document
I just noted that I have installed already the new qt5 version, but it is not shown in Lyx. How do I make Lyx to recognize it? Wolfgang The short answer: you can't. Either you download a qt5-lyx-version or build own from source. Switching between qt4 and qt5 is not possible. Kornel I am not sure about the procedure to download lyx 2.3.2 from https://packages.debian.org/stable-backports/source/lyx Should I first download qtbase5-dev (>=5.6.0) from Other Packages related to lyx and what does * build-depends * build-depends-indep mean? What else is recommended for downloading and is it done before or after lyx download? Wolfgang
Re: One more thing about LyX compile speed
On 25-Apr-19 2:55 PM, Steve Litt wrote: > Hi all, > > My 377 page "Troubleshooting Techniques of the Successful > Technologist", compiled from a shellscript that starts by adding > customization material and ends by displaying the finished PDF, takes > 18 seconds on my 16GB RAM, AMD A6-6400K APU with Radeon(tm) HD > Graphics, dual core at 3.9Ghz. > > This document consists of one LyX file. I've always used one LyX file > and never a master/children document setup. The reasons I never went > master/children are: > > 1. At the >500 page docs I do, a single file compiles well and presents > no problems with viewing or editing. > > 2. I don't split books between authors. > > 3. During the many years I've been on this list, I've seen a heck of a > lot of people posting strange problems with master/children document > setups. > > I don't know whether compiling single file would be significantly > faster, significantly slower, or for practical purposes equal to > master/children. But I imagine it would take about 1/2 hour to find > out, simply by copying the master to a different filename, and then > replacing each child reference with that child's LyX text. > > Doing it this way leaves the original master/children version > untouched, so if there's no difference it can continue to be used. If > the one-file method is significantly faster, a regression test and a > few renames enable the one-file method to be used into the future, with > the master/children as a backup. > > SteveT I wonder the content of the document. Do you have many equations, figures, cross-references, citations etc? Do you turn the instant preview on? -- ↓↓ Please bottom-post. Start your reply here:
