[PATCH] remove kde frontend

this gets rid of the kde config gubbins etc. cvs remove -f config/kde.m4 thanks john -- "Please crack down on the Chinaman's friends and Hitler's commander. Mother is the best bet and don't let Satan draw you too fast. A boy has never wept ... nor dashed a thousand kim. Did you hear me?"

[PATCH] small changes

A random collection of small fixes thanks john -- "Please crack down on the Chinaman's friends and Hitler's commander. Mother is the best bet and don't let Satan draw you too fast. A boy has never wept ... nor dashed a thousand kim. Did you hear me?" - Dutch Schultz Index: ChangeL

compile problem

Dear All, I am trying to compile cvs. I get the following error message, can someone tell me whats going on here? Template problems? I am running redhat 6.2, egcs-1.1.2-30 Thanks, Ed. make[3]: Entering directory `/tmp/lyx-compile/src/support' /bin/sh ../../libtool --mode=compile g++ -DHAVE_

Re: compile problem

On Sat, Jun 02, 2001 at 01:42:40PM +0200, Edwin Leuven wrote: > Dear All, > > I am trying to compile cvs. I get the following error message, can someone > tell me whats going on here? Template problems? I am running redhat 6.2, > egcs-1.1.2-30 This is your problem. Install gcc-2.95.X and yo

Re: compile problem

On Sat, 2 Jun 2001, Kayvan A. Sylvan wrote: > On Sat, Jun 02, 2001 at 01:42:40PM +0200, Edwin Leuven wrote: > > Dear All, > > > > I am trying to compile cvs. I get the following error message, can someone > > tell me whats going on here? Template problems? I am running redhat 6.2, > > egcs-1.1.2-

natbib

Those interested in what's happening to the natbib branch and not subscribed to cvs-log (Mike?), here's what I've been up to: Also, a first stab at making the Citation dialog more "user friendly" with natbib; replaced all those citet, citep, citealt commands in the

Re: Are dead keys dead ?

On Thu, May 31, 2001 at 03:22:44PM +0200, Lars Gullik Bjønnes wrote: > [EMAIL PROTECTED] writes: > > | I will precise here what I had stated earlier about the dead keys not working. > | I am using the latest CVS version, right after an update. > | I have selected "No keymap" in the Edit->Preferen

bug not closed ?!

Lars closed the loa etc. list problem as closed. With current CVS, I don't get this - If I have two algorithm floats, I can't look at the algorithm float list. Clicking on the LOA button does nothing. What's going on ? thanks john -- "Please crack down on the Chinaman's friends and Hitler'

how to crash lyx

empty doc, open TOC dialog, click on "No lists" entry in text browser. thanks john -- "Please crack down on the Chinaman's friends and Hitler's commander. Mother is the best bet and don't let Satan draw you too fast. A boy has never wept ... nor dashed a thousand kim. Did you hear me?"

Scripting Language Shootout

There was a suggestion to do a shootout between scripting languages. It was mostly done already, though not in the context of an embedded editor. Check this site for comparisons: http://www.bagley.org/~doug/shootout/ This is by no means complete or correct, the author says that many of the progr

Re: Scripting Language Shootout

On Sun, 3 Jun 2001, Baruch Even wrote: > There was a suggestion to do a shootout between scripting languages. It > was mostly done already, though not in the context of an embedded > editor. > > Check this site for comparisons: http://www.bagley.org/~doug/shootout/ > > This is by no means complet

tracker and lyx

I think we should "officially" announce the bug tracker in the message for 1.2.0pre1 What do others think ? thanks john -- "Please crack down on the Chinaman's friends and Hitler's commander. Mother is the best bet and don't let Satan draw you too fast. A boy has never wept ... nor dashed a

Lists and tables

At the risk of wormcan opening, is there any chance that lists in table cells will ever be enabled again ? It strikes me as a missing feature :( thanks john -- "Please crack down on the Chinaman's friends and Hitler's commander. Mother is the best bet and don't let Satan draw you too fast. A

Re: Scripting Language Shootout

* John Levon <[EMAIL PROTECTED]> [010603 01:26]: > > I would suggest the simplest solution to this decision is to see what > gets implemented ... since there aren't that many developers I don't > really see a problem in choosing a particular language, since there is > unlikely to be more than one