Jean-Marc Lasgouttes wrote:
The behaviour of M-Return is the exact symmetry of what Return would
do:
I see. I'm fine with that (though I still prefer the old behaviour, i.e. swap
Return and M-Return).
Actually, it could be renamed to something like
break-paragraph-special, or an 'inverse'
On Fri, Sep 14, 2007 at 03:36:10PM +0200, Helge Hafting wrote:
Martin Vermeer wrote:
...
I am not entirely happy with this patch. It works allright, but...
I tested this. Mostly fine, but a few small problems:
Using unit gives two math boxes. One for the numer and one
for the unit
Could you please, if you have not done so, update or add a chapter in
User's Guide (or other document) how to use this feature?
+1
pavel
hello,
am i the only one, who does not see trac timeline anymore ?
pavel
On Fri, Sep 14, 2007 at 09:56:45PM -0400, Richard Heck wrote:
With revision 20282, the merge of the layout modules material is
essentially complete. Please test away, and let me know of any problems.
Also, please have a look at the existing modules in lib/layout/ and
think creatively
Bo Peng wrote:
On 9/14/07, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Abdelrazak Younes [EMAIL PROTECTED] writes:
One question: Why don't we make this the default? I mean that the
present binding will always work with the master document. This means
that new binding should be
I have come across the MathDox project at RIACA (Research Institute for
Applications of Computer Algebra)
http://www.mathdox.org/new-web/projects.html
The MathDox project aims to develop a XML format for interactive
mathematical documents. These MathDox documents can be transformed to
as in attached
intend to commit soon
Index: src/frontends/qt4/ButtonController.cpp
===
--- src/frontends/qt4/ButtonController.cpp (revision 20282)
+++ src/frontends/qt4/ButtonController.cpp (working copy)
@@ -174,14 +174,6 @@
//
On Fri, 14 Sep 2007, David Krebs wrote:
In the file higraphics.css there is this section:
h1, h2, h3, h4, h5, h6, p, ul, ol, dl, td, th, address, caption, pre, blockquote
{
color: rgb(238,238,238);
background: transparent;
}
Why not just change transparent into something like rgb(x, y, z)?
why not simply have the fewer images version as the default?
This should go in branch too Juergen. I had a crash because of it with
attached document (won't crash in Linux because of the disabled pixmap
cache).
Abdel.
[EMAIL PROTECTED] wrote:
Author: younes
Date: Sat Sep 15 14:34:21 2007
New Revision: 20284
URL:
Abdelrazak Younes wrote:
This should go in branch too Juergen. I had a crash because of it with
attached document (won't crash in Linux because of the disabled pixmap
cache).
OK.
Jürgen
Richard Heck wrote:
Leuven, E. wrote:
a second question concerns the copiers. for each file format there can
be one copier. so i am planning to simply add a copiers line edit to
the file formats panel and get rid of the copiers panel.
I like this idea.
updated patch attached. it gets
needs a restart to take effect
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
This should go in branch too Juergen. I had a crash because of it with
attached document (won't crash in Linux because of the disabled pixmap
cache).
OK.
Done. No status.15x because the crash is new.
Abdel.
On Sat, Sep 15, 2007 at 01:06:49PM -, [EMAIL PROTECTED] wrote:
Author: leuven
Date: Sat Sep 15 15:06:48 2007
New Revision: 20285
URL: http://www.lyx.org/trac/changeset/20285
Log:
extract code that sets color of widget from ButtonController and move to
qt_helpers
On second thoughts:
Abdelrazak Younes ha scritto:
Bo Peng wrote:
No. The whole idea of separating chapters from a book is that I can
compile and view the chapters *quicker*. I do not want to compile the
whole book when I am working on a chapter.
Here, I actually agree with Bo. When you separate chapters/sections,
Andre Poenitz wrote:
On Sat, Sep 15, 2007 at 01:06:49PM -, [EMAIL PROTECTED] wrote:
Author: leuven
Date: Sat Sep 15 15:06:48 2007
New Revision: 20285
URL: http://www.lyx.org/trac/changeset/20285
Log:
extract code that sets color of widget from ButtonController and move to
qt_helpers
On
Abdelrazak Younes wrote:
I guess Edwin plans to use it soon...
obviously. i also use it in the file formats patch i posted, and thought
that it was policy to put functions that we reuse in qt_helpers...
On Sat, Sep 15, 2007 at 04:51:21PM +0200, Edwin Leuven wrote:
Abdelrazak Younes wrote:
I guess Edwin plans to use it soon...
obviously. i also use it in the file formats patch i posted, and thought
that it was policy to put functions that we reuse in qt_helpers...
The re-use part was
Andre Poenitz wrote:
The re-use part was non-obvious so far ;-)
i agree obvious was a bit of a hyperbole, but would i ever put something
in qt_helpers without reusing it? ;-)
Anyway, what do people think. Is this an improvement?
sorry to say that, but it looks uglier to me. but its fact that i liked the
current graphics design and the fewer images version on demand (but actually
working which is not the case now) would be enough to me.
anyway, i think that worse
On Sat, Sep 15, 2007 at 05:18:54PM +0200, Edwin Leuven wrote:
Andre Poenitz wrote:
The re-use part was non-obvious so far ;-)
i agree obvious was a bit of a hyperbole, but would i ever put something
in qt_helpers without reusing it? ;-)
Of course not.
Andre'
Bo Peng wrote:
On 9/14/07, Richard Heck [EMAIL PROTECTED] wrote:
With revision 20282, the merge of the layout modules material is
essentially complete. Please test away, and let me know of any problems.
Also, please have a look at the existing modules in lib/layout/ and
think creatively
Martin Vermeer wrote:
On Fri, Sep 14, 2007 at 09:56:45PM -0400, Richard Heck wrote:
With revision 20282, the merge of the layout modules material is
essentially complete. Please test away, and let me know of any problems.
Also, please have a look at the existing modules in lib/layout/ and
Tommaso Cucinotta wrote:
The first thing I'd like to point out is that it is quite annoying to
have to repeat
the same settings to each and every child document, just to allow the
preview
of them in isolation. I would love to see a mechanism for automatic
*inheritance*
of these properties from
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic insets on exit, and both occur
when there has been SOME kind of
i tweaked the layout a bit in attached and added some shortcuts to the keys
i was also wondering about the following:
are the up/down buttons necessary?
can't selecting be done through checkboxes as in the embedded files dialog?
atm it is possible to select all the theorem modules at the same
Richard Heck ha scritto:
I've had the same idea. The mechanism would presumably be a master
document setting in DocumentSettings, which would identify the
master document.
This would be similar to AucTeX, that writes (automatically) into the
child a (commented)
reference to the master, what
On Sat, 15 Sep 2007, Pavel Sanda wrote:
Anyway, what do people think. Is this an improvement?
sorry to say that, but it looks uglier to me. but its fact that i liked the
current graphics design and the fewer images version on demand (but actually
working which is not the case now) would be
Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic insets on exit, and both occur
when there has
Edwin Leuven wrote:
i tweaked the layout a bit in attached and added some shortcuts to the
keys
That's fine. I'm no expert here.
i was also wondering about the following:
are the up/down buttons necessary?
Yes. It may be important to load modules in a certain order, if they
load certain
Abdelrazak Younes wrote:
Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic insets on exit, and
Richard Heck wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic
Edwin Leuven wrote:
updated patch attached. it gets rid of the copier panel
i put it in:
http://www.lyx.org/trac/changeset/20292
Richard Heck wrote:
I.e., do this. But it may be that there are other ways you could see
this problem. What about making the loader a shared_ptr rather than
deleting it explicitly?
It think that the real problem is that the CP stack is not cleaned up
on exit.
Abdel.
On Sat, Sep 15, 2007 at 11:51:50AM -0400, Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic
On Sat, Sep 15, 2007 at 12:40:35PM -0400, Richard Heck wrote:
A better fix would be to transfer the graphics::Cache singleton to
LyX::Singletons.
I.e., do this. But it may be that there are other ways you could see
this problem. What about making the loader a shared_ptr rather than
Andre Poenitz wrote:
On Sat, Sep 15, 2007 at 11:51:50AM -0400, Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in
This should go in branch Jurgen. It is I think the right fix for bug 4178.
Abdel.
[EMAIL PROTECTED] wrote:
Author: younes
Date: Sat Sep 15 19:24:08 2007
New Revision: 20293
URL: http://www.lyx.org/trac/changeset/20293
Log:
Clear out selection and cut stack buffers on exit.
Modified:
I will commit if there is no objection.
Done. I have only done this for InsetGraphics. Other insets like
InsetExternal and InsetBibtex will wait.
Now, the only problem left is when to update the embedding dialog. I
am reluctant to implement a full auto-update facility, that update
this dialog
On Sat, Sep 15, 2007 at 01:55:24PM -0500, Bo Peng wrote:
I will commit if there is no objection.
Done. I have only done this for InsetGraphics. Other insets like
InsetExternal and InsetBibtex will wait.
Now, the only problem left is when to update the embedding dialog. I
am reluctant to
Signal in the core, dialogs connect to that... makes 3 lines of code
plus 1 per connecting dialog.
The problem is where to emit the signal. If I do that at the inset
level, and emit the signal whenever an inset is created, modified and
removed, it may not be efficient because insets get created
I'd like to thank all of you for developing such a lovely program.
I have a suggestion, probably already pointed out.
Can make LyX work with TEX files as native document format?
In this way using LYX in a collaboration would be much easier. Indeed,
some of my collaborators don't want to use LyX
Can make LyX work with TEX files as native document format?
.lyx file stores more information than a .tex file can ever store. For
example, the change-tracking feature can save changes and produce
different output (different .tex files) with or without revision
marks. The branch feature can
I love change tracking in LyX and I struggled to find something
similar in TEX, so I really take care of what you say.
What about a compatibility mode where nice feature like embedding,
versioning, branching and all the .lyx-specific features are not
available? This way the user can choose if use
Roberto Franceschini wrote:
I love change tracking in LyX and I struggled to find something
similar in TEX, so I really take care of what you say.
What about a compatibility mode where nice feature like embedding,
versioning, branching and all the .lyx-specific features are not
available? This
I got the point. I hope something in this direction can be done,
compatibility is always a key issue and being both LyX and Tex open
format they should be able to translate well.
Thanks for the discussion.
On 9/15/07, Abdelrazak Younes [EMAIL PROTECTED] wrote:
Roberto Franceschini wrote:
I
On Sat, Sep 15, 2007 at 02:23:31PM -0500, Bo Peng wrote:
Can make LyX work with TEX files as native document format?
.lyx file stores more information than a .tex file can ever store. For
example, the change-tracking feature can save changes and produce
different output (different .tex
I'm not enetering the technincalities of the thing, i'm not in
position to do so.
I'm just saying that one side LyX is the best word processor, but on
the other side most of the people, dumb like mule, stick to LaTeX just
because it's the standard de-facto.
This make LyX widespreadening much more
What about Scientific Workplace, I never used it, but some my
co-author do. Seems to provide an editor with formula preview, table
preview, etc while editing a .tex file. Why lyx can't run like this?
Roberto
On 9/15/07, Hans Meine [EMAIL PROTECTED] wrote:
On Samstag 15 September 2007, Roberto
Roberto Franceschini wrote:
What about Scientific Workplace, I never used it, but some my
co-author do. Seems to provide an editor with formula preview, table
preview, etc while editing a .tex file. Why lyx can't run like this?
How is one person using SW and one person using LaTeX better than
Roberto Franceschini ha scritto:
Can make LyX work with TEX files as native document format?
You may easily write, as I did, a script that converts a .tex
file to the LyX format into a temporary folder, opens it with
LyX, and, once you close the program, exports it back to
.tex overwriting
Paul A. Rubin ha scritto:
it would help if the LaTeX to LyX conversion were more robust.
So, is there a wiki page on TODO items for the tex-lyx conversions ?
T.
On Sat, Sep 15, 2007 at 11:10:07PM +0200, Roberto Franceschini wrote:
I'm not enetering the technincalities of the thing, i'm not in
position to do so.
I'm just saying that one side LyX is the best word processor, but on
the other side most of the people, dumb like mule, stick to LaTeX just
2) I cannot use LyX anymore because when you write in a
collaborarion a common format is needed and, de-facto, this is Latex,
not lyx file format. Isn't this sad?
You can try to convert your co-authors. If you are the first author,
they do not need to know anything about lyx before they
Hi,
I couldn't really understand what information is
stored inside the BufferView.offset_ref_ variable.
At a first glance, it would seem that anchor_ref_
stores the paragraph offset that is displayed from
the WorkArea top line, and offset_ref_ stores the
pixel offset. Namely, the top WorkArea
Can I make the label of InsetIndex more meaningful by displaying
'Idx:name' instead of 'Idx'?
A simple patch is attached. I will commit it if there is no objection
in one day.
Bo
Index: src/insets/InsetIndex.cpp
===
---
On Sat, Sep 15, 2007 at 11:10:07PM +0200, Roberto Franceschini wrote:
I'm not enetering the technincalities of the thing, i'm not in
position to do so.
I'm just saying that one side LyX is the best word processor, but on
the other side most of the people, dumb like mule, stick to LaTeX just
svn branch 1.5
boost/boost/regex/v4/cpp_regex_traits.hpp contains the lines
#ifdef BOOST_HAS_THREADS
#include boost/regex/pending/static_mutex.hpp
#endif
but boost/boost/regex/pending/ only seems to contain the file
object_cache.hpp
Can anyone tell me why this is?
Roger
Jean-Marc Lasgouttes wrote:
> The behaviour of M-Return is the exact symmetry of what Return would
> do:
I see. I'm fine with that (though I still prefer the old behaviour, i.e. swap
Return and M-Return).
> Actually, it could be renamed to something like
> break-paragraph-special, or an
On Fri, Sep 14, 2007 at 03:36:10PM +0200, Helge Hafting wrote:
> Martin Vermeer wrote:
...
> >I am not entirely happy with this patch. It works allright, but...
> >
> I tested this. Mostly fine, but a few small problems:
>
> Using "unit" gives two math boxes. One for the numer and one
> for
> Could you please, if you have not done so, update or add a chapter in
> User's Guide (or other document) how to use this feature?
+1
pavel
hello,
am i the only one, who does not see trac timeline anymore ?
pavel
On Fri, Sep 14, 2007 at 09:56:45PM -0400, Richard Heck wrote:
>
> With revision 20282, the merge of the layout modules material is
> essentially complete. Please test away, and let me know of any problems.
> Also, please have a look at the existing modules in lib/layout/ and
> think creatively
Bo Peng wrote:
On 9/14/07, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
One question: Why don't we make this the default? I mean that the
present binding will always work with the master document. This means
that new binding should be
I have come across the MathDox project at RIACA (Research Institute for
Applications of Computer Algebra)
http://www.mathdox.org/new-web/projects.html
The MathDox project aims to develop a XML format for interactive
mathematical documents. These MathDox documents can be transformed to
as in attached
intend to commit soon
Index: src/frontends/qt4/ButtonController.cpp
===
--- src/frontends/qt4/ButtonController.cpp (revision 20282)
+++ src/frontends/qt4/ButtonController.cpp (working copy)
@@ -174,14 +174,6 @@
//
On Fri, 14 Sep 2007, David Krebs wrote:
In the file "higraphics.css" there is this section:
h1, h2, h3, h4, h5, h6, p, ul, ol, dl, td, th, address, caption, pre, blockquote
{
color: rgb(238,238,238);
background: transparent;
}
Why not just change "transparent" into something like "rgb(x, y,
why not simply have the "fewer images" version as the default?
This should go in branch too Juergen. I had a crash because of it with
attached document (won't crash in Linux because of the disabled pixmap
cache).
Abdel.
[EMAIL PROTECTED] wrote:
Author: younes
Date: Sat Sep 15 14:34:21 2007
New Revision: 20284
URL:
Abdelrazak Younes wrote:
> This should go in branch too Juergen. I had a crash because of it with
> attached document (won't crash in Linux because of the disabled pixmap
> cache).
OK.
Jürgen
Richard Heck wrote:
Leuven, E. wrote:
a second question concerns the copiers. for each file format there can
be one copier. so i am planning to simply add a copiers line edit to
the file formats panel and get rid of the copiers panel.
I like this idea.
updated patch attached. it gets
needs a restart to take effect
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
This should go in branch too Juergen. I had a crash because of it with
attached document (won't crash in Linux because of the disabled pixmap
cache).
OK.
Done. No status.15x because the crash is new.
Abdel.
On Sat, Sep 15, 2007 at 01:06:49PM -, [EMAIL PROTECTED] wrote:
> Author: leuven
> Date: Sat Sep 15 15:06:48 2007
> New Revision: 20285
>
> URL: http://www.lyx.org/trac/changeset/20285
> Log:
> extract code that sets color of widget from ButtonController and move to
> qt_helpers
On second
Abdelrazak Younes ha scritto:
Bo Peng wrote:
No. The whole idea of separating chapters from a book is that I can
compile and view the chapters *quicker*. I do not want to compile the
whole book when I am working on a chapter.
Here, I actually agree with Bo. When you separate chapters/sections,
Andre Poenitz wrote:
On Sat, Sep 15, 2007 at 01:06:49PM -, [EMAIL PROTECTED] wrote:
Author: leuven
Date: Sat Sep 15 15:06:48 2007
New Revision: 20285
URL: http://www.lyx.org/trac/changeset/20285
Log:
extract code that sets color of widget from ButtonController and move to
qt_helpers
On
Abdelrazak Younes wrote:
I guess Edwin plans to use it soon...
obviously. i also use it in the file formats patch i posted, and thought
that it was policy to put functions that we reuse in qt_helpers...
On Sat, Sep 15, 2007 at 04:51:21PM +0200, Edwin Leuven wrote:
> Abdelrazak Younes wrote:
> >I guess Edwin plans to use it soon...
>
> obviously. i also use it in the file formats patch i posted, and thought
> that it was policy to put functions that we reuse in qt_helpers...
The re-use part was
Andre Poenitz wrote:
The re-use part was non-obvious so far ;-)
i agree obvious was a bit of a hyperbole, but would i ever put something
in qt_helpers without reusing it? ;-)
> Anyway, what do people think. Is this an improvement?
sorry to say that, but it looks uglier to me. but its fact that i liked the
current graphics design and the fewer images version on demand (but actually
working which is not the case now) would be enough to me.
anyway, i think that worse
On Sat, Sep 15, 2007 at 05:18:54PM +0200, Edwin Leuven wrote:
> Andre Poenitz wrote:
> >The re-use part was non-obvious so far ;-)
>
> i agree obvious was a bit of a hyperbole, but would i ever put something
> in qt_helpers without reusing it? ;-)
Of course not.
Andre'
Bo Peng wrote:
On 9/14/07, Richard Heck <[EMAIL PROTECTED]> wrote:
With revision 20282, the merge of the layout modules material is
essentially complete. Please test away, and let me know of any problems.
Also, please have a look at the existing modules in lib/layout/ and
think creatively
Martin Vermeer wrote:
On Fri, Sep 14, 2007 at 09:56:45PM -0400, Richard Heck wrote:
With revision 20282, the merge of the layout modules material is
essentially complete. Please test away, and let me know of any problems.
Also, please have a look at the existing modules in lib/layout/ and
Tommaso Cucinotta wrote:
The first thing I'd like to point out is that it is quite annoying to
have to repeat
the same settings to each and every child document, just to allow the
preview
of them in isolation. I would love to see a mechanism for automatic
*inheritance*
of these properties from
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic insets on exit, and both occur
when there has been SOME kind of
i tweaked the layout a bit in attached and added some shortcuts to the keys
i was also wondering about the following:
are the up/down buttons necessary?
can't selecting be done through checkboxes as in the embedded files dialog?
atm it is possible to select all the theorem modules at the same
Richard Heck ha scritto:
I've had the same idea. The mechanism would presumably be a "master
document" setting in Document>Settings, which would identify the
master document.
This would be similar to AucTeX, that writes (automatically) into the
child a (commented)
reference to the master, what
On Sat, 15 Sep 2007, Pavel Sanda wrote:
Anyway, what do people think. Is this an improvement?
sorry to say that, but it looks uglier to me. but its fact that i liked the
current graphics design and the fewer images version on demand (but actually
working which is not the case now) would be
Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic insets on exit, and both occur
when there has
Edwin Leuven wrote:
i tweaked the layout a bit in attached and added some shortcuts to the
keys
That's fine. I'm no expert here.
i was also wondering about the following:
are the up/down buttons necessary?
Yes. It may be important to load modules in a certain order, if they
load certain
Abdelrazak Younes wrote:
Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic insets on exit, and
Richard Heck wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in destruction of graphic
Edwin Leuven wrote:
updated patch attached. it gets rid of the copier panel
i put it in:
http://www.lyx.org/trac/changeset/20292
Richard Heck wrote:
I.e., do this. But it may be that there are other ways you could see
this problem. What about making the loader a shared_ptr rather than
deleting it explicitly?
It think that the real problem is that the C stack is not cleaned up
on exit.
Abdel.
On Sat, Sep 15, 2007 at 11:51:50AM -0400, Richard Heck wrote:
>
> I don't have time to investigate these further today, so here is what
> I'm thinking, in case anyone else has the time.
>
> These are the same bug, at least in the form Jurgen saw 4082. Both
> crashes occur in destruction of
On Sat, Sep 15, 2007 at 12:40:35PM -0400, Richard Heck wrote:
> >A better fix would be to transfer the graphics::Cache singleton to
> >LyX::Singletons.
>
> I.e., do this. But it may be that there are other ways you could see
> this problem. What about making the loader a shared_ptr rather than
Andre Poenitz wrote:
On Sat, Sep 15, 2007 at 11:51:50AM -0400, Richard Heck wrote:
I don't have time to investigate these further today, so here is what
I'm thinking, in case anyone else has the time.
These are the same bug, at least in the form Jurgen saw 4082. Both
crashes occur in
This should go in branch Jurgen. It is I think the right fix for bug 4178.
Abdel.
[EMAIL PROTECTED] wrote:
Author: younes
Date: Sat Sep 15 19:24:08 2007
New Revision: 20293
URL: http://www.lyx.org/trac/changeset/20293
Log:
Clear out selection and cut stack buffers on exit.
Modified:
1 - 100 of 120 matches
Mail list logo
