Re: LyX2.0 RC and 1.6 on same system

2011-04-09 Thread Liviu Andronic
On Sun, Apr 10, 2011 at 12:51 AM, Julien Rioux wrote: > Unless you configure with the flag --with-version-suffix, then both 1.6 and > 2.0 will be installed as "lyx". Use the flag when compiling RC2, and you > will install as "lyx-2.0.0rc2" and it can live side-by-side with other > versions of lyx.

Re: LyX2.0 RC and 1.6 on same system

2011-04-09 Thread Peter Kümmel
On 10.04.2011 00:51, Julien Rioux wrote: >> >> I realize that LyX 2.0 is not ready for release yet, but I'm still excited >> to try it. >> Not ready? Only because of the corrupted 1.6 installation or have you found other issues? Peter

Re: does trunk compile ?

2011-04-09 Thread Peter Kümmel
On 09.04.2011 14:20, Jürgen Spitzmüller wrote: > Tommaso Cucinotta wrote: >> Is that only me experimenting this ? > > See the message I just posted. You have to > > #include > > in lstrings.cpp. > > However, I wonder whether r38320 was a good idea during the freeze we just > have. Removed it

Re: LyX2.0 RC and 1.6 on same system

2011-04-09 Thread Julien Rioux
On 09/04/2011 3:46 PM, Gustavo Goretkin wrote: I'm running Ubuntu 10.10 and have been using LyX 1.6. I compiled LyX2.0 RC2 and it seems to have clobbered my LyX 1.6 installation a bit. For example, when I make a new file, I get a few message boxes like: "LyX: Document class not available. The la

compiler warnings in trunk

2011-04-09 Thread Julien Rioux
I always saw those two warnings (paraphrased): Lexer.cpp:197 may be used uninitialized Server.cpp:1018 ignoring return value of write(...) I have looked into these two warnings to learn a bit more on cpp. For the first one, I could remove the warning by removing the anonymous namespace, but I

LyX2.0 RC and 1.6 on same system

2011-04-09 Thread Gustavo Goretkin
I'm running Ubuntu 10.10 and have been using LyX 1.6. I compiled LyX2.0 RC2 and it seems to have clobbered my LyX 1.6 installation a bit. For example, when I make a new file, I get a few message boxes like: "LyX: Document class not available. The layout file requested by this document, article lay

Re: does trunk compile ?

2011-04-09 Thread Vincent van Ravesteijn
On 9-4-2011 23:50, Pavel Sanda wrote: Jürgen Spitzmüller wrote: Tommaso Cucinotta wrote: Is that only me experimenting this ? See the message I just posted. You have to #include in lstrings.cpp. However, I wonder whether r38320 was a good idea during the freeze we just have. secondly would

Re: does trunk compile ?

2011-04-09 Thread Pavel Sanda
Jürgen Spitzmüller wrote: > Tommaso Cucinotta wrote: > > Is that only me experimenting this ? > > See the message I just posted. You have to > > #include > > in lstrings.cpp. > > However, I wonder whether r38320 was a good idea during the freeze we just > have. secondly wouldn't be better to

Re: does trunk compile ?

2011-04-09 Thread Jürgen Spitzmüller
Tommaso Cucinotta wrote: > Is that only me experimenting this ? See the message I just posted. You have to #include in lstrings.cpp. However, I wonder whether r38320 was a good idea during the freeze we just have. Jürgen

does trunk compile ?

2011-04-09 Thread Tommaso Cucinotta
Is that only me experimenting this ? make[5]: ingresso nella directory "/home/tommaso/lyx-trunk-ws/lyx-trunk/src/support" CXX lstrings.o lstrings.cpp: In function ‘lyx::docstring lyx::support::bformat(const lyx::docstring&, Arg1) [with Arg1 = lyx::docstring]’: lstrings.cpp:1331: error: ‘cout’

Re: r38320 - lyx-devel/trunk/src/support

2011-04-09 Thread Jürgen Spitzmüller
kuemmel wrote: > Author: kuemmel > Date: Sat Apr 9 11:42:52 2011 > New Revision: 38320 > URL: http://www.lyx.org/trac/changeset/38320 > > Log: > temporary code to find bug #7371 doesn't compile here without included Jürgen

Re: Producing inelegant documents with LyX

2011-04-09 Thread Liviu Andronic
On Sat, Apr 9, 2011 at 12:51 PM, Andrew Parsloe wrote: > Dear LyX devs, > > I discovered LyX sometime in 2007 (LyX 1.4.3?) and it served wonderfully for > the kind of tasks that my dear old Word 95 simply couldn't handle -- big > mathematics documents full of equations and diagrams and cross-refer

Re: A basic requested feature

2011-04-09 Thread Liviu Andronic
On Sat, Apr 9, 2011 at 1:05 PM, Sam Lewis wrote: > Inon Sharony TAU.ac.IL> writes: > > >> As in MS (boo!) Office, when saving a new file, whatever appears in the >> \title section should automatically be guessed as the name that the file >> should be saved as. >> >> Do you agree? > > No really. I

Producing inelegant documents with LyX

2011-04-09 Thread Andrew Parsloe
Dear LyX devs, I discovered LyX sometime in 2007 (LyX 1.4.3?) and it served wonderfully for the kind of tasks that my dear old Word 95 simply couldn't handle -- big mathematics documents full of equations and diagrams and cross-references. It was the cross-references that seemed to grind Word

Re: A basic requested feature

2011-04-09 Thread Sam Lewis
Inon Sharony TAU.ac.IL> writes: > As in MS (boo!) Office, when saving a new file, whatever appears in the > \title section should automatically be guessed as the name that the file > should be saved as. > > Do you agree? No really. I normally add the title as the last thing, long after havin

Re: Too much options in LyX

2011-04-09 Thread Liviu Andronic
On Sat, Apr 9, 2011 at 12:56 PM, Sam Lewis wrote: > >> Why don't we add an option in the Tools -> Preferences (and maybe in >> Document - >> Settings too) dialog to show >> only the most important options, you know, that "basic" and "expert" > > Are not most LyX users "expert" users anyway? > In

Re: Too much options in LyX

2011-04-09 Thread Sam Lewis
> Why don't we add an option in the Tools -> Preferences (and maybe in Document > - > Settings too) dialog to show > only the most important options, you know, that "basic" and "expert" Are not most LyX users "expert" users anyway? Cheers, Sam

Re: A basic requested feature

2011-04-09 Thread Jean-Marc Lasgouttes
Le 08/04/11 21:04, Diego Queiroz a écrit : But this should not be a big deal. Every general purpose system has lots of options and customizations. LyX has an option to set if you prefer a single close button instead of one for each tab, so what's wrong in adding a new option like this? I think