>
> Failing with this message (at link-time):
>
> FloatList.o: In function `global constructors keyed to floatList':
> /home/kayvan/src/lyx-temp/src/FloatList.C:5: undefined reference to
> `FloatList::FloatList(void)'
> insets/.libs/libinsets.a(insetfloat.o): In function `InsetFloat::Latex(Buff
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | > present).
Lars> Won't this always work irrespective of the names given by the
Lars> user ro | > his files? | | I use: | | \use_tempdir false | | So,
Lars> no. It's not guarante
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> This this is very close. Please have a go. (We also have other
Lars> insets where this excact samt thing need to be fixed.)
URL inset comes to mind.
JMarc
> "R" == R Lahaye <[EMAIL PROTECTED]> writes:
R> Hello, [I'm not member of lyx-devel, include my address in a CC for
R> replies]
R> The citation references have some troubles: many and/or long keys
R> cause lines to overflow the right margin, which seems to be too
R> complicated to handle n
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> "Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
>>
>> | What's wrong with offering to rename the directory?
>>
>> That you suddenly might break all the other programs that used this
>> dir without your knowledge?
As
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Forgive me if I'm wrong, but doesn't lyx work from a temporary
Angus> directory? Why not create sym-links in this temporary directory
Angus> to all include/accessed/used files and then do the export to
Angus> TeX etc also in the tmp
> "Duncan" == Duncan Simpson <[EMAIL PROTECTED]> writes:
Duncan> If LyX is going to detect and do special magic to deal with
Duncan> file names with natsty character like spaces in them, then the
Duncan> current suggestions are IMHO the wrong thing. File names with
Duncan> spaces, and practic
Hi All!
If you're interested I just made the whole lot of the LyX Documentation
available online, the link is:
http://www.sad.it/~jug/lyx/lyxdoc
Ciao Jürgen
P.S.: The generation of the documentation is automatized and I don't fix
inconsistences or errors by hand, so just do
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> Hi All! If you're interested I just made the whole lot of the
Juergen> LyX Documentation available online, the link is:
Juergen> http://www.sad.it/~jug/lyx/lyxdoc
Juergen> Ciao Jürgen
Juergen> P.S.: The generat
> That's what a windows application would do. And then this will break
> many other applications which work in the same directory.
No. It will only break applications with that rely on directories names
not to change. Which applications require this? For sure, LyX does not.
> You should now t
> So I just realized that in the last couple months, two new top-level menus
> have been created. Has this been discussed? Are we sure it's a good idea?
I strongly think that the TOC should be a top-level entry.
This menu is the most used menu of all, so it should not be
put away somehere!
The
Hi!
Sorry for the late reply. I didn't mention that I was not subscribed to the
list. Can you add me to the list?
> | Hi!
> |
> | If I export a document of type SGML (LinuxDoc article) as LinuxDoc an
> | additional tag is inserted after each tag. The same
> | happens
>
> Is this cvs lyx? Or
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> That's what a windows application would do. And then this will
>> break many other applications which work in the same directory.
Asger> No. It will only break applications with that rely on
Asger> directories names not to c
> (But why close and open all tags? Wouldn't it suffice to
> just open the new tag:
No, since the tags wouldn't nest properly.
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL PROTECTED]
In a message dated: 30 Jun 2000 12:22:37 +0200
Jean-Marc Lasgouttes said:
>That's great! Lars, would it be possible to have that on the main
>www-site? Nice pdf versions of the docs would be nice too (using ps
>fonts).
Wouldn't it be a lot easier to open the docs up in LyX and export them as P
Hello !
I am trying to compile LyX 1.1.5 on a Solaris 2.7 system, using g++ 2.95.2
It seems like a whole load of include directives look like
#include
instead of
#include
which leads to errors like this:
g++ -DHAVE_CONFIG_H -I. -I. -I../../src -I../../images -I./../ -I../../src/cheaders
-I
On Fri, Jun 30, 2000 at 02:43:08PM +0200, Guenter Grossberger wrote:
> Hi!
>
> Sorry for the late reply. I didn't mention that I was not subscribed to the
> list. Can you add me to the list?
>
> > | Hi!
> > |
> > | If I export a document of type SGML (LinuxDoc article) as LinuxDoc an
> > | addi
> "Paul" == Paul Lussier <[EMAIL PROTECTED]> writes:
>> That's great! Lars, would it be possible to have that on the main
>> www-site? Nice pdf versions of the docs would be nice too (using ps
>> fonts).
Paul> Wouldn't it be a lot easier to open the docs up in LyX and
Paul> export them as PS
> "Jochen" == Jochen Kmietsch <[EMAIL PROTECTED]> writes:
Jochen> Hello ! I am trying to compile LyX 1.1.5 on a Solaris 2.7
Jochen> system, using g++ 2.95.2 It seems like a whole load of include
Jochen> directives look like
Jochen> #include
Jochen> instead of
Jochen> #include
These are
Jochen Kmietsch <[EMAIL PROTECTED]> writes:
| Hello !
|
| I am trying to compile LyX 1.1.5 on a Solaris 2.7 system, using g++ 2.95.2
| It seems like a whole load of include directives look like
|
| #include
|
| instead of
|
| #include
So solaris has broken C++ headers...
Jean-Marc, can we
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jochen Kmietsch <[EMAIL PROTECTED]> writes: |
Lars> Hello ! | | I am trying to compile LyX 1.1.5 on a Solaris 2.7
Lars> system, using g++ 2.95.2 | It seems like a whole load of include
Lars> directives look like | | #include |
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Jochen Kmietsch <[EMAIL PROTECTED]> writes: |
| Lars> Hello ! | | I am trying to compile LyX 1.1.5 on a Solaris 2.7
| Lars> system, using g++ 2.95.2 | It seems like a whol
> I am trying to compile LyX 1.1.5 on a Solaris 2.7 system, using g++ 2.95.2
> It seems like a whole load of include directives look like
> #include
>
> instead of
>
> #include
The first version is correct and should be available with gcc 2.95.
If not, you can create your own iosfwd:
--
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| But he is using g++ 2.95.2, so things should work well.
Lars> gcc 2.95.2 != glibc != glibc++
glibc is not in the equation here. Are you saying that we should
support compiling on gcc 2.95.2 with an older STL version (from sun or
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > I am trying to compile LyX 1.1.5 on a Solaris 2.7 system, using g++ 2.95.2
| > It seems like a whole load of include directives look like
| > #include
| >
| > instead of
| >
| > #include
|
| The first version is correct and should be available wi
Hello Jean !
On 30-Jun-2000 Jean-Marc Lasgouttes wrote concerning Re: LyX 1.1.5 and missing ".h"
on include files:
> These are standard C++ headers, and certinly are available with g++
> 2.95.2. Do you have libstdc++ installed? Which version?
libstdc++.so.2.10.0
I am fiddeling with --with-extr
In a message dated: 30 Jun 2000 15:46:21 +0200
Jean-Marc Lasgouttes said:
>PS: the real reason is that, since I'm not going to do it myself, I
>can propose to do compilcated things without fear.
A, I see :) Then yes! By all means! On-line docs for everyone :)
--
Seeya,
Paul
On Fri, Jun 30, 2000 at 09:41:50AM +0200, Juergen Vigna wrote:
>
> >
> > Failing with this message (at link-time):
> >
> > FloatList.o: In function `global constructors keyed to floatList':
> > /home/kayvan/src/lyx-temp/src/FloatList.C:5: undefined reference to
> > `FloatList::FloatList(void)'
While routine use of catcode magic counts as brain damage, all spaces take is
teeling TeX that space is a letter or other character. the scope of which can
be bracketed by a group. For example one could write
{\aftergroup\input\catcode` =12\aftergroup{File name with spaces}}
which works becau
29 matches
Mail list logo
