Hello,
I have been using LyX periodically for a couple of years, and have grown to
really like it. Thanks for making such a great piece of software! Anyway, I
am interested in helping out with the project. I am interested in finding
out how I can be of the most help given my skill set and interest
Andre Poenitz wrote:
Maybe I still did not fully understand the concepts.
Are 'DocumentClass' and 'LayoutFile' two completely distinct concepts
such that we never can exchange a 'DocumentClass' for a 'LayoutFile'
(but that happen to share a common implementation via some 'TextClass'
base right n
On Thu, Mar 13, 2008 at 12:03:32AM +0100, Juergen Spitzmueller wrote:
> Enrico Forestieri wrote:
>
> >> OK. Put it in.
> >
> > Done.
>
> You need to add bm to chkconfig.ltx and LaTeXConfig.lyx.
Right. I also made sure that bm is loaded after amsmath.
--
Enrico
Abdelrazak Younes wrote:
José Matos wrote:
Hi all,
I, and many others on this list, think that we are ready to
release the first alpha release for 1.6.
Since the code seems stable I think that we can proceed directly
to a beta release 3 to 4 weeks after the first release.
So I
On Mar 12, 2008, at 5:52 PM, Stefan Schimanski wrote:
Am 12.03.2008 um 22:49 schrieb Andre Poenitz:
On Wed, Mar 12, 2008 at 10:40:07PM +0100, Stefan Schimanski wrote:
Here is a series of patches
1) which add an open-in-window mode (enabled on Mac by default)
2) which keep LyX running, even a
This works:
if (cmd.x < xo(cur.bv()) + ADD_TO_TABULAR_WIDTH
|| cmd.x > xo(cur.bv()) + tabular.width()) {
row_type r = 0;
int h = yo(cur.bv()) - tabular.rowAscent(0);
for (;r < tabular.rowCount() && cmd.y > h; ++r) {
h += tabular.rowAscent(r);
Stefan Schimanski wrote:
White board? The text background?
some padding defined by ADD_TO_TABULAR_WIDTH at the beginning of
InsetTabular.cpp
Stefan Schimanski wrote:
Look in BufferView::mouseEventDispatch:
Inset * inset = d->text_metrics_[&buffer_.text()].editXY(cur, cmd.x,
cmd.y);
So only the inset below the cursor will get the event.
it s getting the event alright, you're clicking on the white border
the attached patch incr
Am 13.03.2008 um 00:42 schrieb Edwin Leuven:
Stefan Schimanski wrote:
Why should the table get this mouse event after all if the mouse is
not over the table, but left on it?
there is a white border around it
White board? The text background?
Stefan
Stefan Schimanski wrote:
Why should the table get this mouse event after all if the mouse is not
over the table, but left on it?
there is a white border around it
Look in BufferView::mouseEventDispatch:
Inset * inset = d->text_metrics_[&buffer_.text()].editXY(cur,
cmd.x, cmd.y);
So only the inset below the cursor will get the event.
Stefan
Am 13.03.2008 um 00:37 schrieb Stefan Schimanski:
Am 13.03.2008 um 00:23 schrieb Edwin Leuven:
Stefan Sch
Am 13.03.2008 um 00:23 schrieb Edwin Leuven:
Stefan Schimanski wrote:
Can you send me a complete patch of your changes?
attached. it defines a new lfun that selects a row (once you're in
tabular)
the part that doesn't work is this:
// SELECT ROW
if (cmd.x < xo(cur.bv()) + ADD_TO_TABULAR
Stefan Schimanski wrote:
Can you send me a complete patch of your changes?
attached. it defines a new lfun that selects a row (once you're in tabular)
the part that doesn't work is this:
// SELECT ROW
if (cmd.x < xo(cur.bv()) + ADD_TO_TABULAR_WIDTH
|| cmd.x > xo(cur.bv()) + tabular.width(
1. launch lyx, save file x, close lyx
2. launch lyx, open file y, open outliner
3. remove file x from disk
4. try to open file x from file recent menu
5. crash
can anybody confirm?
pavel
Am 13.03.2008 um 00:07 schrieb Edwin Leuven:
Stefan Schimanski wrote:
Do a cur.bv().cursor() = cur; or something similar.
doesn't do diddly either
Can you send me a complete patch of your changes?
Stefan
Stefan Schimanski wrote:
Do a cur.bv().cursor() = cur; or something similar.
doesn't do diddly either
Enrico Forestieri wrote:
>> OK. Put it in.
>
> Done.
You need to add bm to chkconfig.ltx and LaTeXConfig.lyx.
Jürgen
Am 12.03.2008 um 23:58 schrieb Edwin Leuven:
Stefan Schimanski wrote:
What do you want to do exactly?
select a table row when you click in front of it while the cursor is
outside the table
i added the following in InsetTabular::doDispatch when handling case
LFUN_MOUSE_PRESS:
// SELEC
Stefan Schimanski wrote:
What do you want to do exactly?
select a table row when you click in front of it while the cursor is
outside the table
i added the following in InsetTabular::doDispatch when handling case
LFUN_MOUSE_PRESS:
// SELECT ROW
if (cmd.x < xo(cur.bv()) + ADD_TO_TABULAR_WI
Am 12.03.2008 um 23:43 schrieb Edwin Leuven:
Stefan Schimanski wrote:
So you have to push the inset of the table on the cursor:
cur.push(theTableInset);
tried that too, doesn't work either...
What do you want to do exactly? Maybe it's what Andre was suggesting:
you have to make sure that
Stefan Schimanski wrote:
So you have to push the inset of the table on the cursor:
cur.push(theTableInset);
tried that too, doesn't work either...
Am 12.03.2008 um 23:33 schrieb Edwin Leuven:
Stefan Schimanski wrote:
Look in InsetMathNest::handleNest(...). I do exactly this for math.
i already tried something like like that, and now did this:
cur.idx() = tabular.getFirstCellInRow(r);
cur.pos() = 0;
cur.resetAnchor();
cur.idx() = tabul
Stefan Schimanski wrote:
Look in InsetMathNest::handleNest(...). I do exactly this for math.
i already tried something like like that, and now did this:
cur.idx() = tabular.getFirstCellInRow(r);
cur.pos() = 0;
cur.resetAnchor();
cur.idx() = tabular.getLastCellInRow(r);
cur.pos() = cur.lastpos(
Am 12.03.2008 um 21:43 schrieb Edwin Leuven:
Stefan Schimanski wrote:
* go to first cell
* go to last cell
and how do i do this?
Look in InsetMathNest::handleNest(...). I do exactly this for math.
Stefan
Edwin Leuven wrote:
Stefan Schimanski wrote:
* go to first cell
* go to last cell
and how do i do this?
difficult or trivial?
On Wed, Mar 12, 2008 at 08:42:43PM +0100, Juergen Spitzmueller wrote:
> OK. Put it in.
Done.
--
Enrico
> > 1. Loading open files from last session does not work.
Fixed.
Bo
Am 12.03.2008 um 22:49 schrieb Andre Poenitz:
On Wed, Mar 12, 2008 at 10:40:07PM +0100, Stefan Schimanski wrote:
Here is a series of patches
1) which add an open-in-window mode (enabled on Mac by default)
2) which keep LyX running, even after closing the last window on Mac
3) which close a wi
On Wed, Mar 12, 2008 at 10:40:07PM +0100, Stefan Schimanski wrote:
> Here is a series of patches
>
> 1) which add an open-in-window mode (enabled on Mac by default)
> 2) which keep LyX running, even after closing the last window on Mac
> 3) which close a window when the last tab is closed on Mac
>
Am 12.03.2008 um 22:40 schrieb Stefan Schimanski:
Here is a series of patches
1) which add an open-in-window mode (enabled on Mac by default)
2) which keep LyX running, even after closing the last window on Mac
3) which close a window when the last tab is closed on Mac
3) which add a preferenc
Here is a series of patches
1) which add an open-in-window mode (enabled on Mac by default)
2) which keep LyX running, even after closing the last window on Mac
3) which close a window when the last tab is closed on Mac
3) which add a preference option to change (1)
For (2) I keep the GuiView wi
> >> This one is caused by the Embedded stuff by Bo:
> >
> > Will fix it soon.
Fixed.
> There is also the bug that any included file is marked as (embedded) in
> the InsetInclude label, independently of the embedded status.
I do not see this here.
Bo
Bo Peng wrote:
> 2. Every time I open a file, save it, and open it again, it opens as
> changed, so that if I immediately close it it asks if I want to save.
This one is caused by the Embedded stuff by Bo:
Will fix it soon.
Thanks.
There is also the bug that any included file is marked a
> > 2. Every time I open a file, save it, and open it again, it opens as
> > changed, so that if I immediately close it it asks if I want to save.
>
> This one is caused by the Embedded stuff by Bo:
Will fix it soon.
Bo
Bennett Helm wrote:
On Mar 12, 2008, at 10:30 AM, Bo Peng wrote:
"A first alpha version of LyX 1.6.0 will be released later this week
for those who like the bleeding edge experience." 24/02/08
Is there any big must-have feature which we should wait for?
As far as I know, embedding wa
On Wed, Mar 12, 2008 at 09:23:59PM +0100, Edwin Leuven wrote:
> i am trying to get some row selection code working in insettabular, but am
> baffled by this cursor business
>
> the scenario is the following:
>
> the cursor is outside the tabular
>
> at the moment, on mouse press, i check in front
Stefan Schimanski wrote:
* go to first cell
* go to last cell
and how do i do this?
thanks again!
On Wed, Mar 12, 2008 at 08:47:58PM +0100, Pavel Sanda wrote:
> /usr/bin/uic -tr lyx::qt_ ui/SpellcheckerUi.ui -o ui_SpellcheckerUi.h
> '' isn't a valid widget
>
> i looked into it and havent seen anything strange
It's the empty buddy property in line 37.
I wonder how this was created...
Andre'
Am 12.03.2008 um 21:23 schrieb Edwin Leuven:
i am trying to get some row selection code working in insettabular,
but am baffled by this cursor business
the scenario is the following:
the cursor is outside the tabular
at the moment, on mouse press, i check in front of what row i click
this
i am trying to get some row selection code working in insettabular, but
am baffled by this cursor business
the scenario is the following:
the cursor is outside the tabular
at the moment, on mouse press, i check in front of what row i click
this i do in InsetTabular::doDispatch
now i want to
/usr/bin/uic -tr lyx::qt_ ui/SpellcheckerUi.ui -o ui_SpellcheckerUi.h
'' isn't a valid widget
i looked into it and havent seen anything strange
p
Enrico Forestieri wrote:
> When using \boldsymbol and the amsmath package is not loaded, LyX
> uses an home made definition which is flawed. Indeed, if you have
> a bold super or subscript, the wrong size is used (the same size
> as normalsize). The bm package is recommended by amsmath and produce
On Wed, Mar 12, 2008 at 08:20:21PM +0100, Pavel Sanda wrote:
> running monolithic build here i get:
>
> make[5]: Entering directory
> `/home/installer/lyx/g-free-trunk/src/frontends/qt4'
> /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
> -I../../../src -DQT_CLEAN_NA
On Wed, Mar 12, 2008 at 03:04:43PM -0400, Richard Heck wrote:
> Andre Poenitz wrote:
>> On Wed, Mar 12, 2008 at 12:26:15PM -0400, Richard Heck wrote:
>>
>>> This got started because there was a crash that involved passing a
>>> temporary to Paragraph::setLayout(), and I added a comment to the
>>
running monolithic build here i get:
make[5]: Entering directory `/home/installer/lyx/g-free-trunk/src/frontends/qt4'
/bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../../../src -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_STL
-DQT_NO_KEYWORDS -I../../../src -I..
Thanks for the patch. I am not sure however what the rationale for the
change was. Paul, can you tell us more (assuming you did the change?)
The earlier version used the Theorem environment (no automatic
numbering). The later version used the List environment (automatic
numbering), but
On Tue, Mar 11, 2008 at 03:19:42PM -0400, rgheck wrote:
>
> Can I ask a very silly question? OK. How do you compile something simple
> like this? All my work has been on projects that already have Makefile
> stuff installed.
Well, 'g++ -I/path/to/Qt/includes main.cpp' gives a binary called a.out
On Wed, Mar 12, 2008 at 06:36:13PM +0100, Juergen Spitzmueller wrote:
> Enrico Forestieri wrote:
>
> > BTW, here is a patch for 1.5. Jürgen, Ok to apply it?
>
> I didn't follow the discussion. Could you outline again what the patch
> changes? Does the output of old documents look different?
When
Richard Heck wrote:
Richard Heck wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
This got started because there was a crash that involved passing a
temporary to Paragraph::setLayout(), and I added a comment to the
effect that one ought not to do that. Then Andr
Hi all,
I, and many others on this list, think that we are ready to release the
first
alpha release for 1.6.
Since the code seems stable I think that we can proceed directly to a
beta
release 3 to 4 weeks after the first release.
So I am proposing two dates:
al
Abdelrazak Younes wrote:
And now that we're not just listing the layouts in the order they
were created---they're sorted into categories, or sorted by their
title, or whatever. So, anyway, that's what I was trying to change,
by using an iterator. But maybe, as you said, there is some other way
José Matos wrote:
On Wednesday 12 March 2008 14:13:49 Stefan Schimanski wrote:
Citing our webpage:
"A first alpha version of LyX 1.6.0 will be released later this week
for those who like the bleeding edge experience." 24/02/08
Is there any big must-have feature which we should wait f
Andre Poenitz wrote:
On Wed, Mar 12, 2008 at 12:26:15PM -0400, Richard Heck wrote:
This got started because there was a crash that involved passing a
temporary to Paragraph::setLayout(), and I added a comment to the
effect that one ought not to do that. Then Andre suggested there must
be a be
> Fine with me.
Me too.
Bo
[EMAIL PROTECTED] wrote:
> - if (font.fontInfo().color() != Color_inherit) {
> + if (font.fontInfo().color() != Color_ignore) {
This fails now with "unknown color inherit" when you set the color to reset.
The solution is
if (font.fontInfo().color() != Color_inherit &&
On Wed, Mar 12, 2008 at 01:25:50PM -0400, Richard Heck wrote:
> Maybe there's a better way to do this than by indexing into the
> LayoutList. I didn't like that, and I didn't like the way these
> indices were being used in GuiDocument. In effect, it means that
> GuiDocument has to know that we're
On Wednesday 12 March 2008 17:46:13 Juergen Spitzmueller wrote:
> The remaining problems are: one specific lyx2lyx reversion problem and some
> metrics problems (all non-fill spaces are drawn in the same width). I think
> these are trivial, I just need some time. I'll try to finish it at the
> week
José Matos wrote:
Hi all,
I, and many others on this list, think that we are ready to release the first
alpha release for 1.6.
Since the code seems stable I think that we can proceed directly to a beta
release 3 to 4 weeks after the first release.
So I am proposing two dates:
On Wed, Mar 12, 2008 at 05:54:41PM +0100, Abdelrazak Younes wrote:
> Abdelrazak Younes wrote:
>> Richard Heck wrote:
>
>>> This got started because there was a crash that involved passing a
>>> temporary to Paragraph::setLayout(), and I added a comment to the effect
>>> that one ought not to do t
Richard Heck wrote:
Richard Heck wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
This got started because there was a crash that involved passing a
temporary to Paragraph::setLayout(), and I added a comment to the
effect that one ought not to do that. Then Andr
Pavel Sanda wrote:
> he want to make us a bit surprised by merging the working xml stuff into
> the tree, but little bit shy before polishing last few corners, you know
Now that you found out, I will drop my proposal ;-)
Jürgen
On Wed, Mar 12, 2008 at 12:26:15PM -0400, Richard Heck wrote:
> This got started because there was a crash that involved passing a
> temporary to Paragraph::setLayout(), and I added a comment to the
> effect that one ought not to do that. Then Andre suggested there must
> be a better way, in partic
José Matos wrote:
> Other than Juergen who has another feature waiting in the backburner? How
> much time do you need to put the feature in?
It is basically complete and already works. The feature is a dialog for
InsetSpace similar to our VSpace dialog (bug 2078), which also merges HFill
into Ins
Abdelrazak Younes wrote:
I'd prefer:
vector counter_layout = tclass.counterLayout();
Or maybe:
vector counter_layout = tclass.layoutsWithType(LABEL_COUNTER);
for (size_t i; i != layout ; ++i) {
int const toclevel = counter_layout[i]->toclevel;
if (toclevel != Layout::NOT_IN_TOC) {
Am 12.03.2008 um 19:32 schrieb Juergen Spitzmueller:
[EMAIL PROTECTED] wrote:
- if (font.fontInfo().color() != Color_inherit) {
+ if (font.fontInfo().color() != Color_ignore) {
This fails now with "unknown color inherit" when you set the color
to reset.
The solution is
Richard Heck wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
This got started because there was a crash that involved passing a
temporary to Paragraph::setLayout(), and I added a comment to the
effect that one ought not to do that. Then Andre suggested there
mu
Stefan Schimanski wrote:
> Right. Can you commit it to trunk?
Yes.
Jürgen
> > he want to make us a bit surprised by merging the working xml stuff into
> > the tree, but little bit shy before polishing last few corners, you know
>
> Now that you found out, I will drop my proposal ;-)
i hope this trick will save us from xml hell in 1.7 series too :)
pave
Enrico Forestieri wrote:
> BTW, here is a patch for 1.5. Jürgen, Ok to apply it?
I didn't follow the discussion. Could you outline again what the patch
changes? Does the output of old documents look different?
Jürgen
Richard Heck wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
This got started because there was a crash that involved passing a
temporary to Paragraph::setLayout(), and I added a comment to the
effect that one ought not to do that. Then Andre suggested there
mu
On Wednesday 12 March 2008 14:13:49 Stefan Schimanski wrote:
> Citing our webpage:
>
>"A first alpha version of LyX 1.6.0 will be released later this week
> for those who like the bleeding edge experience." 24/02/08
>
> Is there any big must-have feature which we should wait for? Otherwise
On Wed, Mar 12, 2008 at 02:27:07PM +0100, Abdelrazak Younes wrote:
> Enrico Forestieri wrote:
> > On Mon, Mar 10, 2008 at 11:01:26PM +0100, Enrico Forestieri wrote:
> >> On Mon, Mar 10, 2008 at 10:30:41AM +0100, Jean-Marc Lasgouttes wrote:
> >>
> >>> Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> he want to make us a bit surprised by merging the working xml stuff into the
> tree, but little bit shy before polishing last few corners, you know :D
XML? I have not heard of this word for a while. :-)
Bo
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Richard Heck wrote:
This got started because there was a crash that involved passing a
temporary to Paragraph::setLayout(), and I added a comment to the
effect that one ought not to do that. Then Andre suggested there
must be a better way, i
>>> As far as I know, embedding was the only lagging feature, and it is
>>> ready for alpha testing now.
>> I have yet another feature in the pipe, but this could go in after alpha1.
>
> Tell us about it pretty please :-)
he want to make us a bit surprised by merging the working xml stuff into the
Bo Peng wrote:
But the point of an alpha release isn't simply to impose a feature
freeze on developers, as this suggests; it's to get feedback from
users.
I see your point, although I consider alpha as 'peek for new
features', and only beta as 'let us test and report bugs'. I mean, we
do not
Abdelrazak Younes wrote:
Richard Heck wrote:
Abdelrazak Younes wrote:
rgheck wrote:
Attached is my attempt at using type safety to make Layout objects
safer to use. I tried several things, and this may well not be
best. But other efforts---going back to a vector,
e.g.---all had their own p
Juergen Spitzmueller wrote:
Bo Peng wrote:
As far as I know, embedding was the only lagging feature, and it is
ready for alpha testing now.
I have yet another feature in the pipe, but this could go in after alpha1.
Tell us about it pretty please :-)
Abdel.
Abdelrazak Younes wrote:
Richard Heck wrote:
This got started because there was a crash that involved passing a
temporary to Paragraph::setLayout(), and I added a comment to the
effect that one ought not to do that. Then Andre suggested there must
be a better way, in particular, that maybe w
Richard Heck wrote:
Abdelrazak Younes wrote:
rgheck wrote:
Attached is my attempt at using type safety to make Layout objects
safer to use. I tried several things, and this may well not be best.
But other efforts---going back to a vector, e.g.---all had
their own problems, usually, that the
Abdelrazak Younes wrote:
rgheck wrote:
Attached is my attempt at using type safety to make Layout objects
safer to use. I tried several things, and this may well not be best.
But other efforts---going back to a vector, e.g.---all had
their own problems, usually, that they make iterators beha
> But the point of an alpha release isn't simply to impose a feature
> freeze on developers, as this suggests; it's to get feedback from
> users.
I see your point, although I consider alpha as 'peek for new
features', and only beta as 'let us test and report bugs'. I mean, we
do not need user fe
On Mar 12, 2008, at 11:32 AM, Bo Peng wrote:
There are, I think, a couple of recent bugs that should be addressed
first (or am I the only one experiencing these?).
My understanding is that alpha one means
1. all 1.6.x features are more or less ready
2. a loss feature freeze, basically no ne
> http://permalink.gmane.org/gmane.editors.lyx.devel/81717
So my understanding was more or less correct, and we are ready for
alpha one. :-)
Bo
> My understanding is that alpha one means
>
> 1. all 1.6.x features are more or less ready
> 2. a loss feature freeze, basically no new feature is allowed.
> 3. let us start fixing bugs like what Bennett mentioned.
>
> Of course Jose has the authority to define alpha one, and order the
> release
> There are, I think, a couple of recent bugs that should be addressed
> first (or am I the only one experiencing these?).
My understanding is that alpha one means
1. all 1.6.x features are more or less ready
2. a loss feature freeze, basically no new feature is allowed.
3. let us start fixing
On Mar 12, 2008, at 10:30 AM, Bo Peng wrote:
"A first alpha version of LyX 1.6.0 will be released later this
week
for those who like the bleeding edge experience." 24/02/08
Is there any big must-have feature which we should wait for?
As far as I know, embedding was the only lagging
Bo Peng wrote:
> As far as I know, embedding was the only lagging feature, and it is
> ready for alpha testing now.
I have yet another feature in the pipe, but this could go in after alpha1.
Jürgen
>"A first alpha version of LyX 1.6.0 will be released later this week
> for those who like the bleeding edge experience." 24/02/08
>
> Is there any big must-have feature which we should wait for?
As far as I know, embedding was the only lagging feature, and it is
ready for alpha testing n
Citing our webpage:
"A first alpha version of LyX 1.6.0 will be released later this week
for those who like the bleeding edge experience." 24/02/08
Is there any big must-have feature which we should wait for? Otherwise
I would propose to make it in the next days, maybe the weekend. I
th
Enrico Forestieri wrote:
On Mon, Mar 10, 2008 at 11:01:26PM +0100, Enrico Forestieri wrote:
On Mon, Mar 10, 2008 at 10:30:41AM +0100, Jean-Marc Lasgouttes wrote:
Enrico Forestieri <[EMAIL PROTECTED]> writes:
The attached patch is better, IMO. There's no reason to require
the \boldsymbol defi
On Mon, Mar 10, 2008 at 11:01:26PM +0100, Enrico Forestieri wrote:
> On Mon, Mar 10, 2008 at 10:30:41AM +0100, Jean-Marc Lasgouttes wrote:
>
> > Enrico Forestieri <[EMAIL PROTECTED]> writes:
> >
> > > The attached patch is better, IMO. There's no reason to require
> > > the \boldsymbol definition
rgheck wrote:
Attached is my attempt at using type safety to make Layout objects safer
to use. I tried several things, and this may well not be best. But other
efforts---going back to a vector, e.g.---all had their own
problems, usually, that they make iterators behave badly. (In that case,
Andre Poenitz wrote:
... seems to be completely broken in trunk.
Has anybody tried it lately?
I just tried, seems to work fine. Change Tracking is by the way an
obvious candidate for context menu. Right now, one have to select a
change in order to accept it or reject via the "Document->Chang
Stefan Schimanski <[EMAIL PROTECTED]> writes:
> During changes to some bugzilla bug:
>
> Changes submitted for bug 4091Insufficient disk space; try again later
> Insufficient disk space; try again later returntosender
Should be fixed now. I removed 600M worth of old useless logwatch
stuff. I
Richard Heck <[EMAIL PROTECTED]> writes:
>> pity. would be a correct solution to make InsetCitation::get/setStyle
>> and add lfun-set-style-all-citation which will be just some dociterator
>> calling set style for each citation inset?
>>
>>
> There's a way of just iterating over insets. I think
During changes to some bugzilla bug:
Changes submitted for bug 4091Insufficient disk space; try again later
Insufficient disk space; try again later returntosender
Stefan
97 matches
Mail list logo
