Re: It is that time of year again :-)

Le 22/11/2023 à 20:21, José Matos a écrit : Notice the latest gcc. This time around there is no new warning cropping up (actually with these settings there is no warning at all). Does it mean that the annoying warning with QByteArray that we get with gcc 13 is fixed in Qt 6.6 or that it is fix

Fwd: New Defects reported by Coverity Scan for LyX

Hi, I had to update coverity scan to the version 2023.06.2, and it has a new GLOBAL_INIT_ORDER error. In theory, it is a good idea, but as you will see below, it triggers for static docstring and pretends that these definitions require lyxrc or theCiteEnginesList. This does not make any sens

Re: Using Comment notes the right way

Le 21/11/2023 à 07:54, Daniel a écrit : I see. But my point was that I don't think that it is specific to my use case. The reason being that the comment feature is a default feature found in many applications these days and that this indicates a quite general usefulness of it. As I wrote befo

Re: Using Comment notes the right way

Le 19/11/2023 à 07:47, Daniel a écrit : On 2023-11-15 11:47, Daniel wrote: 2. Allow free spacing in Comments. That is typically a feature in sticky notes in other applications which is handy if one wants just to quickly type stuff down without bothering with special formatting. It basically

Re: Branches and InsetLayout

Le 18/11/2023 à 11:01, Yuriy Skalko a écrit : Sorry, should be fixed. Riki Thanks for the quick fix! Seems your original patch also works good if we remove default labelstring_ value (from_ascii("UNDEFINED")) in InsetLayout.h. And Customization.lyx also says that default LabelString is "",

Re: Using Comment notes the right way

Le 17/11/2023 à 08:00, Daniel a écrit : As it is, a yellow note is the “always inactive” branch. And it serves this purpose pretty well. If you need a bubble-like tool (for revision, for example), it has to be a new one. Don't let the yellow fool you :) I never felt the need for branches. Ma

Re: Using Comment notes the right way

Le 17/11/2023 à 08:43, Daniel a écrit : It still seems to me that LyX should provide a ready to use commenting feature that can be globally toggled on and off in the export. And it seems to me that the "Comment" note is on the right track here. It just needs a facelift (some nice label color an

Re: Using Comment notes the right way

Le 16/11/2023 à 10:58, Daniel a écrit : But couldn't there be a case where you want some people to get the comments in LaTeX but not others? Why do I have to make a decision on this by choosing a particular note. Yes, I could put stuff into branches but it feels a bit like taking a sledgehamme

Re: New macros LYX_BEGIN_MUTE_GCC_WARNING and LYX_END_MUTE_GCC_WARNING not defined in cmake conf

Le 10/11/2023 à 13:24, Kornel Benko a écrit : Thanks, but /usr2/src/lyx/lyx-git/src/Mover.h:18:10: fatal error: support/mute_warning.h: No such file or directory 18 | #include "support/mute_warning.h" | ^~~~ Kornel Sigh. Fixed now. JMarc -- lyx-de

Re: New macros LYX_BEGIN_MUTE_GCC_WARNING and LYX_END_MUTE_GCC_WARNING not defined in cmake conf

Le 10/11/2023 à 12:58, Kornel Benko a écrit : This of course breaks the compilation. Please do not add new stuff at this stage. Would it be possible to add the definitions into some header file instead? Sorry, I did not think of this (better) possibility. Done now. JMarc -- lyx-devel mail

Re: Deprecated functions with lyx-2.3.7dev

Le 10/11/2023 à 12:18, Pavel Sanda a écrit : On Fri, Nov 10, 2023 at 10:48:09AM +0100, Jean-Marc Lasgouttes wrote: The good thing is that removing these patches allowed me to uncover two smaller-scoped warnings that had not been backported (one was a real issue). But, well, this is done now, so

Re: [PATCH] Re: New warning (or at least I only noticed it now)

Le 10/11/2023 à 12:16, Pavel Sanda a écrit : On Fri, Nov 10, 2023 at 10:55:56AM +0100, Jean-Marc Lasgouttes wrote: PS: I have to admit that I have a kink with weird uses of preprocessor macros: https://gitlab.inria.fr/lasgoutt/parameters Funny, I found # and ## operators very handy for

Re: Something's wrong today with git.lyx.org:lyx

Le 10/11/2023 à 12:05, Kornel Benko a écrit : On master I get $ git pull error: Could not read 343a9749abe4f32e67ef9aae9554ee4bd8dae1b4 remote: Counting objects: 42, done. remote: Compressing objects: 100% (26/26), done. remote: Total 26 (delta 22), reused 0 (delta 0) Unpacking objects:

Re: [PATCH] Re: New warning (or at least I only noticed it now)

Le 09/11/2023 à 21:54, José Matos a écrit : On Thu, 2023-11-09 at 20:34 +0100, Pavel Sanda wrote: Looks reasonable. Pavel I agree. After so many dark spells I fear for Jean-Marc's sanity. :-D You mean that I should not rewrite parts of LyX in preprocessor macros as I intended to? JMarc

Re: Deprecated functions with lyx-2.3.7dev

Le 10/11/2023 à 03:38, Richard Kimberly Heck a écrit : The solution can be divided in two parts : 1/ decide that we do not care about obsolete methods or compatibility problems with recent C++ versions. The idea is that 2.3 is stuck with C++11/14 and that what heppens with other versions is no

Re: [PATCH] Re: New warning (or at least I only noticed it now)

can happen is a compilation failure. Thoughts? JMarc PS: I have to say that I learned a lot while making this thing work!From e93a8a431b0b7c3b283af420b571cec49daf44b3 Mon Sep 17 00:00:00 2001 From: Jean-Marc Lasgouttes Date: Wed, 8 Nov 2023 18:07:14 +0100 Subject: [PATCH] Avoid dangling

Re: Deprecated functions with lyx-2.3.7dev

Le 08/11/2023 à 19:41, Richard Kimberly Heck a écrit : On 11/8/23 10:00, Jean-Marc Lasgouttes wrote: Le 07/11/2023 à 18:03, Richard Kimberly Heck a écrit : I think these must be safe. They have all been in master for three years. I had a better idea: let's mute these warnings about fut

[PATCH] Re: New warning (or at least I only noticed it now)

. The question is whether we want to get rid of reference on the left side or fix the temps on the right. We have to do something for this annoying warning. What about the following? JMarc From 71d372b787516a28e9ec726d4a390dcb83bff10c Mon Sep 17 00:00:00 2001 From: Jean-Marc Lasgouttes Date

Re: Deprecated functions with lyx-2.3.7dev

JMarc From 8e096528988b93d17f9406c5ff4330e05c540b21 Mon Sep 17 00:00:00 2001 From: Jean-Marc Lasgouttes Date: Wed, 8 Nov 2023 15:55:05 +0100 Subject: [PATCH] Avoid warnings about deprecated features. At this stage of 2.3.x development, warnings about deprecated features and C++20 reserved key

Re: [LyX/master] Update math macro display when entering from above/balow

Le 07/11/2023 à 18:22, Richard Kimberly Heck a écrit : But since I have no proof or reason to believe than this extra metrics step is costly, I prefer to leave it like that for now. Yes, I knew that would be ugly, but if it does end up being expensive Then I will fix it :) We probably hav

Re: [LyX/master] Update math macro display when entering from above/balow

Le 07/11/2023 à 18:08, Richard Kimberly Heck a écrit : On 11/7/23 08:24, Jean-Marc Lasgouttes wrote: commit 9c3d9cded0b7f40b449bdfab0200d7fb27e1b1a8 Author: Jean-Marc Lasgouttes Date:   Tue Nov 7 15:43:57 2023 +0100 Update math macro display when entering from above/balow This

Re: Deprecated functions with lyx-2.3.7dev

Le 07/11/2023 à 10:14, Jean-Pierre Chrétien a écrit : Dear developers, I recompiled lyx-2.3.7dev to cope with the problem of hunspell library missing with Debian bookstorm, and I got a bunch of warnings about std:unary and std:binary deprecated functions declared in in stl_function.h. There

Re: [LyX/master] Fixup 65cb9fa4: avoid extra spacing when selecting math

Le 18/10/2023 à 16:38, Scott Kostyshak a écrit : I think this commit fixed an issue that I was about to bisect. The issue is fixed now, but since it seems the issue is tricky I thought I would attach another case since it doesn't have to do with a fraction inset. Perhaps that helps to narrow in o

Re: Don't hide menus

Le 14/10/2023 à 18:09, Jürgen Spitzmüller a écrit : As a GNOME user I am quite used to this sort of UI (the search bar in the shell follows a similar spirit and is great for keyboard aficionados). Right. I miss the application menus there, though. I suspect it is not easy to implement this pr

Re: Don't hide menus

Le 14/10/2023 à 17:57, Scott Kostyshak a écrit : Right. And in practice it is also a great tool for experienced users, I agree that experienced users is the intended audience. This is not what I wrote. It is also useful for searching menu entries when you are not familiar with them. I thi

Re: Don't hide menus

Le 14/10/2023 à 14:27, Jürgen Spitzmüller a écrit : Am Samstag, dem 14.10.2023 um 14:18 +0200 schrieb Jean-Marc Lasgouttes: Look at the screenshot here : https://wiki.ubuntu.com/Unity/HUD Thanks. So in simpler words, a search field for menu items. Right. And in practice it is also a great

Re: Don't hide menus

Look at the screenshot here : https://wiki.ubuntu.com/Unity/HUD JMarc Le 14 octobre 2023 08:33:53 GMT+02:00, "Jürgen Spitzmüller" a écrit : >Am Freitag, dem 13.10.2023 um 17:44 +0200 schrieb Jean-Marc Lasgouttes: >> What we could provide is a HUD, like Apple's

Re: Don't hide menus

Le 13/10/2023 à 17:08, Daniel a écrit : > I agree that the menus of these apps are complex. But that might be in their nature. I guess the Ribbon was a (maybe controversial) attempt to solve this problem. But I think LyX with its hidden menus is actually worse to figure out. I am still discover

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Please stay on lyx-devel. There are people here much more competent than I am on these subjects] Le 03/10/2023 à 14:48, Christoph Schmitz a écrit : Jean-Marc, Am 03.10.2023 um 14:19 schrieb Jean-Marc Lasgouttes : Le 03/10/2023 à 13:35, Christoph Schmitz a écrit : Jean-Marc, With which

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

Le 03/10/2023 à 13:35, Christoph Schmitz a écrit : Jean-Marc, With which parameters should I execute "qmake6"? The first thing would be to just run it without parameters and see what happens. The error message "Detected locale "C" with character encoding "UTF-8", which is not UTF-8 . Qt d

Re: [RFC Riki!] Re: Highlighted math in dark mode is hard to see

Le 30/09/2023 à 15:23, Jürgen Spitzmüller a écrit : Am Freitag, dem 29.09.2023 um 15:53 +0200 schrieb Jürgen Spitzmüller: And it only works for fully selected math insets, not for parts of it. Don't know where to set the latter. The issue here is, probably, that Math is missing something like

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

Le 29/09/2023 à 13:55, Christoph Schmitz a écrit : Hi all, I have been compiling LyX for a while now. A few weeks ago, I encountered a problem where LyX could no longer be compiled. I didn't report this issue at the time because I was using a beta version of macOS. However, now that macOS Son

Re: [RFC Riki!] Re: Highlighted math in dark mode is hard to see

Le 29/09/2023 à 15:53, Jürgen Spitzmüller a écrit : Am Freitag, dem 29.09.2023 um 15:11 +0200 schrieb Jürgen Spitzmüller: Or maybe introduce a Color_selectionmath. I think this could be easily implemented for 2.4 without having to fear collateral effects. Like this. Involves a new string, toug

Re: [RFC Riki!] Re: Highlighted math in dark mode is hard to see

Le 29/09/2023 à 15:53, Jürgen Spitzmüller a écrit : Am Freitag, dem 29.09.2023 um 15:11 +0200 schrieb Jürgen Spitzmüller: Or maybe introduce a Color_selectionmath. I think this could be easily implemented for 2.4 without having to fear collateral effects. Like this. Involves a new string, toug

Re: Highlighted math in dark mode is hard to see

Le 23/09/2023 à 21:21, Daniel a écrit : On 2023-09-23 20:09, Scott Kostyshak wrote: Is there a reason why the "selected text" color is not applied to maths? Changing that would solve the problem since this color is visible on a "selection" background. (I guess that is its point.) No, it could

Re: [LyX/master] Get rid of unnecessary flickering when clicking in outliner

Le 18/09/2023 à 11:35, Jürgen Spitzmüller a écrit : Am Montag, dem 18.09.2023 um 10:57 +0200 schrieb Jean-Marc Lasgouttes: QTreeView::expandRecursively has been introduces in QT 5.13. Hm. Would have expected the Qt (5.15) docs to mention that :-( Qt6 docs do not mention it, but Qt 5.15LTS

Re: [LyX/master] Get rid of unnecessary flickering when clicking in outliner

Le 17/09/2023 à 18:01, Juergen Spitzmueller a écrit : commit ac275a66b5d34e211ba6e63ea9a2d02efce7eb72 Author: Juergen Spitzmueller Date: Sun Sep 17 19:17:12 2023 +0200 Get rid of unnecessary flickering when clicking in outliner No need to collapse and re-expand the node where

Re: Bug report: SIGSEGV when copying cross-reference from "description" layout on LyX 2.4.0 beta 5

Le 15/09/2023 à 16:23, Jürgen Spitzmüller a écrit : (Wasn't this bug caught at some point by a static analyser? It seems to be a too common error in C++ for it to slip through.) Apparently not. Coverity scan only tags this if in some other places of the code there is a test for a null pointe

Re: Bug-report - LyX crash

Le 15/09/2023 à 13:18, Stephan Witt a écrit : To me, this looks like this one: https://www.lyx.org/trac/ticket/12818 We have a problem on macOS with the interpretation of the return values of QMessageBox. I see the patch there is not backported to 2.3.x. Is this normal? I think it’s not back

Re: Bug-report - LyX crash

Le 15/09/2023 à 11:40, luxhacker a écrit : Hi Pavel, Please create an account for me. I am very interested in LyX. It's difficult to reproduce or seize a problem without knowing anything about it. When looking at the stack, I get - perhaps wrongly - the impression it's user-interface related

Re: Menus with many entries do not scroll

Le 10/09/2023 à 22:36, Scott Kostyshak a écrit : On Sun, Sep 10, 2023 at 08:02:30PM +0200, Jean-Marc Lasgouttes wrote: Le 10/09/2023 à 17:25, Richard Kimberly Heck a écrit : Still, one would think the menus should scroll. Is it a Qt version issue? Indeed it seems better with Qt 6. Thanks

Re: Menus with many entries do not scroll

Le 10/09/2023 à 17:25, Richard Kimberly Heck a écrit : Still, one would think the menus should scroll. Is it a Qt version issue? JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Phantom mouse movement issues with macOS

Le 05/09/2023 à 15:27, Jürgen Spitzmüller a écrit : Am Dienstag, dem 05.09.2023 um 15:21 +0200 schrieb Jürgen Spitzmüller: I agree that this is a good idea. Just wondering whether it should be done next to the current fix which does a bit more for inset buttons (see my other comment on why I lik

Re: Phantom mouse movement issues with macOS

Le 05/09/2023 à 15:10, Jürgen Spitzmüller a écrit : Am Dienstag, dem 05.09.2023 um 14:51 +0200 schrieb Pavel Sanda: I double checked that the problem I report with 2.3.7 is on Qt 5.15.7. Plus that bug was on Windows, the new ones are on Mac. But the effect is the same, signaling a mouse moveme

Re: Phantom mouse movement issues with macOS

Le 04/09/2023 à 16:39, Jürgen Spitzmüller a écrit : Am Montag, dem 04.09.2023 um 16:31 +0200 schrieb Jean-Marc Lasgouttes: Dear Devvies, These last weeks I have seen without really thinking about them several macOS issues where mouse movement occurred when they should not. I decided to search

Phantom mouse movement issues with macOS

Dear Devvies, These last weeks I have seen without really thinking about them several macOS issues where mouse movement occurred when they should not. I decided to search Qt bugs about that and voilà!: https://bugreports.qt.io/browse/QTBUG-70 This bug has been fixed in Qt 6.5. It is not c

Re: Closing 2.4.0 milestoned & fixedinmaster bugs

Le 02/09/2023 à 11:29, Pavel Sanda a écrit : And the last table here? https://www.lyx.org/trac/wiki/BugTrackerHome#Unresolvedbugstargetedtonextmajorrelease2.4 That's the useful one, which I often need to scroll to :) Or use the "End" key of the keyboard. JMarc -- lyx-devel mailing list lyx-

Re: Closing 2.4.0 milestoned & fixedinmaster bugs

Le 01/09/2023 à 22:40, Pavel Sanda a écrit : On Fri, Sep 01, 2023 at 10:14:33PM +0200, Jean-Marc Lasgouttes wrote: Not me, but I am not sure why you needed it. 3 pages of useless scrolling at https://www.lyx.org/trac/wiki/BugTrackerHome And the last table here? https://www.lyx.org/trac/wiki

Re: [LyX/master] Fixup 7f1b1729: restore lazy caret handling

Le 29/08/2023 à 19:08, Scott Kostyshak a écrit : JMarc, should I open an issue for this? It's not important, so not something we need to look at before 2.4.0. Also note that I can only reproduce the issue if I zoom in enough (although I don't have to zoom in so far). Yes please. I am not sure

Re: Closing 2.4.0 milestoned & fixedinmaster bugs

Le 01/09/2023 à 21:39, Pavel Sanda a écrit : Hi, would anyone mind if I close (2.4.0 milestoned && fixedinmaster) bugs in trac? Not me, but I am not sure why you needed it. Don't we have nice reports that take into account fixedinmaster? JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.

Re: Setting "\tempdir_path" before first start

Le 31/08/2023 à 23:06, Jakob Jakobson a écrit : a) As the access to the home directory is useful anyway, we set the "\tempdir_path" to a directory within the home directory. However, this should be done before the first start of LyX for a smooth user experience. Did you try to set that in lib/

Re: Beta 5 Tarballs

Le 31/08/2023 à 18:43, Lorenzo Bertini a écrit : I think Qt devs created this to be a barebone client side decorations, and assumed the window manager would replace it with it's own. Surprising, considering mutter doesn't do this and it's one of the most used compositor/wm. I've had this prob

Re: Beta 5 Tarballs

Le 31/08/2023 à 17:03, José Matos a écrit : On Thu, 2023-08-31 at 15:51 +0200, Jean-Pierre Chrétien wrote: Compiles and runs fine on Debian stable: Version Qt (à l'exécution) : 5.15.8 sur la plate-forme wayland Version Qt (à la compilation): 5.15.8 Version OS (à la compilation) : Debian GNU/Lin

Re: Next Release?

Le 28/08/2023 à 18:25, Richard Kimberly Heck a écrit : Do we seem ready for another release? My sense is that things have calmed down again. If so, then we might go ahead and do one and then immediately freeze strings to allow our translators to start their work. I think we are. JMarc -- l

Re: Error with Qt 6 and autotools

Le 25/08/2023 à 22:08, Cor Blom a écrit : Sorry, no change. I give up. Maybe you could just try to ask the suse/qt people why qmake6 does not produce a Makefile in this case? JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Error with Qt 6 and autotools

Le 24/08/2023 à 13:27, Cor Blom a écrit : Can I see src/frontends/qt/Makefile too? See attached. I use a recent git checkout, so it should be the same as the one in the git sources. I meant the generated Makefile. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org

Re: Error with Qt 6 and autotools

Le 24/08/2023 à 09:38, Cor Blom a écrit : Op 24-08-2023 om 00:50 schreef Jean-Marc Lasgouttes: Do you have a config.log? The configure mechanism for qt6 now relies on qmake, so there may be quirks. [   22s] run "./configure && make" [   22s] [   22s] + TEXMF=/usr/s

Re: Error with Qt 6 and autotools

Le 22/08/2023 à 20:41, Cor Blom a écrit : Hi, I have tried building the qt6 version using autotools in the buildservice of openSUSE for Tumbleweed. It fails with the following error: [   45s] make  all-am [   45s] make[6]: Entering directory '/home/abuild/rpmbuild/BUILD/lyx-qt6-2.4.169265426

Re: Remove Qt < 5.2 conditionals and special code

+1 JMarc Le 17 août 2023 16:12:43 GMT+02:00, Pavel Sanda a écrit : >I don't think there is a value in keeping LyX compilable with Qt < 5.2, >because 5.2 was released 10 years ago. >Even closed/commerical LTS variants of current distros do not show support >>10y. > >So +1 for removal from my s

Re: Breakdown of remaining 2.4 bugs

Le 27/07/2023 à 16:13, Pavel Sanda a écrit : *Normal bugs JMarc is unf gone for quite some time, anyone willing to look? #12841 - regression with math selection I am still here for 10 minutes :) For the record, I spend some time trying to understand the code and failed. I trust Enrico's analy

Re: Joining newlines in paste (was: Pasting latex in a lyx file)

Le 27/07/2023 à 18:07, Pavel Sanda a écrit : Bunch of people expressed their opinion that our default for paste operation should preserve newlines. I do not have strong opinion but agree that in my experience I have to go to Paste Special sub menu quite often to preserve the newlines. Before loo

Fwd: [LyX features/biginset] Implement quick scroll

n and away from a computer starting thursday evening and until 25 of august at least. I will be reading mail, though. Message transféré Sujet : [LyX features/biginset] Implement quick scroll Date : Tue, 25 Jul 2023 16:07:16 +0200 (CEST) De : Jean-Marc Lasgouttes Répondre à : lyx-

Re: [PATCH] Making Update::SinglePar work inside insets

Le 23/07/2023 à 02:40, Richard Kimberly Heck a écrit : I was hoping to go to RC1 pretty soon, so it might not be the right time for that. We might go ahead and branch 2.5.0dev once RC1 is out. Fine with me. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman

Re: [PATCH] Making Update::SinglePar work inside insets

Le 18/07/2023 à 20:50, Jean-Marc Lasgouttes a écrit : Le 17/07/2023 à 23:19, Jean-Marc Lasgouttes a écrit : It worked well until one tries to use mathed %-] Updated patch below is better in this respect. Err, I posted the same patch twice! Here is the updated one. The patch is now attached

Re: make rpmdist failing

Le 22/07/2023 à 21:05, Richard Kimberly Heck a écrit : I've finally decided to use the rpmdist target rather than installing directly, but it is failing here:     $(LN_S) $(srcdir)/lib/images/lyx.png . ; \ The problem is that LN_S does not seem to be defined, so it is trying to execute the i

Re: Paragraph settings not applied to last selected paragraph

Le 21/07/2023 à 16:27, Pavel Sanda a écrit : Clearly the idea was to iterate over all paragraphs in the range of [cur.selectionBegin();cur.selectionEnd()]. However ++c.pit() increases only paragraph number (c.slices_[0].pit_) and let the relative cursor position within paragraph c.slices_[0].pos_

Re: [PATCH] Is there a reason for not using macros with arguments in lib/symbols?

Le 18/07/2023 à 15:11, Jean-Marc Lasgouttes a écrit : Hello, In the attached patch, I am able to support the mod/bmod/pmod/pod macros by just defining them in lib/symbols with an argument. The result is a more pleasing editing process (IMO) and a simplification of the documentation. It is

Re: [PATCH] Making Update::SinglePar work inside insets

Le 17/07/2023 à 23:19, Jean-Marc Lasgouttes a écrit : It worked well until one tries to use mathed %-] Updated patch below is better in this respect. Err, I posted the same patch twice! Here is the updated one. JMarc From f17ff420bfa7c2390776023c566c4974ea612f28 Mon Sep 17 00:00:00 2001

Re: [PATCH] Is there a reason for not using macros with arguments in lib/symbols?

Le 18/07/2023 à 16:47, Thibaut Cuvelier a écrit : On Tue, 18 Jul 2023 at 16:04, Jean-Marc Lasgouttes <mailto:lasgout...@lyx.org>> wrote: Le 18/07/2023 à 15:54, Thibaut Cuvelier a écrit : > Also, we already have macros with parameters: > https://github.com/cburschka/

Re: [PATCH] Is there a reason for not using macros with arguments in lib/symbols?

Le 18/07/2023 à 15:54, Thibaut Cuvelier a écrit : Also, we already have macros with parameters: https://github.com/cburschka/lyx/blob/master/lib/symbols#L1223 Indeed. I'm the one who pushed that, but it did not impress me at the

Re: [PATCH] Is there a reason for not using macros with arguments in lib/symbols?

Le 18/07/2023 à 15:36, Thibaut Cuvelier a écrit : For the symbols in your patch, yes, export is currently broken, but it's fixable. I think it would still be fixable in the future with macros, as I did in https://github.com/cburschka/lyx/blob/master/lib/symbols#L1128

[PATCH] Is there a reason for not using macros with arguments in lib/symbols?

n the context (script...). JMarcFrom bc03ea8ed0030e470cf7528004a7c9e51b1733b7 Mon Sep 17 00:00:00 2001 From: Jean-Marc Lasgouttes Date: Tue, 18 Jul 2023 14:27:24 +0200 Subject: [PATCH] Use macros with parameters for modulo macros It turns out that it is possible to use macros with parameters in lib/sy

Re: [LyX/master] Acount for all non-negative spaces used by lyx

Le 18/07/2023 à 14:47, Kornel Benko a écrit : Am Tue, 18 Jul 2023 13:58:51 +0200 schrieb Jean-Marc Lasgouttes : Is this octal representation? Why is it needed? I think that we use hexadecimal in the rest of the code, don't we? JMarc True, but we are using here standard regex, so we

Re: [LyX/master] Acount for all non-negative spaces used by lyx

Le 18/07/2023 à 12:03, Kornel Benko a écrit : commit 8eda9e25e00effe8eec6adef8244fc81b888c78f Author: Kornel Benko Date: Tue Jul 18 13:09:55 2023 +0200 Acount for all non-negative spaces used by lyx The unicode representation in an ascii-string string is \302\240

Re: [PATCH] Making Update::SinglePar work inside insets

Le 17/07/2023 à 18:00, Scott Kostyshak a écrit : On Mon, Jul 17, 2023 at 04:03:32PM +0200, Jean-Marc Lasgouttes wrote: Hello, This patch tries to address #12297, where typing in the big branch in the attached big-inset.23.lyx file is painfully slow. Works well! I just did some brief testing

Re: ./configure goes through, build fails with no library

Le 17/07/2023 à 21:14, Enrico Forestieri a écrit : Take into account that modules differ from a Qt version to another, so we would still need 3 different paths. A helper function with parameters? Moreover, I think that the Qt4 version would need a different approach, even if the info can be

Re: ./configure goes through, build fails with no library

Le 17/07/2023 à 20:56, Enrico Forestieri a écrit : I expect it to work with Qt5, at least. But why should we do that? Remember: don't fix it if it ain't broken. Because the rest is a mess and we have now 3 different paths to do the same thing. Are there known cases where qmake is not enough fo

Re: ./configure goes through, build fails with no library

Le 15/07/2023 à 15:31, Enrico Forestieri a écrit : On Sat, Jul 15, 2023 at 01:47:56PM +0200, Jean-Marc Lasgouttes wrote: Le 15/07/2023 à 13:44, Enrico Forestieri a écrit : It suffices replacing LYX_WARNING with AC_MSG_ERROR. However, in this case configure stops there. This is whaty we do

Re: ./configure goes through, build fails with no library

Le 15/07/2023 à 13:44, Enrico Forestieri a écrit : On Sat, Jul 15, 2023 at 01:18:36AM +0200, Jean-Marc Lasgouttes wrote: Le 15/07/2023 à 00:50, Enrico Forestieri a écrit : We want to fail in some way when there is no svg, not build without it, don't we? Yep. What about the attached?

Re: ./configure goes through, build fails with no library

Le 15/07/2023 à 00:50, Enrico Forestieri a écrit : We want to fail in some way when there is no svg, not build without it, don't we? Yep. What about the attached? This looks good (I did not try it yet). The warning at the end should be an error, right? JMarc -- lyx-devel mailing list lyx-

Re: ./configure goes through, build fails with no library

Le 14/07/2023 à 21:42, Enrico Forestieri a écrit : I see (or maybe not). Next question is: why is fake custom target names %? Because that defines a dynamic target in a makefile: https://stackoverflow.com/questions/740/what-does-a-percent-symbol-do-in-a-makefile Thanks! I still have to un

Re: ./configure goes through, build fails with no library

Le 14/07/2023 à 20:32, Enrico Forestieri a écrit : There is nothing special about naming percent a variable and that is simply done because the fake custom target is named "%". See here: https://doc.qt.io/qt-6/qmake-advanced-usage.html#adding-custom-targets I see (or maybe not). Next question

Re: ./configure goes through, build fails with no library

Le 12/07/2023 à 21:39, Enrico Forestieri a écrit : I think that the qmake code could be adapted to issue such warnings. I will have a look if nobody beats me to it. To be frank, I'd love to be able to dispose of most of the stuff in qt.m4 and rely on qmake only. I have to say though that the c

Re: ./configure goes through, build fails with no library

Le 24/05/2023 à 15:48, lorenzobertin...@gmail.com a écrit : Dear list, today I run ./configure to start a Qt6 build and it went through without problems. The build then failed with: In file included from Dialog.cpp:15: GuiView.h:25:10: fatal error: QSvgWidget: File o directory non esistente

Re: lyxerr categories

Le 11/07/2023 à 16:36, Pavel Sanda a écrit : On Thu, Jun 22, 2023 at 02:46:41PM +0200, Pavel Sanda wrote: Hi, I guess this is mainly question on JMarc... I'll commit my changes soon if there is no objection... P Sorry, I could not answer at the time, and then I forgot. Your plan looks fine

Re: Cursor Invisible on Start Up

Le 08/07/2023 à 18:19, Richard Kimberly Heck a écrit : I'm seeing an odd problem now: When I start up LyX, the cursor is not visible. This can also happen sometimes when switching back to LyX from other programs, though I can't see a pattern. I cannot reproduce. Does it help if you use "true"

Re: Unicode characters in mathed

Le 05/07/2023 à 13:39, Thibaut Cuvelier a écrit : On Sat, 1 Apr 2023, 15:10 Jean-Marc Lasgouttes, <mailto:lasgout...@lyx.org>> wrote: Hello, A relative has been using LyX recently, and it is interesting to see how the use is different from what I would do. In p

Re: Change of enchant version with bookworm

Le 03/07/2023 à 11:07, Jean-Pierre Chrétien a écrit : Dear Developers I upgraded recentlt my Debian to bookworm (aka Debian 12) and got this with all my versions of lyx: error while loading shared libraries: libenchant.so.1: cannot open shared object file: No such file or directory SEmmes

Re: [LyX/master] Fixup 7f1b1729: restore lazy caret handling

Le 25/06/2023 à 13:05, Scott Kostyshak a écrit : My main motivation is to annoy JMarc with issues that no one else notices :) And you are good at it :) Does it happens only on this line, or also at the start of the previous one? Looks like an off-by-one calculation when clearing the row. JM

Re: Compiling LyX 2.5 on macOS Sonoma

Le 21/06/2023 à 12:36, Christoph Schmitz a écrit : Hello Scott, Yes, I deleted my local repository already a few times and started from scratch. Hello, Could you please send your config.log file? JMarc These are the commands I use: cd ~/chris/Git git clone git://git.lyx.org/lyx LyX cd

Re: LyXMacros.patch for RC1 instead of rc1

Le 18/06/2023 à 22:12, Stephan Witt a écrit : Hi Kornel, I need to patch LyXMacros.patch to get a working cmake build. W/o the patch I get: CMake Error at development/cmake/modules/LyXMacros.cmake:465 (message): "/Users/stephan/git/lyx/configure.ac": Unable to determine build-type from s

Re: trac & gmail

Le 16/06/2023 à 12:17, Pavel Sanda a écrit : On Fri, Jun 16, 2023 at 06:01:48AM -0400, Scott Kostyshak wrote: On Fri, Jun 16, 2023 at 11:52:56AM +0200, Pavel Sanda wrote: On Fri, Jun 16, 2023 at 05:42:08AM -0400, Scott Kostyshak wrote: I'm still using GMail. I don't remember how I set things

Re: Crash with Insetinfo in master

Le 13/06/2023 à 19:56, Pavel Sanda a écrit : On Tue, Jun 13, 2023 at 07:45:36PM +0200, Jean-Marc Lasgouttes wrote: Le 13/06/2023 ?? 17:36, Jürgen Spitzmüller a écrit : I have no idea how to proceed, though. On my todo list I have the plan to have InsetInfo contain an InsetText object (or

Re: Font Display Problem

Le 13/06/2023 à 18:35, Pavel Sanda a écrit : Can't reproduce either. Actually what looks strange is not the size after italics but before. On my screen Footnote font has the same size as normal text. It should not, AFAIU. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.l

Re: Crash with Insetinfo in master

Le 13/06/2023 à 17:36, Jürgen Spitzmüller a écrit : I have no idea how to proceed, though. On my todo list I have the plan to have InsetInfo contain an InsetText object (or directly InsetGraphics for icons), not derive from it. I think it will make everything less hackish. JMarc -- lyx-dev

Re: Font Display Problem

Le 12/06/2023 à 19:07, Richard Kimberly Heck a écrit : The text in italics, and following that, is larger than the earlier text. (Regular size rather than footnote size.) Right, I missed that. I cannot reproduce, though. Do you have an example file or even better a recipe? I cannot reproduce

Re: 1st line of commit: "Fix #XXXX" -> "Fix " ?

Le 13/06/2023 à 10:39, Scott Kostyshak a écrit : I personally like to see a description in the first line of a Git commit message. e.g., instead of "Fix #", I'd prefer to see "Fix crash when exporting long docs". If the ticket number can be appended, and the line is still under 52 characters,

Re: LyX 2.4 Again

Le 11/06/2023 à 19:04, Richard Kimberly Heck a écrit : I'm intending to build 2.4-beta3 (I guess) early this week (other obligations having been met, at last), unless there are objections. Any? Hopefully, we can move to RC1 soon after that. Go for it. JMarc -- lyx-devel mailing list lyx-devel

Re: Allow space at beginning of (some?) insets

Le 10/06/2023 à 19:06, Daniel a écrit : On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote: Personally, I add the space before the branch. But I can see that it is mildly annoying. I am probably missing something here but I don't see how that is possible at the end of the sentence as in Sc

Re: Allow space at beginning of (some?) insets

Le 12/06/2023 à 06:34, Daniel a écrit : On 2023-06-11 18:57, Richard Kimberly Heck wrote: On 6/10/23 13:06, Daniel wrote: On 2023-06-07 16:16, Jean-Marc Lasgouttes wrote: Le 01/06/2023 à 17:42, Scott Kostyshak a écrit : I come across the example in the attachment often in various forms. It

<    1   2   3   4   5   6   7   8   9   10   >