On Sat, 24 Dec 2022 at 03:49, Scott Kostyshak wrote:
> On Fri, Dec 23, 2022 at 01:00:59AM +0100, Thibaut Cuvelier wrote:
> > On Mon, 21 Nov 2022 at 08:56, Kornel Benko wrote:
> >
> > > Am Sun, 20 Nov 2022 15:23:58 -0500
> > > schrieb Scott Kostyshak :
> > >
> > > > On Sun, Nov 20, 2022 at 08:24:
On Fri, Dec 23, 2022 at 01:00:59AM +0100, Thibaut Cuvelier wrote:
> On Mon, 21 Nov 2022 at 08:56, Kornel Benko wrote:
>
> > Am Sun, 20 Nov 2022 15:23:58 -0500
> > schrieb Scott Kostyshak :
> >
> > > On Sun, Nov 20, 2022 at 08:24:41PM +0100, Thibaut Cuvelier wrote:
> > > > On Sun, 20 Nov 2022 at 1
On Mon, 21 Nov 2022 at 08:56, Kornel Benko wrote:
> Am Sun, 20 Nov 2022 15:23:58 -0500
> schrieb Scott Kostyshak :
>
> > On Sun, Nov 20, 2022 at 08:24:41PM +0100, Thibaut Cuvelier wrote:
> > > On Sun, 20 Nov 2022 at 16:47, Scott Kostyshak
> wrote:
> > >
> > > > On Sun, Nov 20, 2022 at 04:33:36PM
Am Sun, 20 Nov 2022 15:23:58 -0500
schrieb Scott Kostyshak :
> On Sun, Nov 20, 2022 at 08:24:41PM +0100, Thibaut Cuvelier wrote:
> > On Sun, 20 Nov 2022 at 16:47, Scott Kostyshak wrote:
> >
> > > On Sun, Nov 20, 2022 at 04:33:36PM +0100, Thibaut Cuvelier wrote:
> > > > > When I open the expo
On Sun, Nov 20, 2022 at 08:24:41PM +0100, Thibaut Cuvelier wrote:
> On Sun, 20 Nov 2022 at 16:47, Scott Kostyshak wrote:
>
> > On Sun, Nov 20, 2022 at 04:33:36PM +0100, Thibaut Cuvelier wrote:
> > > > When I open the exported de Math.xhtml in Chromium, I get:
> > > >
> > > > "error on line 7159
On Sun, 20 Nov 2022 at 16:47, Scott Kostyshak wrote:
> On Sun, Nov 20, 2022 at 04:33:36PM +0100, Thibaut Cuvelier wrote:
> > > When I open the exported de Math.xhtml in Chromium, I get:
> > >
> > > "error on line 7159 at column 22: Entity 'imaginary' not defined"
> > >
> >
> > That's unrelated
On Sun, Nov 20, 2022 at 04:33:36PM +0100, Thibaut Cuvelier wrote:
> > > (I don't get how to configure CTest to use my version of
> > > Python, hence it fails in strange ways).
> >
> > Let's try to figure out how to fix this.
> >
> > Is it only a problem with the ctests? Meaning, LyX uses your versi
On Sun, 20 Nov 2022 at 16:18, Scott Kostyshak wrote:
> On Sun, Nov 20, 2022 at 03:29:37PM +0100, Thibaut Cuvelier wrote:
> > On Fri, 4 Nov 2022 at 01:59, Scott Kostyshak wrote:
> >
> > > On Thu, Nov 03, 2022 at 10:04:31PM +0100, Thibaut Cuvelier wrote:
> > > > On Thu, 3 Nov 2022 at 21:27, Scott
On Sun, Nov 20, 2022 at 03:29:37PM +0100, Thibaut Cuvelier wrote:
> On Fri, 4 Nov 2022 at 01:59, Scott Kostyshak wrote:
>
> > On Thu, Nov 03, 2022 at 10:04:31PM +0100, Thibaut Cuvelier wrote:
> > > On Thu, 3 Nov 2022 at 21:27, Scott Kostyshak wrote:
> > >
> > > > On Mon, Oct 31, 2022 at 11:38:46
On Fri, 4 Nov 2022 at 01:59, Scott Kostyshak wrote:
> On Thu, Nov 03, 2022 at 10:04:31PM +0100, Thibaut Cuvelier wrote:
> > On Thu, 3 Nov 2022 at 21:27, Scott Kostyshak wrote:
> >
> > > On Mon, Oct 31, 2022 at 11:38:46PM -0400, Scott Kostyshak wrote:
> > > > On Tue, Nov 01, 2022 at 12:01:47AM +0
On Thu, Nov 03, 2022 at 08:59:27PM -0400, Scott Kostyshak wrote:
> On Thu, Nov 03, 2022 at 10:04:31PM +0100, Thibaut Cuvelier wrote:
> > On Thu, 3 Nov 2022 at 21:27, Scott Kostyshak wrote:
> >
> > > On Mon, Oct 31, 2022 at 11:38:46PM -0400, Scott Kostyshak wrote:
> > > > On Tue, Nov 01, 2022 at 1
On Thu, Nov 03, 2022 at 10:04:31PM +0100, Thibaut Cuvelier wrote:
> On Thu, 3 Nov 2022 at 21:27, Scott Kostyshak wrote:
>
> > On Mon, Oct 31, 2022 at 11:38:46PM -0400, Scott Kostyshak wrote:
> > > On Tue, Nov 01, 2022 at 12:01:47AM +0100, Thibaut Cuvelier wrote:
> > > > On Mon, 31 Oct 2022 at 21:
On Thu, 3 Nov 2022 at 21:27, Scott Kostyshak wrote:
> On Mon, Oct 31, 2022 at 11:38:46PM -0400, Scott Kostyshak wrote:
> > On Tue, Nov 01, 2022 at 12:01:47AM +0100, Thibaut Cuvelier wrote:
> > > On Mon, 31 Oct 2022 at 21:12, Jürgen Spitzmüller
> wrote:
> > >
> > > > Am Montag, dem 31.10.2022 um
On Mon, Oct 31, 2022 at 11:38:46PM -0400, Scott Kostyshak wrote:
> On Tue, Nov 01, 2022 at 12:01:47AM +0100, Thibaut Cuvelier wrote:
> > On Mon, 31 Oct 2022 at 21:12, Jürgen Spitzmüller wrote:
> >
> > > Am Montag, dem 31.10.2022 um 14:58 -0400 schrieb Scott Kostyshak:
> > > > I get the following
On Tue, Nov 01, 2022 at 09:12:41AM +0100, Jürgen Spitzmüller wrote:
> Am Montag, dem 31.10.2022 um 16:07 -0400 schrieb Scott Kostyshak:
> > I get the following:
> >
> > The following tests FAILED:
>
> Also after 3c488c22e1d86?
The tex2lyx tests all pass now. I sent my message accidentally from m
Am Montag, dem 31.10.2022 um 16:07 -0400 schrieb Scott Kostyshak:
> I get the following:
>
> The following tests FAILED:
Also after 3c488c22e1d86?
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Tue, Nov 01, 2022 at 12:01:47AM +0100, Thibaut Cuvelier wrote:
> On Mon, 31 Oct 2022 at 21:12, Jürgen Spitzmüller wrote:
>
> > Am Montag, dem 31.10.2022 um 14:58 -0400 schrieb Scott Kostyshak:
> > > I get the following warning:
> > >
> > > /home/scott/lyxbuilds/master-
> > > master/repo/src/in
On Mon, 31 Oct 2022 at 21:12, Jürgen Spitzmüller wrote:
> Am Montag, dem 31.10.2022 um 14:58 -0400 schrieb Scott Kostyshak:
> > I get the following warning:
> >
> > /home/scott/lyxbuilds/master-
> > master/repo/src/insets/InsetIndex.cpp:1691:6: error: function
> > 'printTree' is not needed and wi
On Mon, Oct 31, 2022 at 06:40:15PM +0100, Juergen Spitzmueller wrote:
> commit 4e50da3e655b9f8d26f7d5e439d72b219d32279d
> Merge: 0df63e3 f4d588c
> Author: Juergen Spitzmueller
> Date: Mon Oct 31 19:32:52 2022 +0100
>
> Merge branch 'features/indexmacros'
&
Am Montag, dem 31.10.2022 um 14:58 -0400 schrieb Scott Kostyshak:
> I get the following warning:
>
> /home/scott/lyxbuilds/master-
> master/repo/src/insets/InsetIndex.cpp:1691:6: error: function
> 'printTree' is not needed and will not be emitted [-Werror,-
> Wunneeded-internal-declaration]
> void
Oct 31 19:32:52 2022 +0100
> >
> > Merge branch 'features/indexmacros'
> >
>
> I get the following warning:
>
> /home/scott/lyxbuilds/master-master/repo/src/insets/InsetIndex.cpp:1691:6:
> error: function 'printTree' is not needed and will not be emit
On Mon, Oct 31, 2022 at 06:40:15PM +0100, Juergen Spitzmueller wrote:
> commit 4e50da3e655b9f8d26f7d5e439d72b219d32279d
> Merge: 0df63e3 f4d588c
> Author: Juergen Spitzmueller
> Date: Mon Oct 31 19:32:52 2022 +0100
>
> Merge branch 'features/indexmacros'
>
Am Thu, 1 Sep 2022 01:34:43 +0200 (CEST)
schrieb Thibaut Cuvelier :
> The branch, features/indexmacros, has been updated.
>
> - Log -
>
> commit 92ba7584415cacbea639dbca0199c9fd510ca617
> Author: Thibaut Cuvel
Am Donnerstag, dem 05.05.2022 um 04:27 +0200 schrieb Thibaut Cuvelier:
> I've pushed my refactoring of the XHTML output. According to my
> tests, it is functionally equivalent to the previous code, but with
> cleaner XHTML output (new lines, use of dashes for
> internationalisation).
> Also, I bel
On Mon, 25 Apr 2022 at 07:43, Jürgen Spitzmüller wrote:
> Am Montag, dem 25.04.2022 um 02:43 +0200 schrieb Thibaut Cuvelier:
> > I have pushed a slightly revised patch to your branch with the
> > DocBook implementation. I'm now having a look at the XHTML one, in
> > particular to share some code
Am Montag, dem 25.04.2022 um 02:43 +0200 schrieb Thibaut Cuvelier:
> I have pushed a slightly revised patch to your branch with the
> DocBook implementation. I'm now having a look at the XHTML one, in
> particular to share some code between the two.
Great!
--
Jürgen
signature.asc
Description:
On Fri, 22 Apr 2022 at 13:14, Jürgen Spitzmüller wrote:
> Am Freitag, dem 22.04.2022 um 09:01 +0200 schrieb Jürgen Spitzmüller:
> > > Also, I'm assuming that the user either uses the new insets or the
> > > old, pure LaTeX way of doing index, not a mix of both. Does this
> > > make
> > > sense?
>
Am Freitag, dem 22.04.2022 um 09:01 +0200 schrieb Jürgen Spitzmüller:
> > Also, I'm assuming that the user either uses the new insets or the
> > old, pure LaTeX way of doing index, not a mix of both. Does this
> > make
> > sense?
>
> With LaTeX, both methods can be used in parallel, which might be
Am Freitag, dem 22.04.2022 um 03:49 +0200 schrieb Thibaut Cuvelier:
> Code-wise, the design looks really clean!
Thanks.
> Also, I'm assuming that the user either uses the new insets or the
> old, pure LaTeX way of doing index, not a mix of both. Does this make
> sense?
With LaTeX, both methods
On Tue, 19 Apr 2022 at 13:29, Jürgen Spitzmüller wrote:
> 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.
>
Code-wise, the design looks really clean! The D
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
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
32 matches
Mail list logo