Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Wed, Mar 08, 2000 at 05:46:37AM +0100, Lars Gullik Bjønnes wrote:
| >
| > After that is done, I think we should have a new prerelease to get a
| > broader userbase to have a look. (This will perhaps also be a nice
| > time for rae to update again?) I'l
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Sat, Mar 11, 2000 at 03:34:32PM +0100, Lars Gullik Bjønnes wrote:
| >
| > No, it is just that 2default" is taken out of the array that holds the
| > languages, but shold (as I have forgotten to do) be recognised as a
| > special case.
| >
|
| Why do
I've attached revised scripts. The gtkmmconvert script is newer than the
gtkmmconvert2 script so don't get confused by the names.
On Sun, 12 Mar 2000, Allan Rae wrote:
[...]
> The script does nearly everything that's possible without human
> intervention.
I think that I've just about exhausted
- Forwarded message from "D.Stolte" <[EMAIL PROTECTED]> -
Delivered-To: [EMAIL PROTECTED]
Date: Sun, 12 Mar 2000 20:49:16 +0100
From: "D.Stolte" <[EMAIL PROTECTED]>
Organization: TU-BS
X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.14 i686)
X-Accept-Language: de-DE,en
To: "Kayvan A. Sylva
Can anybody tell me how it works? I am trying to figure out where
this three-day-lag that I observe comes from...
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL PROTECTED]
You probably remember Wolfgang Riedel's report on a strange feature:
You can write \mathrm{\frac{m}{s}} and everything works as expected until
the file is reloaded (in the next session e.g.). Then the \mathrm is
gone. If you use \frac{\mathrm{m}}{\mathrm{s}} everything stays alright.
This resem
"D.Stolte" wrote:
>
> Hello Developers
>
> I am heavily attacked by a nasty bug in lyx since 1.1.4. I tried the
> version 1.1.4{fix1,fix2} and 1.1.5cvs (march 3.), too, but with no
> solution. The version 1.1.2 was ok.
>
> The bug appears after pressing the backspace key several times to
> dele
On Sun, Mar 12, 2000 at 03:04:19PM +0100, D.Stolte wrote:
> Hello Developers
>
> I am heavily attacked by a nasty bug in lyx since 1.1.4. I tried the
> version 1.1.4{fix1,fix2} and 1.1.5cvs (march 3.), too, but with no
> solution. The version 1.1.2 was ok.
>
> The bug appears after pressing the
On Sat, Mar 11, 2000 at 03:34:32PM +0100, Lars Gullik Bj&resh;nnes wrote:
>
> No, it is just that 2default" is taken out of the array that holds the
> languages, but shold (as I have forgotten to do) be recognised as a
> special case.
>
Why do we need the "default" language?
can't we just remov
On Wed, Mar 08, 2000 at 05:46:37AM +0100, Lars Gullik Bj&resh;nnes wrote:
>
> After that is done, I think we should have a new prerelease to get a
> broader userbase to have a look. (This will perhaps also be a nice
> time for rae to update again?) I'll put in some cvs tags.
>
But there are sti
Hello Developers
I am heavily attacked by a nasty bug in lyx since 1.1.4. I tried the
version 1.1.4{fix1,fix2} and 1.1.5cvs (march 3.), too, but with no
solution. The version 1.1.2 was ok.
The bug appears after pressing the backspace key several times to
delete chars. I dont know how to EXACTLY
On Thu, Feb 17, 2000 at 11:37:14AM -0500, Amir Karger wrote:
> -Amir
> ps John: I would respond to your mail, but I'm too busy working on my
> thesis. Quick roundup: I've started writing although I haven't exactly got
> all of my data yet; we may or may not have a date; I'm only somewhat
> freakin
On Thu, Mar 09, 2000 at 12:23:43PM -0500, Amir Karger wrote:
>
> For now, it's a pretty simple one. You know how LyX 1.0.4 and on puts
> citations from a bunch of included documents into the "insert citations"
> menu? Well, what's the status on inter-document references? I've got each
> chapter of
Angus Leeming <[EMAIL PROTECTED]> writes:
| > Yes, we should not use the print form when exporting at all, that is a
| > hack. I got a patch that did the export stuff correct, but I had some
| > comments to that patch and asked that it be corrected before I'd
| > commit it... this was never done.
On Sat, 11 Mar 2000, Ben Cazzolato wrote:
> Is the following better
Yes although you should also do a few other things...
>
> (gdb) where
followed by:
up
until you get to...
> #0 0x401e0111 in __kill ()
> #1 0x401dfd66 in raise (sig=6) at ../sysdeps/posix/raise.c:27
> #2 0x401e
15 matches
Mail list logo