Re: Problem with Noun text in Beamer titles

On Tue, Apr 19, 2022 at 02:56:41PM -0400, Bruce Momjian wrote: > I am using LyX 2.3.4.2 on Ubuntu, but this bug goes back many years. > > I have found that if I am using the Beamer document class, and a > non-default/non-blue Latex text color for PDF output, if I add text to > an existing title by

Problem with Noun text in Beamer titles

I am using LyX 2.3.4.2 on Ubuntu, but this bug goes back many years. I have found that if I am using the Beamer document class, and a non-default/non-blue Latex text color for PDF output, if I add text to an existing title by first enabling Noun mode, and then typing, the text looks fine in LyX.

Re: [LyX/master] Update sk.po

Am Tue, 19 Apr 2022 13:57:17 +0200 schrieb Jürgen Spitzmüller : > terse OK, msgid "Find and replace mechanism, terse version" feels better anyway. Please proceed. Kornel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel pgpJEaKk

Re: [LyX/master] Update sk.po

Am Dienstag, dem 19.04.2022 um 13:16 +0200 schrieb Kornel Benko: > +msgid "Find and replace mechanism, short version" I'd say the antonym of "verbose" is "terse". Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http:/

Re: Expand debug to contain more than 31 cases

Am Tue, 19 Apr 2022 13:05:37 +0200 schrieb Jean-Marc Lasgouttes : > Le 19/04/2022 à 11:07, Kornel Benko a écrit : > >> Besides the discussion of FINDSHORT, I do not think that size_t is a > >> good type, since the only guarantee is that it is more than 16 bits > >> (even on 32bit architectures, it

Re: features/indexmacros

Am Dienstag, dem 19.04.2022 um 13:21 +0200 schrieb Jürgen Spitzmüller: > This adds native macros for subindexes (!level), |see and |seealso and sort keys (sort@key), for that matter. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@l

features/indexmacros

FYI: I have now pushed my current work on index macros to the new features/features/indexmacros branch. This does: Introduce InsetIndexMacros This adds native macros for subindexes (!level), |see and |seealso as well as native support for ranges |( |) and pagination format -- e.g., |textbf -- v

Re: Expand debug to contain more than 31 cases

Le 19/04/2022 à 11:12, Kornel Benko a écrit : I am not sure that we need a verbose level yet. What about -dbg find => FINDSHORT -dbg find --verbose => FIND JMarc I propose to do it as a next step. Better not too many changes at once IMO. As you prefer. JMarc -- lyx-devel mailing list lyx-de

Re: Expand debug to contain more than 31 cases

Le 19/04/2022 à 11:07, Kornel Benko a écrit : Besides the discussion of FINDSHORT, I do not think that size_t is a good type, since the only guarantee is that it is more than 16 bits (even on 32bit architectures, it is probably 32 bits). int64_t is probably what you are after. Yes. I had the (a

Re: Expand debug to contain more than 31 cases

Am Tue, 19 Apr 2022 10:53:40 +0200 schrieb Jean-Marc Lasgouttes : > Le 19/04/2022 à 10:08, Kornel Benko a écrit : > >> We do > >> currently have a "--verbose" but what I mean is to change "--verbose" to > >> accept a "" argument that determines how verbose the debug output > >> is. So this way,

Re: Expand debug to contain more than 31 cases

Am Tue, 19 Apr 2022 10:51:14 +0200 schrieb Jean-Marc Lasgouttes : > Le 18/04/2022 à 12:21, Kornel Benko a écrit : > > The output while debugging findadv is overwhelming, but sometimes > > one needs only a small subset. Therefore the addition of -dbg findshort. > > Besides the discussion of FIND

Re: Expand debug to contain more than 31 cases

Le 19/04/2022 à 10:08, Kornel Benko a écrit : We do currently have a "--verbose" but what I mean is to change "--verbose" to accept a "" argument that determines how verbose the debug output is. So this way, "lyx --debug find --verbose 1" would give the same output as "FIND", and "lyx --debug f

Re: Expand debug to contain more than 31 cases

Le 18/04/2022 à 12:21, Kornel Benko a écrit : The output while debugging findadv is overwhelming, but sometimes one needs only a small subset. Therefore the addition of -dbg findshort. Besides the discussion of FINDSHORT, I do not think that size_t is a good type, since the only guarantee is t

Re: Expand debug to contain more than 31 cases

Am Mon, 18 Apr 2022 21:22:41 -0400 schrieb Scott Kostyshak : > On Mon, Apr 18, 2022 at 12:21:40PM +0200, Kornel Benko wrote: > > The output while debugging findadv is overwhelming, but sometimes > > one needs only a small subset. Therefore the addition of -dbg findshort. > > > > Also it would be