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
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
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 ways away, is it worth
> > committing to stable?
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 ways away, is it worth
> committing to stable?
I think it is not risky and I am attaching the version for stable here.
How
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
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 arguments, s
On 11/17/2014 04:51 PM, Georg Baum wrote:
Jean-Marc Lasgouttes wrote:
The answer really depend on the macro you want to define. In the case of
\pmod, I did not find any inset (in src/mathed) that seems to be similar
enough. You want an inset with only one cell, like in
InsetMathDecoration, whic
Jean-Marc Lasgouttes wrote:
> The answer really depend on the macro you want to define. In the case of
> \pmod, I did not find any inset (in src/mathed) that seems to be similar
> enough. You want an inset with only one cell, like in
> InsetMathDecoration, which implements accents. So the inset wo
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
>
> 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
an, "if I can see
everything right on the screen, what's the problem?"
This is how I feel about the current behavior. LyX is handling everything on
the editor, since all math macros are interpreted correctly when I open any
document, but I can't generate the file because of
On 05/09/2011 11:05 AM, Diego Queiroz wrote:
>
>> If you want to compile just one chapter as part of a larger document,
>> then you need to use the \includeonly support, accessible from
>> Document>Settings.
> I was not aware of this feature. Thanks for the hint.
>
It's new in 2.0.0.
> But it is a
>
> If you ask to compile just the child, then you are asking to compile it
> as a standalone document, so it is no surprise that this does not work.
>
Exactly. :-)
> If you want to compile just one chapter as part of a larger document,
> then you need to use the \includeonly support, accessibl
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
rgheck wrote:
On 01/11/2010 02:03 PM, Abdelrazak Younes wrote:
rgheck wrote:
I'm running into several problems due to the buffer cloning thing
during XHTML output. The latest is that I need the expanded form of
a math macro in the MathML output routines, and I don't have it,
since it seems
On 01/11/2010 02:03 PM, Abdelrazak Younes wrote:
rgheck wrote:
I'm running into several problems due to the buffer cloning thing
during XHTML output. The latest is that I need the expanded form of a
math macro in the MathML output routines, and I don't have it, since
it seems to disappear du
rgheck wrote:
I'm running into several problems due to the buffer cloning thing
during XHTML output. The latest is that I need the expanded form of a
math macro in the MathML output routines, and I don't have it, since
it seems to disappear during cloning. I tried adding calls to
updateMacro
I'm running into several problems due to the buffer cloning thing during
XHTML output. The latest is that I need the expanded form of a math
macro in the MathML output routines, and I don't have it, since it seems
to disappear during cloning. I tried adding calls to updateMacros() and
updateM
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
I don't know if checking also for internal TeX command like \cr is
> possible.
Would it help to use \newcommand{} instead of \def for math-macros?
(Actually, I vote for a choice of \newcommand, \renewcommand,
\providecommand, and \def.)
Günter
> 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 ...
> Deleting the macro \cr, or giving it any other name, solved the problem
> instantly.
\cr is a
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
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
>> 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
>
> Normally, when you cha
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 later move
i
Am 15.03.2008 um 03:26 schrieb Pavel Sanda:
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
Am 15.03.2008 um 03:26 schrieb Pavel Sanda:
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
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 instances of the mac
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
On Fri, Feb 22, 2008 at 12:45:22PM +0100, Stefan Schimanski wrote:
> I do not really understand the parser very well. So here is a simple minded
> patch. Andre, as you are mentioned as author, does this make sense? With
> FLAG_ITEM the parser will stop at the closing \end, but ignoring the
> {si
the file, another "{sideways}" gets added.
Please find attached a simple lyx-file that shows the error.
Why is that, does LyX simply not support environments in math-macros?
Best regards and thanks
Dominik
Number 4573
Which bug number?
Stefan
Am 22.02.2008 um 12:34 schrieb Dominik Böhm:
On Fri, Feb 22, 2008 at 12:18 PM, Stefan Schimanski <[EMAIL PROTECTED]>
wrote:
Looks like a bug in the parser.
Thanks for the quick answer, I just filed a bug report.
On Fri, Feb 22, 2008 at 12:18 PM, Stefan Schimanski <[EMAIL PROTECTED]> wrote:
> Looks like a bug in the parser.
Thanks for the quick answer, I just filed a bug report.
Please find attached a simple lyx-file that shows the error.
Why is that, does LyX simply not support environments in math-macros?
Best regards and thanks
Dominik
acro properly. Instead of
"\begin{sideways}#1\end{sideways}" LyX loads
"\begin{sideways}#1\end{sideways}{sideways}". Each time I save and
reload the file, another "{sideways}" gets added.
Please find attached a simple lyx-file that shows the error.
Why is that, does Ly
Great! I tried already. Perfect! Thanks a lot!!
Sebastian
On Tue, 2008-01-22 at 22:27 +0100, Stefan Schimanski wrote:
> Am 09.01.2008 um 07:02 schrieb sebastian guttenberg:
>
> >> one could think about the compromise to put just a grey box around
> >> without any size change at all and to put the
Right, will add something in the next days.
Stefan
Am 22.01.2008 um 22:33 schrieb Pavel Sanda:
one could think about the compromise to put just a grey box around
without any size change at all and to put the macro name into the
statusbar. Sounds sensible. I will try that out.
That sounds gre
>>> one could think about the compromise to put just a grey box around
>>> without any size change at all and to put the macro name into the
>>> statusbar. Sounds sensible. I will try that out.
>>
>> That sounds great! I am looking forward! Thanks a lot for bothering!
>
> It's implemented. You have
Am 09.01.2008 um 07:02 schrieb sebastian guttenberg:
one could think about the compromise to put just a grey box around
without any size change at all and to put the macro name into the
statusbar. Sounds sensible. I will try that out.
That sounds great! I am looking forward! Thanks a lot for
> one could think about the compromise to put just a grey box around
> without any size change at all and to put the macro name into the
> statusbar. Sounds sensible. I will try that out.
That sounds great! I am looking forward! Thanks a lot for bothering!
Sebastian
--
This message has be
Hi Sebastian!
I wanted to ask you whether the present behaviour of the poping up of
macros will be the final one? You told me once that you will either
allow to choose between the macros not popping up at all and between
popping up as they did earlier, or to make some compromise. I guess
that
Hi Stefan
I wanted to ask you whether the present behaviour of the poping up of
macros will be the final one? You told me once that you will either
allow to choose between the macros not popping up at all and between
popping up as they did earlier, or to make some compromise. I guess that
you decid
Stefan Schimanski wrote:
I have several files that include another file, ggmacros.lyx, that
includes all the math macros I need for most of my papers. In 1.5.x,
and previously, so long as the macro file was loaded before the base
file, the macros would be seen and used by LyX. In the current
Stefan Schimanski wrote:
I have several files that include another file, ggmacros.lyx, that
includes all the math macros I need for most of my papers. In 1.5.x,
and previously, so long as the macro file was loaded before the base
file, the macros would be seen and used by LyX. In the current
I have several files that include another file, ggmacros.lyx, that
includes all the math macros I need for most of my papers. In 1.5.x,
and previously, so long as the macro file was loaded before the base
file, the macros would be seen and used by LyX. In the current
trunk, however, that
I have several files that include another file, ggmacros.lyx, that
includes all the math macros I need for most of my papers. In 1.5.x, and
previously, so long as the macro file was loaded before the base file,
the macros would be seen and used by LyX. In the current trunk, however,
that is
Hi!
I have nearly implemented all of my planned changes to the math
macros. A major one is proper support for multiple arguments in TeX
output. Until now they are supported by the LyX gui, but during export
multiple optionals are "resolved", i.e. expanded in the TeX output.
Andre Poenitz schrieb:
On Tue, Dec 11, 2007 at 09:53:29AM +0100, Stefan Schimanski wrote:
Possibly some magic with STL's algorithms and an order functor or so
might do what I want. If so without any performance hit, I am open to use
that.
[...]
What about lo
On Tue, Dec 11, 2007 at 09:53:29AM +0100, Stefan Schimanski wrote:
>
>>> Possibly some magic with STL's algorithms and an order functor or so
>>> might do what I want. If so without any performance hit, I am open to use
>>> that.
>>>
[...]
>>
>> What about lower_bound on rev
Am Dienstag, 11. Dezember 2007 00:00:10 schrieb Stefan Schimanski:
> > _no_ trailing whitespace would be even nicer ;-)
>
> Wondering if Emacs has some setting to remove those by itself.
No setting AFAIK, but here's what I hacked together, borrowing some
stuff/ideas from something similar propose
Possibly some magic with STL's algorithms and an order functor or so might
do what I want. If so without any performance hit, I am open to use that.
[...]
What about lower_bound on reverse iterators (i.e. map<>.rbegin() etc)?
rbegin() etc. is fine, but how can I use the lower_b
On Tue, Dec 11, 2007 at 12:00:10AM +0100, Stefan Schimanski wrote:
>>> + /// Create lazy MacroData which only queries the macro template when
>>> needed
>>> + MacroData(Buffer const & buf, DocIterator const & pos);
>>>
>>
>> This works?
>>
> Why shouldn't it? What exactly is your doubt
///
class MacroData {
public:
- ///
+ /// Constructor to make STL containers happy
MacroData();
+ /// Create lazy MacroData which only queries the macro template when
needed
+ MacroData(Buffer const & buf, DocIterator const & pos);
This works?
Why s
On Mon, Dec 10, 2007 at 11:02:22PM +0100, Stefan Schimanski wrote:
> Jean-Marc Lasgouttes schrieb:
>> Stefan Schimanski <[EMAIL PROTECTED]> writes:
>>
>>
>>> For insets you are right, I assume they open an environment, which is
>>> not correct in general. Have to check how to do this properly. T
Jean-Marc Lasgouttes schrieb:
Stefan Schimanski <[EMAIL PROTECTED]> writes:
For insets you are right, I assume they open an environment, which is
not correct in general. Have to check how to do this properly. The
InsetBranch is on my list anyway. Haven't looked into that.
The best is
Stefan Schimanski <[EMAIL PROTECTED]> writes:
> For insets you are right, I assume they open an environment, which is
> not correct in general. Have to check how to do this properly. The
> InsetBranch is on my list anyway. Haven't looked into that.
The best is probably a virtual method for insets
Jean-Marc Lasgouttes schrieb:
Stefan Schimanski <[EMAIL PROTECTED]> writes:
Hi!
I was working on the lookup logic of math macros for the last few
weeks in a private branch. Here is the resulting patch.
It basically transforms the macro context into a DocIterator instead
of a
Stefan Schimanski <[EMAIL PROTECTED]> writes:
> Hi!
>
> I was working on the lookup logic of math macros for the last few
> weeks in a private branch. Here is the resulting patch.
>
> It basically transforms the macro context into a DocIterator instead
> of a basic pa
Hi
When writing my thesis, I had splitted it into several parts and
included a file with my standard math-macros into each of them via
input.
Up to 1.5.2, that method worked fine, if the math-macro file was loaded
into the lyx-editor.
Now, each document can have its own math-macros, which is in
Am 15.11.2007 um 14:08 schrieb sebastian guttenberg:
Hi
When writing my thesis, I had splitted it into several parts and
included a file with my standard math-macros into each of them via
input.
Up to 1.5.2, that method worked fine, if the math-macro file was
loaded
into the lyx-editor.
Now
Am 14.11.2007 um 15:04 schrieb sebastian guttenberg:
First of all: I like the new macros a lot, even when I will try next
days to produce a lot of critisism ;-)
I have another small comment about the pasting of macros.
I don't know whether this is related to the pasting-crash that I
reported:
W
First of all: I like the new macros a lot, even when I will try next
days to produce a lot of critisism ;-)
I have another small comment about the pasting of macros.
I don't know whether this is related to the pasting-crash that I
reported:
Whenever one pastes a math-macro with arguments, the curso
Am 13.11.2007 um 17:16 schrieb sebastian guttenberg:
JMarc fixed this at 21584.
Wow. I had just updated before compiling. Probably I had chosen a bad
moment ;-) Updated again - compiling works perfectly now! Thanks a
lot!
Also thanks for the updating-hints!
And I am able to load at least
> JMarc fixed this at 21584.
Wow. I had just updated before compiling. Probably I had chosen a bad
moment ;-) Updated again - compiling works perfectly now! Thanks a lot!
Also thanks for the updating-hints!
And I am able to load at least one of my old documents (didn't try the
others yet ...)!
Bu
sebastian guttenberg wrote:
On Tue, 2007-11-13 at 15:55 +0100, Stefan Schimanski wrote:
I did a commit yesterday about this. Have you updated your code?
Stefan
Ah, interesting! Things evolve quickly!
Now I have updated the source, but I get an error during the
make-procedure:
"make[2]
sebastian guttenberg <[EMAIL PROTECTED]> writes:
> Seems to me that 'make' has not finished due to this error. How can I
> check this at this stage? Anyway, make install then also failed...
> Can you help?
Should be fixed now.
> P.S.: When updating, do I always have to do the complete procedur
On Tue, 2007-11-13 at 15:55 +0100, Stefan Schimanski wrote:
> I did a commit yesterday about this. Have you updated your code?
>
> Stefan
Ah, interesting! Things evolve quickly!
Now I have updated the source, but I get an error during the
make-procedure:
"make[2]: *** No rule to make target `layo
SliceESaIS2_EEE;
}
Aborted (core dumped)"
I have now specified that at least the following combination of math-
macros causes this problem:
"\begin_inset FormulaMacro
\newcommand{\ola}[1]{\overleftarrow{#1}}
\end_inset
\begin_inset FormulaMacro
\newcommand{\funktr}[1]{\frac{\ola{\delt
ex -1,
but
container only holds 1 elements.
Objects involved in the operation:
sequence "this" @ 0x0x9548580 {
type = N15__gnu_debug_def6vectorIN3lyx11CursorSliceESaIS2_EEE;
}
Aborted (core dumped)"
I have now specified that at least the following combination of math
On Thursday 24 May 2007 00:25:46 Uwe Stöhr wrote:
> As André gave his OK and me too this can go in right?
Yep. :-)
> regards Uwe
--
José Abílio
> I would like to hear what André has to say about this patch. :-)
As André gave his OK and me too this can go in right?
regards Uwe
It should be included because it is not properly evaluated. LyX
only has a global macro table at the moment. So "calling" a
recursive macro twice will result in strange results.
s/included/excluded/
Stefan
PGP.sig
Description: Signierter Teil der Nachricht
Am 23.05.2007 um 01:52 schrieb Uwe Stöhr:
First, I like your patch and give an OK.
> FYI, I tried with these examples:
> 5 \newcommand{\foo}[2][\frac{1}{2}]{(#1|#2)} $\foo 1{23}345$
> 6 \newcommand{\foo}[2][\frac{1}{2}]{(#1|#2)} $\foo 1{23}345$
What is the difference?
Nothing :)
Only for i
1 - 100 of 171 matches
Mail list logo
