On Thu, Jul 03, 2025 at 03:13:44PM +0200, Jean-Marc Lasgouttes wrote:
> Le 03/07/2025 à 13:17, Scott Kostyshak a écrit :
>
> > > > #if defined(USE__func__) && USE__func__
> > >
> > > I removed the use of USE__func__. Nothing of value has been lost.
> >
> > Great! That warning's gone now. Only re
Le 03/07/2025 à 13:17, Scott Kostyshak a écrit :
#if defined(USE__func__) && USE__func__
I removed the use of USE__func__. Nothing of value has been lost.
Great! That warning's gone now. Only remaining one is:
src/support/FileName.cpp:687:7: warning: 'MKDIR_TAKES_ONE_ARG' is not
defined
On Thu, Jul 03, 2025 at 12:29:59PM +0200, Jean-Marc Lasgouttes wrote:
> Le 03/07/2025 à 12:17, Kornel Benko a écrit :
> > Am Thu, 3 Jul 2025 12:06:42 +0200
> > schrieb Scott Kostyshak :
> >
> > > I get multiple warnings (from GCC and Clang) when compiling with -Wundef
> > > about two main issues:
Le 03/07/2025 à 12:17, Kornel Benko a écrit :
Am Thu, 3 Jul 2025 12:06:42 +0200
schrieb Scott Kostyshak :
I get multiple warnings (from GCC and Clang) when compiling with -Wundef
about two main issues:
src/support/FileName.cpp:687:7: warning: 'MKDIR_TAKES_ONE_ARG' is not
defined,
evaluates
Am Thu, 3 Jul 2025 12:06:42 +0200
schrieb Scott Kostyshak :
> I get multiple warnings (from GCC and Clang) when compiling with -Wundef
> about two main issues:
>
> src/support/FileName.cpp:687:7: warning: 'MKDIR_TAKES_ONE_ARG' is not
> defined,
> evaluates to 0 [-Wundef] src/tests/../support/d
I get multiple warnings (from GCC and Clang) when compiling with -Wundef
about two main issues:
src/support/FileName.cpp:687:7: warning: 'MKDIR_TAKES_ONE_ARG' is not
defined, evaluates to 0 [-Wundef]
src/tests/../support/debug.h:221:5: warning: 'USE__func__' is not defined,
evaluates to 0 [-
Am Fri, 10 Nov 2023 14:40:01 +0100
schrieb Jean-Marc Lasgouttes :
> Le 10/11/2023 à 13:24, Kornel Benko a écrit :
> > Thanks, but
> > /usr2/src/lyx/lyx-git/src/Mover.h:18:10: fatal error:
> > support/mute_warning.h: No such
> > file or directory 18 | #include "support/mute_warning.h"
> >|
Le 10/11/2023 à 13:24, Kornel Benko a écrit :
Thanks, but
/usr2/src/lyx/lyx-git/src/Mover.h:18:10: fatal error: support/mute_warning.h:
No such
file or directory 18 | #include "support/mute_warning.h"
| ^~~~
Kornel
Sigh. Fixed now.
JMarc
--
lyx-de
Am Fri, 10 Nov 2023 13:16:35 +0100
schrieb Jean-Marc Lasgouttes :
> Le 10/11/2023 à 12:58, Kornel Benko a écrit :
> >
> > This of course breaks the compilation.
> >
> > Please do not add new stuff at this stage.
> >
> > Would it be possible to add the definitions into some header file instead?
Le 10/11/2023 à 12:58, Kornel Benko a écrit :
This of course breaks the compilation.
Please do not add new stuff at this stage.
Would it be possible to add the definitions into some header file instead?
Sorry, I did not think of this (better) possibility.
Done now.
JMarc
--
lyx-devel mail
This of course breaks the compilation.
Please do not add new stuff at this stage.
Would it be possible to add the definitions into some header file instead?
Kornel
pgpKxQrxIxltt.pgp
Description: Digitale Signatur von OpenPGP
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://li
On Sat, 22 Jul 2023 at 00:00, Jean-Marc Lasgouttes
wrote:
> Le 18/07/2023 à 15:11, Jean-Marc Lasgouttes a écrit :
> > Hello,
> >
> > In the attached patch, I am able to support the mod/bmod/pmod/pod macros
> > by just defining them in lib/symbols with an argument.
&
Le 18/07/2023 à 15:11, Jean-Marc Lasgouttes a écrit :
Hello,
In the attached patch, I am able to support the mod/bmod/pmod/pod macros
by just defining them in lib/symbols with an argument.
The result is a more pleasing editing process (IMO) and a simplification
of the documentation.
It is
rit :
> > > Also, we already have macros with parameters:
> > > https://github.com/cburschka/lyx/blob/master/lib/symbols#L1223
> > <https://github.com/cburschka/lyx/blob/master/lib/symbols#L1223>
> > > <https://github.com/cburschka/lyx/b
Le 18/07/2023 à 16:47, Thibaut Cuvelier a écrit :
On Tue, 18 Jul 2023 at 16:04, Jean-Marc Lasgouttes <mailto:lasgout...@lyx.org>> wrote:
Le 18/07/2023 à 15:54, Thibaut Cuvelier a écrit :
> Also, we already have macros with parameters:
> https://github.com/cburschka/
On Tue, 18 Jul 2023 at 16:04, Jean-Marc Lasgouttes
wrote:
> Le 18/07/2023 à 15:54, Thibaut Cuvelier a écrit :
> > Also, we already have macros with parameters:
> > https://github.com/cburschka/lyx/blob/master/lib/symbols#L1223
> > <https://github.com/cburschka/lyx/blob/
Le 18/07/2023 à 15:54, Thibaut Cuvelier a écrit :
Also, we already have macros with parameters:
https://github.com/cburschka/lyx/blob/master/lib/symbols#L1223
<https://github.com/cburschka/lyx/blob/master/lib/symbols#L1223>
Indeed. I'm the one who pushed that, but it did not impres
On Tue, 18 Jul 2023 at 15:45, Jean-Marc Lasgouttes
wrote:
> Le 18/07/2023 à 15:36, Thibaut Cuvelier a écrit :
> > For the symbols in your patch, yes, export is currently broken, but it's
> > fixable.
> > I think it would still be fixable in the future with mac
Le 18/07/2023 à 15:36, Thibaut Cuvelier a écrit :
For the symbols in your patch, yes, export is currently broken, but it's
fixable.
I think it would still be fixable in the future with macros, as I did in
https://github.com/cburschka/lyx/blob/master/lib/symbols#L1128
<https://gi
On Tue, 18 Jul 2023 at 15:11, Jean-Marc Lasgouttes
wrote:
> Hello,
>
> In the attached patch, I am able to support the mod/bmod/pmod/pod macros
> by just defining them in lib/symbols with an argument.
>
> The result is a more pleasing editing process (IMO) and a simpl
Hello,
In the attached patch, I am able to support the mod/bmod/pmod/pod macros
by just defining them in lib/symbols with an argument.
The result is a more pleasing editing process (IMO) and a simplification
of the documentation.
Since this use of \def is not documented, I have to ask: is
On Sat, Jun 23, 2018 at 07:08:52AM +0200, Kornel Benko wrote:
> Am Samstag, 23. Juni 2018 00:36:16 CEST schrieb Richard Kimberly Heck
> :
> > The attached file gives me spacing errors.
> >
> > Riki
> >
>
> Confirmed.
> The first entered character inside the \tmp-parameter looks wrong.
I can't
Am Samstag, 23. Juni 2018 00:36:16 CEST schrieb Richard Kimberly Heck
:
> The attached file gives me spacing errors.
>
> Riki
>
Confirmed.
The first entered character inside the \tmp-parameter looks wrong.
Kornel
signature.asc
Description: This is a digitally signed messag
The attached file gives me spacing errors.
Riki
spacing.lyx
Description: application/lyx
Am Sonntag, den 17.12.2017, 12:45 +0100 schrieb Kornel Benko:
> > + } else if ((!runparams.use_babel
> > #endif
> > + || fontenc_ != "T1" || fontenc_ != "OT1")
>
> This one is always true...
Indeed. Thanks!
Jürgen
signature.asc
Description: This is a digitally signed mes
ullUnicode()) {
> + } else if ((!runparams.use_babel
> #endif
> + || fontenc_ != "T1" || fontenc_ != "OT1")
This one is always true...
Did you mean && instead?
> + || runparams.isFullUnicode()) {
>
providecommand for logical markup macros
>>
>> \strong is already defined by recent fontspec.
>>
>> Also use non-long definition (starred version), since the insets
>> only contain one paragraph.
> This should also go to stable.
OK.
rh
Am Freitag, den 17.02.2017, 08:37 +0100 schrieb Juergen Spitzmueller:
> commit 1db9b50407d109d0516b047ba174b74c49486df1
> Author: Juergen Spitzmueller
> Date: Fri Feb 17 08:35:41 2017 +0100
>
> Use \providecommand for logical markup macros
>
> \strong is alre
On 01/17/2017 06:06 PM, חיים רוזנר wrote:
> Hi,
> I upgraded lyx 2.1 to lyx 2.2 (Win 10). I have a file with lots of
> tikz environments and some math macros. The convertor took the -- line
> command of tikz in the math macro and converted it to \twohyphens.
> This conversion
Hi,
I upgraded lyx 2.1 to lyx 2.2 (Win 10). I have a file with lots of tikz
environments and some math macros. The convertor took the -- line command
of tikz in the math macro and converted it to \twohyphens. This conversion
made me errors.
Attached are a minimal example from LyX 2.1 and its
Dear LyXers,
when the font encoding is switched from T1 (LuX's default) to the legacy
7-bit encoding OT1 (TeX's default), default fonts look better on screen as
the real default (Computer Modern) is used instead of the bitmap
substitution EC.
However, with OT1, hyphenation is wrong in most langua
On Sun, Dec 04, 2016 at 12:22:23AM -0500, Richard Heck wrote:
>
> Looks good to me.
Committed at 9435dd6b.
--
Enrico
On 12/02/2016 07:05 PM, Enrico Forestieri wrote:
> On Fri, Dec 02, 2016 at 12:27:03AM +0100, Enrico Forestieri wrote:
>> On Thu, Dec 01, 2016 at 04:31:44PM -0500, Richard Heck wrote:
>>> I'm no expert on this part of the code, but this doesn't look too
>>> dangerous. Since 2.2.3 is still a little w
macro_);
+ // We may already be in the argument of a macro
+ bool const inside_macro = os.insideMacro();
+ os.insideMacro(true);
+
+ // Enclose in braces to avoid latex errors with xargs if we have
+ // optional arguments and are in the optional argument of a
acro
+ bool const inside_macro = os.insideMacro();
+ os.insideMacro(true);
+
+ // Enclose in braces to avoid latex errors with xargs if we have
+ // optional arguments and are in the optional argument of a macro
+ if (d->optionals_ && inside_macro)
+ os << '{';
+
// Al
nrico Forestieri
> Date: Thu Dec 1 18:02:47 2016 +0100
>
> Fix display and output of math macros with optional arguments
>
> This is a long standing issue, present since the new math macros
> inception in version 1.6. It manifests as a display issue when a
> mac
t print useless messages while parsing math macros
> >
> > Math macros can be displayed on screen by providing a different
> > representation than the one used for latex output. This representation is
> > actually used by lyx even while it is being updated.
>
>
On 10/31/2016 10:24 AM, Enrico Forestieri wrote:
> commit e3c3719643c46819aa586346a313d514c5903898
> Author: Enrico Forestieri
> Date: Mon Oct 31 15:23:20 2016 +0100
>
> Don't print useless messages while parsing math macros
>
> Math macros can be displaye
Le 25/09/2016 à 20:37, Enrico Forestieri a écrit :
commit 6642152e6610f1e885babfaeb3c99bd0004916fc
Author: Enrico Forestieri
Date: Sun Sep 25 20:31:13 2016 +0200
Do not rely on math macros being updated
Trying to spare a few cycles by avoiding computing metrics during
screen
On 2015-06-16, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> 2015-06-16 15:45 GMT+02:00 Guenter Milde:
>> Dear LyX developers,
>> some LICR (LaTeX internal character representation) macros require
>> termination by a {}, so th
2015-06-16 15:45 GMT+02:00 Guenter Milde:
> Dear LyX developers,
>
> some LICR (LaTeX internal character representation) macros require
> termination by a {}, so that the macro name can be separated from the
> following text.
>
> Example: "\\OE", e.g. used in \OE
Dear LyX developers,
some LICR (LaTeX internal character representation) macros require
termination by a {}, so that the macro name can be separated from the
following text.
Example: "\\OE", e.g. used in \OE{}vre
However, "lib/unicodesymbols" has also replacement c
Am Mittwoch, 29. April 2015 um 10:15:54, schrieb LyX Ticket Tracker
> #6369: InstantPreview multiplies math macros definitions
> ---+-
> Reporter: sanda | Owner: lasgouttes
> Type: defect | Statu
Richard Heck wrote:
> You know what would be really cool? The ability to custom-define default
> macros in a module, including ones with arguments.
Yes. And I guess it would not be difficult to implement. If I find some time
I might at least extend lib/symbols to support macros with arg
a way to define a set of default macros that are known to LyX
from start. Then the macro inset machinery would be sue for the display
part.
What do the others think?
Something like a set of default macros is already implemented. It is read
from lib/symbols (where \pmod is already defined, that is
have a way to define a set of default macros that are known to LyX
> from start. Then the macro inset machinery would be sue for the display
> part.
>
> What do the others think?
Something like a set of default macros is already implemented. It is read
from lib/symbols (where \pmod
Le 09/11/2014 22:06, Guy Rutenberg a écrit :
Hi,
Suppose I want to add to LyX new built-in math macros, like \pmod. Which
files do I need to modify?
(To clarify, I want to change the sources not my specific document).
Dear Guy, I see you did not get any answer, so I'll try to
Hi,
Suppose I want to add to LyX new built-in math macros, like \pmod. Which
files do I need to modify?
(To clarify, I want to change the sources not my specific document).
Thanks,
Guy
In general, the metrics() functions should not change the Buffer; we have
updateBuffer/updateMacros for that purpose.
---
src/mathed/MathMacroTemplate.cpp |8 ++--
src/mathed/MathMacroTemplate.h |4 ++--
2 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/src/mathed/MathM
Daniel Vainsencher wrote:
> Update:
> I have found that my current examples for "macros that are lost"
> are all explained (and fixed) by movement between the preamble and
> the document. That is, at some point they moved above the
> \begin{
Update:
I have found that my current examples for "macros that are lost"
are all explained (and fixed) by movement between the preamble and
the document. That is, at some point they moved above the
\begin{document} in the latex, I would guess
>
> Yes I am able to do what you describe in 1.6. In your example child doc,
> you did not set the master setting, did you?
>
Indeed.
I was in a hurry and I forgot it. ;/
---
Diego Queiroz
On 05/09/2011 02:38 PM, Julien Rioux wrote:
>
> Yes I am able to do what you describe in 1.6. In your example child
> doc, you did not set the master setting, did you? But anyway, I
> corrected it and still in 2.1.0svn the compilation of the child is
> broken:
>
> Undefined control sequence \anymac
Il 09/05/2011 20:23, Diego Queiroz ha scritto:
I've attached two files: the child and the master document.
I can't compile the child document. Can you try?
I can confirm the child doesn't compile as standalone,
despite the macro is correctly expanded on the screen.
T.
$\anymacro
$
The c
On 09/05/2011 2:23 PM, Diego Queiroz wrote:
Which workaround? You said math macros don't work within child docs, I say
they work for me. No workaround necessary.
Maybe I misunderstood you.
I was citing your workaround to include bibtex in the childs.
"I use a branch named &
>
> Which workaround? You said math macros don't work within child docs, I say
> they work for me. No workaround necessary.
>
Maybe I misunderstood you.
I was citing your workaround to include bibtex in the childs.
>> "I use a branch named "child only"
On 09/05/2011 1:44 PM, Diego Queiroz wrote:
So, I do not experience your problem. However document settings and stuff
that gets defined in the preamble need to be set in both master and child
docs.
--
Julien
Actually, the answer is: yes, you do experience the very same problem.
Otherwise you
won't need to go after a workaround, right? :-)
As I said before, I'm sure there are several ways to workaround this
limitation (I am not searching for one).
I just think we should focus on make LyX avoid these errors by itself.
Cheers,
---
Diego
Which workaround? You said math ma
>
> So, I do not experience your problem. However document settings and stuff
> that gets defined in the preamble need to be set in both master and child
> docs.
> --
> Julien
>
Actually, the answer is: yes, you do experience the very same problem.
Otherwise you won't need to go after a workaround
On 09/05/2011 10:22 AM, Diego Queiroz wrote:
I'm not sure if this is a bug report or a feature request. Probably the
second one.
In LyX it's ok to define a Math Macro in a Master document and use it in a
child one. It's also ok to use math macros that are defined in a child and
>
> But what if you really want to compile it as a standalone document?
> People do this.
>
> Richard
>
But if it was really a standalone document, I would have to unset master
document property, right?
Anyway, in my case, the problem is that my child document with the
Of course there are several workarounds, i.e you can create a document with
> all your macros and insert it on the beggining of all documents. This is a
> not so elegant solution, but it does the job. Probably one can suggest a
> better solution as well.
>
> But I really think LyX can do th
ment before I want to compile the whole
set.
Of course there are several workarounds, i.e you can create a document with
all your macros and insert it on the beggining of all documents. This is a
not so elegant solution, but it does the job. Probably one can suggest a
better solution as well.
On 05/09/2011 10:22 AM, Diego Queiroz wrote:
> I'm not sure if this is a bug report or a feature request. Probably the
> second one.
>
> In LyX it's ok to define a Math Macro in a Master document and use it in a
> child one. It's also ok to use math macros that are d
I'm not sure if this is a bug report or a feature request. Probably the
second one.
In LyX it's ok to define a Math Macro in a Master document and use it in a
child one. It's also ok to use math macros that are defined in a child and
use it in other child document.
In both case
Il 03/05/2011 22:48, venom00 ha scritto:
Would it be possible to disable the instant preview in such case (in
which its latex compilation fails, as in this case) ?
Well, actually it doesn't fail, but gives an empty output. Could you please open
a bug for that? I'm quite busy right now, but I sho
> Would it be possible to disable the instant preview in such case (in
> which its latex compilation fails, as in this case) ?
Well, actually it doesn't fail, but gives an empty output. Could you please open
a bug for that? I'm quite busy right now, but I should be able to investigate
the problem
If I use an undefined macro, i.e., I type in LyX:
[C-m]\mymacro
and I have instant preview on (trunk), then after exiting the math
context I cannot find anymore the macro, as its instant preview is
nothing on the screen.
Would it be possible to disable the instant preview in such case (in
acro_ is 0, i.e., all macros are
treated as "unknown".
I suspect that there may be similar problem in the LaTeX output, due
to the fact that the same calls are made there.
This macro business is a mess
It generally works great, but I find it hard to understand how it works.
I un
disappear during cloning. I tried adding calls to
updateMacros() and updateMacroInstances() to the beginning of
Buffer::writeLyXHTMLSource(), but this doesn't do the trick: The
expanded form does not get created, because when we get to
MathMacro::updateRepresentation(), macro_ is 0, i.e.,
g calls to
updateMacros() and updateMacroInstances() to the beginning of
Buffer::writeLyXHTMLSource(), but this doesn't do the trick: The
expanded form does not get created, because when we get to
MathMacro::updateRepresentation(), macro_ is 0, i.e., all macros are
treated as "unknown".
I
cros() and
updateMacroInstances() to the beginning of Buffer::writeLyXHTMLSource(),
but this doesn't do the trick: The expanded form does not get created,
because when we get to MathMacro::updateRepresentation(), macro_ is 0,
i.e., all macros are treated as "unknown".
I suspect that the
On Sat, Nov 14, 2009 at 06:37:01PM -0500, rgheck wrote:
> I'm posting it because there is one part that is potentially problematic,
> namely, the line I've commented out from clone(). I don't see why this is
> likely to be necessary, and it hasn't caused me problems in my limited
> testing.
Give
Attached is a patch that gets math macros working for MathML output. The
patch is fairly simple, though it took me forever to figure this out.
I'm posting it because there is one part that is potentially
problematic, namely, the line I've commented out from clone(). I don't
Hi,
when I played around a little bit with the math macros of LyX 1.6.3 under
Windows I realized that the corresponding Latex commands do not use curly
braces for the arguments, e.g.
\newcommand{\Vektor}[1]{\vec{#1}} CTRL-M for macro creation
leads to
\Vektor x instead of \Vektor{x} (but
Helge Hafting schreef:
The color settings have several settings for math macros, that I don't
understand.
I have no idea what these two are, so I cannot translate:
math macro blended out
math macro hovered frame
These two I can translate, but it'd nice to know what &quo
The color settings have several settings for math macros, that I don't
understand.
I have no idea what these two are, so I cannot translate:
math macro blended out
math macro hovered frame
These two I can translate, but it'd nice to know what "old" and "new"
pa
giving it any other name, solved the
> > problem instantly.
> \cr is a basic internal TeX command. So when you name your macro \cr
> you overwrote its original meaning. LyX tries to check that you don't
> overwrite existing commands with macros but in this case it failed and
>
ntly.
\cr is a basic internal TeX command. So when you name your macro \cr you overwrote its original
meaning. LyX tries to check that you don't overwrite existing commands with macros but in this case
it failed and I don't know if checking also for internal TeX command like \cr is possible.
regards Uwe
Hi,
I'm using LyX 1.6.2 on Windows Vista SP1 with MiKTeX 2.7.
While trying to compile a document which contains a math macro named \cr (I
used it for the cross sign, \times) and also contains a matrix, I got the
following error from latex several times (one error for each line in each
matrix, I gue
Stefan Schimanski writes:
>> I think that \global\newcommand works in any case.
>
> It does? I think I tried and it did not.
I might be wrong. I cannot find reference to that right now.
> A second requirement: the distinction between \newcommand and
> \renewcommand is very fragile. It is far fro
Am 07.01.2009 um 22:45 schrieb Jean-Marc Lasgouttes:
xargs is only needed if you have macros with optional arguments. Of
course, \newcommand could handle the case with one optional. But,
what we need in fact is something equivalent to \global\def for
this case. Is there a way to do this
Am 07.01.2009 um 22:45 schrieb Jean-Marc Lasgouttes:
xargs is only needed if you have macros with optional arguments. Of
course, \newcommand could handle the case with one optional. But,
what we need in fact is something equivalent to \global\def for
this case. Is there a way to do this
xargs is only needed if you have macros with optional arguments. Of
course, \newcommand could handle the case with one optional. But,
what we need in fact is something equivalent to \global\def for
this case. Is there a way to do this with \newcommand?
Why \global?
I think that \global
marter in the kind of code it exports and only use weird
packages when really needed?
In fact it is supposed to be smart enough.
xargs is only needed if you have macros with optional arguments. Of
course, \newcommand could handle the case with one optional. But, what
we need in fact is somet
[cc:ing to lyx-devel]
"James C. Sutherland" writes:
> Okay, I think that I found the problem: I am missing the "xargs"
> package. The exported LaTeX file actually had a line:
> \usepackage{xargs}[2008/03/08]
> which I discarded. This is presumably where the "\newcommandx" tag is
> define
Small Bug report:
I wanted to put a 2 by 2 matrix at the counter of a fraction and typed
in the command-line buffer:
"math-matrix 2 2"
The answer was "Command disabled (math-matrix 2 2)".
I can, however, generate this matrix with the same command outside the
fraction and copy and paste it afterwa
On Saturday 15 March 2008 10:56:03 Stefan Schimanski wrote:
> Added it to development/mathmacros.
>
> Moreover I also commited some testcases which I used frequently.
>
> Stefan
Thanks. :-)
--
José Abílio
cell right of the macro as content of a new cell, i.e. they eat from
> the right. If you reduce the arity they spit the contents out again.
>
> This can be helpful for example if you had defined a macro in the preamble
> of a tex file, imported the file in LyX, and then you have plent
Am 15.03.2008 um 10:00 schrieb José Matos:
On Saturday 15 March 2008 03:01:57 Stefan Schimanski wrote:
I have documented the macros some time ago here:
http://1stein.org/download/dynmacro.pdf
Could you add this documentation to lyx if it is not in yet?
If necessary we can add this to the
On Saturday 15 March 2008 03:01:57 Stefan Schimanski wrote:
> I have documented the macros some time ago here:
> http://1stein.org/download/dynmacro.pdf
Could you add this documentation to lyx if it is not in yet?
If necessary we can add this to the developers directory and then late
where whats the purpose?
pavel
I have documented the macros some time ago here:
http://1stein.org/download/dynmacro.pdf
Stefan
cell, i.e. they
eat from the right. If you reduce the arity they spit the contents out
again.
This can be helpful for example if you had defined a macro in the
preamble of a tex file, imported the file in LyX, and then you have
plenty of undefined \bla macros in the LyX buffer. Now define
next question for these strings:
msgid "Append Parameter Eating From The Right"
msgid "Append Optional Parameter Eating From The Right"
msgid "Remove Last Parameter Spitting Out To The Right"
do we have documented somewhere whats the purpose?
pavel
>>> Define a macro with the "\foo :=" button. Then go into math mode and use
>>> the macro. When you enter with the cursor, the different editing modes
>>> come
>>> into play.
>>
>> sorry i'm lost, whatsoever i do, no difference.
>> can you describe step by step what exactly should i do?
>> pavel
Am 15.03.2008 um 01:44 schrieb Pavel Sanda:
Define a macro with the "\foo :=" button. Then go into math mode
and use
the macro. When you enter with the cursor, the different editing
modes come
into play.
sorry i'm lost, whatsoever i do, no difference.
can you describe step by step what ex
> Define a macro with the "\foo :=" button. Then go into math mode and use
> the macro. When you enter with the cursor, the different editing modes come
> into play.
sorry i'm lost, whatsoever i do, no difference.
can you describe step by step what exactly should i do?
pavel
Am 15.03.2008 um 01:26 schrieb Pavel Sanda:
hi,
we have three different modes of macros editation.
how do they differ? switching between them and and the insert & edit
macro
does not seem to make difference. what should i do to see whats
their purpose?
It's about the instanc
hi,
we have three different modes of macros editation.
how do they differ? switching between them and and the insert & edit macro
does not seem to make difference. what should i do to see whats their purpose?
pavel
oring the
> {sideways}. All the other cases of the \begin handler use the FLAG_END.
That's what should be used there..
> Btw, the bug has nothing to do with macros: just type
> $\begin{sideways}a\end{sideways}$, select it and press Ctrl-m.
>
> diff --git a/src/mathed/MathParser.cp
1 - 100 of 347 matches
Mail list logo
