On Tue, 2006-09-12 at 16:38 +0200, Abdelrazak Younes wrote:
> Lars Gullik Bjønnes wrote:
> > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> > |
> > | You've just described my very plan ;-). I just thought it was obvious
> > | so I didn't care to write it so explicitly. The problem is just that
>
We should get rid of clean_dvi.py as it prevents many LyX-files to be
converted to DVI (tested under MiKTeX and TeXLive). I described the
problematic in detail in bug 2836
http://bugzilla.lyx.org/show_bug.cgi?id=2836
The problem occured in february this year when MiKTeX changed the
hyperref dr
Helge Hafting <[EMAIL PROTECTED]> writes:
| On Tue, Sep 12, 2006 at 02:43:05PM +0200, Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >
| > | You've just described my very plan ;-). I just thought it was obvious
| > | so I didn't care to write it so explicitly. The
On Tue, Sep 12, 2006 at 10:35:57PM +0200, Andreas Karlsson wrote:
> I am using LyX 1.4.2 on Windows XP. I am not sure if this is a bug, but I
> think it is.
>
> When changing the text style of word to Typewriter, the text style of the
> word seen on screen does not change, i.e., it is not seen i
I am using LyX 1.4.2 on Windows XP. I am not sure if this is a bug, but I
think it is.
When changing the text style of word to Typewriter, the text style of the
word seen on screen does not change, i.e., it is not seen in typewriter
font. But when compiling the document the word does appear in
On Tue, Sep 12, 2006 at 10:11:31PM +0200, Helge Hafting wrote:
> It isn't a model - it is how this computer stuff actually happen on a
> low level.
Precisely the problem.
> Saving is *often* unnecessary because the app should do that
> when you close it anyway. But sometimes I want to save some
On Tue, Sep 12, 2006 at 02:43:05PM +0200, Lars Gullik Bjønnes wrote:
> Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> | You've just described my very plan ;-). I just thought it was obvious
> | so I didn't care to write it so explicitly. The problem is just that
> | Lars won't allow step 1.
>
On Tue, Sep 12, 2006 at 03:50:12PM +0100, John Levon wrote:
> On Tue, Sep 12, 2006 at 11:32:44AM +0200, Helge Hafting wrote:
>
> > Please tell - what is the problem with File->Save? Logically,
> > saving is an operation on a file. What do you want instead,
> > document->save? Or something comple
On Tue, Sep 12, 2006 at 12:09:59PM +0200, Abdelrazak Younes wrote:
...
> > Honestly do you think that xforms would have remained after including
> >unicode?
>
> The xform frontend could have been maintained and restricted to the 8
> bit ascii subset of unicode. It _was_ possible really and n
Hi.
For those of you who don't know, the very first international LyX
developers meeting was held in Denmark.
http://www.lyx.org/~jug/lyx/meetings/Denmark/
So it's only natural that we return to Denmark again. I must admit I
have lost count, so I'm not sure it is the 9th or 10th.
Anyway, a
On Tue, Sep 12, 2006 at 07:31:16PM +0200, Lars Gullik Bjønnes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> | On Tue, Sep 12, 2006 at 06:01:12PM +0200, Lars Gullik Bjønnes wrote:
> | > Enrico Forestieri <[EMAIL PROTECTED]> writes:
> | >
> | > | # define BOOST_FS_FUNC(BOOST_FS_TYPE)
Enrico Forestieri <[EMAIL PROTECTED]> writes:
| On Tue, Sep 12, 2006 at 06:01:12PM +0200, Lars Gullik Bjønnes wrote:
| > Enrico Forestieri <[EMAIL PROTECTED]> writes:
| >
| > | # define BOOST_FS_FUNC(BOOST_FS_TYPE) inline BOOST_FS_TYPE
| > | # define BOOST_INLINE_FS_FUNC(BOOST_FS_TYPE) inline
On Tue, Sep 12, 2006 at 06:01:12PM +0200, Lars Gullik Bjønnes wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> | # define BOOST_FS_FUNC(BOOST_FS_TYPE) inline BOOST_FS_TYPE
> | # define BOOST_INLINE_FS_FUNC(BOOST_FS_TYPE) inline BOOST_FS_TYPE
> | typedef boost::filesystem::path Pa
On Tue, Sep 12, 2006 at 03:59:16PM +, Angus Leeming wrote:
> Enrico Forestieri <[EMAIL PROTECTED]> writes:
> > The problem occurs when BOOST_FILESYSTEM_NARROW_ONLY is defined as
> > in this case the "typedef boost::filesystem::path Path;" kicks in.
>
> I'd say that you've found a bug in the Bo
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | > #ifdef NEW_CODE
| > | > #endif
| > | > or:
| > | > create new files for the ne
Abdelrazak Younes wrote:
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > #ifdef NEW_CODE
| > #endif
| > or:
| > create new files for the newstuff and conditional compile so that you
| > c
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > #ifdef NEW_CODE
| > #endif
| > or:
| > create new files for the newstuff and conditional compile so that you
| > can get the new stuff and a
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > #ifdef NEW_CODE
| > #endif
| > or:
| > create new files for the newstuff and conditional compile so that you
| > can get the new stuff and all others get the ols stuff.
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
#ifdef NEW_CODE
#endif
or:
create new files for the newstuff and conditional compile so that you
can get the new stuff and all others get the ols stuff.
I don't think that's a good way to do any development sorry. If we
Enrico Forestieri <[EMAIL PROTECTED]> writes:
| # define BOOST_FS_FUNC(BOOST_FS_TYPE) inline BOOST_FS_TYPE
| # define BOOST_INLINE_FS_FUNC(BOOST_FS_TYPE) inline BOOST_FS_TYPE
| typedef boost::filesystem::path Path;
| # define BOOST_FS_TYPENAME
| # endif
|
| The problem occurs when BOOST
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> The problem occurs when BOOST_FILESYSTEM_NARROW_ONLY is defined as
> in this case the "typedef boost::filesystem::path Path;" kicks in.
I'd say that you've found a bug in the Boost code. Library code shouldn't
pollute the global namespace in this wa
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Lars Gullik Bjønnes wrote:
>>> Very right. If the bus thing happens after step 1, we are left with no
>>> spellchecker.
>>>
>>
>> Additionally it is possible that A. is a terrorist
>> who wanna destroy LyX by leaving after step 1, we
>> are living i
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | > | | You've just described my very plan ;-). I just thought it was
| > | > obvi
Peter Kümmel wrote:
Lars Gullik Bjønnes wrote:
Very right. If the bus thing happens after step 1, we are left with no
spellchecker.
Additionally it is possible that A. is a terrorist
who wanna destroy LyX by leaving after step 1, we
are living in hard times. ;)
How do you know that? Now I h
Lars Gullik Bjønnes wrote:
>
> Very right. If the bus thing happens after step 1, we are left with no
> spellchecker.
>
Additionally it is possible that A. is a terrorist
who wanna destroy LyX by leaving after step 1, we
are living in hard times. ;)
Sorry, couldn't resist.
Peter
On Tue, Sep 12, 2006 at 02:12:01PM +0200, Rainer Dorsch wrote:
> g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -DQT_CLEAN_NAMESPACE
> -DQT_GENUINE_STR -DQT_NO_STL -DQT_THREAD_SUPPORT -I../../../src -I../../../s\
> rc/frontends -I../../../images -I/usr/lib/qt-3.0.5//include -I../../../boost
> -I../.
1. Need option to overwrite files without a dialog option. Often, when you
select "export pdf" it takes a while to generate the pdf, so the error dialog
for "overwrite file?" pops up and gets lost among your windows. Some options
somewhere should allow for default overwrite of files without err
OK, one last mail on that issue to be polite with John who asked me a
question. Then I'm done with it and all the remaining discussions.
John Levon wrote:
On Tue, Sep 12, 2006 at 04:38:20PM +0200, Abdelrazak Younes wrote:
| You've just described my very plan ;-). I just thought it was obviou
On Tue, Sep 12, 2006 at 08:43:01AM -0500, Bo Peng wrote:
> >> Author: forenr
> >> Date: Tue Sep 12 02:54:07 2006
> >> New Revision: 14980
> >
> >I am very pleased by this Enrico!
>
> Me too. I do not have to apply Enrico's patches any more. :-)
You all really dragged me in ;-)
--
Enrico
Rainer Dorsch <[EMAIL PROTECTED]> writes:
> Angus,
> I extracted the sources and followed the INSTALL file:
...
> I did not use a separate build tree, I am surprised that I need
> to do that...
You don't *need* to, but it's always a good idea to try to do so.
> I noticed that I find only referen
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | | You've just described my very plan ;-). I just thought it was
| > obvious
| > | so I didn't care to write it so explicitly. The problem
John Levon wrote:
On Tue, Sep 12, 2006 at 12:09:59PM +0200, Abdelrazak Younes wrote:
Now, the consensus was there for xforms so, no, I don't think it would
have survived unicode.
If consensus isn't there, isn't a discussion (lengthy or not) exactly
the right thing?
Sure but we are repeating
On cygwin, when compiling lyx_cb.C and a few other files, I get the
following error:
if g++ -DHAVE_CONFIG_H -I. -I../../src -I. -I../../boost -Wno-uninitialized
-O2 -MT lyx_cb.o -MD -MP -MF ".deps/lyx_cb.Tpo" -c -o lyx_cb.o
../../src/lyx_cb.C; \
then mv -f ".deps/lyx_cb.Tpo" ".deps/ly
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | | You've just described my very plan ;-). I just thought it was
| > obvious
| > | so I didn't care to write it so explicitly. The problem is just that
| > | Lars won't
On Tue, Sep 12, 2006 at 04:38:20PM +0200, Abdelrazak Younes wrote:
> >| You've just described my very plan ;-). I just thought it was obvious
> >| so I didn't care to write it so explicitly. The problem is just that
> >| Lars won't allow step 1.
> >
> >Very right. If the bus thing happens after st
On Tue, Sep 12, 2006 at 11:32:44AM +0200, Helge Hafting wrote:
> Please tell - what is the problem with File->Save? Logically,
> saving is an operation on a file. What do you want instead,
> document->save? Or something completely different?
I can only point you to "About Face", a pretty excell
On Tue, Sep 12, 2006 at 12:09:59PM +0200, Abdelrazak Younes wrote:
> Now, the consensus was there for xforms so, no, I don't think it would
> have survived unicode.
If consensus isn't there, isn't a discussion (lengthy or not) exactly
the right thing?
john
Am Dienstag, 12. September 2006 15:33 schrieb Angus Leeming:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> > Rainer Dorsch ...> writes:
> >> I retried not to compile lyx 1.4.2 with QT 3.3 and got another
> >> compile issue:
> >> No such file or directory: opening dependency file
> >> .deps/ui/QRef
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
|
| You've just described my very plan ;-). I just thought it was obvious
| so I didn't care to write it so explicitly. The problem is just that
| Lars won't allow step 1.
Very right. If the bus thing happens after step 1
> Author: forenr
> Date: Tue Sep 12 02:54:07 2006
> New Revision: 14980
I am very pleased by this Enrico!
Me too. I do not have to apply Enrico's patches any more. :-)
Bo
Angus Leeming <[EMAIL PROTECTED]> writes:
> Rainer Dorsch ...> writes:
>> I retried not to compile lyx 1.4.2 with QT 3.3 and got another
>> compile issue:
>> No such file or directory: opening dependency file
>> .deps/ui/QRefDialogBase.Tpo
>> Any ideas what is going wrong here?
> Looks like conf
Rainer Dorsch <[EMAIL PROTECTED]> writes:
> I retried not to compile lyx 1.4.2 with QT 3.3 and got another compile issue:
> No such file or directory: opening dependency file
> .deps/ui/QRefDialogBase.Tpo
> Any ideas what is going wrong here?
Looks like configure and make have got confused about t
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Angus Leeming wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >> Well, I think I communicate a lot already.
| > LOL! Email is a notoriously bad way to communicate. I'm forever
| > writing emails that are clear and lucid and which are taken
José,
I found another issue when running make -k:
g++ -DHAVE_CONFIG_H -I. -I. -I../../../src -DQT_CLEAN_NAMESPACE
-DQT_GENUINE_STR -DQT_NO_STL -DQT_THREAD_SUPPORT -I../../../src -I../../../s\
rc/frontends -I../../../images -I/usr/lib/qt-3.0.5//include -I../../../boost
-I../../../src/frontends
Hello,
I retried not to compile lyx 1.4.2 with QT 3.3 and got another compile issue:
./configure --prefix /opt/lyx-1.4.2 --with-frontend=qt
--with-qt-dir=/usr/lib/qt3 --with-qt-libraries=/usr/lib/qt3/lib64
make
if /bin/sh ../../../libtool --tag=CXX --mode=compile
g++ -DHAVE_CONFIG_H -I. -I.
Angus Leeming wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Man, it's easy to select only some mail and not others...
| I have taken into account all comments except for the spellchecker
| changes. I am tired and too lazy to do it... But I will put Ispell
| back if there is consensus abo
it seems that there is a consensus to end the support of qt3,
so let's do that starting from now.
i suggest that for the time being qt3 is treated as gtk.
it is time to close this thread.
lars?
-Original Message-
From: José Matos [mailto:[EMAIL PROTECTED]
Sent: Tue 9/12/06 11:54
To:
On Tuesday 12 September 2006 11:51, José Matos wrote:
> So if you can support qt 3.0 with very few effort we should do it. :-)
Sorry I meant *we* not *you*.
My point is that there are several places in code where we test for qt < 3.1
and for some reason that chunk avoided that check.
If
On Tuesday 12 September 2006 11:35, Rainer Dorsch wrote:
> So that means lyx 1.4.2 does not support qt 3.0.x, right?
I think so.
The question now is if this is the only place where this happens or if there
are others.
If you run with make -k where are there other places in code where you
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Man, it's easy to select only some mail and not others...
>
> | I have taken into account all comments except for the spellchecker
> | changes. I am tired and too lazy to do it... But I will put Ispell
> | back if there is consensus about that.
>
>
Am Montag, 11. September 2006 23:23 schrieb Enrico Forestieri:
> On Mon, Sep 11, 2006 at 08:00:21PM +0200, Rainer Dorsch wrote:
> > Hello,
> >
> > I tried to compile lyx 1.4.2 with QT 3.0.5 using
> >
> > $ ./configure --prefix /opt/lyx-1.4.2 --with-frontend=qt
> > --with-qt-dir=/usr/lib/qt-3.0.5
>
Angus Leeming wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
You've just described my very plan . I just thought it was obvious so
I didn't care to write it so explicitly. The problem is just that Lars
won't allow step 1.
Man, you really are too prickly.
Yep, happens to me sometimes
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> You've just described my very plan . I just thought it was obvious so
> I didn't care to write it so explicitly. The problem is just that Lars
> won't allow step 1.
Man, you really are too prickly.
Read his mails again (snippets below). I don't
José Matos wrote:
On Tuesday 12 September 2006 10:10, Abdelrazak Younes wrote:
I believe on the contrary that that's the only way to achieve something
in this list. If not for the shouting xforms and qt3 would have been
maintained painfully until 1.5.
That is the problem with the "cry wolf"
Angus Leeming wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Well, I think I communicate a lot already.
LOL! Email is a notoriously bad way to communicate. I'm forever writing emails
that are clear and lucid and which are taken to mean something else by the
eejit reading them. Often I
On Tuesday 12 September 2006 10:10, Abdelrazak Younes wrote:
> I believe on the contrary that that's the only way to achieve something
> in this list. If not for the shouting xforms and qt3 would have been
> maintained painfully until 1.5.
That is the problem with the "cry wolf" type of strategi
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> Well, I think I communicate a lot already.
LOL! Email is a notoriously bad way to communicate. I'm forever writing emails
that are clear and lucid and which are taken to mean something else by the
eejit reading them. Often I seem to offend them. H
John Levon wrote:
On Mon, Sep 11, 2006 at 09:25:24PM +0200, Michael Gerz wrote:
Sorry but I have to disagree strongly. Why on earth do we have "cut" &
"paste" in the "edit" menu? Because it is so efficient to use the menu?
Definitely not! Because every word processor has it? Ugh, didn't Joh
On Tue, Sep 12, 2006 at 10:44:10AM +0200, Georg Baum wrote:
> Abdelrazak Younes wrote:
>
> > [EMAIL PROTECTED] wrote:
> >> Author: forenr
> >> Date: Tue Sep 12 02:54:07 2006
> >> New Revision: 14980
> >
> > I am very pleased by this Enrico!
>
> Me too, although I had to think a bit what "forenr"
Michael Gerz wrote:
Hello,
please let me summarize the QT3 discussion:
- Edwin: Qt3 should either go or get the same status as gtk
- Michael: Qt3 should go; reduce maintainence effort
- Abdel: Qt3 should go
Small correction: I am the same as Edwin. If someone is willing to do
the job, fine w
Ozgur Ugras BARAN wrote:
I am not a core developer, but as a user here is my opinion on the
subject:
[...]
And also there are many people, who do not upgrade his/her distro that
frequently. (For example I use SuSE 9.3 at home, simply because I
prefer gcc 3.3 over 4.0 on that particular machine
Angus Leeming wrote:
John Levon <[EMAIL PROTECTED]> writes:
On Mon, Sep 11, 2006 at 09:10:08PM +0200, Michael Gerz wrote:
Decide on your own what that means for Qt3...
One small note: if qt3 dies (and the development cost does seem quite
onerous), then the first 1.5.0 release should have cle
José Matos wrote:
On Monday 11 September 2006 17:23, Abdelrazak Younes wrote:
The code and logic in ControlSpellchecker are completely backward. Start
again!
Yep, my patch was a first step in this direction but Lars just think in
terms of (unused) features. My strategy was to do the API right f
Abdelrazak Younes wrote:
> [EMAIL PROTECTED] wrote:
>> Author: forenr
>> Date: Tue Sep 12 02:54:07 2006
>> New Revision: 14980
>
> I am very pleased by this Enrico!
Me too, although I had to think a bit what "forenr" means.
Georg
[EMAIL PROTECTED] wrote:
Author: forenr
Date: Tue Sep 12 02:54:07 2006
New Revision: 14980
I am very pleased by this Enrico!
:-)
Abdel.
Ozgur Ugras BARAN wrote:
> Well, the Akademy did not held, yet, therefore the release date of
> KDE4 did not announced. But my guess is it will be around Sept. 2007
> as earliest. Therefore, many distros that releases yearly or twice
> yearly will be released with KDE4/QT4 default earliest in May
On Tuesday 12 September 2006 08:50, Martin Vermeer wrote:
> Hmmm, the fact that the inset name is character style doesn't
> necessarily mean that the menu item has to be. Just find the name that
> fits best.
+1
> - Martin
--
José Abílio
On Mon, 2006-09-11 at 22:28 +0200, Lars Gullik Bjønnes wrote:
> John Levon <[EMAIL PROTECTED]> writes:
>
> | On Mon, Sep 11, 2006 at 09:55:36PM +0200, Michael Gerz wrote:
> |
> | > BTW: I changed "Text Style" into "Character Style", because Martin calls
> | > them character styles. The terms sho
Jean-Pierre Chretien wrote:
> What is the status of 1.4.2 w.r.t. qt4 ?
It doesn't work and 1.4.x never will. Qt4 support will be introduced with 1.5
Jürgen
I am not a core developer, but as a user here is my opinion on the subject:
QT3 is popular and is everywhere due to KDE basically. The next major
version of the KDE (4) will be based on QT4 and before KDE4 do not
expect to have QT4 by default in your favourite *NIX distro.
Well, the Akademy did
Peter Kümmel <[EMAIL PROTECTED]> writes:
> >
>
> Maybe it works without /lib:
>
> --with-extra-lib=/usr/local/qt-4.1.4
>
Same result. Reading more closely the configure log on screen, I see this:
checking for Qt library name... failed
Any option to configure to get a more explicit message
71 matches
Mail list logo
