José Matos wrote:
> I did so I suppose the list got it. Certainly we are interested, I was
> expecting someone more knowledge to answer (Hello Georg, or Angus). :-)
I got it, too, so the list definitely received it. I have not yet answered
for the very same reason: not enough time.
Georg
Peter & Abdel are certified heroes.
They squashed a good deal of bugs yesterday, and put things back on
track in this everlasting LyX drama. Hope is restored!
But no crisis without a new one building up. Here is a new batch of bad
guys to go after.
Showstoppers:
- Printing the tutorial cra
Andre Poenitz wrote:
On Mon, Oct 30, 2006 at 11:12:41AM +0100, Abdelrazak Younes wrote:
Andre Poenitz wrote:
Good in theory but it looks as if this is the kind of infomration that
would be useful for a 'non-drawing real painter' (as opposed to the
original nullpainter)
I have implemented that
Martin Vermeer wrote:
On Thu, Nov 02, 2006 at 08:50:45PM +, John Levon wrote:
On Thu, Nov 02, 2006 at 08:28:45PM +0100, Asger Ottar Alstrup wrote:
More bugs are being reported recently, and none of the old ones have
been fixed. Thus, we are moving in the wrong direction.
Or people have be
Enrico Forestieri wrote:
On Fri, Nov 03, 2006 at 01:18:08AM +0100, Abdelrazak Younes wrote:
Enrico Forestieri wrote:
On Fri, Nov 03, 2006 at 12:07:56AM +, José Matos wrote:
On Friday 03 November 2006 12:05 am, Enrico Forestieri wrote:
Bo, View->Source seems currently broken. I don't kno
On Thursday 02 November 2006 2:13 pm, Helge Hafting wrote:
> More lyx-1.5svn testing:
>
> Insert a URL into the document, fill in the URL field with
> http://www.free-firewall.org
>
> Try view->pdflatex or view->latex,
> get the error message
> "Undefined control sequence" \url{http://www.free-fire
Joost Verburg wrote:
Hi,
I'm not able to compile LyX 1.5svn anymore with MSVC 2005 on Windows now
the namespaces have all been changed. Compilation of support/mkdir.C and
tex2lyx/tex2lyx.C fails.
Can someone take a look at this? I'm trying to make the Windows
installer available for 1.5.
José Matos wrote:
> On Thursday 02 November 2006 7:28 pm, Asger Ottar Alstrup wrote:
>> - No UTF-8 support in LaTeX export.
>
> What needs to be done here? I would like to help fixing it. Any
> pointers?
I explained it already at least two times but here we go again:
- uncomment the utf8 li
Enrico Forestieri wrote:
On Fri, Nov 03, 2006 at 01:18:08AM +0100, Abdelrazak Younes wrote:
Enrico Forestieri wrote:
On Fri, Nov 03, 2006 at 12:07:56AM +, José Matos wrote:
On Friday 03 November 2006 12:05 am, Enrico Forestieri wrote:
Bo, View->Source seems currently broken. I don't kno
Asger Ottar Alstrup wrote:
Peter & Abdel are certified heroes.
They squashed a good deal of bugs yesterday, and put things back on
track in this everlasting LyX drama. Hope is restored!
But no crisis without a new one building up. Here is a new batch of bad
guys to go after.
Showstoppers:
On Fri, 2006-11-03 at 00:05 +0100, Abdelrazak Younes wrote:
> Asger Ottar Alstrup wrote:
> > - Crashes with multiple windows open. It seems that Buffer contains Rows
> > of paragraphs, and this is no good in a multiple view setting. Options:
> > a) Rework Buffer to not have Rows (big change, risk
Martin Vermeer wrote:
- Cursor trouble: Full refresh on each blink. Abdel says it's a lot of
work to fix this without the pixamp. Options a) Spend that time, b)
Revert to old painting scheme. Given that the removal of the pixmap did
not give us any noticable speed-up, I think we should revert t
Abdelrazak Younes wrote:
> Asger Ottar Alstrup wrote:
>> - Printing the tutorial crashes LyX. Reproduce: Ctrl+p & enter. It
>> happens at the very start of Buffer::makeLaTeXFile, because
>> encodings.getEncoding(params().inputenc) returns 0.
>
> Confirmed.
Me too. That was a misunderstanding on
Martin Vermeer wrote:
The culprit appears to be the statement
view()->buffer()->changed()
in lyxfunc.C. This sends a signal LyXView to redraw the whole screen in
WorkArea. There is no way to specify anything less than a full screen.
Unfortunately commenting out this line isn't good
Bo or Peter,
Please fix this:
Generating Code...
d:\devel\lyx\trunk\src\frontends\toolbars.c(144) : warning C4715:
'lyx::Toolbars::getToolbarState' : not all control paths return a value
Abdel.
Abdelrazak Younes wrote:
> Bo or Peter,
>
> Please fix this:
>
> Generating Code...
> d:\devel\lyx\trunk\src\frontends\toolbars.c(144) : warning C4715:
> 'lyx::Toolbars::getToolbarState' : not all control paths return a value
>
> Abdel.
>
>
Done:
Index: frontends/Toolbars.C
==
Abdelrazak Younes wrote:
Martin Vermeer wrote:
The culprit appears to be the statement
view()->buffer()->changed()
in lyxfunc.C. This sends a signal LyXView to redraw the whole screen in
WorkArea. There is no way to specify anything less than a full screen.
Unfortunately commenting out th
On Thu, Nov 02, 2006 at 07:51:07PM -0600, Bo Peng wrote:
> > > On Friday 03 November 2006 12:05 am, Enrico Forestieri wrote:
> > > I have used today, and now as I have double checked and it works for
> > > me...
> >
> > Really? When I select "View source" I only see a line
> >
> > % Preview sou
Georg Baum wrote:
> Abdelrazak Younes wrote:
>
>> Asger Ottar Alstrup wrote:
>>> - Printing the tutorial crashes LyX. Reproduce: Ctrl+p & enter. It
>>> happens at the very start of Buffer::makeLaTeXFile, because
>>> encodings.getEncoding(params().inputenc) returns 0.
>>
>> Confirmed.
>
> Me too
Georg Baum wrote:
> José Matos wrote:
>
>> On Thursday 02 November 2006 7:28 pm, Asger Ottar Alstrup wrote:
>>> - No UTF-8 support in LaTeX export.
>>
>> What needs to be done here? I would like to help fixing it. Any
>> pointers?
>
> I explained it already at least two times but here we go
Enrico Forestieri wrote:
On Thu, Nov 02, 2006 at 07:51:07PM -0600, Bo Peng wrote:
On Friday 03 November 2006 12:05 am, Enrico Forestieri wrote:
I have used today, and now as I have double checked and it works for me...
Really? When I select "View source" I only see a line
% Preview source c
Abdelrazak Younes wrote:
I am afraid not many people use MSVC with scons these days. If you post
your compile error someone could probably help though.
Aren't you're a MSVC user as well? Or does it work fine with CMake?
Out of curiosity Joost, don't you know C++?
I just thought that everyon
On Fri, Nov 03, 2006 at 11:41:13AM +0100, Abdelrazak Younes wrote:
> Enrico Forestieri wrote:
> > On Thu, Nov 02, 2006 at 07:51:07PM -0600, Bo Peng wrote:
> >
> On Friday 03 November 2006 12:05 am, Enrico Forestieri wrote:
> I have used today, and now as I have double checked and it w
Joost Verburg wrote:
Abdelrazak Younes wrote:
I am afraid not many people use MSVC with scons these days. If you
post your compile error someone could probably help though.
Aren't you're a MSVC user as well?
yes.
Or does it work fine with CMake?
yes.
Out of curiosity Joost, don't you
José Matos wrote:
> Thank you. Note that I still don't see utf-8 as an option for encoding
> in
> Document->Settings, what is missing?
I forgot that in my list. See the FIXME in
src/frontends/qt4/QDocumentDialog.C.
Georg
On Friday 03 November 2006 10:38 am, Georg Baum wrote:
>
> I just saw that I already implemented that for the general unicode
> conversion, so I enabled the utf8 encoding in lib/encodings.
Thank you. Note that I still don't see utf-8 as an option for encoding in
Document->Settings, what is miss
On Fri, Nov 03, 2006 at 11:56:43AM +0100, Enrico Forestieri wrote:
> On Fri, Nov 03, 2006 at 11:41:13AM +0100, Abdelrazak Younes wrote:
>
> > Enrico Forestieri wrote:
> > > On Thu, Nov 02, 2006 at 07:51:07PM -0600, Bo Peng wrote:
> > >
> > On Friday 03 November 2006 12:05 am, Enrico Foresti
Georg, I have updated your patch as you can see in the attachments. I
find this way easier. I think you will find it easier to review, too.
The draft documentations is also attached. I have written it
considering the new User Guide (UserGuideNV.lyx). Consider this as the
section 5.8.
And, don't
On Friday 03 November 2006 11:00 am, Georg Baum wrote:
>
> I forgot that in my list. See the FIXME in
> src/frontends/qt4/QDocumentDialog.C.
I found it later with this comment:
// FIXME: This list is incomplete. It should not be hardcoded but come from
// the available encodings in src/encoding
Abdelrazak Younes wrote:
> Once you're done you could perhaps update Bennett's recipe for MacOSX? I
> am sure Peter (the author of the CMake support) would be happy to help
> you for any request you have.
Hi Andreas,
don't hesitate to ask me. I've tested the cmake build under linux
and it compile
On 11/2/06, José Matos <[EMAIL PROTECTED]> wrote:
On Thursday 02 November 2006 12:15 pm, Georg Baum wrote:
> Ozgur Ugras BARAN wrote:
> >
> > Oh, this is bad news, since I have almost completed the multiple indices
> > stuff..
Do you have the code? :-)
Yes I do.. At least 80% of it :)) I can
From: José Matos [mailto:[EMAIL PROTECTED]
> If no one shouts until tomorrow you can put in.
it is in:
http://www.lyx.org/trac/changeset/15707
(would be nice if someone can try it out...)
Title: citation dialog
the attached adds a toolbutton that clears the search box (and restores the full citation list):
http://leuven.ecodip.net/lyx/cit.png
ok to commit?
cit.patch
Description: cit.patch
On Friday 03 November 2006 11:35 am, Ozgur Ugras BARAN wrote:
> It is not that big. I will send the patch and you decide, whether it
> can go in or not. If it can not go in, we can put it in trunk after
> the release of 1.5.
Thank you.
--
José Abílio
On Friday 03 November 2006 11:36 am, Leuven, E. wrote:
> (would be nice if someone can try it out...)
It seems to work for me.
I have tried to change an existing document and to insert a new figure. It
worked in both cases.
--
José Abílio
OK, one useless question, should the lyx name be utf8 or utf-8?
--
José Abílio
On Friday 03 November 2006 12:09 pm, José Matos wrote:
> OK, one useless question, should the lyx name be utf8 or utf-8?
Regardless I have committed the change that allows to export utf-8 encoding.
--
José Abílio
A colleague of mine discovered a math parser bug that was introduced in 1.4.
The attached test file works fine in 1.3 but produces a LaTeX error in 1.4.
The reason is special treatment of things like {}_0 that was introduced in
1.4.
The attached patch (against 1.4) refines this treatment by testing
José Matos wrote:
> OK, one useless question, should the lyx name be utf8 or utf-8?
I don't care. I used utf8 because it was used in latex. I am not 100% sure
whether the name is hardcoded somewhere, but I think it is only in lyx2lyx.
Georg
Abdelrazak Younes wrote:
I just thought that everyone would be able to reproduce this. I'll try
to fix it or I'll post the errors.
Good.
I fixed the mkdir problem but still can't get tex2lyx to compile with
SCons. It's somehow related to the Unicode conversion of the lyxerr
output in suppor
On Fri, 2006-11-03 at 10:58 +0100, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
> >>> - Cursor trouble: Full refresh on each blink. Abdel says it's a lot of
> >>> work to fix this without the pixamp. Options a) Spend that time, b)
> >>> Revert to old painting scheme. Given that the removal of
Sorry... off to the summer cottage... other takers?
- Martin
On Fri, 2006-11-03 at 11:08 +0100, Abdelrazak Younes wrote:
> Martin Vermeer wrote:
>
> > The culprit appears to be the statement
> >
> > view()->buffer()->changed()
> >
> > in lyxfunc.C. This sends a signal LyXView to redraw
On Fri, 2006-11-03 at 11:28 +0100, Abdelrazak Younes wrote:
> Abdelrazak Younes wrote:
> > Martin Vermeer wrote:
> >
> >> The culprit appears to be the statement
> >>
> >> view()->buffer()->changed()
> >>
> >> in lyxfunc.C. This sends a signal LyXView to redraw the whole screen in
> >> WorkAre
Helge Hafting <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Helge Hafting <[EMAIL PROTECTED]> writes:
| >
| > | Michael Gerz wrote:
| > | > Lars Gullik Bjønnes wrote:
| > | >
| > | >> IMHO we should not merge translations from 1.4 at all. (or at most on
| > | >> a case by case b
José wrote:
> It seems to work for me.
> I have tried to change an existing document and to insert a new figure.
> It worked in both cases.
thanks
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Asger Ottar Alstrup wrote:
| > - Crashes with multiple windows open. It seems that Buffer contains
| > Rows of paragraphs, and this is no good in a multiple view setting.
| > Options: a) Rework Buffer to not have Rows (big change, risky), b)
| > Disa
People, when adding debug output please use the provided mechanisms so
that all other do not have to see the messages.
Currently trunk is close to untestable because of massive amounts of
debug output.
--
Lgb
I am afraid not many people use MSVC with scons these days. If you post
your compile error someone could probably help though.
Even if Joost is the only one to use scons/msvc, I am responsible for
fixing it, if this is a scons problem.
Bo
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Asger Ottar Alstrup wrote:
| > - Crashes with multiple windows open. It seems that Buffer contains
| > Rows of paragraphs, and this is no good in a multiple view setting.
| > Options: a) Rework Buffer to not have Rows (bi
when i click in the workarea (to put the cursor in another part of the text)
the screen is repainted *twice* whereas it seems to me that no repainting is
necessary at all
there is also a lot of painting going on when selecting text:
- when selecting a word the whole screen is repainted
- the s
Bo Peng wrote:
I am afraid not many people use MSVC with scons these days. If you post
your compile error someone could probably help though.
Even if Joost is the only one to use scons/msvc, I am responsible for
fixing it, if this is a scons problem.
The CMake system does not yet support all
Leuven, E. wrote:
when i click in the workarea (to put the cursor in another part of the text)
the screen is repainted *twice* whereas it seems to me that no repainting is
necessary at all
there is also a lot of painting going on when selecting text:
- when selecting a word the whole screen i
Joost Verburg wrote:
Bo Peng wrote:
I am afraid not many people use MSVC with scons these days. If you post
your compile error someone could probably help though.
Even if Joost is the only one to use scons/msvc, I am responsible for
fixing it, if this is a scons problem.
The CMake system doe
Abdelrazak Younes wrote:
Leuven, E. wrote:
when i click in the workarea (to put the cursor in another part of the
text) the screen is repainted *twice* whereas it seems to me that no
repainting is necessary at all
there is also a lot of painting going on when selecting text:
- when selecting
Bo Peng wrote:
I am afraid not many people use MSVC with scons these days. If you post
your compile error someone could probably help though.
Even if Joost is the only one to use scons/msvc, I am responsible for
fixing it, if this is a scons problem.
Sure. Scons is still way ahead of CMake in
I fixed the mkdir problem but ...
http://www.lyx.org/trac/changeset/15709 This is certainly not a scons problem.
But why does cmake compile? If cmake does not detect HAVE_DIRECT_H,
whcih mkdir it uses?
Checking tex2lyx now.
Bo
Bo Peng wrote:
http://www.lyx.org/trac/changeset/15709 This is certainly not a scons
problem.
But why does cmake compile? If cmake does not detect HAVE_DIRECT_H,
whcih mkdir it uses?
I think CMake doesn't detect any mkdir at all, so it uses the API call.
This is indeed unrelated to SCons.
Am Freitag, 3. November 2006 14:44 schrieb Leuven, E.:
> José wrote:
> > It seems to work for me.
> > I have tried to change an existing document and to insert a new figure.
> > It worked in both cases.
>
Load a document with a figure which is _not_ displayed in lyx.
Go to graphics dialog->Extr
Helge Hafting wrote:
> I opened an existing document, went to document->settings->branches, and
> discovered:
> 1. I can't activate/deactivate the existing branch. The branch
>name is non-ascii.
>I can add a new one and activate/deactivate it, if the name is ascii.
> 2. Adding a new branch
Here's an update on the status of 1.5.0 on Mac, with issues listed in
rough order of importance. I'm trying to pick out issues that may be
unique to Mac.
1. Speed is *much* improved. It could be better -- there seems to be
a fraction of a second lag between when I press a key and when the
> Load a document with a figure which is _not_ displayed in lyx.
> Go to graphics dialog->Extra options
> Enable "Show in LyX"
> ==> OK button remains gray.
thanks, will have a look...
LyX-1.5.0 on Mac reliably crashes in two situations:
1. On launch from GUI (by double-clicking on the LyX icon). As I
reported before, this happens only when using the GUI; I can
successfully start LyX from the Terminal, with or without gdb. Hence
the only debug information I get is this, p
Bennett Helm wrote:
> 3. There are some drawing oddities -- lines occasionally overlapping
> vertically, math characters not properly aligned vertically. Not sure
> if anyone else has seen these, but I don't have the time now to
> determine if there's an obvious pattern.
This reminds me of a metr
Bennett Helm wrote:
> 3. There are some drawing oddities -- lines occasionally overlapping
> vertically, math characters not properly aligned vertically. Not sure
> if anyone else has seen these, but I don't have the time now to
> determine if there's an obvious pattern.
This reminds me of a metr
On Friday 03 November 2006 3:25 pm, Bennett Helm wrote:
> 5. Many issue with dialogs (most obviously: the Preferences dialog --
> which can only be accessed now via keyboard command, not from the
> menu -- appears initially too small and must be resized; not possible
> to select buttons with
Kornel wrote:
> Load a document with a figure which is _not_ displayed in lyx.
> Go to graphics dialog->Extra options
> Enable "Show in LyX"
> ==> OK button remains gray.
should work now...
>> 5. Many issue with dialogs (most obviously: the Preferences dialog --
>> which can only be accessed now via keyboard command, not from the
>> menu -- appears initially too small and must be resized; not possible
>> to select buttons with the keyboard).
>
> I see the too small size also on linux.
Bennett Helm <[EMAIL PROTECTED]> writes:
>
> LyX-1.5.0 on Mac reliably crashes in two situations:
>
> 1. On launch from GUI (by double-clicking on the LyX icon). As I
> reported before, this happens only when using the GUI; I can
> successfully start LyX from the Terminal, with or without gd
Georg Baum wrote:
José Matos wrote:
I did so I suppose the list got it. Certainly we are interested, I was
expecting someone more knowledge to answer (Hello Georg, or Angus). :-)
I got it, too, so the list definitely received it. I have not yet answered
for the very same reason: not
Am Freitag, 3. November 2006 17:34 schrieb Leuven, E.:
> Kornel wrote:
> > Load a document with a figure which is _not_ displayed in lyx.
> > Go to graphics dialog->Extra options
> > Enable "Show in LyX"
> > ==> OK button remains gray.
>
> should work now...
confirmed. I like it.
Kornel
-
Checking tex2lyx now.
This is caused by src/tex2lyx/gettext.h/C, which is not well patched
for unicode.
Trying to get a patch.
Bo
Hi,
The reported scons/tex2lyx problem with msvc is caused by imcomplete
intl/unicode support for tex2lyx. I have tested that if we remove
src/tex2lyx/gettext.h/C and copy src/gettext.h/C and src/messages.h/C
when compling tex2lyx, tex2lyx would compile under both linux and
msvc.
Any objection t
Helge Hafting wrote:
I am working slowly on them help would be appreciated.
I can look at it, like I did for 1.3. It should be simpler now, with
only one frontend.
Should I start with the nb.po that is in lyx1.5svn right now, or
should I wait
for some merge from 1.4?
I already merged wi
Bo Peng wrote:
What is TabWidget? I will be satisfied with a split (vertical or
horizontal) window option, even if there are at most two windows, and
the split has to be half half.
I agree. A split window would be fine.
Michael
Bo,
if I start LyX 1.5, the "standard" toolbar and the "extra" toolbar are
shown. All other toolbars are invisible.
However, if I look at View>Toolbars, all toolbars seem to be deactivated.
If I click on View>Toolbars>Standard, nothing happens, no matter how
often I try.
Moreover, I cannot
Michael Gerz wrote:
Ahhh... wait... there is a localization problem! If I switch from
German to English interface, everything works perfectly. I guess there
is one _(...) to much in the code!
Bo,
this will probably not work (not related to the problem above):
./MenuBackend.C:
Ahhh... wait... there is a localization problem! If I switch from German
to English interface, everything works perfectly. I guess there is one
_(...) to much in the code!
I only have an English environment so I can not test. Anyway, maybe
you can tell what goes wrong:
1. src/MenuBackend.C, lin
On Sat, Nov 04, 2006 at 12:27:48PM +1800, Bo Peng wrote:
> Hi,
>
> The reported scons/tex2lyx problem with msvc is caused by imcomplete
> intl/unicode support for tex2lyx. I have tested that if we remove
> src/tex2lyx/gettext.h/C and copy src/gettext.h/C and src/messages.h/C
> when compling tex2l
./MenuBackend.C:
docstring label = char_type(uppercase(cit->name[0])) +
_(cit->name.substr(1));
You apply _(...) to a substring that is not defined in the po files.
I guess the problem was:
tomenu.add(MenuItem(MenuItem::Command, label,
I don't understand what the problem is. At least on *nix and cygwin
tex2lyx seems working ok.
Compare src/tex2lyx/gettext.h and src/gettext.h
tex2lyx still uses std::string const _(std::string)
while lyx uses docstring const _(std::string)
Therefore, tex2lyx uses the no-translation _(). and
su
Bo Peng wrote:
./MenuBackend.C:
docstring label = char_type(uppercase(cit->name[0])) +
_(cit->name.substr(1));
You apply _(...) to a substring that is not defined in the po files.
I guess the problem was:
tomenu.add(MenuItem(MenuItem::Command, label,
On Sat, Nov 04, 2006 at 02:01:11PM +1800, Bo Peng wrote:
> > I don't understand what the problem is. At least on *nix and cygwin
> > tex2lyx seems working ok.
>
> Compare src/tex2lyx/gettext.h and src/gettext.h
>
> tex2lyx still uses std::string const _(std::string)
> while lyx uses docstring co
If I understand it correctly, that funtion is a stub put there to not
bring useless stuff in tex2lyx. I think that you can simply change
std::string with docstring and be done.
OK. this also works, but I really do not like the idea of a separate
gettext.h. You know, it took me three hours to tra
Juergen Spitzmueller wrote:
I think we could just take some from the KDE classic iconset, where the
other icons are taken from IIRC. Like the attached, for instance.
I committed the icons as xpm files. There is still one icon missing for
"note-next".
Michael
Pavel Sanda wrote:
If appropriate, we took your translations from the 1.4.X stable branch
such that your prior work didn't get lost.
this was not good note ;)
Don't worry, Pavel. In case of cs.po, I kept the 1.5 translations which
were better than the 1.4 translations.
1. more menu it
Hello,
just in case someone is interested in bug reports: please see the
attached file.
I think there is still a lot of work ahead of us...
Michael
Bugs (highest priority first):
- Spell checking cannot be invoked a second time!
- In the TOC dialog, switching between the different TOC
typ
Hi,
I just compiled the current LyX 1.5svn on Windows. There are still many
major bugs. Here are some things I noticed during the first few minutes
of testing:
* Performance is bad. On my system, scrolling the User Guide takes 10
seconds with LyX 1.4 and more than 30 seconds with LyX 1.5. Al
Hi,
I tried to create a lyx 1.5.0 status wiki page that collects all bug
reports (bugzilla is too cumbersome for this task at this stage), but
get "PmWiki can't process your request". Is wiki still working?
Bo
Dear all,
We have repeated long bug list posted to this list and it is hard to
keep track of them. I propose that we put a file status.15x in trunk
and start a debugging spree. I am interested in knowing who will be
our champion (although the answer is almost obvious :-) when I get
back.
Agreed?
Bo Peng wrote:
We have repeated long bug list posted to this list and it is hard to
keep track of them. I propose that we put a file status.15x in trunk
and start a debugging spree. I am interested in knowing who will be
our champion (although the answer is almost obvious :-) when I get
back.
Ag
Bo Peng wrote:
Dear all,
We have repeated long bug list posted to this list and it is hard to
keep track of them. I propose that we put a file status.15x in trunk
and start a debugging spree. I am interested in knowing who will be
our champion (although the answer is almost obvious :-) when I ge
Asger Ottar Alstrup wrote:
Bo Peng wrote:
We have repeated long bug list posted to this list and it is hard to
keep track of them. I propose that we put a file status.15x in trunk
and start a debugging spree. I am interested in knowing who will be
our champion (although the answer is almost obvi
92 matches
Mail list logo