I have forwarded your msg to the devel lyx.
I am sure our DocBook person will answer your questions.
Lgb
--- Start of forwarded message ---
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 06 Sep 1999 18:10:16 +
From: "Andrew S. Townley" <[EMAIL PROTECTED]>
To: Lars Gullik =?iso-
Duncan Simpson <[EMAIL PROTECTED]> writes:
Ok, this is known. But what has this _really_ to do with the Subject?
| According to my man page strcasecmp is conforming to BSD 4.3 (and
| all unicies
| I have seen so far, inclduign SunOS). AFAIK GNU libc 2.1 is
| conforming to ANSI
| and POSIX b
According to my man page strcasecmp is conforming to BSD 4.3 (and all unicies
I have seen so far, inclduign SunOS). AFAIK GNU libc 2.1 is conforming to ANSI
and POSIX but also includes common extensions, like mmap, lstat, setrlimit,
snprintf, select, fileno, *BSD sockets and whole bunch of oth
On Fri, 3 Sep 1999, Amir Karger wrote:
> Question for the latex gurus in the audience.
>
> One popular complaint about lyx 1.0 is that you can't get the equivalent of
> \section[short]{long section title}.
> [...]
Hi Amir,
I posted exactly the same trick some months ago to get short caption
en
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
| Lars> Do you build inside the development tree? I get that with 0.88.1
| Lars> | because I build outside the dev tree.
On Mon, 6 Sep 1999 14:38:31 +0200 (MET DST), Jean-Marc Lasgouttes
wrote:
>
>Do you use the static or dynamic xforms library? One has libxpm
>built-in but with the other, it might happen that you have a dynamic
>libxpm with version !=3.4k (the one used by xforms) and that there is
>a binary incompa
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
Lars> Do you build inside the development tree? I get that with 0.88.1
Lars> | because I build outside the dev tree. In this case, when
Lars> starting lyx | as 'src/lyx', the c
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| Do you build inside the development tree? I get that with 0.88.1
| because I build outside the dev tree. In this case, when starting lyx
| as 'src/lyx', the code which finds the library path gets confused
| (some of-by-one error in string handlin
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Hava anyone been able to compile and run LyX with xfroms 0.89?
Lars> I get a (gdb) run Starting program:
Lars> /home/larsbj/Development/lyx/src/lyx BadDrawable (invalid Pixmap
Lars> or Window parameter)
Lars> when trying. It
Hava anyone been able to compile and run LyX with xfroms 0.89?
I get a
(gdb) run
Starting program: /home/larsbj/Development/lyx/src/lyx
BadDrawable (invalid Pixmap or Window parameter)
when trying. It seems that it crashes in the initialization of the xpm
part of the lib.
(I don't link with
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> fwrite is essentially fprintf without buffering. So it should be
| Lars> no problem switching to fprintf. (actually fprintf are
| Lars> preferrable because of the bufferin
Jean-Marc Lasgouttes wrote:
>
> > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Lars> fwrite is essentially fprintf without buffering. So it should be
> Lars> no problem switching to fprintf. (actually fprintf are
> Lars> preferrable because of the buffering)
>
> fwrite was
Hi,
I wish to know if lyx 0.10 and 0.12 are year 2000 compliant.
Cany you answer it?
Thanks,
--
Oscar Guell Perez
University of Catalonia
Tel 93 401 73 27
[EMAIL PROTECTED]
http://www.lsi.upc.es/~oskar
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> fwrite is essentially fprintf without buffering. So it should be
Lars> no problem switching to fprintf. (actually fprintf are
Lars> preferrable because of the buffering)
fwrite was used instead of fprintf because it is suppose
On 6 Sep 1999 06:13:13 +0900, [EMAIL PROTECTED] wrote:
>"Arnd Hanses" <[EMAIL PROTECTED]> wrote:
>
>> Going up the stack 'till main() I'm now convinced that _heapset(9)
>> produces on my box a self-induced crash (heap corruption) in emx libs.
>> I'm unsure why this happens, it shouldn't, I think
15 matches
Mail list logo
