On 22 Sep, Garst R. Reese wrote:
I think you have not used LyX long enough :)
I normally use LaTeX to write my documents :)
My co-workers use LyX. But I cannot convince everybody else!!
Get busy with perl or python an script an interface.
I cannot write this type of software, I do not
On 22-Sep-99 Pablo De Napoli wrote:
Hello!
Hi Pablo!
My name is Pablo De Napoli , and I work at the mathemathics department of
Buenos Aires University (Argentina).
A really nice city (I loved it :)!!! Have been there in March and will
probably return there in November. I have been in
On 22 Sep 1999 14:59:01 +0200, Lars Gullik Bj°nnes wrote:
| For wizards:
| Does the *internal* implementation of those 'killer templates
| :)' or abstraction schemes eventually employ malloc()?
No. Not malloc. But you might see a new in there.
Then compilers like gcc use internally
"Pablo" == Pablo De Napoli [EMAIL PROTECTED] writes:
Hello,
Pablo Let me make a few suggestions , to improove this good
Pablo points of LyX:
Pablo 1) To make Lyx faster and easier to use , it would be nice
Pablo to be able to enter a big \ just like in latex (I mean
Pablo
"Arnd Hanses" [EMAIL PROTECTED] writes:
| Then compilers like gcc use internally behind the scenes malloc() as
| part of their implementation of the 'builtin' operator new.
This is not visible to us, so we don't really care.
| To be avoided. But I remember several huuuge routines free()ing and
Hello,
Thanks for your report. While I am not sure about the crash itself
(I'll have to get 0.89 and try it out), I have a question about your
patch: why is the following stuff needed?
Carlos + /* for compatibilities */ + #ifndef FALSE + # define
Carlos FALSE 0 + # define TRUE 1 +
I have just released a new prerelease of LyX. This is believed to be
the last prerelease before 1.0.4 proper. Some bugfixes since pre6 and
improvements to DocBook support.
As always with prerreleases you should be careful when trying it our,
but there are no known serious bugs in this
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| I have just released a new prerelease of LyX. This is believed to be
| the last prerelease before 1.0.4 proper. Some bugfixes since pre6 and
| improvements to DocBook support.
Ops. Forgot to say where you can get it.
On Thu, Sep 23, 1999 at 06:00:50PM +0200, Lars Gullik Bjønnes wrote:
I have just released a new prerelease of LyX. This is believed to be
the last prerelease before 1.0.4 proper. Some bugfixes since pre6 and
improvements to DocBook support.
If no real bugs are reported LyX 1.0.4 will be
On 23 Sep 1999 15:33:51 +0200, Lars Gullik Bj°nnes wrote:
I'm a little curious why you think that using inline funcs can help
us not using heap mem.
Stuff like this is unfortunately endemic e.g. in figinset.C:
[...]
{
[VIP (do Very Important Processing here)]
FOO *p = (FOO
On 23 Sep 1999, Jean-Marc Lasgouttes wrote:
I have a question about your patch: why is the following stuff needed?
Carlos + /* for compatibilities */ + #ifndef FALSE + # define
Carlos FALSE 0 + # define TRUE 1 + #endif + #endif /* _CONFIG_H
Carlos */
Previous versions of
"Arnd Hanses" [EMAIL PROTECTED] writes:
| {
| [VIP (do Very Important Processing here)]
|
| FOO *p = (FOO *)malloc(sizeof(FOO *));
|
| [VIP, not using p]
|
| while (1) {
|
| [VIP using p]
|
| if (BAR) break;
| }
|
| [VIP, not using p]
|
| free(p);
|
| [VIP]
| }
|
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| And of course, the maintainers of the various po-files are welcome to
| send us their updates...
I have sent them a special mail already.
Lgb
"Carlos" == Carlos A M dos Santos [EMAIL PROTECTED] writes:
Where are these TRUE and FALSE used?
Carlos LaTeXLog.C
You are right. I did not spot it because these references have been
fixed in the current cvs repository. You should find out that version
1.0.4pre8 compiles fine under
bg I need toget captions next to figures. Maybe I missed something
important but following the recipe in the Extended Features Documentation
section 2.5.7 didn't work out.
A minor inconsistency appeared in step 3:
"Press return to move the cursor above the caption"
The cursor just moved to the
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| I have just released a new prerelease of LyX. This is believed to be
| the last prerelease before 1.0.4 proper. Some bugfixes since pre6 and
| improvements to DocBook support.
Ops. Forgot to say where you can get it.
On Thu, Sep 23, 1999 at 06:00:50PM +0200, Lars Gullik Bjønnes wrote:
>
> I have just released a new prerelease of LyX. This is believed to be
> the last prerelease before 1.0.4 proper. Some bugfixes since pre6 and
> improvements to DocBook support.
>
> If no real bugs are reported LyX 1.0.4
On 23 Sep 1999 15:33:51 +0200, Lars Gullik Bj°nnes wrote:
>I'm a little curious why you think that using inline funcs can help
>us not using heap mem.
Stuff like this is unfortunately endemic e.g. in figinset.C:
[...]
{
[VIP (do Very Important Processing here)]
FOO *p = (FOO
On 23 Sep 1999, Jean-Marc Lasgouttes wrote:
> I have a question about your patch: why is the following stuff needed?
>
> Carlos> + /* for compatibilities */ + #ifndef FALSE + # define
> Carlos> FALSE 0 + # define TRUE 1 + #endif + #endif /* _CONFIG_H
> Carlos> */
Previous versions
"Arnd Hanses" <[EMAIL PROTECTED]> writes:
| {
| [VIP (do Very Important Processing here)]
|
| FOO *p = (FOO *)malloc(sizeof(FOO *));
|
| [VIP, not using p]
|
| while (1) {
|
| [VIP using p]
|
| if (BAR) break;
| }
|
| [VIP, not using p]
|
| free(p);
|
| [VIP]
| }
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| And of course, the maintainers of the various po-files are welcome to
| send us their updates...
I have sent them a special mail already.
Lgb
> "Carlos" == Carlos A M dos Santos <[EMAIL PROTECTED]> writes:
>> Where are these TRUE and FALSE used?
Carlos> LaTeXLog.C
You are right. I did not spot it because these references have been
fixed in the current cvs repository. You should find out that version
1.0.4pre8 compiles
bg I need toget captions next to figures. Maybe I missed something
important but following the recipe in the Extended Features Documentation
section 2.5.7 didn't work out.
A minor inconsistency appeared in step 3:
"Press return to move the cursor above the caption"
The cursor just moved to the
On 22 Sep, Garst R. Reese wrote:
> I think you have not used LyX long enough :)
I normally use LaTeX to write my documents :)
My co-workers use LyX. But I cannot convince everybody else!!
> Get busy with perl or python an script an interface.
I cannot write this type of software, I do not
On 22-Sep-99 Pablo De Napoli wrote:
> Hello!
Hi Pablo!
>
> My name is Pablo De Napoli , and I work at the mathemathics department of
> Buenos Aires University (Argentina).
>
A really nice city (I loved it :)!!! Have been there in March and will
probably return there in November. I have
On 22 Sep 1999 14:59:01 +0200, Lars Gullik Bj°nnes wrote:
>| For wizards:
>| Does the *internal* implementation of those 'killer templates
>| :)' or abstraction schemes eventually employ malloc()?
>
>No. Not malloc. But you might see a new in there.
Then compilers like gcc use internally
> "Pablo" == Pablo De Napoli <[EMAIL PROTECTED]> writes:
Hello,
Pablo> Let me make a few suggestions , to improove this good
Pablo> points of LyX:
Pablo> 1) To make Lyx faster and easier to use , it would be nice
Pablo> to be able to enter a big \ just like in latex (I mean
"Arnd Hanses" <[EMAIL PROTECTED]> writes:
| Then compilers like gcc use internally behind the scenes malloc() as
| part of their implementation of the 'builtin' operator new.
This is not visible to us, so we don't really care.
| To be avoided. But I remember several huuuge routines free()ing
Hello,
Thanks for your report. While I am not sure about the crash itself
(I'll have to get 0.89 and try it out), I have a question about your
patch: why is the following stuff needed?
Carlos> + /* for compatibilities */ + #ifndef FALSE + # define
Carlos> FALSE 0 + # define TRUE 1 +
I have just released a new prerelease of LyX. This is believed to be
the last prerelease before 1.0.4 proper. Some bugfixes since pre6 and
improvements to DocBook support.
As always with prerreleases you should be careful when trying it our,
but there are no known serious bugs in this
30 matches
Mail list logo
