Re: master crashes in updateMacros()
On Mon, Apr 14, 2025 at 05:43:33PM +0200, Jürgen Spitzmüller wrote: > Am Montag, dem 14.04.2025 um 17:04 +0200 schrieb Jean-Marc Lasgouttes: > > > Not for very much longer, hopefully. > > > > If I were you, I would not hold my breath. > > But I hold my breath for breakable insets! Well played! At first, JMarc makes us think that breakable insets are a reach and uncertain. Now we make him think that "OK well if you aren't going to fix the macros mess, the LEAST you could do is to implement the breakable insets" ;) Scott signature.asc Description: PGP signature -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Le 14 avril 2025 20:08:11 GMT+02:00, Richard Kimberly Heck a écrit : >Agreed, as well, though I'm curious why this machinery wouldn't be in >InsetCollapsible and so 'just work' for footnotes and branches and so forth. First, I suspect that multipar insets will be more difficult and will not make much sense. Then, I am not sure what a proper mockup would look like for a regular insetcollpsable and I propose to defer this to later. It may turn out that it is trivial, we'll see. There is also the question of whether the inner inset has an indent of even a left/right margin. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
On 4/14/25 12:39 PM, Jürgen Spitzmüller wrote: Am Montag, dem 14.04.2025 um 18:28 +0200 schrieb Jean-Marc Lasgouttes: We'll see whether this works out. What is you shopping list on this BTW? For now I am eyeing single-paragraph text insets with décoration below. Does it make sense? Yes. Most importantly I'd like to have it for all sorts of flex insets for inline markup. I use such insets particularly for csquotes (\enquote, \enquote* etc.) a lot, and having them breaking would make reading and editing so much more comfortable. I am not sure that we need this thing for footnotes. I agree. Footnotes work well without it. Agreed, as well, though I'm curious why this machinery wouldn't be in InsetCollapsible and so 'just work' for footnotes and branches and so forth. Reading this, I realize that I did not consider command insets and that I do not know how to handle them. Or whether we want to. Not urgently needed at least. Of course, having citations and (formatted) cross-references break would be nifty. But they are usually not that long to make this really something else than "nice-to-have". Also agreed. Riki -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Le 14/04/2025 à 16:23, Jean-Marc Lasgouttes a écrit : Any idea why you were doing at that time ? I'll take a look this evening. I see that it is not difficult to trigger, but I am surprised by the location. This was mainly tested with the "it still compiles" strategy. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Am Montag, dem 14.04.2025 um 18:28 +0200 schrieb Jean-Marc Lasgouttes: > We'll see whether this works out. What is you shopping list on this > BTW? For now I am eyeing single-paragraph text insets with décoration > below. Does it make sense? Yes. Most importantly I'd like to have it for all sorts of flex insets for inline markup. I use such insets particularly for csquotes (\enquote, \enquote* etc.) a lot, and having them breaking would make reading and editing so much more comfortable. > I am not sure that we need this thing for footnotes. I agree. Footnotes work well without it. > Reading this, I realize that I did not consider command insets and > that I do not know how to handle them. Or whether we want to. Not urgently needed at least. Of course, having citations and (formatted) cross-references break would be nifty. But they are usually not that long to make this really something else than "nice-to-have". > The idea is to put the rows of the nested inset as row elements of > the host inset. I see. I really hope you can make that happen. As I said earlier, I think this would be an absolute killer feature. -- Jürgen -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Le 14 avril 2025 18:15:18 GMT+02:00, Scott Kostyshak a écrit : >Well played! At first, JMarc makes us think that breakable insets are a reach >and uncertain. I will implement them. But it may be such a mess that you will beg me to revert :) >Now we make him think that "OK well if you aren't going to fix the macros >mess, the LEAST you could do is to implement the breakable insets" ;) If you fix the macro mess, I will gladly do the insets. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Le 14 avril 2025 17:43:33 GMT+02:00, "Jürgen Spitzmüller" a écrit : >Am Montag, dem 14.04.2025 um 17:04 +0200 schrieb Jean-Marc Lasgouttes: >> > Not for very much longer, hopefully. >> >> If I were you, I would not hold my breath. > >But I hold my breath for breakable insets! > >-- >Jürgen >-- >lyx-devel mailing list >[email protected] >https://lists.lyx.org/mailman/listinfo/lyx-devel We'll see whether this works out. What is you shopping list on this BTW? For now I am eyeing single-paragraph text insets with décoration below. Does it make sense? I am not sure that we need this thing for footnotes. Reading this, I realize that I did not consider command insets and that I do not know how to handle them. Or whether we want to. The idea is to put the rows of the nested inset as row elements of the host inset. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Am Montag, dem 14.04.2025 um 17:04 +0200 schrieb Jean-Marc Lasgouttes: > > Not for very much longer, hopefully. > > If I were you, I would not hold my breath. But I hold my breath for breakable insets! -- Jürgen -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Le 14/04/2025 à 16:52, Jürgen Spitzmüller a écrit : You see how I am rewarded ;) There is a 1V electric fence around this thing. Not for very much longer, hopefully. If I were you, I would not hold my breath. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Am Montag, dem 14.04.2025 um 16:23 +0200 schrieb Jean-Marc Lasgouttes: > Sigh. I really thought these did not change anything. > > Any idea why you were doing at that time ? I'll take a look this > evening. I believe it was due to a document with external references that attempted to open the referred document (on launch of LyX). Anyway, you seemed to have fixed it. > You see how I am rewarded ;) There is a 1V electric fence around > this thing. Not for very much longer, hopefully. -- Jürgen -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Le 14/04/2025 à 15:14, Jürgen Spitzmüller a écrit : Other than that, great to see you are brave enough to touch this, JMarc. Stupid error fixed now. For the record, it was in a super-safe renaming patch :-/ I am not really daring to change the macro thing. I am currently just trying to simplify and reorganize redoParagraph to prepare to breakable insets. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
Re: master crashes in updateMacros()
Le 14/04/2025 à 15:14, Jürgen Spitzmüller a écrit : after the recent macro-related commits. Sigh. I really thought these did not change anything. Any idea why you were doing at that time ? I'll take a look this evening. Other than that, great to see you are brave enough to touch this, JMarc. You see how I am rewarded ;) There is a 1V electric fence around this thing. JMarc -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
