Maria Gouskova wrote:
> Hi developers,
>
> I just upgraded to 2.2.1 today. I can see that there have been a lot of
> changes in the appearance of the interface, so obviously quite a lot of
> work went into the redesign. I confess I was stumped, though, when I went
> to insert a citation. The
Pavel Sanda wrote:
Pavel Sanda wrote:
Well, he launches it and discovers that his Office has similar order as
his
s/Office/LyX/
Office (just tried here): File, Edit, View, Insert, Format (mixture of
our text style and Doc settings), Table, Tools, Windows, Help.
Pavel
Why LyX could
Pavel Sanda wrote:
> Pavel Sanda wrote:
>> Well, he launches it and discovers that his Office has similar order as
>> his
>
> s/Office/LyX/
>
>> Office (just tried here): File, Edit, View, Insert, Format (mixture of
>> our text style and Doc settings), Table, Tools, Windows, Help.
>>
>> Pavel
Jean-Marc Lasgouttes wrote:
Hunspell can be seen as some kind of successor to aspell. At least it is
supposed to be better (am I right?)
Yes. Hunspell can deal with coumpound words (two words joined in one) which
are very common in German and suffix and affix which are used in Hungarian
Rainer Dorsch wrote:
Hello,
I have a small LyX document, which shows a combination of a hyperlink and
an svg figure break html/opendocument generation:
The source documentation is here
http://bokomoko.de/~rd/lyxtest/
The output I get is here
Jean-Marc Lasgouttes wrote:
> Hunspell can be seen as some kind of successor to aspell. At least it is
> supposed to be better (am I right?)
>
Yes. Hunspell can deal with coumpound words (two words joined in one) which
are very common in German and suffix and affix which are used in Hungarian
Rainer Dorsch wrote:
> Hello,
>
> I have a small LyX document, which shows a combination of a hyperlink and
> an svg figure break html/opendocument generation:
>
> The source documentation is here
>
> http://bokomoko.de/~rd/lyxtest/
>
> The output I get is here
>
>
Vincent van Ravesteijn - TNW wrote:
* http://www.lyx.org/trac/ticket/2625
convert the search dialog to a search bar
to me it was fixed by new search pane. Vincent however have idea
to convert the current simple search dialog into search bar. opinions?
anybody wants to work on it? otherwise c.
Vincent van Ravesteijn - TNW wrote:
Did you update today ? I think they are now exactly the same.
Thank you. It is much better. Still, I would go further and get rid of the
advanced tab:
- At the top of the pane I would put the scope as a combo box
- Then a smaller Find TextEdit
- Then
Vincent van Ravesteijn - TNW wrote:
>>* http://www.lyx.org/trac/ticket/2625
>>convert the search dialog to a search bar
>>
>>to me it was fixed by new search pane. Vincent however have idea
>>to convert the current simple search dialog into search bar. opinions?
>>anybody wants to work on it?
Vincent van Ravesteijn - TNW wrote:
>
> Did you update today ? I think they are now exactly the same.
>
Thank you. It is much better. Still, I would go further and get rid of the
advanced tab:
- At the top of the pane I would put the scope as a combo box
- Then a smaller Find TextEdit
- Then
rgheck wrote:
Feel free to grab Qt Designer and work on this. Or at least produce a
mock-up.
I found the CitationUi.ui file and opened it in Qt Designer. But before
playing with it, I was wondering about the possibility to have multiple
Citations.
The only use case is, if I
Hello,
I have compiled LyX through the cmake way and it looks faster than the old
autotools
I would like to do a make install but not mess my LyX 1.6 and install the
files in /usr/share/LyX20
How should I do that ?
Maybe INSTALL.Cmake could be a little bit fleshed out. At least for the
rgheck wrote:
> Feel free to grab Qt Designer and work on this. Or at least produce a
> mock-up.
>
I found the CitationUi.ui file and opened it in Qt Designer. But before
playing with it, I was wondering about the possibility to have multiple
Citations.
The only use case is, if I
Hello,
I have compiled LyX through the cmake way and it looks faster than the old
autotools
I would like to do a make install but not mess my LyX 1.6 and install the
files in /usr/share/LyX20
How should I do that ?
Maybe INSTALL.Cmake could be a little bit fleshed out. At least for the
John McCabe-Dansted wrote:
The attached patch resolved the following tickets:
#6486 Citation not selected by default.
#6487 Add file and url links to Citation Dialog.
Thank you for #6486
I think the dialog would be simpler to use if it had a more classical look
like Endnote X2 insertion
John McCabe-Dansted wrote:
> The attached patch resolved the following tickets:
> #6486 Citation not selected by default.
> #6487 Add "file" and "url" links to Citation Dialog.
Thank you for #6486
I think the dialog would be simpler to use if it had a more classical look
like Endnote X2
jezZiFeR wrote:
Dear list,
The question is not really for lyx.devel but more for lyx.users. Please use
the correct list next time.
I have a question regarding the declarations of editions. This is
maybe more a BibDesk than a LyX-question, but maybe somebody could help…
I use BibLateX
jezZiFeR wrote:
> Dear list,
The question is not really for lyx.devel but more for lyx.users. Please use
the correct list next time.
>
> I have a question regarding the declarations of editions. This is
> maybe more a BibDesk than a LyX-question, but maybe somebody could help…
> I use
Hello,
I have updated to 1.6.3 and the full screen mode works much better. Thanks
for the work.
But after working a full day in full screen mode on an 17 monitor my eyes
were strained because lines of text are much too wide if you cannot resize
the window.
Fullscreen wordprocessors tend to
Pavel Sanda wrote:
there is hard to get any consensus on those issues and thats why we have
limit text width checkbox in preferences which you are probably not
aware of.
pavel
No Thanks, it is all I need !
Sorry for the noise.
Charles
--
http://www.kde-france.org
Hello,
I have updated to 1.6.3 and the full screen mode works much better. Thanks
for the work.
But after working a full day in full screen mode on an 17" monitor my eyes
were strained because lines of text are much too wide if you cannot resize
the window.
Fullscreen wordprocessors tend to
Pavel Sanda wrote:
> there is hard to get any consensus on those issues and thats why we have
> "limit text width" checkbox in preferences which you are probably not
> aware of.
> pavel
No Thanks, it is all I need !
Sorry for the noise.
Charles
--
http://www.kde-france.org
rgheck wrote:
Just to be clear, here are what I regard as the showstoppers:
Theorem-type environments aren't rendered; math support is marginal, esp
with regard to custom macros; BibTeX isn't supported, so far as I can
tell; cross-references omit the related text. Other things I'd want to
rgheck wrote:
> Just to be clear, here are what I regard as the showstoppers:
> Theorem-type environments aren't rendered; math support is marginal, esp
> with regard to custom macros; BibTeX isn't supported, so far as I can
> tell; cross-references omit the related text. Other things I'd want
Hello,
In the April 2009 of the mainstream French computer magazine PC Expert there
is a n nice positive two pages review of LyX.
If some people are interested, I can try to post some scans.
Cheers,
Charles
--
http://www.kde-france.org
Hello,
In the April 2009 of the mainstream French computer magazine PC Expert there
is a n nice positive two pages review of LyX.
If some people are interested, I can try to post some scans.
Cheers,
Charles
--
http://www.kde-france.org
Jean-Marc Lasgouttes wrote:
rgheck rgh...@bobjweil.com writes:
Jürgen Spitzmüller wrote:
2. implement the possibility to add comments to the outliner items.
As Helge wrote, these will need to be stored in the document (as
specific properties). I suppose this would be much easier to
Jean-Marc Lasgouttes wrote:
> rgheck writes:
>
>> Jürgen Spitzmüller wrote:
>>> 2. implement the possibility to add comments to the outliner items.
>>> As Helge wrote, these will need to be stored in the document (as
>>> specific properties). I suppose this would be much
Jürgen Spitzmüller wrote:
I think we really need OK/Apply/Cancel buttons in the long term (there's
also an old bug report somewhere).
+1
C.
--
http://www.kde-france.org
Jürgen Spitzmüller wrote:
Vincent van Ravesteijn wrote:
I'm fixing the current design of the dialog. Whether the design should
be changed is the next question ?
It should have been changed long ago. Maybe you'll find the time. The
current design is only a burden of the past.
I would
Jürgen Spitzmüller wrote:
> I think we really need OK/Apply/Cancel buttons in the long term (there's
> also an old bug report somewhere).
>
+1
C.
--
http://www.kde-france.org
Jürgen Spitzmüller wrote:
> Vincent van Ravesteijn wrote:
>> I'm fixing the current design of the dialog. Whether the design should
>> be changed is the next question ?
>
> It should have been changed long ago. Maybe you'll find the time. The
> current design is only a burden of the past.
>
I
Great stuff. I was hoping for a better search and replace in LyX since many
yeard.
I hope it could be merged in trunk for 1.6.1
Cheers,
Charles
--
http://www.kde-france.org
Great stuff. I was hoping for a better search and replace in LyX since many
yeard.
I hope it could be merged in trunk for 1.6.1
Cheers,
Charles
--
http://www.kde-france.org
Abdelrazak Younes wrote:
The UserGuide doesn't work for me either. I suspect it's simply too
complex for htlatex. Does the Tutorial work?
Here (Debian Sid, LyX SVN, tex4ht 20080701-2) it works for the tutorial.
Cheers,
Charles
--
http://www.kde-france.org
Abdelrazak Younes wrote:
>
>> The UserGuide doesn't work for me either. I suspect it's simply too
>> complex for htlatex. Does the Tutorial work?
>>
Here (Debian Sid, LyX SVN, tex4ht 20080701-2) it works for the tutorial.
Cheers,
Charles
--
http://www.kde-france.org
=??B?SsO8cmdlbiBTcGl0em3DvGxsZXI=?= wrote:
are not installed.
I would not talk of moving. We should provide support for XeTeX, but not
at the price of dropping support for other LaTeX variants. There will
always be enough reasons to not use XeTeX (as long as it misses support
for micro
=??B?SsO8cmdlbiBTcGl0em3DvGxsZXI=?= wrote:
>> are not installed.
>
> I would not talk of "moving". We should provide support for XeTeX, but not
> at the price of dropping support for other LaTeX variants. There will
> always be enough reasons to not use XeTeX (as long as it misses support
> for
Pavel Sanda wrote:
i tend for 3. solution but would like to hear your opinions.
Why not have a Multiple View Component architecture ? The Outliner would be
one view and the main window another view ; each view would have a
infrastucture to remember what is collapsed or not. It would make
Pavel Sanda wrote:
>
> i tend for 3. solution but would like to hear your opinions.
>
Why not have a Multiple View Component architecture ? The Outliner would be
one view and the main window another view ; each view would have a
infrastucture to remember what is collapsed or not. It would make
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
That looks interesting indeed. Putting the development list in copy.
Jürgen, José, do you know about that?
I heard of it. But I'm pretty ignorant when it comes to markup languages.
Jürgen
TEI is an archival format. I doubt it is
Charles de Miramon wrote:
Xml is slow to parse, the text is buried in very noisy formatting
information and is difficult to hack. In my opinion, history has proved it
is not adapted for wordprocessors.
Interesting blog measuring the performance impact when MsWord switched to an
xml format
Abdelrazak Younes wrote:
Xml is slow to parse,
That's a generalisation that is not really true, it really depends on
your XML syntax. We are free to do what we want, so I am pretty sure the
parsing will be as fast as nowadays. Really, do you see an increased
difficulty when parsing
José Matos wrote:
This idea was discussed before and it was abandoned more than 10 years
ago. Every once in a while someone comes with that suggestion, and again
we conclude that it does not work, the best that could be done would be
that subject plus meta comments with annotations.
I'm
Jürgen Spitzmüller wrote:
> Abdelrazak Younes wrote:
>> That looks interesting indeed. Putting the development list in copy.
>> Jürgen, José, do you know about that?
>
> I heard of it. But I'm pretty ignorant when it comes to markup languages.
>
> Jürgen
TEI is an archival format. I doubt it
Charles de Miramon wrote:
>>
> Xml is slow to parse, the text is buried in very noisy formatting
> information and is difficult to hack. In my opinion, history has proved it
> is not adapted for wordprocessors.
>
Interesting blog measuring the performance impact when MsWord
Abdelrazak Younes wrote:
>> Xml is slow to parse,
> That's a generalisation that is not really true, it really depends on
> your XML syntax. We are free to do what we want, so I am pretty sure the
> parsing will be as fast as nowadays. Really, do you see an increased
> difficulty when parsing
José Matos wrote:
>
> This idea was discussed before and it was abandoned more than 10 years
> ago. Every once in a while someone comes with that suggestion, and again
> we conclude that it does not work, the best that could be done would be
> that subject plus meta comments with annotations.
>
I like Richard's solution better. Having a zip based solution means that you
can 'unbundle' from the command line even without LyX, the base64 solution
is more complex.
I would favour a simple bundling / unbundling where everything is bundled
and everything is unbundled but add the possibility
Bo Peng wrote:
On the other hand, the file format in my proposal is still plain text.
For many other operations such as search and replace, you do not have
to unzip. I consider this as an advantage.
You have got a point. But the mix of text and base64 which is what is done
in rtf, if I'm
I like Richard's solution better. Having a zip based solution means that you
can 'unbundle' from the command line even without LyX, the base64 solution
is more complex.
I would favour a simple bundling / unbundling where everything is bundled
and everything is unbundled but add the possibility
Bo Peng wrote:
> On the other hand, the file format in my proposal is still plain text.
> For many other operations such as search and replace, you do not have
> to unzip. I consider this as an advantage.
You have got a point. But the mix of text and base64 which is what is done
in rtf, if I'm
Helge Hafting wrote:
If F11 switches to fullscreen mode, then surely F11 again
should switch back. The accidental user
can then press the same key again - no guessing
about other keys.
Hmm. All applictaions I know have some visual clue to get out of the
fullscreen mode (look Firefox,
Helge Hafting wrote:
> If F11 switches to fullscreen mode, then surely F11 again
> should switch back. The accidental user
> can then press the same key again - no guessing
> about other keys.
>
Hmm. All applictaions I know have some visual clue to get out of the
fullscreen mode (look
Pavel Sanda wrote:
please look at Tools-Preferences-User interface.
Yes. I have looked the options but there are no options to keep the menu, or
the status bar.
Somebody typing F11 by mistake will end in a full screen mode qithout any
clue how to come back to normal mode
Something that
Pavel Sanda wrote:
> please look at Tools->Preferences->User interface.
Yes. I have looked the options but there are no options to keep the menu, or
the status bar.
Somebody typing F11 by mistake will end in a full screen mode qithout any
clue how to come back to normal mode
Something
Abdelrazak Younes wrote:
UI Question:
In the outliner type combo, do you prefer an entry for each type of
notes (LyX, Comment, Greyed out) or one entry like what we have now?
Abdel.
I have just compiled svn. It looks very nice.
In the long run. I think it would be nice to have the
Abdelrazak Younes wrote:
> UI Question:
>
> In the outliner type combo, do you prefer an entry for each type of
> notes (LyX, Comment, Greyed out) or one entry like what we have now?
>
> Abdel.
I have just compiled svn. It looks very nice.
In the long run. I think it would be nice to have the
Abdelrazak Younes wrote:
Qt designer is a good example. Open Office is another one. Typically OO
would dock a paragraph settings dialog.
Has someone tried scrivener (I don't have a Mac) :
http://www.literatureandlatte.com/scrivener.html
The interface looks innovative with interesting
Abdelrazak Younes wrote:
>
> Qt designer is a good example. Open Office is another one. Typically OO
> would dock a paragraph settings dialog.
>
>
Has someone tried scrivener (I don't have a Mac) :
http://www.literatureandlatte.com/scrivener.html
The interface looks innovative with
Jean-Marc Lasgouttes wrote:
Public release of LyX version 1.5.0
===
We are pleased to announce the release of LyX 1.5.0.
Congratulations for all. It was great to see all this energy going into LyX
lately. Riding my hobby horse, I would say that the qt port
Jean-Marc Lasgouttes wrote:
>
> Public release of LyX version 1.5.0
> ===
>
> We are pleased to announce the release of LyX 1.5.0.
Congratulations for all. It was great to see all this energy going into LyX
lately. Riding my hobby horse, I would say that the qt
Martin Vermeer wrote:
We already have that: charstyles, which are however pretty
limited. But they could be extended (under a different name
probably, style insets?)
Could something like that do the trick for beamer? (I haven't
used beamer myself . . .)
Would be a partial solution
Martin Vermeer wrote:
>
> We already have that: charstyles, which are however pretty
> limited. But they could be extended (under a different name
> probably, "style insets"?)
>
>> Could something like that do the trick for beamer? (I haven't
>> used beamer myself . . .)
>
> Would be a
Martin Vermeer wrote:
What feature do you think that lyx is missing badly?
The beamer layout requires too much ERT and non-intuitive tweaking.
Perhaps something can be done about it in the frame of short title /
optional argument. My dream is to have a LyX-beamer that is compatitive
also
Martin Vermeer wrote:
>
>> What feature do you think that lyx is missing badly?
>
> The beamer layout requires too much ERT and non-intuitive tweaking.
> Perhaps something can be done about it in the frame of short title /
> optional argument. My dream is to have a LyX-beamer that is
Richard Heck wrote:
Modular layouts, which are close to complete, modulo comments and such.
Then add a local layout option similar to preamble. (So, in
DocumentSettings you can add on-the-fly layout info.) This will make
Bo's embedded layout idea pretty simple to implement. May start
Richard Heck wrote:
> Modular layouts, which are close to complete, modulo comments and such.
> Then add a "local layout" option similar to preamble. (So, in
> Document>Settings you can add on-the-fly layout info.) This will make
> Bo's "embedded layout" idea pretty simple to implement. May
Jürgen Spitzmüller wrote:
José Matos wrote:
We should do this for 1.5.1, this is not a file format change in the
sense that new files will work with lyx 1.5.0. :-)
Sure.
Maybe with another name, like argument and not short title. Having a common
mechanism for supporting arguments between
Jürgen Spitzmüller wrote:
Not for 1.5.x, though.
At least the menu entry should not be called shorttitle
Cheers,
Charles
--
http://www.kde-france.org
Jürgen Spitzmüller wrote:
> José Matos wrote:
>> We should do this for 1.5.1, this is not a file format change in the
>> sense that new files will work with lyx 1.5.0. :-)
>
> Sure.
Maybe with another name, like argument and not short title. Having a common
mechanism for supporting arguments
Jürgen Spitzmüller wrote:
>
> Not for 1.5.x, though.
>
At least the menu entry should not be called shorttitle
Cheers,
Charles
--
http://www.kde-france.org
Ekkehart Schlicht wrote:
Jean-Marc:
I deposited an example to
http://www.semverteilung.vwl.uni-muenchen.de/temp/short.zip
It contains
1. short.doc: Shortened version of a winword file I obtained from the
publisher
2. short.tex: short.doc exported by OpenOfficeWriter 2.2 to Latex.
Ekkehart Schlicht wrote:
> Jean-Marc:
>
> I deposited an example to
>
> http://www.semverteilung.vwl.uni-muenchen.de/temp/short.zip
>
> It contains
>
> 1. short.doc: Shortened version of a winword file I obtained from the
> publisher
>
> 2. short.tex: short.doc exported by OpenOfficeWriter
Abdelrazak Younes wrote:
That was what I was going to suggest. But then I remembered that the
goal of 1.6 is XML and this alone will take time I guess.
What LyX is going to gain with a XML file format ? Except being buzz
compliant.
I am not sure
that switching to XML and doing minor file
Jürgen Spitzmüller wrote:
What would that mean if someone opens a file done with, say, 1.5.2 (with
cline support) with 1.5.1 (without cline support)? Will this file be
displayed and exported correctly? Will it be saved correctly, so that the
file again opens without dataloss in 1.5.2?
José Matos wrote:
We gain xsl to write converters to other formats
If KOffice can be point of comparison. Before switching to ODF, we had a xml
format and nobody (well actually one man) wrote any xsl converters because
it seems that everybody hates xslt.
Cheers,
Charles
--
Lars Gullik Bjønnes wrote:
ODF is also xml based afaik.
Yes but the logic of formatting of an ODF file and of a LyX file (modelled
on LaTeX) is very different. There is no preamble for example in ODF.
This blog is interesting and it seems to me that LaTeX is rather similar to
Wordperfect.
Abdelrazak Younes wrote:
> That was what I was going to suggest. But then I remembered that the
> goal of 1.6 is XML and this alone will take time I guess.
What LyX is going to gain with a XML file format ? Except being buzz
compliant.
> I am not sure
> that switching to XML and doing minor
Jürgen Spitzmüller wrote:
>
> What would that mean if someone opens a file done with, say, 1.5.2 (with
> cline support) with 1.5.1 (without cline support)? Will this file be
> displayed and exported correctly? Will it be saved correctly, so that the
> file again opens without dataloss in 1.5.2?
José Matos wrote:
>
> We gain xsl to write converters to other formats
If KOffice can be point of comparison. Before switching to ODF, we had a xml
format and nobody (well actually one man) wrote any xsl converters because
it seems that everybody hates xslt.
Cheers,
Charles
--
Lars Gullik Bjønnes wrote:
> ODF is also xml based afaik.
>
Yes but the logic of formatting of an ODF file and of a LyX file (modelled
on LaTeX) is very different. There is no preamble for example in ODF.
This blog is interesting and it seems to me that LaTeX is rather similar to
Wordperfect.
Georg Baum wrote:
Edwin Leuven wrote:
the insert citation dialog crashes here with attached bib entry
hints anyone?
Yes. The contents of .bib files is implicitly treated as UTF8, and your
file is encoded in latin1. What we need to do is to convert them from the
encoding that will be
Georg Baum wrote:
> Edwin Leuven wrote:
>
>> the insert citation dialog crashes here with attached bib entry
>>
>> hints anyone?
>
> Yes. The contents of .bib files is implicitly treated as UTF8, and your
> file is encoded in latin1. What we need to do is to convert them from the
> encoding
Jean-Marc Lasgouttes wrote:
Georg == Georg Baum
[EMAIL PROTECTED]
writes:
Georg I guess this should also go in 1.4?
Yes please.
JMarc
I've played a little bit with importing quotes with tex2lyx and it seems
quite broken, even round trip LyX -- LaTeX -- LyX is not perfect.
The Ducth
Jean-Marc Lasgouttes wrote:
I think most of the quotes are too difficult to get right...
Mmm If the latex parser could extract the pair of quotes, I think it
should be possible to have a one to one translation matrix.
Cheers,
Charles
--
http://www.kde-france.org
Jean-Marc Lasgouttes wrote:
>> "Georg" == Georg Baum
>> <[EMAIL PROTECTED]>
>> writes:
>
> Georg> I guess this should also go in 1.4?
>
> Yes please.
>
> JMarc
I've played a little bit with importing quotes with tex2lyx and it seems
quite broken, even round trip LyX --> LaTeX -->
Jean-Marc Lasgouttes wrote:
> I think most of the quotes are too difficult to get right...
Mmm If the latex parser could extract the pair of quotes, I think it
should be possible to have a one to one translation matrix.
Cheers,
Charles
--
http://www.kde-france.org
Abdelrazak Younes wrote:
I would be interested in coding some kind of global ERT search and
replace in LyX.
Why not a real searchreplace function for LyX 1.5.x, where you can find
anything in your documment LyX, LaTeX in ERT, math, citations, styles ?
Cheers,
Charles
--
Georg Baum wrote:
If the integrated latex support is based on writer2latex, then I would do
something else: Tell writer2latex to ignore visual markup, and only to
export the document structure. This could be done with a config file, and
I got very good results with that some time ago.
Yes,
Abdelrazak Younes wrote:
> I would be interested in coding some kind of global ERT search and
> replace in LyX.
>
Why not a real search function for LyX 1.5.x, where you can find
anything in your documment LyX, LaTeX in ERT, math, citations, styles ?
Cheers,
Charles
--
Georg Baum wrote:
> If the integrated latex support is based on writer2latex, then I would do
> something else: Tell writer2latex to ignore visual markup, and only to
> export the document structure. This could be done with a config file, and
> I got very good results with that some time ago.
José Matos wrote:
I have discovered that the release procedure needs some work, make
distcheck is not working for one. I would like to catch an fix this
problems before entering the pre phase.
Maybe at some point, everybody should align on one set of building tools
(autotools, scons or
José Matos wrote:
> I have discovered that the release procedure needs some work, make
> distcheck is not working for one. I would like to catch an fix this
> problems before entering the pre phase.
>
Maybe at some point, everybody should align on one set of building tools
(autotools, scons or
cmiramon == cmiramon [EMAIL PROTECTED] writes:
cmiramon I have compiled yesterday svn lyx and ran it through
cmiramon cachegrind (start lyx, load tutorial, page down twice exit).
Did you compile lyx with --disable-stdlib-debug and --disable-assertions?
It seems to me that you did not.
>> "cmiramon" == cmiramon <[EMAIL PROTECTED]> writes:
>
> cmiramon> I have compiled yesterday svn lyx and ran it through
> cmiramon> cachegrind (start lyx, load tutorial, page down twice exit).
>
> Did you compile lyx with --disable-stdlib-debug and --disable-assertions?
>
> It seems to me
Georg Baum wrote:
I tried that, and failed. Any pointer?
qtconfig and use the plastic theme that is the standard for KDE.
Cheers,
Charles
--
http://www.kde-france.org
Jean-Marc Lasgouttes wrote:
1. who is going to do that? I still got no offer.
I will try to create a klik package
2. when proposed more liberty about qt4, your first reaction is to
demand 4.2 only (which will probably become 4.3 only by the time
1/5 is released)
The 4.x series is
Jean-Marc Lasgouttes wrote:
Charles == Charles de Miramon
[EMAIL PROTECTED] writes:
Charles Jean-Marc Lasgouttes wrote:
1. who is going to do that? I still got no offer.
Charles I will try to create a klik package
Try it. Very easy to use :
http://klik.atekon.de/
I don't know
1 - 100 of 201 matches
Mail list logo