Re: Bug while cutting rows of a table
Le 19/05/2024 à 19:14, emile a écrit : On several occasions I have encountered a LyX2.4R4 crash when trying to delete several consecutive rows from a table, either under Windows or Linux. I have reproduced this phenomenon on the empty table attached. Hello Émile, Can you describe precisely what you do to obtain a crash? I tried a bit, but I am probably not doing the right things. JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Bug while cutting rows of a table
On several occasions I have encountered a LyX2.4R4 crash when trying to delete several consecutive rows from a table, either under Windows or Linux. I have reproduced this phenomenon on the empty table attached. BugLyX2.4.lyx Description: application/lyx -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
bug tracker registration
Greetings! I tried to get in the bug tracking as I usually do with many other applications but Lyx BTS looks hopeless. No registration link. Even the IRC is so silent, people hanging there do not answer. What's the normal/usual scenario of interaction with users of LyX? Best regards, -- Ildar Mulyukov, (ΙΧΘΥΣ) child of God email: ildar.mulyu...@gmail.com matrix: @ildar:matrix.org blog: http://johan-notes.blogspot.com/ -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing + bits and pieces
On 4/13/24 03:00, Bernt Lie wrote: So far,... * I greatly appreciate that you have not changed the main parts of the user interface. I hate it when developers come out with a new version of a tool, and the user doesn't recognize where the menus are, etc. I think it's fair to say that we do, too. It's our policy to change such things only when there is a clear reason to do so, and consensus among the developers, at least. * These are the main things I have had time to notice in some 3 days, while converting a large portion of my key documents from v. 2.3.x to v. 2.4 -- As a person who combines text with loads of math and computer code... * The Program Listing settings --- --> Do I set them individually every time I insert a program listing? --> Or are they document settings, so that if I change one setting (e.g., font setting), then this takes precedence for the entire document? You can make global settings in Document> Settings> Listings. Also, I'm using a couple of computer languages that are not supported by Program Listing... * Modelica (for specifying mathematical models) * Julia Is there an ASCII file where it is possible to add specifications for more computer languages so that they show up in the Program Listing settings? Unfortunately, that is hard-coded. It would make a lot of sense for it not to be, but be configurable, but that would take some doing (though I doubt it would be hard to do). But it would be a format change, so not doable until 2.5. But please do file an enhancement request if you wish. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
RE: LyX 2.4.0 RC4 - bug? Abstract headline is missing + bits and pieces
A difference - perhaps -- between a missing Abstract label and the Chapter label in *LyX* is that sections headings are quite big compared to the standard text, so it is easy to see the difference. While the abstract text font is only marginally smaller than the standard text font, so it is more difficult to see what it is. *If* one sets "abstract=on" to enforce "Abstract" to be printed in the PDF file, it would perhaps be natural if this text also shows up in LyX. -- Anyways, this is not a major problem -- I can always switch to the standard article style. -- Thanks a lot for your great job with creating v. 2.4. I really appreciate all the work you have put into it, and look forward to start reading the manuals. Although I've used LyX for some 10 years or so, I think it will be useful to re-read the documentation to better familiarize myself with what is new. So far,... * I greatly appreciate that you have not changed the main parts of the user interface. I hate it when developers come out with a new version of a tool, and the user doesn't recognize where the menus are, etc. * I have already used the improved system for finding missing citations and broken references. * The search system looks improved. * These are the main things I have had time to notice in some 3 days, while converting a large portion of my key documents from v. 2.3.x to v. 2.4 -- As a person who combines text with loads of math and computer code... * The Program Listing settings --- --> Do I set them individually every time I insert a program listing? --> Or are they document settings, so that if I change one setting (e.g., font setting), then this takes precedence for the entire document? --> The above question is related to how to keep consistency in listings... Also, I'm using a couple of computer languages that are not supported by Program Listing... * Modelica (for specifying mathematical models) * Julia Is there an ASCII file where it is possible to add specifications for more computer languages so that they show up in the Program Listing settings? -Original Message- From: lyx-users On Behalf Of Richard Kimberly Heck Sent: Friday, April 12, 2024 10:02 PM To: Herbert Voss ; lyx-users@lists.lyx.org Subject: Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing On 4/12/24 12:42, Herbert Voss wrote: > Am 12.04.24 um 13:41 schrieb Bernt Lie via lyx-users: >> Aha! It only adds "Abstract" to the PDF file when using KOMA-script, >> not in the LyX editor itself! >> >> For the Standard Article style, "Abstract" is inserted into the LyX >> editor by default. I find that clarifying, and it would be nice if >> the same happened when using KOMA-script. > > It is easy to add the abstract part into the LyX layout file of the > scrartcl class or creating an own layout file. For some reason, scrclass.inc explicitly removes the heading: Input stdstruct.inc Style Abstract LabelType No_Label End If we're agreed that's wrong, it's easy enough to fix. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Am Freitag, dem 12.04.2024 um 16:02 -0400 schrieb Richard Kimberly Heck: > For some reason, scrclass.inc explicitly removes the heading: The reason is to indicate on the output. That's intentional. For the same reason, we remove the chapter labels in KOMA layouts. -- Jürgen -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
On 4/12/24 12:42, Herbert Voss wrote: Am 12.04.24 um 13:41 schrieb Bernt Lie via lyx-users: Aha! It only adds "Abstract" to the PDF file when using KOMA-script, not in the LyX editor itself! For the Standard Article style, "Abstract" is inserted into the LyX editor by default. I find that clarifying, and it would be nice if the same happened when using KOMA-script. It is easy to add the abstract part into the LyX layout file of the scrartcl class or creating an own layout file. For some reason, scrclass.inc explicitly removes the heading: Input stdstruct.inc Style Abstract LabelType No_Label End If we're agreed that's wrong, it's easy enough to fix. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Am 12.04.24 um 13:41 schrieb Bernt Lie via lyx-users: Aha! It only adds "Abstract" to the PDF file when using KOMA-script, not in the LyX editor itself! For the Standard Article style, "Abstract" is inserted into the LyX editor by default. I find that clarifying, and it would be nice if the same happened when using KOMA-script. It is easy to add the abstract part into the LyX layout file of the scrartcl class or creating an own layout file. Herbert -Original Message- From: lyx-users On Behalf Of José Matos Sent: Friday, April 12, 2024 1:02 PM To: lyx-users@lists.lyx.org Subject: Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing On Fri, 2024-04-12 at 09:57 +, Bernt Lie via lyx-users wrote: Thanks. I have tried with inserting the text “abstract=on” (with and withough prepending/appending it with “), but this has no effect. Note that the abstract=on option only changes the (pdf) output, it does not change how the document looks in lyx. -- José Abílio -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
On Fri, 12 Apr 2024, José Matos wrote: So the question is if the label should be there for consistency. I am inclined to say yes but I have no strong feelings about this. :-) On 2.3.7.1 The word "Abstract" appears on the LyX screen when the document is scrreport (KOMA-Script Report) and on the PDF (pdflatex) but only in the body text font and left-aligned. It used to be in a section font and centered. HTH, Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Am Freitag, dem 12.04.2024 um 12:27 + schrieb Bernt Lie: > As far as I know, KOMA is independent of LyX. So I don't understand > why inserting the label "Abstract" in the LyX *editor* can be seen as > overriding KOMA's default settings. Well, it indicates what people can expect in the output (at least by default) > At least not if the user inserts the command "abstract=on" in the > settings. That's not possible. -- Jürgen -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
RE: LyX 2.4.0 RC4 - bug? Abstract headline is missing
As far as I know, KOMA is independent of LyX. So I don't understand why inserting the label "Abstract" in the LyX *editor* can be seen as overriding KOMA's default settings. At least not if the user inserts the command "abstract=on" in the settings. -Original Message- From: lyx-users On Behalf Of Jürgen Spitzmüller Sent: Friday, April 12, 2024 1:52 PM To: lyx-users@lists.lyx.org Subject: Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing Am Freitag, dem 12.04.2024 um 11:41 + schrieb Bernt Lie via lyx- users: > For the Standard Article style, "Abstract" is inserted into the LyX > editor by default. I find that clarifying, and it would be nice if the > same happened when using KOMA-script. No, we don't want to override KOMA's default settings, which are well rationalized in the manual. -- Jürgen -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Am Freitag, dem 12.04.2024 um 11:41 + schrieb Bernt Lie via lyx- users: > For the Standard Article style, "Abstract" is inserted into the LyX > editor by default. I find that clarifying, and it would be nice if > the same happened when using KOMA-script. No, we don't want to override KOMA's default settings, which are well rationalized in the manual. -- Jürgen -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Am Freitag, dem 12.04.2024 um 09:41 + schrieb Bernt Lie via lyx-
users:
> When I use KOMA script and Article style, and insert an Abstract, the
> headline "Abstract" is not inserted. This is different from previous
> versions, I think??
No, it has been the case for KOMA since a long time (always?)
> Is this a bug?
No. See KOMA script manual, sec. 3.8 and the abstract={on,off} KOMA
script option.
--
Jürgen
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
RE: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Aha! It only adds "Abstract" to the PDF file when using KOMA-script, not in the LyX editor itself! For the Standard Article style, "Abstract" is inserted into the LyX editor by default. I find that clarifying, and it would be nice if the same happened when using KOMA-script. -Original Message- From: lyx-users On Behalf Of José Matos Sent: Friday, April 12, 2024 1:02 PM To: lyx-users@lists.lyx.org Subject: Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing On Fri, 2024-04-12 at 09:57 +, Bernt Lie via lyx-users wrote: > > Thanks. > > I have tried with inserting the text “abstract=on” (with and withough > prepending/appending it with “), but this has no effect. Note that the abstract=on option only changes the (pdf) output, it does not change how the document looks in lyx. -- José Abílio -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
On Fri, 2024-04-12 at 09:57 +, Bernt Lie via lyx-users wrote: > > Thanks. > > I have tried with inserting the text “abstract=on” (with and withough > prepending/appending it with “), but this has no effect. Note that the abstract=on option only changes the (pdf) output, it does not change how the document looks in lyx. -- José Abílio -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Am 12.04.24 um 11:57 schrieb Bernt Lie: Thanks. I have tried with inserting the text “abstract=on” (with and withough prepending/appending it with “), but this has no effect. no problem here ... Used File->new, then Document->Settings abd abstract=on. I have nothing in the added into the preamble. Herbert -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
RE: LyX 2.4.0 RC4 - bug? Abstract headline is missing
OK -- in 2.3.7, I did not use KOMA script article, but standard LaTeX article. And there the label shows up in my installation. The "problem" to me is that it is not just that the "label" is missing in the LyX editor, but the word "Abstract" does not show up in the pdf file either. -Original Message- From: José Matos Sent: Friday, April 12, 2024 11:55 AM To: Bernt Lie ; lyx-de...@lists.lyx.org; lyx-users Subject: Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing On Fri, 2024-04-12 at 09:41 +, Bernt Lie via lyx-users wrote: > When I use KOMA script and Article style, and insert an Abstract, the > headline "Abstract" is not inserted. This is different from previous > versions, I think?? > > Is this a bug? I tested in 2.3.x and it does not show there as well. So at least the change is not specific to lyx 2.4. If you change to the standard class then the label is there both for 2.3 and 2.4. So the question is if the label should be there for consistency. I am inclined to say yes but I have no strong feelings about this. :-) -- José Abílio -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
RE: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Thanks. I have tried with inserting the text "abstract=on" (with and withough prepending/appending it with "), but this has no effect. [cid:image001.png@01DA8CD0.A6429AC0] -Original Message- From: lyx-users On Behalf Of Herbert Voss Sent: Friday, April 12, 2024 11:50 AM To: lyx-users@lists.lyx.org Subject: Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing Am 12.04.24 um 11:41 schrieb Bernt Lie via lyx-users: > When I use KOMA script and Article style, and insert an Abstract, the > headline "Abstract" is not inserted. This is different from previous > versions, I think?? > > Is this a bug? Use documentclass option "abstract=on" Herbert -- lyx-users mailing list lyx-users@lists.lyx.org<mailto:lyx-users@lists.lyx.org> http://lists.lyx.org/mailman/listinfo/lyx-users -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
On Fri, 2024-04-12 at 09:41 +, Bernt Lie via lyx-users wrote: > When I use KOMA script and Article style, and insert an Abstract, the > headline "Abstract" is not inserted. This is different from previous > versions, I think?? > > Is this a bug? I tested in 2.3.x and it does not show there as well. So at least the change is not specific to lyx 2.4. If you change to the standard class then the label is there both for 2.3 and 2.4. So the question is if the label should be there for consistency. I am inclined to say yes but I have no strong feelings about this. :-) -- José Abílio -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: LyX 2.4.0 RC4 - bug? Abstract headline is missing
Am 12.04.24 um 11:41 schrieb Bernt Lie via lyx-users: When I use KOMA script and Article style, and insert an Abstract, the headline "Abstract" is not inserted. This is different from previous versions, I think?? Is this a bug? Use documentclass option "abstract=on" Herbert -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
LyX 2.4.0 RC4 - bug? Abstract headline is missing
When I use KOMA script and Article style, and insert an Abstract, the headline "Abstract" is not inserted. This is different from previous versions, I think?? Is this a bug? -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unable to use Trac + bug report
On Fri, Mar 15, 2024 at 10:59:02AM -0300, Carlos Pita wrote: > because the current one is really slow, particularly when browsing the > git repository. If you need faster git browsing, there is an alternative here: https://git.lyx.org Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unable to use Trac + bug report
Le 15/03/2024 à 14:59, Carlos Pita a écrit : The looks are ok, I'm an old timer that has used Trac many times in the past, it's a fine tool. Glad to hear you got a new server though, because the current one is really slow, particularly when browsing the git repository. That said, today it's working faster so perhaps it was a temporary issue after all. The server is still a virtual server, but now we have two separate ones. So it will be a bit faster, but not that much. This does not look good indeed. I encourage you to create a bug report when this becomes possible again so that the issue does not get forgotten (I cannot investigate this myself, not on macOS). There you go https://www.lyx.org/trac/ticket/13043. Thanks! JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unable to use Trac + bug report
> Our bug tracker is in end-of-life support (old OS, old tracker) and we > had to disable account creation to avoid spam. > > The good news is that we should have a brand new version on a brand new > server (same basic appearance, though) next week. The looks are ok, I'm an old timer that has used Trac many times in the past, it's a fine tool. Glad to hear you got a new server though, because the current one is really slow, particularly when browsing the git repository. That said, today it's working faster so perhaps it was a temporary issue after all. > This does not look good indeed. I encourage you to create a bug report > when this becomes possible again so that the issue does not get > forgotten (I cannot investigate this myself, not on macOS). There you go https://www.lyx.org/trac/ticket/13043. Thanks! -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unable to use Trac + bug report
Le 12/03/2024 à 23:27, Carlos Pita a écrit : Hi, I tried to report a bug after 5 years of having used your bug tracker for the last time and I found that: - I cannot login with my old saved password (that's probably on me) - From the reset password form, I don't get any reset password email (I've tried many times and there is no email in my Spam folder either) - I cannot register, the link sends me to a page that shows "No handler matched request to /register" Hi Carlos, Our bug tracker is in end-of-life support (old OS, old tracker) and we had to disable account creation to avoid spam. The good news is that we should have a brand new version on a brand new server (same basic appearance, though) next week. So I'm reporting the bug here. The tab bar in macOS is not rendering fine, as shown in the attached screenshot. This is for LyX 2.3.7 and macOS Sonoma. OTOH LyX 2.4.0 correctly renders a flat tab bar (IMO better looking). This does not look good indeed. I encourage you to create a bug report when this becomes possible again so that the issue does not get forgotten (I cannot investigate this myself, not on macOS). JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Unable to use Trac + bug report
Carlos Pita said on Tue, 12 Mar 2024 19:27:40 -0300 >Hi, > >I tried to report a bug after 5 years of having used your bug tracker >for the last time and I found that: Bug trackers are where bug reports go to die. On a lot of projects I tried using their bug tracker, and the bug never got addressed because putting in the bug tracker is like sweeping it under the table. Half of the 50 free softwares I use have bug trackers, and they're all different. I'm expected to learn and remember 25 different bug tracker interfaces. I can't accuse LyX of this because I never submitted a LyX problem to a bug tracker. Bug trackers ALWAYS ask questions that are n/a for the problem being reported, and occasionally you find one that *demands* an answer before letting you go on. When I was the Vimoutliner maintainer, we fixed problems that came in on the mailing list, right away. Either we helped the user get it right, or if it was a bug we fixed it and released. Everyone was happy. The point could be made that our application was rather simple, but a) We had only two developers, both very part time, and b) Maybe that's the point: If the software's too complicated to handle on the mailing list, maybe it's just too complicated. One time I put on the mailing list a way to make the first new paragraph non-indented, the rest indented, in HTML, so in the HTML export they didn't need to do that mickey-mouse technique of two different paragraph styles, one for the first paragraph and the other for the rest. By the way, my solution was about 5 lines of CSS. Did anyone thank me? No. They said "put it on the bug tracker." I said "I'm not familiar with the bug tracker, can one of you do it?" The response I got was that I was a lazy free-rider. Bug trackers really do suck. SteveT Steve Litt Autumn 2023 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Unable to use Trac + bug report
Hi, I tried to report a bug after 5 years of having used your bug tracker for the last time and I found that: - I cannot login with my old saved password (that's probably on me) - From the reset password form, I don't get any reset password email (I've tried many times and there is no email in my Spam folder either) - I cannot register, the link sends me to a page that shows "No handler matched request to /register" So I'm reporting the bug here. The tab bar in macOS is not rendering fine, as shown in the attached screenshot. This is for LyX 2.3.7 and macOS Sonoma. OTOH LyX 2.4.0 correctly renders a flat tab bar (IMO better looking). Best regards, Carlos -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Opening documents from a link in Libreoffice (OSX Bug?)
On 3/1/24 05:32, Daniel CLEMENT via lyx-users wrote: Hello, I am using LyX 2.3.7 under the latest MacOS. I have a Libreoffice spreadsheet with many links to LyX documents. When I click on such a link, it does launch LyX and the associated document. But several functions (Python-related, I guess) are missing: shortcuts and (more importantly) lyx2lyx. Granted, if I open a document from a link, it’s just to have a quick look, not for heavy editing. But if the document is old, lyx2lyx fails and the file just won’t open (whereas it opens quite nicely if I open it from within LyX). I hope I’m being clear… IIRC this issue was not present under Linux. Nor does it happen with other file types than LyX. I don’t know what to think. I’m not even sure it has to do with LyX (maybe Libreoffice trying to enforce its own Python flavour?), but I thought as well to report it. It probably does have something to do with the environment under which LyX is running in this case. I'm cc'ing our Mac person. Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Bug report: wrong unicode conversion from JabRef
Herbert Voss identified part of my issue of an accented character in a
bibiography citation is the bib_key. Removing the ã from the bib_key and
leaving it in the first author's name produced the attached citation image.
In the doc's preamble I inserted:
\usepackage{newunicodechar}
\newunicodechar{ã}{\~{a}}
but the resulting citation was still wrong.
Can this be fixed?
TIA,
Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
bug-report
Hi everybody, hope this is an ok channel to report this... I might have found a bug, which I described here: https://tex.stackexchange.com/q/698031/72037 (also see my comments to the accepted answer for reproducibility) Best, Leo -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug Report - 2.3.7
Lyx 2.3.6.1 on Windows 11 here, no problem. *Dr. Julio Rojas Mora* Director del Dpto. de Ing. Informática Universidad Católica de Temuco Campus San Juan Pablo II Rudecindo Ortega 02950 Edif. Biblioteca, 2do Piso, Oficina EB1-213 Temuco, Chile Tlf: +56-45-2205229 El mar, 11 jul 2023 a la(s) 12:39, Richard Kimberly Heck (rikih...@gmail.com) escribió: > On 7/11/23 08:42, Xm Z wrote: > > Latex code \approx cannot be correctly displayed in lyx window, but can be > compiled correctly. Like the plot in the following. > Version: LyX 2.3.7. > [image: image.png] > > This is the mailing list for discussing documentation. I'm transferring > discussion to lyx-users. > > I use \approx sometimes and have not seen this error. What OS? > > Riki > > > -- > lyx-users mailing list > lyx-users@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-users > -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug Report - 2.3.7
On 7/11/23 08:42, Xm Z wrote: Latex code \approx cannot be correctly displayed in lyx window, but can be compiled correctly. Like the plot in the following. Version: LyX 2.3.7. image.png This is the mailing list for discussing documentation. I'm transferring discussion to lyx-users. I use \approx sometimes and have not seen this error. What OS? Riki -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Can you reproduce this bug?
On Tue, Dec 06, 2022 at 10:20:30AM +0100, kzsta...@gmail.com wrote: > > > > -Oorspronkelijk bericht- > > Van: lyx-users Namens Scott Kostyshak > > Verzonden: zondag 4 december 2022 21:39 > > Aan: LyX Users > > Onderwerp: Can you reproduce this bug? > > > > Dear all, > > > > Can you reproduce this bug on your system? > > > > https://www.lyx.org/trac/ticket/12435 > > > > It's helpful to know the type of systems on which it can be reproduced. > > Specifically, it will be helpful to figure out whether the bug only > surfaces on > > certain operating systems, and only with certain configurations. > > > > Here is the recipe to reproduce the bug: > > > > 1. Maximize (non-fullscreen) the window > > 2. Enter Full screen mode > > 3. Exit Full screen. > > > > After step 3, does the LyX window return to the state after step (1)? > > i.e., is the window maximized? > > > > If you try to reproduce it, please state: > > > > 1. Can you reproduce the bug? > > 2. Your operating system and version number (version number is > >especially helpful for macOS users). > > 3. Copy/paste the info from Help > About. > > 1. No. The screen returns to a maximized view. > 2. Windows 11 Pro 22H2, build: 22621.900 > 3. LyX versie 2.3.6.1 > (dinsdag 29 december 2020) > Bibliotheek-map: C:\Program Files\LyX 2.3\Resources\ > Gebruikersmap: ~\AppData\Roaming\LyX2.3\ > Qt-versie (run-time): 5.15.2 > Qt-versie (compile-time): 5.15.2 Thank you all, this information is helpful! I think we've got enough information. I guess it's not the Qt version then, because Wolfgang can reproduce with 5.15.2 and kzstatis cannot reproduce with 5.15.2. It's also not a macOS-specific issue since Wolfgang is on Linux. I'll move discussion to the trac ticket now. Thanks for your help! Scott signature.asc Description: PGP signature -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
RE: Can you reproduce this bug?
> -Oorspronkelijk bericht- > Van: lyx-users Namens Scott Kostyshak > Verzonden: zondag 4 december 2022 21:39 > Aan: LyX Users > Onderwerp: Can you reproduce this bug? > > Dear all, > > Can you reproduce this bug on your system? > > https://www.lyx.org/trac/ticket/12435 > > It's helpful to know the type of systems on which it can be reproduced. > Specifically, it will be helpful to figure out whether the bug only surfaces on > certain operating systems, and only with certain configurations. > > Here is the recipe to reproduce the bug: > > 1. Maximize (non-fullscreen) the window > 2. Enter Full screen mode > 3. Exit Full screen. > > After step 3, does the LyX window return to the state after step (1)? > i.e., is the window maximized? > > If you try to reproduce it, please state: > > 1. Can you reproduce the bug? > 2. Your operating system and version number (version number is >especially helpful for macOS users). > 3. Copy/paste the info from Help > About. 1. No. The screen returns to a maximized view. 2. Windows 11 Pro 22H2, build: 22621.900 3. LyX versie 2.3.6.1 (dinsdag 29 december 2020) Bibliotheek-map: C:\Program Files\LyX 2.3\Resources\ Gebruikersmap: ~\AppData\Roaming\LyX2.3\ Qt-versie (run-time): 5.15.2 Qt-versie (compile-time): 5.15.2 -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Can you reproduce this bug?
On 12/4/22 15:38, Scott Kostyshak wrote: Dear all, Can you reproduce this bug on your system? https://www.lyx.org/trac/ticket/12435 It's helpful to know the type of systems on which it can be reproduced. Specifically, it will be helpful to figure out whether the bug only surfaces on certain operating systems, and only with certain configurations. Here is the recipe to reproduce the bug: 1. Maximize (non-fullscreen) the window 2. Enter Full screen mode 3. Exit Full screen. After step 3, does the LyX window return to the state after step (1)? i.e., is the window maximized? If you try to reproduce it, please state: 1. Can you reproduce the bug? 2. Your operating system and version number (version number is especially helpful for macOS users). 3. Copy/paste the info from Help > About. 1. No. The window is correctly restored as maximized, regardless of whether I use Alt V to get the menu or F11 to exit full screen mode. 2. Linux Mint 21 (MATE). 3. From Help > About: LyX Version 2.3.6 (Friday, November 27, 2020) Library directory: /usr/share/lyx/ User directory: ~/.lyx/ Qt Version (run-time): 5.15.3 Qt Version (compile-time): 5.15.2 Paul -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Can you reproduce this bug?
Am Sonntag, 4. Dezember 2022, 21:38:59 CET schrieb Scott Kostyshak: > Here's my own responses to the 3 questions: > > 1. No. (the window is correctly restored as maximized after 3 for me). > 2. Ubuntu 22.04. > 3. Pasted info is below: > >Version 2.4.0dev >(Sunday, December 4, 2022) > >Built from git commit hash abd69b06 >Qt Version (run-time): 5.15.3 on platform xcb >Qt Version (compile-time): 5.15.3 >Python detected: python3 -tt Scott, 1. I can't reproduce this bug. 2. openSUSE Leap 15.3 3. LyX 2.3.6.1 | Qt 5.12.7 Axel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Can you reproduce this bug?
Am 04.12.22 um 21:38 schrieb Scott Kostyshak: Dear all, Can you reproduce this bug on your system? https://www.lyx.org/trac/ticket/12435 It's helpful to know the type of systems on which it can be reproduced. Specifically, it will be helpful to figure out whether the bug only surfaces on certain operating systems, and only with certain configurations. Here is the recipe to reproduce the bug: 1. Maximize (non-fullscreen) the window 2. Enter Full screen mode 3. Exit Full screen. After step 3, does the LyX window return to the state after step (1)? i.e., is the window maximized? If you try to reproduce it, please state: 1. Can you reproduce the bug? yes 2. Your operating system and version number (version number is especially helpful for macOS users). uname -v #1 SMP Debian 5.10.149-2 (2022-10-21) 3. Copy/paste the info from Help > About. Version 2.4.0dev (not released yet) Built from git commit hash 53ed3dc0 Qt Version (run-time): 5.15.2 on platform xcb Qt Version (compile-time): 5.15.2 Python detected: python3 -tt Wolfgang -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Can you reproduce this bug?
On Sun, Dec 4, 2022 at 1:39 PM Scott Kostyshak wrote: > Dear all, > > Can you reproduce this bug on your system? > > https://www.lyx.org/trac/ticket/12435 > > It's helpful to know the type of systems on which it can be reproduced. > Specifically, it will be helpful to figure out whether the bug only > surfaces on certain operating systems, and only with certain > configurations. > > Here is the recipe to reproduce the bug: > > 1. Maximize (non-fullscreen) the window > 2. Enter Full screen mode > 3. Exit Full screen. > > After step 3, does the LyX window return to the state after step (1)? > i.e., is the window maximized? > > If you try to reproduce it, please state: > > 1. Can you reproduce the bug? > 2. Your operating system and version number (version number is >especially helpful for macOS users). > 3. Copy/paste the info from Help > About. > > > Here's my own responses to the 3 questions: > 1. Somewhat. When I go "full screen" from half-width, I restore correctly. When I go "full screen" from full width, it returns to something like half width (not the previous full width). This is observed with BetterTouchTool running. If I quit it, then both approaches appear to restore correctly. 2. macOS 12.5 3. Version 2.4.0-alpha3 (February 14, 2021) Qt Version (run-time): 5.12.9 Qt Version (compile-time): 5.12.9 Python detected: python3 -tt Hope this helps, Joel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Can you reproduce this bug?
Dear all, Can you reproduce this bug on your system? https://www.lyx.org/trac/ticket/12435 It's helpful to know the type of systems on which it can be reproduced. Specifically, it will be helpful to figure out whether the bug only surfaces on certain operating systems, and only with certain configurations. Here is the recipe to reproduce the bug: 1. Maximize (non-fullscreen) the window 2. Enter Full screen mode 3. Exit Full screen. After step 3, does the LyX window return to the state after step (1)? i.e., is the window maximized? If you try to reproduce it, please state: 1. Can you reproduce the bug? 2. Your operating system and version number (version number is especially helpful for macOS users). 3. Copy/paste the info from Help > About. Here's my own responses to the 3 questions: 1. No. (the window is correctly restored as maximized after 3 for me). 2. Ubuntu 22.04. 3. Pasted info is below: Version 2.4.0dev (Sunday, December 4, 2022) Built from git commit hash abd69b06 Qt Version (run-time): 5.15.3 on platform xcb Qt Version (compile-time): 5.15.3 Python detected: python3 -tt Thanks! Scott signature.asc Description: PGP signature -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug tracker accounts
On Wed, 2022-07-20 at 14:49 +0200, Dr Eberhard Lisse wrote: > > On 15/07/2022 23:16, Steve Litt wrote: > [...] > > Or, how's this for a novel idea: How about discussing bugs on the > > mailing list so that many eyes can effortlessly and immediately peruse > > it and many voices can effortlessly narrow it down. This will weed > > out the "defective user" caused bugs, and will produce a pinpoint > > accurate symptom description for the overworked developer. > [...] > While deliberation on email lists are very helpful that just will not > work for software development, not even in closed shops, but most > certainly not in Open Source projects and large ones such as this. > > el N O T T R U E ! SteveT -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug tracker accounts
While deliberation on email lists are very helpful that just will not work for software development, not even in closed shops, but most certainly not in Open Source projects and large ones such as this. el On 15/07/2022 23:16, Steve Litt wrote: [...] Or, how's this for a novel idea: How about discussing bugs on the mailing list so that many eyes can effortlessly and immediately peruse it and many voices can effortlessly narrow it down. This will weed out the "defective user" caused bugs, and will produce a pinpoint accurate symptom description for the overworked developer. [...] -- To email me replace 'nospam' with 'el' -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug tracker accounts
Le 15/07/2022 à 23:16, Steve Litt a écrit : Or, how's this for a novel idea: How about discussing bugs on the mailing list so that many eyes can effortlessly and immediately peruse it and many voices can effortlessly narrow it down. This will weed out the "defective user" caused bugs, and will produce a pinpoint accurate symptom description for the overworked developer. There are many things that are possible with a bug tracker and not email. For example, a new developer can understand what choices were made 10 years before, and why. But, yes, we do use the mailing list at times to pinpoint bugs. Actually some bugs or even new features just got fixed/implemented this way recently. JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug tracker accounts
Pavel Sanda said on Thu, 14 Jul 2022 01:07:33 +0200 >Dear LyXers, > >we recently suffer massive spam abuse in our bug tracker. For the >moment we disabled automatized account creation and removed approx. >30k fake user accounts. [snip] >If new account needs to be (re)created, please send the request to >mailling list and we'll do it for you until new solution is found >(captcha/migration to different platform). Or, how's this for a novel idea: How about discussing bugs on the mailing list so that many eyes can effortlessly and immediately peruse it and many voices can effortlessly narrow it down. This will weed out the "defective user" caused bugs, and will produce a pinpoint accurate symptom description for the overworked developer. SteveT Steve Litt Summer 2022 featured book: Making Mental Models: Advanced Edition http://www.troubleshooters.com/mmm -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Bug tracker accounts
Dear LyXers, we recently suffer massive spam abuse in our bug tracker. For the moment we disabled automatized account creation and removed approx. 30k fake user accounts. While we tried to avoid removal of legit accounts (by pairing to existing bug reports) some of this work was manual and could possibly lead to inadvertent removal of real user (sorry!). If new account needs to be (re)created, please send the request to mailling list and we'll do it for you until new solution is found (captcha/migration to different platform). Sorry for the inconveniece, Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
On Wed, 15 Dec 2021, Virgil Arrington Jr. via lyx-users wrote: And, then there was my even-older brother-in-law, who always ended his emails with LOL (as in Lots of Love) until my wife asked him what he was always laughing about. Virgil, If he were a reporter/journalist he would have ended his emails with --30--. :-) Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
On 12/15/2021 8:47 AM, Rich Shepard via lyx-users wrote: I don't know about others, but I'm a touch-typist (thanks to the Army decades ago) and I use a laptop-size keyboard with my desktops. That's one reason I prefer to type. And, while many moons ago I objected to the devs that I found nothing evil in typing LaTeX code in the document body so perhaps some other name than Evil Red Text would be appropriate, I learned to just ignore what ERT abbreiated and use it for my convenience. So, *that's* what ERT stands for. I had gathered that it referred to LaTeX code inserted into a LyX document, but I never knew how it got the initials ERT. Echoes of the recent discussion about MWE (it took me a while to figure out how an attached file would earn the acronym MWE). And, then there was my even-older brother-in-law, who always ended his emails with LOL (as in Lots of Love) until my wife asked him what he was always laughing about. Virgil -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
On Wed, 15 Dec 2021, Virgil Arrington Jr. via lyx-users wrote: I do the same, but I think that Rich makes a valid point about using the keyboard vs. the mouse. Virgil, I don't know about others, but I'm a touch-typist (thanks to the Army decades ago) and I use a laptop-size keyboard with my desktops. That's one reason I prefer to type. And, while many moons ago I objected to the devs that I found nothing evil in typing LaTeX code in the document body so perhaps some other name than Evil Red Text would be appropriate, I learned to just ignore what ERT abbreiated and use it for my convenience. And, yes, back in the 1980's I, too, used DOS and WordPerfect regularly. Regards, Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
On 12/15/2021 7:46 AM, Dr Eberhard Lisse via lyx-users wrote: Rich, Steve, that was a rhetorical question of course :-)-O I do however find that whenever I find myself using ERT I always try and look for a LyX way to do it, because I don't like ERT :-)-O I do the same, but I think that Rich makes a valid point about using the keyboard vs. the mouse. In my experience, there are many LyX functions for which it appears the only way to access them is through a mouse (or trackpad, etc.). I'm old enough to remember working with DOS and WordStar style keystroke combinations and I learned to fly on the keyboard. Even when learning GUIs in the early days of Windows, I always looked for keyboard shortcuts as I hated the interruption of taking my fingers off the home row and onto a mouse. This is especially true in a function like word processing that is heavy on typing. I'm always frustrated when I can't easily find a keyboard shortcut for a LyX function, so I can understand why someone might resort to ERT just to avoid interrupting the flow of the work. Virgil -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
Rich, Steve,
that was a rhetorical question of course :-)-O
I do however find that whenever I find myself using ERT I always try and
look for a LyX way to do it, because I don't like ERT :-)-O
I just found out myself, that on the Mac I can just do Option-0 :-)-O
BTW, it should be \textdegree{}
el
On 14/12/2021 22:22, Rich Shepard via lyx-users wrote:
On Tue, 14 Dec 2021, Steve Litt via lyx-users wrote:
Maybe because he didn't know about Insert -> Symbols -> Superscripts.
I didn't know it either, but now I do, and will use it. Thanks for
the information!
I frequently use Insert -> Formatting -> Superscripts (or Subscripts,
but just type ctrl-l and insert \textdegree because a) I don't need to
move my hands from the keyboard and use the trackball, and b) I've
used it many times over the past decades.
When there are multiple ways of doing things all work while each of us
prefers one way. Same with OSes, text editors, etc.
Rich
--
To email me replace 'nospam' with 'el'
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
On Tue, 14 Dec 2021, Steve Litt via lyx-users wrote: Maybe because he didn't know about Insert -> Symbols -> Superscripts. I didn't know it either, but now I do, and will use it. Thanks for the information! I frequently use Insert -> Formatting -> Superscripts (or Subscripts, but just type ctrl-l and insert \textdegree because a) I don't need to move my hands from the keyboard and use the trackball, and b) I've used it many times over the past decades. When there are multiple ways of doing things all work while each of us prefers one way. Same with OSes, text editors, etc. Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
Dr Eberhard Lisse via lyx-users said on Tue, 14 Dec 2021 13:53:48 +0200
>Or use curly braces.
>
>But why would you do this with ERT in the first place?
>
>Instead of \textdegree{} I just used the first character from
>
> Insert -> Symbols -> Superscripts
>
>and Subscripts and get ⁰C.
Maybe because he didn't know about Insert -> Symbols -> Superscripts. I
didn't know it either, but now I do, and will use it. Thanks for the
information!
SteveT
Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
Or use curly braces.
But why would you do this with ERT in the first place?
Instead of \textdegree{} I just used the first character from
Insert -> Symbols -> Superscripts
and Subscripts and get ⁰C.
Never mind that this not only was not an MWE. as you not only don't need
the graphic, it also had an absolute path so wasn't found until manually
changed and a number of lines in the Preamble, some of which are even
superfluous during the non MWE run (like the graphicx one)
greetings, el
On 10/12/2021 00:08, Rich Shepard via lyx-users wrote:
On Thu, 9 Dec 2021, Paul A. Rubin via lyx-users wrote:
"For want of a nail the shoe was lost. ..." Here, substitute space
for nail. You need to put a space between the ERT and the letter C.
The error message is because LaTeX thinks you are invoking the
nonexistent command \textdegreeC.
Paul,
Well, shame on me for not seeing that! I've used a space elsewhere in
the document and missed the lack of a space in the figure caption.
Thanks for successfully applying the fresh eyes solution.
Regards,
Rich
--
To email me replace 'nospam' with 'el'
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 [FIXED]
On Thu, 9 Dec 2021, Paul A. Rubin via lyx-users wrote: "For want of a nail the shoe was lost. ..." Here, substitute space for nail. You need to put a space between the ERT and the letter C. The error message is because LaTeX thinks you are invoking the nonexistent command \textdegreeC. Paul, Well, shame on me for not seeing that! I've used a space elsewhere in the document and missed the lack of a space in the figure caption. Thanks for successfully applying the fresh eyes solution. Regards, Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 (fwd)
On 12/9/21 4:36 PM, Rich Shepard via lyx-users wrote: Not sent to list by mistake. -- Forwarded message -- Date: Thu, 9 Dec 2021 13:21:31 -0800 (PST) From: Rich Shepard To: parubi...@gmail.com Subject: Re: Glitch (bug?) in 2.3.6.1 On Thu, 9 Dec 2021, Paul A. Rubin via lyx-users wrote: So methinks an MWE is needed. Paul, et al.: See attached. It produces the error message box here. Rich "For want of a nail the shoe was lost. ..." Here, substitute space for nail. You need to put a space between the ERT and the letter C. The error message is because LaTeX thinks you are invoking the nonexistent command \textdegreeC. Paul -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1
On Thu, 9 Dec 2021, Paul A. Rubin via lyx-users wrote: So methinks an MWE is needed. Paul, et al.: Attached is a screenshot of the error message box and caption highlighting. Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1 (fwd)
Not sent to list by mistake.
-- Forwarded message --
Date: Thu, 9 Dec 2021 13:21:31 -0800 (PST)
From: Rich Shepard
To: parubi...@gmail.com
Subject: Re: Glitch (bug?) in 2.3.6.1
On Thu, 9 Dec 2021, Paul A. Rubin via lyx-users wrote:
So methinks an MWE is needed.
Paul, et al.:
See attached. It produces the error message box here.
Rich#LyX 2.3 created this file. For more info see http://www.lyx.org/
\lyxformat 544
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass scrreprt
\begin_preamble
\date{}
%\usepackage{newpxtext}
%\usepackage{newpxmath}
\usepackage{mathpazo}
\usepackage{graphicx,relsize}
\usepackage{scrlayer-scrpage}
\pagestyle{scrheadings}
\lehead{Biological Evaluation}
\rohead{Biological Evaluation}
\refoot{Applied Ecosystem Services, LLC}
\lofoot{Applied Ecosystem Services, LLC}
\automark*{section}
%DeclareNolabel{
% \nolabel{\regexp{[\p{S}\p{Z}\p{C}]+}}
%}
\end_preamble
\options headsepline=on, footsepline=on
\use_default_options true
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding utf8
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\use_microtype false
\use_dash_ligatures true
\graphics default
\default_output_format pdf2
\output_sync 0
\bibtex_command biber mergedate=compact
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize letterpaper
\use_geometry true
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 0
\use_package mathdots 0
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine biblatex-natbib
\cite_engine_type authoryear
\biblatex_bibstyle authoryear
\biblatex_citestyle authoryear
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\use_minted 0
\index Index
\shortcut idx
\color #008000
\end_index
\leftmargin 2cm
\topmargin 4cm
\bottommargin 2cm
\headsep 1.5cm
\secnumdepth 2
\tocdepth 2
\paragraph_separation skip
\defskip medskip
\is_math_indent 0
\math_numbering_side default
\quotes_style english
\dynamic_quotes 0
\papercolumns 1
\papersides 2
\paperpagestyle plain
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Standard
MWE
\begin_inset Float figure
wide false
sideways false
status collapsed
\begin_layout Plain Layout
\align center
\begin_inset Graphics
filename
/home/rshepard/documents/monographs/regulatory-science/npdes-wqbel/images/temperature-all.png
width 75text%
clip
\end_inset
\end_layout
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
\begin_inset CommandInset label
LatexCommand label
name "fig: temp-boxplot"
\end_inset
Water temperature (in
\begin_inset ERT
status open
\begin_layout Plain Layout
\backslash
textdegree
\end_layout
\end_inset
C) at each of the four monitoring locations.
Water temperature greatly affects aquatic biots as well as the rate of
chemical reactions.
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\end_body
\end_document
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1
On Thu, 9 Dec 2021, Herbert Voss via lyx-users wrote: \mu is onyl available in math: start inline mathmode and insert \mu There is also a \textmu for text mode. Herbert, I did change that to inline math. Thanks, Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1
Am 09.12.21 um 21:35 schrieb Paul A. Rubin via lyx-users: On 12/9/21 3:27 PM, Rich Shepard via lyx-users wrote: I've encountered unusual behavior when compiling the document using pdflatex. When I've used an ERT within a float figure's caption lyx highlights the string containing that ERT and pops up an error box which tells me only that there's an error. Closing that error box and repeating the command, ctrl-x/ctrl-h, presents the message that the pdf files's been created in the status bar. In one figure caption I had '\mu' in an ERT box, in the other caption it is '\textdegree' in the box. Since I don't subscribe to the dev's mail list I'm posting this here. It might be a bug, or the error message box and highlighting might be only a distracting glitch. Rich I can't reproduce this (with 2.3.6.1). Putting \textdegree in ERT in the float caption works fine. Putting \mu in ERT predictably does not, but putting it in a math environment works, as does putting $\mu$ in ERT. \mu is onyl available in math: start inline mathmode and insert \mu There is also a \textmu for text mode. Herbert -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1
On 12/9/21 3:27 PM, Rich Shepard via lyx-users wrote: I've encountered unusual behavior when compiling the document using pdflatex. When I've used an ERT within a float figure's caption lyx highlights the string containing that ERT and pops up an error box which tells me only that there's an error. Closing that error box and repeating the command, ctrl-x/ctrl-h, presents the message that the pdf files's been created in the status bar. In one figure caption I had '\mu' in an ERT box, in the other caption it is '\textdegree' in the box. Since I don't subscribe to the dev's mail list I'm posting this here. It might be a bug, or the error message box and highlighting might be only a distracting glitch. Rich I can't reproduce this (with 2.3.6.1). Putting \textdegree in ERT in the float caption works fine. Putting \mu in ERT predictably does not, but putting it in a math environment works, as does putting $\mu$ in ERT. So methinks an MWE is needed. Paul -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Glitch (bug?) in 2.3.6.1
On Thu, 9 Dec 2021, Rich Shepard via lyx-users wrote: Closing that error box and repeating the command, ctrl-x/ctrl-h, presents the message that the pdf files's been created in the status bar. Er, confusing. I should have written, that the comand presents in the status bar the message that the file's been created. Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Glitch (bug?) in 2.3.6.1
I've encountered unusual behavior when compiling the document using pdflatex. When I've used an ERT within a float figure's caption lyx highlights the string containing that ERT and pops up an error box which tells me only that there's an error. Closing that error box and repeating the command, ctrl-x/ctrl-h, presents the message that the pdf files's been created in the status bar. In one figure caption I had '\mu' in an ERT box, in the other caption it is '\textdegree' in the box. Since I don't subscribe to the dev's mail list I'm posting this here. It might be a bug, or the error message box and highlighting might be only a distracting glitch. Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Weird compile result -- bug?
Am Freitag, dem 15.10.2021 um 20:34 +0200 schrieb Herbert Voss: > > I'm not sure what bibtex8 does, but biblatex and biber are a mated > > pair. > > bibtex8 is bibtex for 8bit, but also outdated! Right. But in the seldom case biber is not installed (found) if someone uses biblatex, LyX falls back to bibtex8. This is supposedly what happened in Paul's case. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Weird compile result -- bug?
Am 15.10.21 um 18:40 schrieb Rich Shepard: On Fri, 15 Oct 2021, Paul A. Rubin wrote: So I went to the original document and, in the bibliography settings, changed the processor option from default to bibtex8, and sure enough the original compiled correctly. I'm not sure if this is a bug or something the user is responsible for knowing (it was news to me, but I never use biblatex). So I'm reporting it here to let wiser minds decide. Paul, Thanks for digging further into the issue. I clarify a couple of points because I think the problem is a bug, not a "feature." :-) Biblatex replaced bibtxt a number of years ago, and the application which works on biblatex-formatted bibliographic databases is Biber. In my document the Settings -> Bibliography -> Bibliography Generator Processer is set to biber. I'm not sure what bibtex8 does, but biblatex and biber are a mated pair. bibtex8 is bibtex for 8bit, but also outdated! Herbert -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Weird compile result -- bug?
On Fri, 15 Oct 2021, Rich Shepard wrote: Biblatex replaced bibtxt a number of years ago, and the application which ex, not xt Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Weird compile result -- bug?
On Fri, 15 Oct 2021, Paul A. Rubin wrote: So I went to the original document and, in the bibliography settings, changed the processor option from default to bibtex8, and sure enough the original compiled correctly. I'm not sure if this is a bug or something the user is responsible for knowing (it was news to me, but I never use biblatex). So I'm reporting it here to let wiser minds decide. Paul, Thanks for digging further into the issue. I clarify a couple of points because I think the problem is a bug, not a "feature." :-) Biblatex replaced bibtxt a number of years ago, and the application which works on biblatex-formatted bibliographic databases is Biber. In my document the Settings -> Bibliography -> Bibliography Generator Processer is set to biber. I'm not sure what bibtex8 does, but biblatex and biber are a mated pair. Carpe weekend, Rich -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Auto-Correct and Delimiters Bug
On 12/9/20 10:10 AM, Rudi Gaelzer wrote:
On terça-feira, 8 de dezembro de 2020 20:22:04 -03 you wrote:
> At the moment, the * thing works with paired delimiters, but it only
> changes the first one, which is definitely a bug. It should obviously
> change both. I also don't know how hard that would be.
>
> Riki
>
Indeed. It works separately for "[" and for "]".
It also works separately for "[" and for ")", which is not a bad thing
per se.
About my idea of browsing through the variable-sized delimiters,
should I put it on the wishlist?
Sure. You can also play around with this yourself. There's a file,
autocorrect, that you can find in your LyX system directory. (Here it is
at /usr/share/lyx/autocorrect.) It's just a text file. The part that
controls this behavior looks like:
( * \bigl( \bigl( * \Bigl( \Bigl( * \biggl( \biggl( * \Biggl( \Biggl( *
( ) * \bigl) \bigl) * \Bigl) \Bigl) * \biggl) \biggl) * \Biggl) \Biggl)
* ) The first thing is what's there already; the next is the 'trigger';
the latter is the result. So you could do e.g.
( / [ [ / { { / (
and similarly for the right side, and now slash cycles through delimiter
types. You'd also have to do
\bigl( / \bigl[
etc for the sizes.
I think that if you copy the system autocorrect file to your local LyX
user directory (so, here, I'd put it at $HOME/.lyx/autocorrect), then
LyX will pick use your modified version. (This is generally true with
configuration files.)
I was just looking throguh that file. There's all kinds of cool stuff in
there!
Riki
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Auto-Correct and Delimiters Bug
On terça-feira, 8 de dezembro de 2020 20:22:04 -03 you wrote: > At the moment, the * thing works with paired delimiters, but it only > changes the first one, which is definitely a bug. It should obviously > change both. I also don't know how hard that would be. > > Riki > Indeed. It works separately for "[" and for "]". It also works separately for "[" and for ")", which is not a bad thing per se. About my idea of browsing through the variable-sized delimiters, should I put it on the wishlist? -- Rudi Gaelzer Institute of Physics Federal University of Rio Grande do Sul BRAZIL Registered linux user # 153741 -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Auto-Correct and Delimiters Bug
On 12/8/20 6:18 PM, Rudi Gaelzer wrote:
>
> Worked.
>
> Interesting development. I usually employ variable-sized delimiters,
> but often need to use \big, \Big, ...
>
>
>
> Another development that would be handy would be the possibility to
> browse through matched delimiters
>
> ( ), [ ], { }, | |, ...
>
> or to change them hierarchically using shortcuts.
>
Yes, that's a very good idea. I don't know how difficult that would or
wouldn't be.
At the moment, the * thing works with paired delimiters, but it only
changes the first one, which is definitely a bug. It should obviously
change both. I also don't know how hard that would be.
Riki
>
>
>
>
> On terça-feira, 8 de dezembro de 2020 15:42:00 -03 Richard Kimberly
> Heck wrote:
>
> > On 12/8/20 7:45 AM, Rudi Gaelzer wrote:
>
> > > Hi there.
>
> > >
>
> > > Where can I find a more detailed description of the following update
>
> > > listed in the announcement of LyX 2.3.6:
>
> > >
>
> > >
>
> > >
>
> > > Update autocorrect in mathed so that pressing '*' after a
> delimiter will
>
> > >
>
> > > cycle through all sizes.
>
> >
>
> > There's not one, but here's how it works: Enter math by pressing Ctrl-M
>
> > (say). Then hit "[". Now hit "*". This will take you through different
>
> > sizes of [. (If math auto-correct is off, this will not work, but you
>
> > should get a message on the status bar about how to enable it. Usually
>
> > by pressing "!".)
>
> >
>
> > Riki
>
> >
>
> >
>
>
>
> --
>
> Rudi Gaelzer
>
> Institute of Physics
>
> Federal University of Rio Grande do Sul
>
> BRAZIL
>
> Registered linux user # 153741
>
>
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
lyxbooks layout bug(?)
Bonjour,
{Macos Mojave; Version LyX 2.3.4.2}
Un mot pour vous signaler une sorte de bug. J'ai voulu utiliser le layout
lyxbooks. Impossible de reconfigurer lyx une fois mis les fichiers de lyxbooks
à leur place (dans le dossier layout de Lyx {dossier utilisateur}. Peut-être
que lyxbooks devrait être dans les layouts par défaut
J'arrive à utiliser lyxbooks en suivant les instructions ici (même dans mon cas
les fichiers lyxbooks sont sur mon bureau):
https://tex.stackexchange.com/questions/263418/lyx-2-1-4-doest-load-document-classes-after-using-reconfigure
To solve this problem: 1 - I removed the .layout file I am trying to use from
the Layouts folders (both user and for all users). 2 - I run the Reconfigure
and after restarting LyX, all the previous default document classes were add. 3
- To use the layout file that I want, on Lyx, I put the .layout file in the
same folder I have my LyX file. 4 - Using the option "Local Layouts", I
selected the .layout file, and now when I close and open the Lyx, I don't get
any error.
En tout cas merci de faire Lyx!
Que la force soit avec vous!
Manuel--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: lyxbooks layout bug(?)
Le 14/04/2020 à 16:34, Manuel a écrit :
Bonjour,
{Macos Mojave; Version LyX 2.3.4.2}
Un mot pour vous signaler une sorte de bug. J'ai voulu utiliser le
layout lyxbooks. Impossible de reconfigurer lyx une fois mis les
fichiers de lyxbooks à leur place (dans le dossier layout de Lyx
{dossier utilisateur}. Peut-être que lyxbooks devrait être dans les
layouts par défaut
Bonjour,
As-tu fait Outils>Reconfigure pour que LyX reconnaisse le layout?
Qu'est-ce que c'est lyxbooks au fait?
JMarc
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: margin text and labelling environment generates a bug
Am Samstag, den 08.02.2020, 07:08 + schrieb John Beattie: > When I create a margin text on the same line as a labelling > environment, the > document will not compile. This happens with lyx 2.3.3 on Windows > and with lyx > 2.3.1 on linux mint 18.2. Details of the two environments are below. You need to put the margin outside of the description label (the first item of the line) > > The mwe is attached and the picture shows the error which the > compiler reports. > > Should I raise a bug? Thanks, but this is already tracked. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
margin text and labelling environment generates a bug
Hi, When I create a margin text on the same line as a labelling environment, the document will not compile. This happens with lyx 2.3.3 on Windows and with lyx 2.3.1 on linux mint 18.2. Details of the two environments are below. The mwe is attached and the picture shows the error which the compiler reports. Should I raise a bug? Thanks, John Windows 10 -- LyX help >> about: LyX Version 2.3.3 (10 June 2019) Library directory: C:\bin\lyx 2.3\Resources\ User directory: ~\AppData\Roaming\LyX2.3\ Qt Version (run-time): 5.11.3 Qt Version (compile-time): 5.11.3 > pdflatex --version MiKTeX-pdfTeX (MiKTeX 2.9.6300) using bzip2 version 1.0.6, 6-Sept-2010 compiled with curl version 7.53.1; using libcurl/7.53.1 WinSSL compiled with expat version 2.2; using expat_2.2.0 compiled with jpeg version 9.2 compiled with liblzma version 50020032; using 50020032 compiled with libpng version 1.6.29; using 1.6.29 compiled with libressl version LibreSSL 2.4.5; using LibreSSL 2.4.5 compiled with MiKTeX Application Framework version 1.6300; using 1.6300 compiled with MiKTeX Core version 1.6300; using 1.6300 compiled with MiKTeX Archive Extractor version 1.6300; using 1.6300 compiled with MiKTeX Package Manager version 1.6300; using 1.6300 compiled with poppler version 0.53.0 compiled with uriparser version 0.8.4 compiled with zlib version 1.2.11; using 1.2.11 Mint 18.2 - > lsb_release -a mint Distributor ID: LinuxMint Description:Linux Mint 18.2 Sonya Release:18.2 Codename: sonya LyX help >> about: LyX Version 2.3.1 (Monday, 27 August 2018) Library directory: /usr/share/lyx/ User directory: ~/.lyx/ Qt Version (run-time): 4.8.7 Qt Version (compile-time): 4.8.7 > pdflatex --version pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) kpathsea version 6.2.1 Copyright 2015 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX source. Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Compiled with libpng 1.6.17; using libpng 1.6.17 Compiled with zlib 1.2.8; using zlib 1.2.8 Compiled with poppler version 0.41.0 ws.2a.lyx Description: application/lyx -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug in Lyx 1.3.4 ?
> Am 05.02.2020 um 23:33 schrieb emile lunardon :
>
> I have installed LyX 2.3.4 on Windows10 and the same crash already seen on
> LyX for Linux occurs when trying to enter the two Math Symbols :
> $\textrm{Ø}\textrm{Å}$
>
> Le mer. 5 févr. 2020 à 08:32, emile lunardon a
> écrit :
> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols
> shown in the attached file (written with LyX 1.3.3), there is a crash of LyX
> 1.3.4 with the attached messages.
>
> Can someone confirm this strange phenomena ?
I can confirm your bug with Qt5 on macOS with LyX 2.3.4. I think this is the
version you’re talking about all the time.
One has to use the math toolbar and there choose the symbol Å from the
miscellaneous pane.
The backtrace is:
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x18)
frame #0: 0x0001000699dc
LyX`lyx::Buffer::params(this=0x) at Buffer.cpp:719:9
frame #1: 0x00010079fa18 LyX`lyx::(anonymous
namespace)::Parser::parse1(this=0x7ffeefbf5b20, grid=0x7ffeefbf23e0,
flags=128, mode=TEXT_MODE, numbered=false) at MathParser.cpp:2080:20
* frame #2: 0x000100790987 LyX`lyx::(anonymous
namespace)::Parser::parse(this=0x7ffeefbf5b20, array=0x000113353690,
flags=64, mode=TEXT_MODE) at MathParser.cpp:782:2
frame #3: 0x00010079f18c LyX`lyx::(anonymous
namespace)::Parser::parse1(this=0x7ffeefbf5b20, grid=0x7ffeefbf5a30,
flags=0, mode=MATH_MODE, numbered=false) at MathParser.cpp:2013:6
frame #4: 0x000100790987 LyX`lyx::(anonymous
namespace)::Parser::parse(this=0x7ffeefbf5b20, array=0x7ffeefbf6530,
flags=0, mode=MATH_MODE) at MathParser.cpp:782:2
frame #5: 0x000100790874
LyX`lyx::mathed_parse_cell(ar=0x7ffeefbf6530, str=L"\\textrm \\AA",
f=NORMAL) at MathParser.cpp:2156:37
frame #6: 0x0001007c28d2 LyX`lyx::asArray(str=L"\\textrm \\AA",
ar=0x7ffeefbf6530, pf=NORMAL) at MathSupport.cpp:990:38
frame #7: 0x0001006deba4
LyX`lyx::InsetMathNest::doDispatch(this=0x0001112cde10,
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathNest.cpp:1237:4
frame #8: 0x00010065baa2
LyX`lyx::InsetMathGrid::doDispatch(this=0x0001112cde10,
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathGrid.cpp:1733:18
frame #9: 0x00010067e615
LyX`lyx::InsetMathHull::doDispatch(this=0x0001112cde10,
cur=0x000106149098, cmd=0x7ffeefbf9068) at InsetMathHull.cpp:2024:18
frame #10: 0x000100811520
LyX`lyx::Inset::dispatch(this=0x0001112cde10, cur=0x000106149098,
cmd=0x7ffeefbf9068) at Inset.cpp:325:2
frame #11: 0x0001001e018b
LyX`lyx::Cursor::dispatch(this=0x000106149098, cmd0=0x00011123dd68) at
Cursor.cpp:337:11
frame #12: 0x000100d876b4
LyX`lyx::frontend::GuiView::dispatchToBufferView(this=0x00011159b6f0,
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiView.cpp:3687:15
frame #13: 0x000100d80df6
LyX`lyx::frontend::GuiView::dispatch(this=0x00011159b6f0,
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiView.cpp:4343:4
frame #14: 0x000100a96008
LyX`lyx::frontend::GuiApplication::dispatch(this=0x000105d0a1d0,
cmd=0x00011123dd68, dr=0x7ffeefbfc7a0) at GuiApplication.cpp:2076:19
frame #15: 0x000100a8ff88
LyX`lyx::frontend::GuiApplication::dispatch(this=0x000105d0a1d0,
cmd=0x00011123dd68) at GuiApplication.cpp:1405:3
frame #16: 0x00010037a4ea LyX`lyx::dispatch(action=0x00011123dd68)
at LyX.cpp:1462:19
frame #17: 0x000100a41c4b
LyX`lyx::frontend::Action::action(this=0x00011334a560) at Action.cpp:87:2
frame #18: 0x000100a41d51
LyX`lyx::frontend::Action::qt_static_metacall(_o=0x00011334a560,
_c=InvokeMetaMethod, _id=1, _a=0x7ffeefbfc970) at moc_Action.cpp:81:21
frame #19: 0x00010554d63a QtCore`QMetaObject::activate(QObject*, int,
int, void**) + 2298
frame #20: 0x00010474e185
QtWidgets`QAction::activate(QAction::ActionEvent) + 309
frame #21: 0x000104841be3 QtWidgets`QAbstractButtonPrivate::click() +
147
frame #22: 0x000104842d6c
QtWidgets`QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 268
frame #23: 0x000104939bbf
QtWidgets`QToolButton::mouseReleaseEvent(QMouseEvent*) + 15
frame #24: 0x0001047931d2 QtWidgets`QWidget::event(QEvent*) + 450
frame #25: 0x00010493a14f QtWidgets`QToolButton::event(QEvent*) + 319
frame #26: 0x0001047576ff
QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 271
frame #27: 0x00010475a59d QtWidgets`QApplication::notify(QObject*,
QEvent*) + 7373
frame #28: 0x000100a9d033
LyX`lyx::frontend::GuiApplication::notify(this=0x000105d0a1d0,
receiver=0x0001114debf0, event=0x7ffeefbfd060) at
GuiApplication.cpp:2712:24
frame #29: 0x00010551c684
Re: Bug in Lyx 1.3.4 ?
I have installed LyX 2.3.4 on Windows10 and the same crash already seen on
LyX for Linux occurs when trying to enter the two Math Symbols :
$\textrm{Ø}\textrm{Å}$
Le mer. 5 févr. 2020 à 08:32, emile lunardon a
écrit :
> When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols
> shown in the attached file (written with LyX 1.3.3), there is a crash of
> LyX 1.3.4 with the attached messages.
>
> Can someone confirm this strange phenomena ?
>
> --
>
> ( 1) ./lyx: ./lyx() [0x906d2a]
> ( 2) ./lyx: ./lyx() [0x9062e6]
> ( 3) ./lyx: ./lyx() [0x63e005]
> ( 4) /lib/x86_64-linux-gnu/libc.so.6:
> /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]
> ( 5) ./lyx: ./lyx() [0x5553f0]
> ( 6) ./lyx: ./lyx() [0x7bcbcd]
> ( 7) ./lyx: ./lyx() [0x7b6231]
> ( 8) ./lyx: ./lyx() [0x7bcf6a]
> ( 9) ./lyx: ./lyx() [0x7b6231]
> ( 10) ./lyx: ./lyx() [0x7b6381]
> ( 11) ./lyx: ./lyx() [0x7c4f15]
> ( 12) ./lyx: ./lyx() [0x791b67]
> ( 13) ./lyx: ./lyx() [0x7e87a8]
> ( 14) ./lyx: ./lyx() [0x77274b]
> ( 15) ./lyx: ./lyx() [0x812b46]
> ( 16) ./lyx: ./lyx() [0x5d41dd]
> ( 17) ./lyx: ./lyx() [0x9321bb]
> ( 18) ./lyx: ./lyx() [0x9429f6]
> ( 19) ./lyx: ./lyx() [0x911f0e]
> ( 20) ./lyx: ./lyx() [0x90c5e9]
> ( 21) ./lyx: ./lyx() [0x98abf1]
> ( 22) ./lyx: ./lyx() [0x98ac78]
> ( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
> ( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
> ( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QAction::activate(QAction::ActionEvent)
> ( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
> ( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QAbstractButton::mouseReleaseEvent(QMouseEvent*)
> ( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QToolButton::mouseReleaseEvent(QMouseEvent*)
> ( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
> ( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplicationPrivate::notify_helper(QObject*, QEvent*)
> ( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplication::notify(QObject*, QEvent*)
> ( 32) ./lyx: ./lyx() [0x916195]
> ( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QCoreApplication::notifyInternal(QObject*, QEvent*)
> ( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*,
> QWidget*, QWidget**, QPointer&, bool)
> ( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
> ( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> QApplication::x11ProcessEvent(_XEvent*)
> ( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
> ( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7)
> [0x7fbd1b301417]
> ( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
> ( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)
> [0x7fbd1b3016dc]
> ( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventDispatcherGlib::processEvents(QFlags)
> ( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
> ( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventLoop::processEvents(QFlags)
> ( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
> QEventLoop::exec(QFlags)
> ( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
> ( 46) ./lyx: ./lyx() [0x643306]
> ( 47) ./lyx: ./lyx() [0x50827d]
> ( 48) /lib/x86_64-linux-gnu/libc.so.6:
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]
> ( 49) ./lyx: ./lyx() [0x512eba]
>
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug in Lyx 1.3.4 ?
On Wed, Feb 05, 2020 at 08:32:21AM +0100, emile lunardon wrote: > When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols > shown in the attached file (written with LyX 1.3.3), there is a crash of > LyX 1.3.4 with the attached messages. > > Can someone confirm this strange phenomena ? I can not (tried with Qt 4 as you do). (My entering was copy paste from your document.) Your backtrace is not much useful, if you compile on your own we would need it with debug symbols... Pavel -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug in Lyx 1.3.4 ?
On 2/5/20 2:32 AM, emile lunardon wrote: When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols shown in the attached file (written with LyX 1.3.3), there is a crash of LyX 1.3.4 with the attached messages. Can someone confirm this strange phenomena ? -- ( 1) ./lyx: ./lyx() [0x906d2a] ( 2) ./lyx: ./lyx() [0x9062e6] ( 3) ./lyx: ./lyx() [0x63e005] ( 4) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20] ( 5) ./lyx: ./lyx() [0x5553f0] ( 6) ./lyx: ./lyx() [0x7bcbcd] ( 7) ./lyx: ./lyx() [0x7b6231] ( 8) ./lyx: ./lyx() [0x7bcf6a] ( 9) ./lyx: ./lyx() [0x7b6231] ( 10) ./lyx: ./lyx() [0x7b6381] ( 11) ./lyx: ./lyx() [0x7c4f15] ( 12) ./lyx: ./lyx() [0x791b67] ( 13) ./lyx: ./lyx() [0x7e87a8] ( 14) ./lyx: ./lyx() [0x77274b] ( 15) ./lyx: ./lyx() [0x812b46] ( 16) ./lyx: ./lyx() [0x5d41dd] ( 17) ./lyx: ./lyx() [0x9321bb] ( 18) ./lyx: ./lyx() [0x9429f6] ( 19) ./lyx: ./lyx() [0x911f0e] ( 20) ./lyx: ./lyx() [0x90c5e9] ( 21) ./lyx: ./lyx() [0x98abf1] ( 22) ./lyx: ./lyx() [0x98ac78] ( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool) ( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::activate(QAction::ActionEvent) ( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3] ( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAbstractButton::mouseReleaseEvent(QMouseEvent*) ( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QToolButton::mouseReleaseEvent(QMouseEvent*) ( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*) ( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplication::notify(QObject*, QEvent*) ( 32) ./lyx: ./lyx() [0x916195] ( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::notifyInternal(QObject*, QEvent*) ( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) ( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc] ( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplication::x11ProcessEvent(_XEvent*) ( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592] ( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7fbd1b301417] ( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650] ( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fbd1b3016dc] ( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventDispatcherGlib::processEvents(QFlags) ( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666] ( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::processEvents(QFlags) ( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::exec(QFlags) ( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec() ( 46) ./lyx: ./lyx() [0x643306] ( 47) ./lyx: ./lyx() [0x50827d] ( 48) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97] ( 49) ./lyx: ./lyx() [0x512eba] LyX 1.3.4 is rather old. Have you tried a more recent version? I cannot reproduce the crash, but I'm using LyX 2.3.3. Paul -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug in Lyx 1.3.4 ?
I seem to have no problem entering them on MacOS. Though if I use the
keyboard to enter them I get
$\mathrm{\mathring{A}}$$\mathrm{\slashed{O}}$
instead of
$\textrm{Å}$$\textrm{Ø}$
However, if I copy and paste the symbols from the file, I get the latter
and no crash either.
Daniel
On 2020-02-05 08:32, emile lunardon wrote:
When I try to enter, under LyX 1.3.4 (Linux), one of the two Math
symbols shown in the attached file (written with LyX 1.3.3), there is a
crash of LyX 1.3.4 with the attached messages.
Can someone confirm this strange phenomena ?
--
( 1) ./lyx: ./lyx() [0x906d2a]
( 2) ./lyx: ./lyx() [0x9062e6]
( 3) ./lyx: ./lyx() [0x63e005]
( 4) /lib/x86_64-linux-gnu/libc.so.6:
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20]
( 5) ./lyx: ./lyx() [0x5553f0]
( 6) ./lyx: ./lyx() [0x7bcbcd]
( 7) ./lyx: ./lyx() [0x7b6231]
( 8) ./lyx: ./lyx() [0x7bcf6a]
( 9) ./lyx: ./lyx() [0x7b6231]
( 10) ./lyx: ./lyx() [0x7b6381]
( 11) ./lyx: ./lyx() [0x7c4f15]
( 12) ./lyx: ./lyx() [0x791b67]
( 13) ./lyx: ./lyx() [0x7e87a8]
( 14) ./lyx: ./lyx() [0x77274b]
( 15) ./lyx: ./lyx() [0x812b46]
( 16) ./lyx: ./lyx() [0x5d41dd]
( 17) ./lyx: ./lyx() [0x9321bb]
( 18) ./lyx: ./lyx() [0x9429f6]
( 19) ./lyx: ./lyx() [0x911f0e]
( 20) ./lyx: ./lyx() [0x90c5e9]
( 21) ./lyx: ./lyx() [0x98abf1]
( 22) ./lyx: ./lyx() [0x98ac78]
( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QMetaObject::activate(QObject*, QMetaObject const*, int, void**)
( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool)
( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QAction::activate(QAction::ActionEvent)
( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3]
( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QAbstractButton::mouseReleaseEvent(QMouseEvent*)
( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QToolButton::mouseReleaseEvent(QMouseEvent*)
( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*)
( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplicationPrivate::notify_helper(QObject*, QEvent*)
( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplication::notify(QObject*, QEvent*)
( 32) ./lyx: ./lyx() [0x916195]
( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QCoreApplication::notifyInternal(QObject*, QEvent*)
( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*,
QWidget*, QWidget**, QPointer&, bool)
( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc]
( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
QApplication::x11ProcessEvent(_XEvent*)
( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592]
( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7fbd1b301417]
( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650]
( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0:
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fbd1b3016dc]
( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QEventDispatcherGlib::processEvents(QFlags)
( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4:
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666]
( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QEventLoop::processEvents(QFlags)
( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4:
QEventLoop::exec(QFlags)
( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec()
( 46) ./lyx: ./lyx() [0x643306]
( 47) ./lyx: ./lyx() [0x50827d]
( 48) /lib/x86_64-linux-gnu/libc.so.6:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97]
( 49) ./lyx: ./lyx() [0x512eba]
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
Bug in Lyx 1.3.4 ?
When I try to enter, under LyX 1.3.4 (Linux), one of the two Math symbols shown in the attached file (written with LyX 1.3.3), there is a crash of LyX 1.3.4 with the attached messages. Can someone confirm this strange phenomena ? -- ( 1) ./lyx: ./lyx() [0x906d2a] ( 2) ./lyx: ./lyx() [0x9062e6] ( 3) ./lyx: ./lyx() [0x63e005] ( 4) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fbd1b80ef20] ( 5) ./lyx: ./lyx() [0x5553f0] ( 6) ./lyx: ./lyx() [0x7bcbcd] ( 7) ./lyx: ./lyx() [0x7b6231] ( 8) ./lyx: ./lyx() [0x7bcf6a] ( 9) ./lyx: ./lyx() [0x7b6231] ( 10) ./lyx: ./lyx() [0x7b6381] ( 11) ./lyx: ./lyx() [0x7c4f15] ( 12) ./lyx: ./lyx() [0x791b67] ( 13) ./lyx: ./lyx() [0x7e87a8] ( 14) ./lyx: ./lyx() [0x77274b] ( 15) ./lyx: ./lyx() [0x812b46] ( 16) ./lyx: ./lyx() [0x5d41dd] ( 17) ./lyx: ./lyx() [0x9321bb] ( 18) ./lyx: ./lyx() [0x9429f6] ( 19) ./lyx: ./lyx() [0x911f0e] ( 20) ./lyx: ./lyx() [0x90c5e9] ( 21) ./lyx: ./lyx() [0x98abf1] ( 22) ./lyx: ./lyx() [0x98ac78] ( 23) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ( 24) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::triggered(bool) ( 25) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAction::activate(QAction::ActionEvent) ( 26) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7fbd1d2cafa3] ( 27) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QAbstractButton::mouseReleaseEvent(QMouseEvent*) ( 28) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QToolButton::mouseReleaseEvent(QMouseEvent*) ( 29) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QWidget::event(QEvent*) ( 30) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplicationPrivate::notify_helper(QObject*, QEvent*) ( 31) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplication::notify(QObject*, QEvent*) ( 32) ./lyx: ./lyx() [0x916195] ( 33) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::notifyInternal(QObject*, QEvent*) ( 34) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) ( 35) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249ddc) [0x7fbd1cf73ddc] ( 36) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: QApplication::x11ProcessEvent(_XEvent*) ( 37) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7fbd1cf9c592] ( 38) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7fbd1b301417] ( 39) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650) [0x7fbd1b301650] ( 40) /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fbd1b3016dc] ( 41) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventDispatcherGlib::processEvents(QFlags) ( 42) /usr/lib/x86_64-linux-gnu/libQtGui.so.4: /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7fbd1cf9c666] ( 43) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::processEvents(QFlags) ( 44) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QEventLoop::exec(QFlags) ( 45) /usr/lib/x86_64-linux-gnu/libQtCore.so.4: QCoreApplication::exec() ( 46) ./lyx: ./lyx() [0x643306] ( 47) ./lyx: ./lyx() [0x50827d] ( 48) /lib/x86_64-linux-gnu/libc.so.6: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbd1b7f1b97] ( 49) ./lyx: ./lyx() [0x512eba] Crash.lyx Description: application/lyx -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
Re: Bug in LyX regarding page format and hyperref
Am Montag, den 05.08.2019, 16:19 +0200 schrieb Jürgen Spitzmüller: > But still, if A4 is selected in LyX and memoir outputs US > letter, that's simply plain wrong. We can do better. This will be fixed in LyX 2.3.4. Jürgen signature.asc Description: This is a digitally signed message part
Re: Bug in LyX regarding page format and hyperref
Am Montag, den 05.08.2019, 08:22 -0500 schrieb Les: > I doubt if accounting for Memoir's idiosyncracies is practical. The > Memoir class allows fine tuning of numerous parameters that LyX > doesn't > even know about. I know. But still, if A4 is selected in LyX and memoir outputs US letter, that's simply plain wrong. We can do better. Jürgen signature.asc Description: This is a digitally signed message part
Re: Bug in LyX regarding page format and hyperref
On Mon, 05 Aug 2019 10:40:53 +0200
Jürgen Spitzmüller wrote:
> Yes, memoir overrides geometry (which is used for the custom margins).
> However, we could account for that in LyX. See
> https://www.lyx.org/trac/ticket/10970
I doubt if accounting for Memoir's idiosyncracies is practical. The
Memoir class allows fine tuning of numerous parameters that LyX doesn't
even know about. It's not just page format, its:
\setstocksize
\settrimmedsize
\settrims
\settypeblocksize
\setlrmargins
\setlength{\marginparwidth}
\pagestyle
\chapterstyle
and many other parameters I've never used.
If you're not prepared to read the 609 page Memoir manual (memman.pdf)
you really shouldn't try to use Memoir.
If you do read it, and understand it, you will view page layout in a
completely new way.
I have used memoir extensively for years, and I'm still learning how to
improve page layout. If you want good page layout that is nearly what
you need, use KOMA-script Book. If you want an exact page layout, use
Memoir, but be prepared to learn how to do it.
Les
--
Les Denham
Re: Bug in LyX regarding page format and hyperref
Am Samstag, den 27.07.2019, 11:06 -0400 schrieb Paul A. Rubin: > I don't have any experience with book classes, so I do not know the > peculiarities of the Memoir class. I suspect this is problem with > how > Memoir reacts to certain combinations of things, rather than a LyX > bug. Yes, memoir overrides geometry (which is used for the custom margins). However, we could account for that in LyX. See https://www.lyx.org/trac/ticket/10970 Jürgen signature.asc Description: This is a digitally signed message part
Re: Bug in LyX regarding page format and hyperref
On 27-Jul-19 9:32 AM, Marius Shekow wrote: > Hi again, > > I forgot to mention that you also need to set custom page margins. An > example file is attached. > > Best regards! > > Am 26.07.2019 um 20:14 schrieb Marius Shekow: >> Hi, >> >> I've noticed that the recent Lyx versions (2.3.x) generate a PDF that >> is of "US Letter" size, even though I've explicitly set up A4 in the >> document settings (Page Layout -> Format). This happens once I enable >> Hyperref support in the document settings. >> >> As suggested in >> https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size >> >> >> it seems that adding "a4paper" as custom option to the documentclass >> seems to work. This is extreme expert knowledge that you should not >> expect your users to have. When a normal/novice user sets up A4, then >> the generated PDF should be A4 (and the same goes for any other page >> format). >> >> Is this something that you could fix? >> >> Best regards! >> Marius >> Hello Marius, As you may be aware of that LyX serves as a front-end for the LaTeX system. When you select a paper size in LyX, LyX -probably- simply adds that paper size as an option to the document class in the generated tex file. On the other hand, LaTeX is a sophisticated typesetting system, where many packages and classes are used. Sometimes, some of these packages and classes have conflicts and associated rules. When you try to use some specific packages for a given class, you may not be allowed to change some settings. As far as I observe, LyX developers are trying to identify these conflicts and implement LyX-based solutions for some of them. However, it is not always possible to follow every single one of these conflicts/rules since there are so many of these packages and classes. Further, LaTeX packages are being updated constantly and may result a conflict after an update, which makes it very difficult to track them. To put this in another way, if you are not using LyX, but using conventional text-based LaTeX typesetting, you will probably encounter these issues as well. If this issue is a well-known issue, LyX developers might have provided a solution in LyX. However, it is not always possible for LyX to have a solution. In this case, you are supposed to identify the issue and provide a solution by yourself, which we LyX-used do all the time. Best Regards, Baris -- ↓↓ Please bottom-post. Start your reply here:
Re: Bug in LyX regarding page format and hyperref
Hi, I was aware of https://wiki.lyx.org/LyX/UsingMemoirInLyX but at the same time that page seems outdated, as it explicitly mentions Lyx 1.5, which is dated. I saw that it also mentions section 6.3 of the "Additional Features" LyX help document (valid for LyX 2.x), but did not see this caveat (US Letter) being listed. It may still make sense for LyX to handle this specific case, but that's up to you. I'm content with the fix I found (which I mentioned in the original post). I've been using memoir simply out of habit. I don't think I'm using specific features that other book classes wouldn't offer. I'd say that I just liked the look of the generated PDF that came out of the box, in comparison to other book classes. I may look into scrbook for the next project, though. Best! Marius Am 27.07.2019 um 17:27 schrieb Axel Dessecker: Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow: Hi again, I forgot to mention that you also need to set custom page margins. An example file is attached. Best regards! Am 26.07.2019 um 20:14 schrieb Marius Shekow: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa ge-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius Marius, I can reproduce this behaviour, which seems to be associated with the memoir class. Very configurable but tricky, as announced at https://wiki.lyx.org/LyX/UsingMemoirInLyX . Is there a specific reason why you are not using scrbook? Axel
Re: Bug in LyX regarding page format and hyperref
Am Samstag, 27. Juli 2019, 08:32:33 CEST schrieb Marius Shekow: > Hi again, > > I forgot to mention that you also need to set custom page margins. An > example file is attached. > > Best regards! > > Am 26.07.2019 um 20:14 schrieb Marius Shekow: > > Hi, > > > > I've noticed that the recent Lyx versions (2.3.x) generate a PDF that > > is of "US Letter" size, even though I've explicitly set up A4 in the > > document settings (Page Layout -> Format). This happens once I enable > > Hyperref support in the document settings. > > > > As suggested in > > https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-packa > > ge-change-the-paper-size it seems that adding "a4paper" as custom option > > to the documentclass seems to work. This is extreme expert knowledge that > > you should not expect your users to have. When a normal/novice user sets > > up A4, then the generated PDF should be A4 (and the same goes for any > > other page format). > > > > Is this something that you could fix? > > > > Best regards! > > Marius Marius, I can reproduce this behaviour, which seems to be associated with the memoir class. Very configurable but tricky, as announced at https://wiki.lyx.org/LyX/UsingMemoirInLyX . Is there a specific reason why you are not using scrbook? Axel
Re: Bug in LyX regarding page format and hyperref
On 7/27/19 2:32 AM, Marius Shekow wrote: Hi again, I forgot to mention that you also need to set custom page margins. An example file is attached. Best regards! Am 26.07.2019 um 20:14 schrieb Marius Shekow: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius Please bottom post in messages to the forum. I can confirm your example compiles to US letter when it should compile to A4, but the trigger mechanism is more complex than hyperref + custom margins + A4 paper size. It only seems to happen with the Memoir class. I tried the basic book class, the AMS book class and also the basic article class, and they all compiled to A4. I don't have any experience with book classes, so I do not know the peculiarities of the Memoir class. I suspect this is problem with how Memoir reacts to certain combinations of things, rather than a LyX bug. Perhaps an experience Memoir user can weigh in. Paul
Re: Bug in LyX regarding page format and hyperref
Hi again, I forgot to mention that you also need to set custom page margins. An example file is attached. Best regards! Am 26.07.2019 um 20:14 schrieb Marius Shekow: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius newfile2.lyx Description: application/lyx
Re: Bug in LyX regarding page format and hyperref
On 7/26/19 2:14 PM, Marius Shekow wrote: Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius I'm unable to reproduce that here. I switched a document from US Letter to A4 in the page layout settings, turned on hyperref in the PDF settings, viewed the document (using pdflatex), and the resulting file was A4 (confirmed by checking File > Properties in the PDF viewer). I also tried A2, which produces a visibly different result (many fewer pages). If you can reproduce the bug, please reply with a minimal working example of it. Paul
Bug in LyX regarding page format and hyperref
Hi, I've noticed that the recent Lyx versions (2.3.x) generate a PDF that is of "US Letter" size, even though I've explicitly set up A4 in the document settings (Page Layout -> Format). This happens once I enable Hyperref support in the document settings. As suggested in https://tex.stackexchange.com/questions/356545/why-does-the-hyperref-package-change-the-paper-size it seems that adding "a4paper" as custom option to the documentclass seems to work. This is extreme expert knowledge that you should not expect your users to have. When a normal/novice user sets up A4, then the generated PDF should be A4 (and the same goes for any other page format). Is this something that you could fix? Best regards! Marius
Re: serious bug (fedora issue?)
Le 05/01/2019 à 20:46, Patrick Dupre a écrit : Hello, Was the information that I provided useful? I also have to face other crash issues. I will try to communicate after the previous one have been solved. Dear Patrick, I just stumbled on your posts while looking at my old inbox content before leaving in vacation... I am very sorry that we did not follow up on this. Do you still experience this painful situation? What I see from the log is that : 1/ the spellchecker is launched (#53-#56) 2/ it sets selection and triggers explicitly an update (#52-#53) 3/ this eventually triggers the computation of metrics for a graphics 4/ the graphics is loaded (so presumably it was not yet the case) 5/ this in turn causes a call to an external unzip program (#41-#40) 6/ the mechanism to show progress (wheel and timing) triggers (#32-#30) 7/ it updates the statusbar [#30-#26) 8/ this leads to a repaint of something (#25) 9/ the backing store (the thing on which we actually paint) of some widget tries to synchronize itself (#16-#14) 10/ it leads to a full repaint of our workarea (why, I am not sure) (#4] 11/ this eventually crashes, presumably because the backing store is not ready yet to receive things to paint. (#11-#10) After wrtigin all this, that does not really help yet (except that we could probably avoid 2/ and maybe forbid updates around 7/). But now I notice that the warnings show first: QBackingStore::endPaint() called with active painter on backingstore paint device are bugs in particular Qt versions. See e.g. https://bugreports.qt.io/browse/QTBUG-66452 althoug this doe snot involve a crash. So, first question: what is your Qt version? JMarc
Re: Outline pane bug
On Wed, May 08, 2019 at 02:04:22PM -0400, Paul A. Rubin wrote: > On 5/8/19 4:37 AM, Horsfield, Andrew P wrote: > > Hi, > > > > I am using LyX Version 2.3.2 on a desktop machine running Kubuntu 19.04 > > (Qt 5.12.2). I find that the outline pane refreshes itself every time I > > type a character, which is rather distracting. That would be very distracting to me as well. > > The work-around is to > > close the pane when typing. I do not have this problem on my Mac > > laptop. > > > > Andrew > I don't see that (LyX 2.3.2, Mint 18.3, Qt 4.8.7), which suggests that it > might be related either to the operating system (or window manager?) or to > the Qt version. I also can't reproduce. I'm on Ubuntu (default GNOME) 19.04 with system Qt 5.12.2. I self-compiled LyX though. I can test tomorrow on the Ubuntu version from the repository, if that would help. How did you get LyX? From the Ubuntu repository or self-compiled or PPA? Scott signature.asc Description: PGP signature
Re: Outline pane bug
On 5/8/19 4:37 AM, Horsfield, Andrew P wrote: Hi, I am using LyX Version 2.3.2 on a desktop machine running Kubuntu 19.04 (Qt 5.12.2). I find that the outline pane refreshes itself every time I type a character, which is rather distracting. The work-around is to close the pane when typing. I do not have this problem on my Mac laptop. Andrew I don't see that (LyX 2.3.2, Mint 18.3, Qt 4.8.7), which suggests that it might be related either to the operating system (or window manager?) or to the Qt version. Paul
Outline pane bug
Hi, I am using LyX Version 2.3.2 on a desktop machine running Kubuntu 19.04 (Qt 5.12.2). I find that the outline pane refreshes itself every time I type a character, which is rather distracting. The work-around is to close the pane when typing. I do not have this problem on my Mac laptop. Andrew -- *---* Andrew Horsfield a.horsfi...@imperial.ac.uk Department of Materials, Imperial College London South Kensington Campus, London SW7 2AZ, U.K. Phone:+44-(0)20-7594-6753 *---*
Re: serious bug (fedora issue?)
On Sat, Jan 05, 2019 at 08:46:42PM +0100, Patrick Dupre wrote: > Hello, > > Was the information that I provided useful? From what I understand, yes it does look useful because you have debug symbols installed. > I also have to face other crash issues. I will try to communicate after > the previous one have been solved. Do all of the crash issues you see require you to use a private document? Did you try buffer-anonymize? It might not help since this issue is related to spell-checking, but it's worth a try. If you can find a way to get a crash from a document you can share, please let us know. It might be a while before we figure out a fix to the other bug (since we don't have a document to reproduce). Scott signature.asc Description: PGP signature
Re: LyX 2.3.1: bug with preview of \oiint... what about LyX 2.3.2?
On Thu, Jan 17, 2019 at 09:45:34AM -0500, Richard Kimberly Heck wrote: > On 1/17/19 8:12 AM, Pavel Sanda wrote: > > On Tue, Jan 15, 2019 at 04:21:06PM +, Bernt Lie wrote: > >> I???m still using LyX 2.3.1 on one PC. There appears to be a bug on Win 10 > >> 64bit, latest version. If I insert \oiint in a math expression, nothing is > >> displayed. > > https://www.lyx.org/trac/ticket/8493 > > > > It will be fixed in next major (2.4.x) release. > > Not nice workaround but it should be at least visible if you have instant > > preview on and leave the math inset. > > I take it there is no way to #ifdef this stuff? It's not code, but changes in fonts and symbols file - nothing processed by compiler. > I suppose I could patch 2.3.x for Windows myself, right? Since I'm > compiling with Qt5? Just next burden on your shoulders, but in principle yes. Cherrypick commits listed in #8493 it should work with Qt5 (I tested only in Linux so you need to check stmary10.lyx in Windows). The bug is there for a long time and we get rarely reports like this, so I assume it's not big issue... Pavel
Re: LyX 2.3.1: bug with preview of \oiint... what about LyX 2.3.2?
On 1/17/19 8:12 AM, Pavel Sanda wrote: > On Tue, Jan 15, 2019 at 04:21:06PM +, Bernt Lie wrote: >> I???m still using LyX 2.3.1 on one PC. There appears to be a bug on Win 10 >> 64bit, latest version. If I insert \oiint in a math expression, nothing is >> displayed. > https://www.lyx.org/trac/ticket/8493 > > It will be fixed in next major (2.4.x) release. > Not nice workaround but it should be at least visible if you have instant > preview on and leave the math inset. I take it there is no way to #ifdef this stuff? I suppose I could patch 2.3.x for Windows myself, right? Since I'm compiling with Qt5? Riki
Re: LyX 2.3.1: bug with preview of \oiint... what about LyX 2.3.2?
On Tue, Jan 15, 2019 at 04:21:06PM +, Bernt Lie wrote: > I???m still using LyX 2.3.1 on one PC. There appears to be a bug on Win 10 > 64bit, latest version. If I insert \oiint in a math expression, nothing is > displayed. https://www.lyx.org/trac/ticket/8493 It will be fixed in next major (2.4.x) release. Not nice workaround but it should be at least visible if you have instant preview on and leave the math inset. Pavel
LyX 2.3.1: bug with preview of \oiint... what about LyX 2.3.2?
I’m still using LyX 2.3.1 on one PC. There appears to be a bug on Win 10 64bit, latest version. If I insert \oiint in a math expression, nothing is displayed. [cid:image001.png@01D4ACF6.B3925130] However, the preview works: If I click outside of the math expression, I get the expected result. [cid:image002.png@01D4ACF6.B3925130] -B
Re: serious bug (fedora issue?)
Hello, Was the information that I provided useful? I also have to face other crash issues. I will try to communicate after the previous one have been solved. Thank. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | ===
Re: serious bug (fedora issue?)
Here it is. gdb /usr/bin/lyx GNU gdb (GDB) Fedora 8.1.1-3.fc28 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/lyx...Reading symbols from /usr/bin/lyx...(no debugging symbols found)...done. (no debugging symbols found)...done. Missing separate debuginfos, use: dnf debuginfo-install lyx-2.3.2-1.fc28.x86_64 (gdb) run Starting program: /usr/bin/lyx warning: Loadable section ".note.gnu.property" outside of ELF segments [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments [New Thread 0x7fffdebc6700 (LWP 6067)] warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments [New Thread 0x7fffd5331700 (LWP 6068)] [New Thread 0x7fffd4b30700 (LWP 6069)] [New Thread 0x7fffc700 (LWP 6070)] warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments [New Thread 0x7fffcdc57700 (LWP 6071)] warning: Loadable section ".note.gnu.property" outside of ELF segments warning: Loadable section ".note.gnu.property" outside of ELF segments Detaching after fork from child process 6072. Detaching after fork from child process 6074. Detaching after fork from child process 6077. Detaching after fork from child process 6078. Detaching after fork from child process 6079. Detaching after fork from child process 6080. Detaching after fork from child process 6081. Detaching after fork from child process 6082. Detaching after fork from child process 6083. Detaching after fork from child process 6084. Detaching after fork from child process 6085. Detaching after fork from child process 6086. Detaching after fork from child process 6087. Detaching after fork from child process 6088. Detaching after fork from child process 6089. Detaching after fork from child process 6090. Detaching after fork from child process 6091. Detaching after fork from child process 6092. Detaching after fork from child process 6093. Detaching after fork from child process 6094. Detaching after fork from child process 6095. Detaching after fork from child process 6096. Detaching after fork from child process 6097. Detaching after fork from child process 6098. Detaching after fork from child process 6099. Detaching after fork from child process 6100. Detaching after fork from child process 6101. Detaching after fork from child process 6102. Detaching after fork from child process 6103. Detaching after fork from child process 6104. Detaching after fork from child process 6105. Detaching after fork from child process 6106. Detaching after fork from child process 6107. Detaching after fork from child process 6108. Detaching after fork from child process 6109. Detaching after fork from child process 6110. Detaching after fork from child process 6111. Detaching after fork from child process 6289. Detaching after fork from child process 6290. QBackingStore::endPaint() called with active painter on backingstore paint device QBackingStore::endPaint() called with active painter on backingstore paint device Thread 1 "lyx" received signal SIGSEGV, Segmentati
