On 06-Oct-2000 Gaillard Pierre-Olivier wrote:
> Hello, the sources to the xml directory that I am using right now. It's
> currently VERY SMALL. But when we start using libxml to be more
> compliant with xml (unicode and so on) then we will have something much
> bigger to bundle in LyX. But I gue
> "Matthias" == Matthias Peick <[EMAIL PROTECTED]> writes:
Matthias> Hello, 1. "export LANG=de_DE" 2. Make sure that
Matthias> LC_-variables aren't set. 3. "lyx &" 4. Create a new
Matthias> document from template "dinbrief.lyx". 5. Look at your
Matthias> xterm: "Achtung: Benötige LyX-Format 2
> "Ed" == Ed Hurst <[EMAIL PROTECTED]> writes:
Ed> What would yuo need to see to examine this problem? -- I formatted
Ed> an article for printing. I had a title, and author and date. Below
Ed> the date, I inserted a medskip and a horizontal line. Then came a
Ed> paragraph, all emphasized, fol
Attached are two patches. Both are physically large but very simple.
patch_insets
==
In patch_insets, I modified the Inset::Clone method, so that it is passed a
Buffer const & parameter. I also modified all Inset c-tors that are passed a
Buffer *. They are now passed a Buffer const & al
> "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
Baruch> I wanted to know if users of GCC 2.95.2 (the base for the
Baruch> AthlonGCC) have any such troubles compiling LyX? I'm using the
Baruch> --enable-assertions --enable-warnings configure options.
I've got trouble compiling with 2.95
On Mon, 9 Oct 2000, Baruch Even wrote:
> Hi,
>
> While setting up my new computer I've upgraded the compiler from the
> distributions egcs 1.1.2 to AthlonGCC 2.95.3, the AthlonGCC is a patch
> over the PGCC 2.95.3 which is a patch against GCC 2.95.2. The PGCC is a
> pentium optimized version of
> "Eli" == Eli Tziperman <[EMAIL PROTECTED]> writes:
Eli> It did indeed help. Thanks. The compilation did get stuck at
Eli> another step later... see below. Eli
Eli> ld32: WARNING 84 :
Eli> /usr/local/lib/libiberty.a is not used for resolving any symbol.
Eli> ld32: FATAL 12 : Expecting n32 o
I see someone added cases in lyxinclude for 2.97 (latest CVS gcc). Well
it won't compile without disabling -pedantic either, because of this error
:
In file included from insetgraphicsParams.C:20:
../../src/support/translator.h:93: parse error before ';' token In file
included from insetgraphics
is available now from http://sourceforge.net/projects/qtarch
Anyone editing KDE dialogs please update, thanks.
john
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Lars what do you think? Now or after 1.1.6? (I guess after we really
| should concentrate on removing the bugs we have and not continuing on
| introducing new stuff otherwise we won't get 1.1.6 out this year!
| (this applies also to Dekels last patch IM
John Levon <[EMAIL PROTECTED]> writes:
| > I wanted to know if users of GCC 2.95.2 (the base for the AthlonGCC) have
| > any such troubles compiling LyX? I'm using the --enable-assertions
| > --enable-warnings configure options.
| >
|
| I have yet to be able to compile with 2.95.2 - internal co
On 9 Oct 2000, Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | > I wanted to know if users of GCC 2.95.2 (the base for the AthlonGCC) have
> | > any such troubles compiling LyX? I'm using the --enable-assertions
> | > --enable-warnings configure options.
> | >
> |
> |
John Levon <[EMAIL PROTECTED]> writes:
| I see someone added cases in lyxinclude for 2.97 (latest CVS gcc). Well
| it won't compile without disabling -pedantic either, because of this error
| :
We absolutely do not want -pedantic, that was just a forgotten case by
me.
| Also, I made -fhonor-std
On 09-Oct-2000 Lars Gullik Bjønnes wrote:
>
> I have _no_ problems with gcc 2.95.2
>
I'm actually compiling with gcc-2.96 (from a RedHat 7.0 installation).
The only problem I had was the LString.h error message as I think some
stl include-file includes before LString.h can be included and
it
On 9 Oct 2000, Lars Gullik Bjønnes wrote:
> We absolutely do not want -pedantic, that was just a forgotten case by
> me.
>
ok. just out of interest why is this ? I'm not enough of a C++ boffin to
see what's so wrong with pedantic ;)
>
> If you compile 2.97 without --enable-libstdcxx-v3 I don't
> BTW: Could someone tell me what: RTFM means? (for translation)
;-)
Read The F...ing Manual
:-(
Insert your favourite F-word here!
A
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> After reading the ui file, we have a representation of the menu
Dekel> by a rooted tree, whose nodes are instances of the Menu class
Dekel> (if I read the code correctly, the edges of the tree are stored
Dekel> using the submenu_ stri
On Mon, 9 Oct 2000, Juergen Vigna wrote:
>
> On 09-Oct-2000 Lars Gullik Bjønnes wrote:
> >
> > I have _no_ problems with gcc 2.95.2
> >
>
> I'm actually compiling with gcc-2.96 (from a RedHat 7.0 installation).
> The only problem I had was the LString.h error message as I think some
> stl inc
On 09-Oct-2000 John Levon wrote:
>
> I got this as a result of the -fhonor-std flag - it means that the simple
> string test fails with "string undeclared", so it thinks the actual
> implementation is buggy. Remove -fhonor-std and it will go away (at least
> it did for me). Latest CVS I noticed
John Levon <[EMAIL PROTECTED]> writes:
| On 9 Oct 2000, Lars Gullik Bjønnes wrote:
|
| > We absolutely do not want -pedantic, that was just a forgotten case by
| > me.
| >
|
| ok. just out of interest why is this ? I'm not enough of a C++ boffin to
| see what's so wrong with pedantic ;)
|
| >
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 09-Oct-2000 John Levon wrote:
| >
| > I got this as a result of the -fhonor-std flag - it means that the simple
| > string test fails with "string undeclared", so it thinks the actual
| > implementation is buggy. Remove -fhonor-std and it will go aw
On 9 Oct 2000, Lars Gullik Bjønnes wrote:
> gcc 3 will certainly use libstdc++-v3 so why not use that for testing.
>
yep, makes sense as long as testers are aware that codesourcery RPMs and
the like won't work ... I'm aware now so ... :)
>
> My trick is to ave a small Build script that build t
On Mon, 9 Oct 2000, John Levon wrote:
> On Mon, 9 Oct 2000, Baruch Even wrote:
>
> > Hi,
> >
> > While setting up my new computer I've upgraded the compiler from the
> > distributions egcs 1.1.2 to AthlonGCC 2.95.3, the AthlonGCC is a patch
> > over the PGCC 2.95.3 which is a patch against GCC
On 9 Oct 2000, Jean-Marc Lasgouttes wrote:
> > "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
>
> Baruch> I wanted to know if users of GCC 2.95.2 (the base for the
> Baruch> AthlonGCC) have any such troubles compiling LyX? I'm using the
> Baruch> --enable-assertions --enable-warnings co
On Mon, 9 Oct 2000, Baruch Even wrote:
> I've tried with 2.95.2 (unpatched) on my machine and had troubles too. I'm
> also having troubles with egcs 1.1.2 for what it matters (It cant find
> GroupCache::find on linking, I'm forced to make the function un-inlined).
>
Same problem for me, I need
On Mon, Oct 09, 2000 at 09:58:27AM +0300, Andrew Zabolotny wrote:
> On Sat, 7 Oct 2000 17:46:13 +0200, Dekel Tsur wrote:
>
> >Actually we (I) plan to remove the encoding selection from the document
> >dialog. There will be only one available encoding: Unicode.
> Um... does TeX eat unicode files?
On Mon, Oct 09, 2000 at 09:50:16AM +0200, Juergen Vigna wrote:
> Lars what do you think? Now or after 1.1.6? (I guess after we really
> should concentrate on removing the bugs we have and not continuing on
> introducing new stuff otherwise we won't get 1.1.6 out this year!
> (this applies also to
Hello,
Attached is a patch for the InsetGraphics and related stuff, this patch
touches mostly on InsetGraphics and adding some stuff for GUII, it does
not touch anything outside that EXCEPT a small change to the Painter class
to add a method that draws images that come from LyXImage, this is an
a
Small changes to lyxrc.example
patch.gz
"Lars Gullik Bjønnes" wrote:
>
> Gaillard Pierre-Olivier <[EMAIL PROTECTED]> writes:
>
> | XMLAttributes is a subclass of map that defines a method
> | "set(string name, int value)".
>
> By adding a [] operator you can at least make things a bit nicer.
>
I tried this (see lower) but since it
Following is a report on a bug that was already reported here, namely when
closing an open file LyX will crash.
The reason is that when the Buffer is d-tor'ed it runs a signal
updateBufferDependent (this is done in BufferView::Pimpl), this signal in
turn runs a method updateAllVisibleBufferRelate
On Mon, 9 Oct 2000, Baruch Even wrote:
> On 9 Oct 2000, Jean-Marc Lasgouttes wrote:
>
> > > "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
> >
> > Baruch> I wanted to know if users of GCC 2.95.2 (the base for the
> > Baruch> AthlonGCC) have any such troubles compiling LyX? I'm using th
On Tue, 10 Oct 2000, Allan Rae wrote:
> On Mon, 9 Oct 2000, Baruch Even wrote:
>
> > On 9 Oct 2000, Jean-Marc Lasgouttes wrote:
> >
> > > > "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes:
> > >
> > > Baruch> I wanted to know if users of GCC 2.95.2 (the base for the
> > > Baruch> Athlon
On Mon, 9 Oct 2000, Dekel Tsur wrote:
> Small changes to lyxrc.example
I'll apply this.
Allan. (ARRae)
On Mon, 9 Oct 2000, Angus Leeming wrote:
> Attached are two patches. Both are physically large but very simple.
>
> patch_insets
> ==
Haven't looked at this one.
> patch_xforms
> ==
> the updateBufferDependent signal is now connected to
> FormBase::updateOrHide(). If the daugh
On Mon, 9 Oct 2000, John Levon wrote:
> On Mon, 9 Oct 2000, Baruch Even wrote:
>
> > I've tried with 2.95.2 (unpatched) on my machine and had troubles too. I'm
> > also having troubles with egcs 1.1.2 for what it matters (It cant find
> > GroupCache::find on linking, I'm forced to make the funct
On Tue, 10 Oct 2000, Baruch Even wrote:
> Following is a report on a bug that was already reported here, namely when
> closing an open file LyX will crash.
Fixed.
updateBufferDependent was being called when there were no buffers left.
This is just plain wrong.
Angus is there any reason why the
On Sun, 8 Oct 2000, Allan Rae wrote:
> On Fri, 6 Oct 2000, Angus Leeming wrote:
>
> > Defining the following function in FormPreferences resolves the
> >
> > BadDrawable (invalid Pixmap or Window parameter)
[...]
> > void FormPreferences::hide()
> > {
> > i
38 matches
Mail list logo
