On Thu, 26 Jul 2001, Kayvan A. Sylvan wrote:
On Thu, Jul 26, 2001 at 05:13:54PM +0200, Herbert Voss wrote:
Juergen Vigna wrote:
I'm now able to load the UserGuide in lyx-cvs. But when I want to LaTeX
it I get errors because some subsection have an underscore for the first
character in
I have been laboring mightily to convert all the docs to 1.2.0 and have
not yet succeeded in getting the UG, Tutorial, and Customization to
convert for all of the above reasons. Keep an eye on lyxdoc CVS; I will
keep banging on them for the next couple of days ...
Mike
The problems are
Can you remove the space after the first $ ?
Namely, the formula 'x' is written as $ x$, where it should be $x$.
Does this hurt? If I do that I need to be careful with empty formulae as
LaTeX does not seen to like two $ in a row...
Andre'
--
André Pönitz
Juergen Vigna wrote:
On 23-Jul-2001 Jean-Marc Lasgouttes wrote:
Michael == Michael Schmitt [EMAIL PROTECTED] writes:
Michael Hi, when running Purify, it complains that it has to link a
Michael directory. Could you please tell me what option
Michael -Wl,/usr/openwin/lib means when
If this feature is not needed any longer, I propose alternative 1. Alt 2
could be implemented as well for backward-compatibility (if this is really
necessary; the question is whether there are any users with selfmade
layout files that are not member of this mailing list)
Well me too would
Promise, this is my last patch about quotes (:
This one displays ' as ´ if an appropriate encoding is used, and french
guillemets are also displayed in 8859-9 (some encodings dont't support
both quotes, but they are not yet handled separatly by LyX)
--
Yves
Index:
lyx cvs current now only crashes in the math panel with sigma and misc
and it does an emergency save. xforms-0.89.5 gcc-3.0
Garst
On 27-Jul-2001 Kayvan A. Sylvan wrote:
The problems are due to bugs introduced by the ERT inset changes.
They will be fixed soon, I'm sure.
IMO they are already fixed the bugs we see are related to other stuff
(LaTeX incompatibilities)
Jürgen
--
On 27-Jul-2001 Kayvan A. Sylvan wrote:
The \color latex causes the color feature to be set to true, which
then causes the \usepackage[none]{color} line to be output.
Ok this should be fixed, BUT we still have problem with usepackage color
AND section headings IF we use REAL colors in the
Hello Andre, could you please have a look at this.
Try open a mathed inset and type the following:
\int x
then try to latex it it will give you errors. Also saving an reloading
it will not work! The problem is that you miss the space after the \int
command in the output. (seen in the
Try open a mathed inset and type the following:
\int x
then try to latex it it will give you errors.
It does not.
Also saving an reloading it will not work! The problem is that you miss
the space after the \int command in the output.
I can't see that.
void
Title: Your Web Site is Now Responding
We are pleased to inform you that Your Web site http://www.lyx.org/ is back up and is no longer on error.
URL: http://www.lyx.org/
Time: 2001-07-27 05:21:47
As mentioned in the first alert, InternetSeer is
On 27-Jul-2001 Andre Poenitz wrote:
Try open a mathed inset and type the following:
\int x
then try to latex it it will give you errors.
It does not.
Well maybe I'm not really uptodate, but cvs is down and I cannot update.
Just to be sure what's the file and whats the byte number? in
Well maybe I'm not really uptodate, but cvs is down and I cannot update.
Just to be sure what's the file and whats the byte number? in it so I'll
have a look if we have the same one.
math_bigopinset.C:19
Anyway did you just have a look at the code or did you actually try it?
I tried it.
On Thursday 26 July 2001 18:08, you wrote:
On Thu, Jul 26, 2001 at 05:17:57PM +0100, Angus Leeming wrote:
| All of your citation commands are still cite aren't they?
|
| There is little point in including natbib if you aren't going to use
it!
But... I thought that natbib
On 27-Jul-2001 Andre Poenitz wrote:
math_bigopinset.C:19
Ok I miss the last ' ' in that line until I can update I add this here by
hand so that I'm able to read/latex the UserGuide (which is a very good test
file ;)
Jürgen
--
On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
And it should probably not be output in the .lyx file. Probably a few
changes in lyxfont.C will be enough.
It HAS to be outputed, BUT as the document_wide language, otherwise we're
not able to switch back and remain in the previously defined
Now we have a new one! You somehow output a 0 character in $ $ stuff.
Trye subsection 5.1.8 Other Math Symbols in the UserGuide. There is
something strange in the second paragraph:
a symbol whose LaTeX name you know, like \oint for in[] ...
Have a look at the in[] part seems strange to me!
Hi Andre,
I have found a very small example that crashes when being read. Obviously,
macros are not handled correctly (in the given example, \Nat is a
selfmade macro that should be defined somewhere in the LaTeX preamble)
Michael
--
On Fri, Jul 27, 2001 at 12:03:04PM +0200, Juergen Vigna wrote:
On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
And it should probably not be output in the .lyx file. Probably a few
changes in lyxfont.C will be enough.
It HAS to be outputed, BUT as the document_wide language, otherwise
Hi,
there seems to be a memory leak in the text editing code (splitting
paragraphs, undoing paragraph splitting, etc.) that is not big but
happens quite often.
Michael
*
MLK: 256 bytes leaked at 0xe71b20
This memory was allocated from:
On Thu, Jul 26, 2001 at 05:37:51PM -0400, Amir Karger wrote:
On Thu, Jul 26, 2001 at 08:26:21PM +0300, Dekel Tsur wrote:
On Wed, Jul 25, 2001 at 10:34:05PM +0100, Jose Abilio Oliveira Matos wrote:
On Wed, Jul 25, 2001 at 03:03:40PM +0200, Jean-Marc Lasgouttes wrote:
3. The \L and
On 27-Jul-2001 Dekel Tsur wrote:
Why the language in insetERT is changed to ignore_language ???
No your're right it should be inherit_language and now it is!
The correct way for implementing insetERT is to have an InsetEditor and use
Your free to provide one!
it instead of insetText.
On Wed, Jul 25, 2001 at 10:39:33AM +0200, Jean-Marc Lasgouttes wrote:
8. When several insets are placed consecutively (this can happen
with error insets), clicking on an inset can result in opening the
wrong one. A workaround is to use C-o, with the cursor placed just
before the desired
a symbol whose LaTeX name you know, like \oint for in[] ...
Have a look at the in[] part seems strange to me!
Uuh... yes... that's ugly. The math parser is not (yet) re-entrant, so
builting the table of 'builtin macros' during the reading of a 'real
formula' breaks everything...
Andre'
--
On Fri, Jul 27, 2001 at 02:17:19PM +0200, Jean-Marc Lasgouttes wrote:
Dekel == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel On Thu, Jul 26, 2001 at 05:37:51PM -0400, Amir Karger wrote:
On Thu, Jul 26, 2001 at 08:26:21PM +0300, Dekel Tsur wrote: On
Wed, Jul 25, 2001 at 10:34:05PM +0100,
On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
The interesting methods in LyX Font are
/** Reduce font to fall back to template where possible.
Equal fields are reduced to INHERIT */
void reduce(LyXFont const tmplt);
/// Realize font from a template (INHERIT
On Fri, Jul 27, 2001 at 02:30:47PM +0200, Juergen Vigna wrote:
On 27-Jul-2001 Dekel Tsur wrote:
Yes, if the document in an English-Arabic document, then
\L{text} = \foreignlanguage{english}{text}
\R{text} = \foreignlanguage{arabic}{text}
So why do we need this \L \R macros if we
21. When entering a multi-line equation, and the beginning of the
second (or following) line begins with a [ character, LaTeX
sometimes gets confused. To avoid problems, it is necessary to add
{} in TeX mode just before the bracket, as in the following
example:x(t) = 1\nonumber
On Fri, Jul 27, 2001 at 02:15:56PM +0200, Jean-Marc Lasgouttes wrote:
Dekel Why the language in insetERT is changed to ignore_language ???
We need a way to say inherit language. This works well for everything
in a font when one specifies ALL_INHERIT, _except_ for language. Why?
Because the
Do I really need the 'fragile' flag anymore to write(ostream , bool
fragile) if I output inline math in '$...$'?
The only place it seems to be used currently is to write a \protect in
front of \\begin{array} and \\end{array} when set.
Would removing that mean that arrays would not work in
On Fri, Jul 27, 2001 at 02:37:30PM +0200, Andre Poenitz wrote:
21. When entering a multi-line equation, and the beginning of the
second (or following) line begins with a [ character, LaTeX
sometimes gets confused. To avoid problems, it is necessary to add
{} in TeX mode just
On Fri, Jul 27, 2001 at 02:49:33PM +0200, Juergen Vigna wrote:
On 27-Jul-2001 Dekel Tsur wrote:
1. Because people use the shorter \L and \R commands.
This is no reason you use short-cuts because it's faster to type we don't
have a reason to use this shortcuts. If this means introducing
Nothing. As I said, this problem doesn't exist in align, and align is the
preferred way for multi-line equations.
Jean-Marc seems to think otherwise and personally I am clueless.
If aligned is indeed prefered we could as well required ams by default and
I do not have to check everything
Anyway now I'm able to read the UserGuide, LaTeX it, save it, read it again
and then when saving again and diffing against the save before I have NO
diffs!
Thanks for checking that.
Andre'
--
André Pönitz . [EMAIL PROTECTED]
Hi,
could anybody please apply the following minipatch (alternatively, you
might remove the word font)? g++ -Wall complains about redundant
parameters all the times.
Michael
***
Index: src/insets/inset.h
===
On 27-Jul-2001 Dekel Tsur wrote:
Because the language property is not inherited.
If you write some text in an English document, and then copy it to a French
document, the language of the text should remain English (there are
exceptions if for example you copy source code).
You're right we
On Fri, Jul 27, 2001 at 02:52:04PM +0200, Andre Poenitz wrote:
Do I really need the 'fragile' flag anymore to write(ostream , bool
fragile) if I output inline math in '$...$'?
The only place it seems to be used currently is to write a \protect in
front of \\begin{array} and \\end{array}
On Fri, Jul 27, 2001 at 11:25:57AM +0200, Jean-Marc Lasgouttes wrote:
You could maybe ask the AikSaurus author to include his small command
line program in the distribution. This is after all the way unix
programs work.
You seem to be suggesting UNIX doesn't use shared libraries !
What if
On 27-Jul-2001 Dekel Tsur wrote:
Relyx should support any reasonable latex file which was written by a human,
so it should support the \L and \R command.
We aren't talking about Relyx we where talking about LyX-source-code. Sure
Relyx should honor them and output the right \lang whatever
On Fri, Jul 27, 2001 at 11:33:33AM +0200, Jean-Marc Lasgouttes wrote:
Did it work with 1.1.6? I cam to the conclusion at the time that
font-emph did not really work like that.
hmm, you're right. I must have been luck enough to have always pressed space
first (really I had never noticed such
On Friday 27 July 2001 14:04, Dekel Tsur wrote:
On Fri, Jul 27, 2001 at 02:52:04PM +0200, Andre Poenitz wrote:
Do I really need the 'fragile' flag anymore to write(ostream , bool
fragile) if I output inline math in '$...$'?
The only place it seems to be used currently is to write a
On Friday 27 July 2001 14:05, John Levon wrote:
On Fri, Jul 27, 2001 at 11:25:57AM +0200, Jean-Marc Lasgouttes wrote:
You could maybe ask the AikSaurus author to include his small command
line program in the distribution. This is after all the way unix
programs work.
You seem to be
On 27-Jul-2001 Michael Schmitt wrote:
Hi,
Hi Michael!
could anybody please apply the following minipatch (alternatively, you
might remove the word font)? g++ -Wall complains about redundant
parameters all the times.
- virtual bool checkInsertChar(LyXFont font) { return true; }
+
On Fri, Jul 27, 2001 at 02:18:34PM +0100, Angus Leeming wrote:
Corba? Basically, it boiled down to if the external shared library SIGSEGVs,
then my program bombs out. Using an external program, this isn't true.
ok so that's 1 dubious reason for uglifying lyx's code ...
john
--
I'd rather
Errr. Wasn't the whole point of yesterdays discussion that by $...$ is
robust. That means, therefore, that since André has changed mathed to use
$...$, then the \protect is NOT needed.
Well... we can read $...$ delimited math now, too. Which is nice per se.
Anyway, André, the real answer
On Fri, Jul 27, 2001 at 03:25:43PM +0200, Jean-Marc Lasgouttes wrote:
It is not the design philosophy of unix. Many unix features rely on
programs and pipes, after all.
even plan9 uses libs
This just mean that we have to build two versions of LyX
Kayvan has already said it's not a
On Fri, Jul 27, 2001 at 03:26:27PM +0200, Andre Poenitz wrote:
Errr. Wasn't the whole point of yesterdays discussion that by $...$ is
robust. That means, therefore, that since André has changed mathed to use
$...$, then the \protect is NOT needed.
Well... we can read $...$ delimited
On Fri, Jul 27, 2001 at 03:29:04PM +0200, Jean-Marc Lasgouttes wrote:
I don't know what we want to do, actually. Stealing ideas from others
is always good.
Do I take it it is fairly easy to separate the mechanisms ?
Index entry should always work on last word.
Font changes etc. should be
On Fri, Jul 27, 2001 at 02:08:45PM +0100, John Levon wrote:
at least openoffice doesn't change the preceding word. But this is not necessarily
a thing to copy ...
so perhaps the current behaviour is fine; it just surprised me ...
In my opinion the current behavior is not fine.
Please revert
I wonder how much mathed specific code is in reLyX that could be removed
if we had support for it in mathed.
I think I could e.g. support everything on the bottom of
lib/reLyX/syntax.default natively, so this reLyXmt thingy could go...
Who knows how reLyX works nowadays?
Andre'
--
André
On Fri, Jul 27, 2001 at 04:50:56PM +0300, Dekel Tsur wrote:
In my opinion the current behavior is not fine.
Please revert to the old one.
which old one ? it did this in 116 at least ...
john
--
I'd rather be rudely informed than politely left in the dark.
On Fri, Jul 27, 2001 at 02:58:28PM +0100, John Levon wrote:
On Fri, Jul 27, 2001 at 04:50:56PM +0300, Dekel Tsur wrote:
In my opinion the current behavior is not fine.
Please revert to the old one.
which old one ? it did this in 116 at least ...
argh,sorry, no it didn't of course.
This patch includes several modifications to InsetGraphics
It fixes a bug with the file selection where by default it didn't
suggest jpeg/gif/eps files
It makes all IG be inline, if the user wants it in a new paragraph he
should do it himself.
It adds compatibility reading of InsetFig.
It
Jose Abilio Oliveira Matos a écrit :
[...] Did you try db2lyx with xlst from gnome. If that takes me the trouble to
keep java well installed and configured I will switch right now. :-)
I've tried xsltproc (linked with libxslt-0.14.0 and libxml2-2.4.1) running on the
db2lyx stylesheets
On Fri, Jul 27, 2001 at 03:54:27PM +0200, Andre Poenitz wrote:
I wonder how much mathed specific code is in reLyX that could be removed
if we had support for it in mathed.
I think I could e.g. support everything on the bottom of
lib/reLyX/syntax.default natively, so this reLyXmt thingy
Ask Lars, I changed it at the time to Graphics and got it changed back
to GRAPHICS. I'm tired of changing this myself.
* Jean-Marc Lasgouttes [EMAIL PROTECTED] [010727 19:45]:
Baruch == Baruch Even [EMAIL PROTECTED] writes:
Baruch This patch includes several modifications to InsetGraphics
Hi,
below find a list of all compiler warnings reported by g++ 2.95.3.
/Michael
*
formulabase.C:131: warning: #warning This is needed as long the math parser is not
re-entrant
formulabase.C:213: warning: #warning Please
* Lars Gullik Bjønnes [EMAIL PROTECTED] [010727 20:41]:
Baruch Even [EMAIL PROTECTED] writes:
| Ask Lars, I changed it at the time to Graphics and got it changed back
| to GRAPHICS. I'm tired of changing this myself.
eh? Are you saying that I changed from Graphics to GRAPHICS? I don't
* Lars Gullik Bjønnes [EMAIL PROTECTED] [010727 20:41]:
Michael Schmitt [EMAIL PROTECTED] writes:
| Hi,
|
| below find a list of all compiler warnings reported by g++ 2.95.3.
And these are the only real warnings.
| insetgraphics.C:264: warning: initialization to `int' from `float'
On 27 Jul 2001, Lars Gullik Bjønnes wrote:
| So, would you please consider to apply the patch instead of arguing
| wildly? I don't have write access yet.
BS!, of course you have.
Thanks. Unfortunately, I didn't think you'd move so fast, so I deleted
the patch from my mailbox a long time
Hi,
it's Friday and I have nothing to complain about :-( After a much too long
week of struggling, I am finally able to read, write, edit and even
print my PhD again. What a good feeling!!!
Even though the day is almost over I wonder whether I should test some
specific code for you. Up to now
Hi,
I took a closer look at one of my former reports:
UMR: Uninitialized memory read
This is occurring while in:
find_if__H2ZPQ25boostt10shared_ptr1Z15ParameterStructZQ2t14ShareContainer1Z15ParameterStruct7isEqual_X01X01X11G26random_access_iterator_tag_X01
[ParameterStruct.h:85]
On Fri, Jul 27, 2001 at 02:26:52PM +0100, John Levon wrote:
On Fri, Jul 27, 2001 at 02:18:34PM +0100, Angus Leeming wrote:
Corba? Basically, it boiled down to if the external shared library SIGSEGVs,
then my program bombs out. Using an external program, this isn't true.
ok so that's 1
Hi,
I would you like to point out that an old bug is still in the LyX code:
Clicking into the right half of a footnote still does not work. The
cursor is set after the footnote, to the right at the same line as the
footnote label. This place is normally not reachable using the
cursor keys.
Hi,
when opening the new citation dialog (which is EXCELLENT!), I noticed that
I forgot to mention a bibtex file in my bibliography reference. With the
citation dialog being open, I moved to the bibref, added the file name and
closed the corresponding dialog. At this time, the following message
Hello,
just a small bug in the citation code:
1. Add a citation to your document
2. Click at the citation; the dialog pops up
3. Click on the box where you can choose between
Author Year, Year, Author, etc.
4. Click OK
- A _new_ citation is added (this shouldn't happen)
Please
John Levon wrote:
On Fri, Jul 27, 2001 at 05:13:38AM -0300, Garst R. Reese wrote:
lyx cvs current now only crashes in the math panel with sigma and misc
and it does an emergency save. xforms-0.89.5 gcc-3.0
Garst
Garst do you have optimisation turned on ? Can you try it without ?
Hi,
I noticed that my bibtex citations are not resolved correctly at once. I
have to make some changes to my document and invoke dvi export again in
order to get the ? replaced by the correct citations.
Could you please tell me which information you need (latex log?) in order
to find the source
On Fri, Jul 27, 2001 at 09:14:34AM -0700, Kayvan A. Sylvan wrote:
On Fri, Jul 27, 2001 at 03:54:27PM +0200, Andre Poenitz wrote:
I wonder how much mathed specific code is in reLyX that could be removed
if we had support for it in mathed.
I think I could e.g. support everything on the
Howdy,
Some bugs in current cvs:
* Can't insert spaces using C-space or Maths Panel:
LyXFunc::Dispatch: protected-space-insert [61] is disabled ad this
location
* Strange cursor behavior in \vec insets:
In a new document, type C-m M-v v left left left left
* When there's math stuff in
On Fri, Jul 27, 2001 at 04:46:23PM -0300, Garst R. Reese wrote:
I did an update at 2PM EST and compiled without optimizations and now it
crashes again on anything from greek to misc.
I'll try again with opt. Compiling without opt did not help in the past.
so it isn't an optimisation bug in
John Levon wrote:
so it isn't an optimisation bug in the compiler.have you tried another compiler
version if possible ?
I'm at a loss to understand why things should change like it has for you and me
unless there is a compiler bug, or we are doing bad things with pointers.
It is indeed
John Levon wrote:
so it isn't an optimisation bug in the compiler.have you tried another compiler
version if possible ?
I just tried 2.95.2.1 and it failed to link. Log available on request.
Not really interested in pursuing that route further.
Garst
On Thu, 26 Jul 2001, Kayvan A. Sylvan wrote:
> On Thu, Jul 26, 2001 at 05:13:54PM +0200, Herbert Voss wrote:
> > Juergen Vigna wrote:
> > > I'm now able to load the UserGuide in lyx-cvs. But when I want to LaTeX
> > > it I get errors because some subsection have an underscore for the first
> > >
> I have been laboring mightily to convert all the docs to 1.2.0 and have
> not yet succeeded in getting the UG, Tutorial, and Customization to
> convert for all of the above reasons. Keep an eye on lyxdoc CVS; I will
> keep banging on them for the next couple of days ...
>
> Mike
The problems
> Can you remove the space after the first $ ?
> Namely, the formula 'x' is written as $ x$, where it should be $x$.
Does this hurt? If I do that I need to be careful with empty formulae as
LaTeX does not seen to like two $ in a row...
Andre'
--
André Pönitz
Juergen Vigna wrote:
>
> On 23-Jul-2001 Jean-Marc Lasgouttes wrote:
> >> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
> >
> > Michael> Hi, when running Purify, it complains that it has to link a
> > Michael> directory. Could you please tell me what option
> > Michael>
> If this feature is not needed any longer, I propose alternative 1. Alt 2
> could be implemented as well for backward-compatibility (if this is really
> necessary; the question is whether there are any users with selfmade
> layout files that are not member of this mailing list)
Well me too
Promise, this is my last patch about quotes (:
This one displays ' as ´ if an appropriate encoding is used, and french
guillemets are also displayed in 8859-9 (some encodings dont't support
both quotes, but they are not yet handled separatly by LyX)
--
Yves
Index:
lyx cvs current now only crashes in the math panel with sigma and misc
and it does an emergency save. xforms-0.89.5 gcc-3.0
Garst
On 27-Jul-2001 Kayvan A. Sylvan wrote:
> The problems are due to bugs introduced by the ERT inset changes.
>
> They will be fixed soon, I'm sure.
IMO they are already fixed the bugs we see are related to other stuff
(LaTeX incompatibilities)
Jürgen
--
On 27-Jul-2001 Kayvan A. Sylvan wrote:
> The "\color latex" causes the color feature to be set to true, which
> then causes the \usepackage[none]{color} line to be output.
Ok this should be fixed, BUT we still have problem with usepackage color
AND section headings IF we use REAL colors in the
Hello Andre, could you please have a look at this.
Try open a mathed inset and type the following:
\int x
then try to latex it it will give you errors. Also saving an reloading
it will not work! The problem is that you miss the space after the \int
command in the output. (seen in the
> Try open a mathed inset and type the following:
>
> \int x
>
> then try to latex it it will give you errors.
It does not.
> Also saving an reloading it will not work! The problem is that you miss
> the space after the \int command in the output.
I can't see that.
void
Title: Your Web Site is Now Responding
We are pleased to inform you that Your Web site http://www.lyx.org/ is back up and is no longer on error.
URL: http://www.lyx.org/
Time: 2001-07-27 05:21:47
As mentioned in the first alert, InternetSeer is
On 27-Jul-2001 Andre Poenitz wrote:
>> Try open a mathed inset and type the following:
>>
>> \int x
>>
>> then try to latex it it will give you errors.
>
> It does not.
Well maybe I'm not really uptodate, but cvs is down and I cannot update.
Just to be sure what's the file and whats the byte
> Well maybe I'm not really uptodate, but cvs is down and I cannot update.
> Just to be sure what's the file and whats the byte number? in it so I'll
> have a look if we have the same one.
math_bigopinset.C:19
> Anyway did you just have a look at the code or did you actually try it?
I tried
On Thursday 26 July 2001 18:08, you wrote:
> On Thu, Jul 26, 2001 at 05:17:57PM +0100, Angus Leeming wrote:
> > > | All of your citation commands are still "cite" aren't they?
> > > |
> > > | There is little point in including natbib if you aren't going to use
it!
> > >
> > > But... I thought
On 27-Jul-2001 Andre Poenitz wrote:
> math_bigopinset.C:19
Ok I miss the last ' ' in that line until I can update I add this here by
hand so that I'm able to read/latex the UserGuide (which is a very good test
file ;)
Jürgen
--
On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
> And it should probably not be output in the .lyx file. Probably a few
> changes in lyxfont.C will be enough.
It HAS to be outputed, BUT as the document_wide language, otherwise we're
not able to switch back and remain in the previously defined
Now we have a new one! You somehow output a 0 character in $ $ stuff.
Trye subsection 5.1.8 Other Math Symbols in the UserGuide. There is
something strange in the second paragraph:
a symbol whose LaTeX name you know, like \oint for "in[]" ...
Have a look at the "in[]" part seems strange to me!
Hi Andre,
I have found a very small example that crashes when being read. Obviously,
macros are not handled correctly (in the given example, "\Nat" is a
selfmade macro that should be defined somewhere in the LaTeX preamble)
Michael
--
On Fri, Jul 27, 2001 at 12:03:04PM +0200, Juergen Vigna wrote:
>
> On 27-Jul-2001 Jean-Marc Lasgouttes wrote:
>
> > And it should probably not be output in the .lyx file. Probably a few
> > changes in lyxfont.C will be enough.
>
> It HAS to be outputed, BUT as the document_wide language,
Hi,
there seems to be a memory leak in the text editing code (splitting
paragraphs, undoing paragraph splitting, etc.) that is not big but
happens quite often.
Michael
*
MLK: 256 bytes leaked at 0xe71b20
This memory was allocated from:
On Thu, Jul 26, 2001 at 05:37:51PM -0400, Amir Karger wrote:
> On Thu, Jul 26, 2001 at 08:26:21PM +0300, Dekel Tsur wrote:
> > On Wed, Jul 25, 2001 at 10:34:05PM +0100, Jose Abilio Oliveira Matos wrote:
> > > On Wed, Jul 25, 2001 at 03:03:40PM +0200, Jean-Marc Lasgouttes wrote:
> > > >
> >
> >
On 27-Jul-2001 Dekel Tsur wrote:
> Why the language in insetERT is changed to ignore_language ???
No your're right it should be inherit_language and now it is!
> The correct way for implementing insetERT is to have an InsetEditor and use
Your free to provide one!
> it instead of insetText.
On Wed, Jul 25, 2001 at 10:39:33AM +0200, Jean-Marc Lasgouttes wrote:
> >> 8. When several insets are placed consecutively (this can happen
> >> with error insets), clicking on an inset can result in opening the
> >> wrong one. A workaround is to use C-o, with the cursor placed just
> >> before
> a symbol whose LaTeX name you know, like \oint for "in[]" ...
>
> Have a look at the "in[]" part seems strange to me!
Uuh... yes... that's ugly. The math parser is not (yet) re-entrant, so
builting the table of 'builtin macros' during the reading of a 'real
formula' breaks everything...
On Fri, Jul 27, 2001 at 02:17:19PM +0200, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> On Thu, Jul 26, 2001 at 05:37:51PM -0400, Amir Karger wrote:
> >> On Thu, Jul 26, 2001 at 08:26:21PM +0300, Dekel Tsur wrote: > On
> >> Wed, Jul 25, 2001 at
1 - 100 of 152 matches
Mail list logo
