Re: Broken document

Am Freitag, dem 17.03.2023 um 11:26 +0100 schrieb Jürgen Spitzmüller: > Seems like the refstyle author has been made aware of the problem, > but it is unknown whether he is still willing to take care of the > package. FWIW I have contacted him, and he immediately responded and proposed to take

Re: Broken document

Am Mittwoch, dem 15.03.2023 um 16:54 +0200 schrieb Udicoudco: > You get the error because you load amsmath (it is loaded via > newtxmath) before refstyle. See the attached .tex file which produces > the same error.  If you will load newtxmath via Document->Settings- > >Latex Preamble and set the

Re: Broken document

Daniel said on Thu, 16 Mar 2023 08:18:33 +0100 >Thanks, awesome! > >Maybe a solution would be if LyX loads fonts later in general? Or >would that lead to other problems? Of course the later font load might screw up other things, and would certainly need to be done before things start getting

Re: Broken document

On my Ventura M2 with 2.3.7 and TexLive 2022 it does reporduce. el On 15/03/2023 09:42, Stephan Witt wrote: > Am 15.03.2023 um 14:34 schrieb Daniel : >> >> On 15/03/2023 14:28, Eckhard Höffner wrote: >>> That's another possible LyX specific cause: >>> \makeatletter >>>

Re: Broken document

On 16/03/2023 10:39, Udicoudco wrote: On Thu, Mar 16, 2023 at 11:13 AM Daniel wrote: On 16/03/2023 08:18, Daniel wrote: On 15/03/2023 15:54, Udicoudco wrote: On Wed, Mar 15, 2023 at 10:57 AM Daniel mailto:xraco...@gmx.de>> wrote: Hi! I somehow managed to break one of my

Re: Broken document

On Thu, Mar 16, 2023 at 11:13 AM Daniel wrote: > > On 16/03/2023 08:18, Daniel wrote: > > On 15/03/2023 15:54, Udicoudco wrote: > >> > >> > >> On Wed, Mar 15, 2023 at 10:57 AM Daniel >> > wrote: > >> > >> Hi! > >> > >> I somehow managed to break one of my

Re: Broken document

On 16/03/2023 08:18, Daniel wrote: On 15/03/2023 15:54, Udicoudco wrote: On Wed, Mar 15, 2023 at 10:57 AM Daniel > wrote:     Hi!     I somehow managed to break one of my documents and cannot see where the     problem is. I have attached a minimal example that I

Re: Broken document

On 15/03/2023 15:54, Udicoudco wrote: On Wed, Mar 15, 2023 at 10:57 AM Daniel > wrote: Hi! I somehow managed to break one of my documents and cannot see where the problem is. I have attached a minimal example that I produced after a longer error hunt

Re: Broken document

On Wed, Mar 15, 2023 at 4:54 PM Udicoudco wrote: > > > On Wed, Mar 15, 2023 at 10:57 AM Daniel wrote: > >> Hi! >> >> I somehow managed to break one of my documents and cannot see where the >> problem is. I have attached a minimal example that I produced after a >> longer error hunt (because LyX

Re: Broken document

On 15/03/2023 14:55, Scott Kostyshak wrote: On Wed, Mar 15, 2023 at 01:17:33PM +0100, Daniel wrote: On 15/03/2023 12:18, Axel Dessecker via lyx-users wrote: Am Mittwoch, 15. März 2023, 12:05:24 CET schrieb Eckhard Höffner: Accroding to the log, the error ist in refstyle.cfg ! Argument of

RE: Broken document

> -Oorspronkelijk bericht- > Van: lyx-users Namens Daniel > Verzonden: woensdag 15 maart 2023 09:57 > Aan: lyx-users@lists.lyx.org > Onderwerp: Broken document > > Hi! > > I somehow managed to break one of my documents and cannot see where > the problem is. I have attached a minimal

Re: Broken document

On Wed, Mar 15, 2023 at 10:57 AM Daniel wrote: > Hi! > > I somehow managed to break one of my documents and cannot see where the > problem is. I have attached a minimal example that I produced after a > longer error hunt (because LyX did not give me helpful error feedback on > this). > > Does

Re: Broken document

I can reproduce the error. I have TeX Live (https://tug.org/texlive) version 2022. But refstyle.cfg and refstyle.sty haven't changed since 2010 (according to the files). That's what  Lyx produces, if refstyle is used: \documentclass[british]{article}

Re: Broken document

On Wed, Mar 15, 2023 at 01:17:33PM +0100, Daniel wrote: > On 15/03/2023 12:18, Axel Dessecker via lyx-users wrote: > > Am Mittwoch, 15. März 2023, 12:05:24 CET schrieb Eckhard Höffner: > > > Accroding to the log, the error ist in refstyle.cfg > > > > > > > > > ! Argument of \eqref has an extra

Re: Broken document

Yes. That's part of the log file: Package refstyle Info: \eqlabel created on input line 526. Package refstyle Info: \eqref created on input line 526. ! Argument of \eqref has an extra }. \par l.526 lsttxt = \RSlsttxt} I've run across a `}' that doesn't seem to match anything. For

Re: Broken document

Am 15.03.2023 um 14:34 schrieb Daniel : > > On 15/03/2023 14:28, Eckhard Höffner wrote: >> That's another possible LyX specific cause: >> \makeatletter >> %% LyX specific LaTeX commands. >> \AtBeginDocument{\providecommand\figref[1]{\ref{fig:#1}}} >>

Re: Broken document

On 15/03/2023 14:28, Eckhard Höffner wrote: That's another possible LyX specific cause: \makeatletter %% LyX specific LaTeX commands. \AtBeginDocument{\providecommand\figref[1]{\ref{fig:#1}}} \RS@ifundefined{subsecref}   {\newref{subsec}{name = \RSsectxt}}   {}

Re: Broken document

That's another possible LyX specific cause: \makeatletter %% LyX specific LaTeX commands. \AtBeginDocument{\providecommand\figref[1]{\ref{fig:#1}}} \RS@ifundefined{subsecref}   {\newref{subsec}{name = \RSsectxt}}   {} \RS@ifundefined{thmref}  

Re: Broken document

On 15/03/2023 12:18, Axel Dessecker via lyx-users wrote: Am Mittwoch, 15. März 2023, 12:05:24 CET schrieb Eckhard Höffner: Accroding to the log, the error ist in refstyle.cfg ! Argument of \eqref has an extra }. \par l.526lsttxt= \RSlsttxt} I've run across a `}'

Re: Broken document

Am Mittwoch, 15. März 2023, 12:05:24 CET schrieb Eckhard Höffner: > Accroding to the log, the error ist in refstyle.cfg > > > ! Argument of \eqref has an extra }. > > \par > l.526lsttxt= \RSlsttxt} > > I've run across a `}' that doesn't seem to match anything. > >

Re: Broken document

Accroding to the log, the error ist in refstyle.cfg ! Argument of \eqref  has an extra }.     \par l.526    lsttxt    = \RSlsttxt} I've run across a `}' that doesn't seem to match anything. Runaway argument? ! Paragraph ended before \eqref  was complete.    \par

Re: Broken document

On 15/03/2023 10:56, Axel Dessecker via lyx-users wrote: Am Mittwoch, 15. März 2023, 10:49:33 CET schrieb Daniel: On 15/03/2023 10:37, Axel Dessecker via lyx-users wrote: Am Mittwoch, 15. März 2023, 09:57:13 CET schrieb Daniel: Hi! I somehow managed to break one of my documents and cannot

Re: Broken document

Am Mittwoch, 15. März 2023, 10:49:33 CET schrieb Daniel: > On 15/03/2023 10:37, Axel Dessecker via lyx-users wrote: > > Am Mittwoch, 15. März 2023, 09:57:13 CET schrieb Daniel: > >> Hi! > >> > >> I somehow managed to break one of my documents and cannot see where the > >> problem is. I have

Re: Broken document

On 15/03/2023 10:37, Axel Dessecker via lyx-users wrote: Am Mittwoch, 15. März 2023, 09:57:13 CET schrieb Daniel: Hi! I somehow managed to break one of my documents and cannot see where the problem is. I have attached a minimal example that I produced after a longer error hunt (because LyX did

Re: Broken document

Am Mittwoch, 15. März 2023, 09:57:13 CET schrieb Daniel: > Hi! > > I somehow managed to break one of my documents and cannot see where the > problem is. I have attached a minimal example that I produced after a > longer error hunt (because LyX did not give me helpful error feedback on > this). >