On 3/15/23 12:46, Ehud Behar wrote:
Just created it.
The message pane says "Unknown function. Warning: unknown command
definition 'newframe'
Are you sure it is this name for the function?
Sorry, I forgot that long ago I set up the "newframe" command for this
purpose. I have the attached
Just created it.
The message pane says "Unknown function. Warning: unknown command
definition 'newframe'
Are you sure it is this name for the function?
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
On 3/15/23 11:49, Ehud Behar wrote:
I want to create a shortcut to insert the short thin red line that
separates frames when the document class is Beamer.
I know how to create shortcuts, I just don't know the name of the
"function" that actually inserts this red line.
In the lyx file this
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
I want to create a shortcut to insert the short thin red line that
separates frames when the document class is Beamer.
I know how to create shortcuts, I just don't know the name of the
"function" that actually inserts this red line.
In the lyx file this red line is called "Separator plain".
> On Tue, Mar 14, 2023 at 05:17:51PM +0100, Patrick Dupre wrote:
> > Indeed, this bug is very old 14 years!
> > Maybe it is time to fix it?
> >
> > Unfortunately, I cannot do it myself.
>
> I see that the bug claims there is a workaround, namely if you write your
> \textcolor{Gold} in normal
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
> -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
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
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}
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
On Tue, Mar 14, 2023 at 05:17:51PM +0100, Patrick Dupre wrote:
> Indeed, this bug is very old 14 years!
> Maybe it is time to fix it?
>
> Unfortunately, I cannot do it myself.
I see that the bug claims there is a workaround, namely if you write your
\textcolor{Gold} in normal text, copy it into
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
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}}}
>>
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}}
{}
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}
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 `}'
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.
>
>
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
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
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
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
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).
>
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 someone have an idea how the error occurred or how I might
24 matches
Mail list logo
