On Thursday 03 August 2006 14:44, Lars Gullik Bjønnes wrote:
> Right. The internal format (which will be ucs-4, unless somehting
> happens) has little or nothing to do with the external format.
I know and that is how it work in python as well, the internal
representation is ucs-4. Not that I ca
On Thursday 03 August 2006 14:26, Lars Gullik Bjønnes wrote:
> IMHO we should drop \inputencoding from the fileformat when moving to
> utf-8, it is not as if you have a choice...
Such as it is the code supports ucs-4 and ucs-2, but I think that I agree
that we can use utf-8 as the ("de facto")
Hi,
the following patch adds support for a fictitious file format called
249
which has the property that file encoding is utf-8.
The revert part is more difficult. I should revert to the encoding
associated
with the language, and then verify each character to guarantee that we
On Monday 31 July 2006 12:27, Lars Gullik Bjønnes wrote:
> I made some huge progress on the unicode branch this weekend, and we
> are getting closer to a point where it can be merged with maintrunk.
>
> However, it would be nice if you could try it out. Especially if you
> have easy access to somet
On Wednesday 02 August 2006 01:37, Lars Gullik Bjønnes wrote:
> Jose' Matos <[EMAIL PROTECTED]> writes:
> | Hi,
> | probably Lars knows the answer to this question. :-)
> |
> | What is the difference between default and auto as values of
> | \\inputenconding?
On Tuesday 01 August 2006 22:50, [EMAIL PROTECTED] wrote:
> Congratulations.
Thanks. :-)
> Finishing a thesis is like lifting a heavy weight from
> your stomach.
I am in such a good mood that I have almost finished the support for lyx2lyx
to formats from lyx 0.7 and 0.8. :-)
Does anyone
Hi,
probably Lars knows the answer to this question. :-)
What is the difference between default and auto as values of
\\inputenconding?
The code is not terribly clear. :-)
When did we change this code? I suppose it was in 0.12, if so I should
take
care of it in
On Monday 31 July 2006 19:51, Edwin Leuven wrote:
> Jose' Matos wrote:
> > Thanks to the help of lyx developers and users, tips, advice, humour, no
> > smile Fridays and so on, I have today officially delivered my thesis.
>
> welcome doctor, congratulations!
Well no
On Monday 31 July 2006 19:46, Lars Gullik Bjønnes wrote:
> Very good. Now get your python conversion tools cranking. Unicode
> branch is ready for lyx2lyx magic.
I am thinking about that and also about this (if you still remember it)
http://www.mail-archive.com/lyx-devel%40lists.lyx.org/msg2216
Thanks to the help of lyx developers and users, tips, advice, humour, no smile
Fridays and so on, I have today officially delivered my thesis. It was a
breeze with LyX. :-)
Thanks guys (and gals),
--
José Abílio
On Monday 31 July 2006 11:47, Georg Baum wrote:
> I like that idea. Actually I would nut put any energy at all in the native
> ascii export, that is difficult to get right.
Supposedly this is a minimum dependency path, no need to require external
references. It is a fallback path and it was nev
On Sunday 30 July 2006 20:30, Sven Hoexter wrote:
> I donno which way would be the best from a technical point of view.
> If it works the ps2ascii conversion doesn't sound bad at all. Maybe make it
> optional to choose in which way you'd like to export a document?
This is like the option to expo
On Sunday 30 July 2006 20:10, Paul A. Rubin wrote:
> He recently posted that he hit the same bug in another image. Both
> images were produced by MATLAB. If MATLAB were the culprit, though, I
> doubt commenting out the aiksaurus environment variable would fix anything.
Fair enough, it looks li
On Sunday 30 July 2006 14:42, Sven Hoexter wrote:
> Reported in this bug report against the Debian package:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=198380
Like in the previous bug we can either fix that in text output, that will be
difficult, and it will imply a new way to export sim
On Sunday 30 July 2006 14:29, Sven Hoexter wrote:
> Hi,
> if you export a document with footnotes to ascii the handling still
> suboptimal.
>
> If you've a a construction like
> "This is a first sentence[And here is a footnote.]."
>
> The export will look like:
> cut--
> This is a first
Hi,
I would like to rename two files from lxy2lyx:
lyx_1_1_6.py -> lyx_1_1_6_0.py
lyx_1_1_6fix3.py -> lyx_1_1_6_3.py
The change is minimal and purely aesthetically but it helps to see the
relation between both. :-)
This rename implies to change two lines in LyX.py and
On Saturday 29 July 2006 23:41, Paul A. Rubin wrote:
> Hi,
>
> This is a synopsis of a bug reported by someone on the user list. I'm
> hesitant to put it in bugzilla (but will if asked to), because I can't
> reproduce it at my end, and he's rolled back to 1.4.1.
Hi Paul,
an obvious ques
On Friday 28 July 2006 09:30, Nicolás wrote:
> Hi!
>
> I have just notice yet another curious behaviour of line-break in LyX142
>
> If we have some text and insert a line-break just after an space
> separating two words, LyX will show the new line starting with an space
> (i.e. like if it was inden
On Thursday 27 July 2006 18:57, Juergen Spitzmueller wrote:
> congratulations then!
Thank you. :-)
> Jürgen
--
José Abílio
On Thursday 27 July 2006 17:03, Juergen Spitzmueller wrote:
> Jose' Matos wrote:
> > I attach a patch that does exactly this.
>
> Aren't deadlines nice? ;-)
Better yet after finishing the thesis. :-)
Now the thesis is in the press. Meanwhile it broke and they are e
On Thursday 27 July 2006 12:40, Jose' Matos wrote:
> On Thursday 27 July 2006 09:48, Jose' Matos wrote:
> > I will move the functions used from parser_tools.py to the
> > corresponding files. This will allow us to avoid the dreadful
> > alternatives scenario
On Thursday 27 July 2006 09:48, Jose' Matos wrote:
> I will move the functions used from parser_tools.py to the
> corresponding files. This will allow us to avoid the dreadful alternatives
> scenarios where we have to consider all possible syntaxes.
Just to be clear, I
Hi all,
I intend to work on lyx2lyx soon and continue its evolution. I have
some
crazy ideas about what to do, but for the moment I want to start with
something simple.
I will move the functions used from parser_tools.py to the
corresponding
files. This will allow us to avoid
On Wednesday 26 July 2006 18:34, Martin Vermeer wrote:
> This is a perfect job for an external (Python) utility. Most of the
> work seems already done in ldiff.
It is my todo list such a script. Before I have a paper deadline next
Monday. :-)
I intend to wrap the functionality around LyX pyt
On Saturday 22 July 2006 23:39, Lars Gullik Bjønnes wrote:
> Jose' Matos <[EMAIL PROTECTED]> writes:
> | On Saturday 22 July 2006 14:13, Georg Baum wrote:
> | > > What is the problem with included boost there?
> |
> | I am using FC-5.
> |
> | I had the p
On Monday 24 July 2006 23:41, Charles de Miramon wrote:
> I know there is a Ugaritic package for LaTeX. But is it really serious to
> multiply the memory cost of LyX for the two thousand people in the world
> that can write cuneiforms ?
With all the due respect Charles but if you ever saw lyx sp
On Saturday 22 July 2006 14:13, Georg Baum wrote:
> > What is the problem with included boost there?
I am using FC-5.
I had the problems that Georg and Jürgen reported, as I have told before an
easy way to me to crash lyx is:
1) insert a figure in lyx
2) overwrite that figure in the backgro
On Friday 21 July 2006 16:50, Juergen Spitzmueller wrote:
> Definitely. The gcc-4.1/boost-1.33 problems are the source of the most
> severe bugs in 1.4 currently.
I agree, overwriting a figure currently displayed by lyx and therefore
crashing lyx is not fun. :-(
> Jürgen
--
José Abílio
On Friday 21 July 2006 16:00, Lars Gullik Bjønnes wrote:
> I belive we should just decide that we will support system boost from
> 1.34 and further on... (and then we can also remove boost from our
> sources.)
I like this option.
> --
> Lgb
--
José Abílio
On Wednesday 19 July 2006 07:33, Georg Baum wrote:
> Yes, there are objections. Jean-Marc introduced lyxrc.dist exactly for this
> purpose. Just create that file with the wanted settings, and you are done.
Thanks Georg.
If my memory serves me well this was done after I brought the exactly sam
Hi,
Rex Dieter (Fedora Extras packager of LyX) has this patch for the
fedora rpm
(that follows attached).
The reason given for carrying the patch is:
"""
Normally, manual modifications to (the global) lyxrc.defaults get lost
the next time configure is run. With this patch, users can
On Tuesday 18 July 2006 15:36, Bo Peng wrote:
> {} outputs nothing, just makes ' ' after it significant. In the
> a[comment]b case, the last line of the latex output is {}b, which is
> simply b.
That is fair. Thanks. :-)
> Cheers,
> Bo
--
José Abílio
On Tuesday 18 July 2006 15:26, Bo Peng wrote:
> + // Adding {} before ' b' fixes this.
> + if (params_.type == InsetNoteParams::Comment)
> + ss << "{}";
Shouldn't this code be conditional?
This will work for 'a[comment] b' what about the 'a[comment]b' case? In this
c
On Monday 17 July 2006 01:20, Bo Peng wrote:
> I can not view this page. Firefox does not show the svn'ed page at
> all, and IE shows an image-not-found kind of box.
It works with konqueror, but not with links, it says something like "Your
browser does not support including other html pages"...
On Sunday 16 July 2006 22:27, [EMAIL PROTECTED] wrote:
> Does this URI still show valid files? If not, I think ViewCVS should be
> disabled.
It shows the files from cvs repository that is now frozen.
> http://www.lyx.org/cgi-bin/viewcvs.cgi/lyx-devel/src/
The new general purpose viewe
On Wednesday 12 July 2006 17:46, Andre Poenitz wrote:
> Shouldn't we simply embed Python now that it has become de facto the
> Chosen Scripting Language?
No, no, we will start the LI (Language Independent) sub-project since we
don't want to alienate the perl, ruby, lua and scheme developers in
On Thursday 13 July 2006 18:56, Bo Peng wrote:
> Didn't I said that normal windows users do not read any instruction or
> documentations :-)
Could you please remove the word windows there, the sentence is still true
without it. ;-)
> Bo
--
José Abílio
On Thursday 13 July 2006 10:15, Jean-Marc Lasgouttes wrote:
> We could even release 1.4.3 in September with these features.
>
> Thoughts?
I like this plan, I think that we should try to do time schedule releases
for the stable branch.
Since you are the release manager you can decide what is
On Tuesday 11 July 2006 18:22, Andre Poenitz wrote:
> qt2 looks odd.
And it is wrong for 1.5.x, I only support qt3+ there.
> Andre'
--
José Abílio
On Wednesday 28 June 2006 21:18, Asger Ottar Alstrup wrote:
> Will you be able to go at that time?
I am sorry Asger, I have been busy and I was unable to answer before. This
year at the time that you propose I will be presenting my thesis (Viva).
I am truly sorry, maybe next time. :-)
> Reg
On Wednesday 12 July 2006 15:32, Jean-Marc Lasgouttes wrote:
> So, what shall we do?
Throw a coin (?!).
I am running out of useful suggestion. :-)
> JMarc
--
José Abílio
On Wednesday 12 July 2006 10:59, Abdelrazak Younes wrote:
> I believe Angus was talking about some program communicating with the
> LyXServer without any GUI interaction.
I know, I was referring to --remote-url (if not this another similar), that
ask to recycle an existing instance and not to o
On Wednesday 12 July 2006 10:33, Angus Leeming wrote:
> What happens in the (hypothetical for now) case when we have two LyXViews
> neither of which have focus and the LyXServer receives the setBuffer LFUN?
> Which LyXView do we choose is "active"?
Using firefox, as an example, I would say that
On Sunday 09 July 2006 19:40, Lars Gullik Bjønnes wrote:
> |
> | Not only easily available but they are already there, and so they have
> | been for some time.
>
> I'll admit to a few weeks.
FWIW since 2006-05-24
--
José Abílio
On Sunday 09 July 2006 14:57, Charles de Miramon wrote:
> For Fedora there are easily available packages
>
> http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/qt4
Not only easily available but they are already there, and so they have been
for some time.
--
José Abílio
On Sunday 09 July 2006 01:53, Bo Peng wrote:
> I vote against this behavior. Users should be given a clear idea what
> C-y (or C-v) do. The webpage Georg refers to also recommends clear
> separation of CLIPBOARD and SELECTION.
OTOH if you use emacs keybindings you expect emacs behaviour...
--
On Friday 07 July 2006 17:13, Georg Baum wrote:
> I fear he will, because this has nothing to do with the other stuff in your
> branch.
+1
> If I were you I would announce that this patch will go in trunk tomorrow
> unless there are objections. This is a perfect example for this procedure:
> It i
On Friday 07 July 2006 16:41, Joost Verburg wrote:
> Maybe it's a good idea to create a separate branch/directory on the SVN
> server for the installer and all related software? I have modified
> versions of Aspell, Aiksaurus, Dvipost and Libiconv for Windows.
As far as possible you should try t
On Friday 07 July 2006 10:12, Jean-Marc Lasgouttes wrote:
> Why not just apply the following patch?
Please do. It should not hurt.
> See the gentoo guy comment:
> http://comments.gmane.org/gmane.comp.sysutils.autoconf.general/6848
>
> Libtool 2.0 is supposed to fix that.
Ah, the old mantra "
On Friday 07 July 2006 09:12, Abdelrazak Younes wrote:
> > It works for qt4 now. Thanks.
>
> Cool, thanks for checking.
It is easy to do.
> > PS: I disregard you comment about yesterday... ;-)
>
> Which one?
The one regarding sadness, we are never sad, only less happy.
I learned that re
On Friday 07 July 2006 06:45, Juergen Spitzmueller wrote:
> I wonder why this was undetected so long.
Because we don't do spelling mistakes?
(Even for a Friday this is a lame excuse.)
--
José Abílio
On Friday 07 July 2006 04:27, Bo Peng wrote:
> Lars, you might want to fix autotools for this as well. I just tried
> lyx.1.4.2svn with system boost 1.33.1. When I use
> --without-included-boost, configure did not complain with (wrong boost
> version) or without (no boost header)
> --with-extra-inc
On Thursday 06 July 2006 15:10, Abdelrazak Younes wrote:
>
> By the way Jose, do you still see the problem with accentuated chars?
>
> Abdel.
It works for qt4 now. Thanks.
PS: I disregard you comment about yesterday... ;-)
--
José Abílio
On Thursday 06 July 2006 11:07, Jean-Marc Lasgouttes wrote:
> As I said, we tweak local boost files to support new systems. So,
> assuming that your system version of boost is adapted to your system
> (which should be the case), no change should be needed.
My version always complains in 1.4.x sa
On Wednesday 05 July 2006 10:59, Jean-Marc Lasgouttes wrote:
> Andre> I think it is sufficient to keep Qt 3 compilable, let GTK rot
> Andre> (in the sense to declare it 'tolerated, but not supported by
> Andre> the core team'), and put all effort into Qt 4.
>
> Also, are we sure that at that time q
On Tuesday 04 July 2006 11:34, Enrico Forestieri wrote:
> Ops, forgot to ":set expandtab" in vim. Why not put a
> "# vim: set et ts=4 sw=4:" line at the end of python scripts?
I am not against such a change. :-)
The same applies for emacs settings although we are using the emacs default
setti
Hi,
like the title says.
Not much to add now. :-)
--
José Abílio
On Monday 03 July 2006 14:03, Lars Gullik Bjønnes wrote:
> But when I say something you take everything as gospel?
Actually it is easy for someone who does not know you personally.
For those who don't know Lars in this list, Lars is a very reasonable person
with a clear set of principles. Th
On Monday 03 July 2006 14:21, Jean-Marc Lasgouttes wrote:
>
> It was supposed to be SCNR...
In the previous context any of the following alternatives seems plausible:
Acronym Definition
SCNR Signal to Clutter plus Noise Ratio
SCNR Somatic Cell Nuclear Replacement
SCNR Sorry, Could Not Re
On Monday 03 July 2006 10:57, Jean-Marc Lasgouttes wrote:
> OK, once again: when 1.5 ships I would expect that people who have
> installed a new distribution in July 2006 are not laughed at because
> their distribution is really inadequate for using LyX.
FWIW I agree.
--
José Abílio
On Sunday 02 July 2006 21:57, Abdelrazak Younes wrote:
> > Or maybe two: I WANT TO HAVE ABDEL BACK IN THIS PROJECTS.
>
> No need to shout Michael :-)
I leave you (all) alone for 4 days and is this what you do? ;-)
Torino (Turin) is a fine place, and I should tell you that they were
supportin
On Tuesday 27 June 2006 18:10, Jose' Matos wrote:
> Usually laptops have more cache L2 then desktops...
OK, I am referring to Centrinos. :-)
--
José Abílio
On Tuesday 27 June 2006 18:00, Lars Gullik Bjønnes wrote:
> mm what is your laptop?
>
> (My desktop is supposed to be faster than my laptop... but not with
> lyx and qt4)
Usually laptops have more cache L2 then desktops...
> --
> Lgb
--
José Abílio
On Tuesday 27 June 2006 17:41, Juergen Spitzmueller wrote:
> But only if the user does not use the Bibliography environment.
... and we should walk through all include files to guarantee this.
> Jürgen
--
José Abílio
On Tuesday 27 June 2006 15:27, Georg Baum wrote:
> One general comment: Right now, we have all sorts of indentation in .py
> files (mainly two spaces, four spaces, and tabs).
>
> IMO we should use the same indentation rule as in C++ files: tabs for
> logical indentation, and spaces for alignment, e
On Tuesday 27 June 2006 10:06, Abdelrazak Younes wrote:
> Hello Bo,
>
> I have these messages printed on console:
Already reported by Lars in previous thread. :-)
One of the possible solution is to add
# -*- coding: iso-8859-15 -*-
in the second line.
At least to deal with the warnings.
On Tuesday 27 June 2006 09:14, Jean-Marc Lasgouttes wrote:
> Well, it seems that the prospect of doing a joke overshadowed the
> prospect of looking stupid. I know what an harmonic series is. At
> least I am supposed to.
I do too but I must confess here that I have not yet calculated all its
te
On Tuesday 27 June 2006 01:33, Bo Peng wrote:
> BTW, I was using 8859-1, but 8859-15 may be better.
Is there any reason for us not using utf-8 for 1.5?
I think that those files should follow the same spirit of the project
changes.
> Bo.
--
José Abílio
On Tuesday 27 June 2006 01:33, Bo Peng wrote:
> BTW, I was using 8859-1, but 8859-15 may be better.
If you need to talk about € then yes else no (mostly there are only two
other changes). :-)
> Bo.
--
José Abílio
On Monday 26 June 2006 21:29, Jean-Marc Lasgouttes wrote:
>
> The difference is that harmonic series are difficult to predict
> because they alternate between positive and negative contributions to
> the sum.
Although its name is harmonic all the series terms are positive (and
decreasing).
h
On Monday 26 June 2006 17:52, Jean-Marc Lasgouttes wrote:
> Do you want to bet?
I can always apply forecast from my research. ;-)
> You do not know how trivial some of these things are.
I know my to do list and it has lots of trivial stuff. After all even the
harmonic series diverges, and
On Monday 26 June 2006 17:44, Jean-Marc Lasgouttes wrote:
> Yes. I hope to have time to finish some of mine this summer.
Famous last words. ;-)
> JMarc
--
José Abílio
On Monday 26 June 2006 13:47, Abdelrazak Younes wrote:
> 1) call "setAttribute(Qt::WA_InputMethodEnabled, true)" in GuiWorkArea
> constuctor. This is in replacement for the former Qt3
> "setInputMethodEnabled(true)" and I hope that it will solve the accent
> problem reported by Jose.
Now I do no
On Monday 26 June 2006 13:58, Abdelrazak Younes wrote:
> > Yes, this is what I wrote. When it is out, we should be able to
> > support distributions that are about 2 years old.
>
> Sorry but I still think this is not our problem if some two years old
> distribution won't distribute a Qt4 package.
On Monday 26 June 2006 11:02, Abdelrazak Younes wrote:
> Who talk about maintaining a Qt copy?
That is what you are saying below. :-)
> In the past, software were
> distributed in a tar.gz and it worked fine for all distrib.
The past is the past. :-)
> We just need
> to extract the librar
On Monday 26 June 2006 09:51, Abdelrazak Younes wrote:
> Because it is part of the Qt4 API not part of some external module anymore.
FWIW I can not insert accents in qt4, both in your branch and in trunk. :-(
> Abdel.
--
José Abílio
OK, trying to compile your branch for qt4 only I get two errors:
Application.C: In member function 'virtual bool
lyx::frontend::Application::x11EventFilter(XEvent*)':
Application.C:77: error: 'class lyx::frontend::GuiWorkArea' has no member
named 'view'
Application.C:82: error: 'class lyx::
Hi,
this is another subjective report so please take it with a grain of
salt. :-)
I have updated qt4 to the latest 4.1.4 and I perceive it as faster, I
can
certainly notice the difference from the first version I tried (4.1.2).
FWIW I have lyx configure with:
./configur
On Friday 23 June 2006 17:43, Andre Poenitz wrote:
> No. But xforms could be removed right away.
Is there any reason for it to here?
What is the reason for not removing it now?
As a compromise I propose to mark it in the same level as gtk, people don't
try to break it on purpose, keep it w
On Friday 23 June 2006 13:30, Jose' Matos wrote:
> Surprisingly (at least to me) there was a so clear cut between those two
> options.
there was _not_ a clear cut...
Today is a "no smiley day, not as I and Abdel seem to be doing a no no day.
--
José Abílio
On Friday 23 June 2006 13:12, Edwin Leuven wrote:
>> I also see that most peoble would like to retain the ability to insert
>> tabulars with lines...
>
>
>
> sure, more is better, but that is besides the point
I am sorry but that is the point. You changing one arbitrary default by
another arbit
On Friday 23 June 2006 11:00, Peter Kümmel wrote:
> Abdelrazak Younes wrote:
> > Peter Kümmel wrote:
>
>
>
> I didn't know the 'no-smiley day', but it looks
> interesting, and I think I like it.
The concept is best expressed here:
http://www.lyx.org/news/2726.php#item3
--
José Abílio
On Friday 23 June 2006 08:44, Abdelrazak Younes wrote:
> Does your "No" weight more than our three "Yes"?
That is one of the privileges of the BDFL (python jargon).
> The weather is hot today...
Foggy around here, so not much. But then we always expected our lost king to
appear in a foggy m
On Thursday 22 June 2006 17:30, Abdelrazak Younes wrote:
>
> PODs I mean...
I like this more:
http://www.parashift.com/c++-faq-lite/intrinsic-types.html#faq-26.7
--
José Abílio
On Thursday 22 June 2006 17:30, Abdelrazak Younes wrote:
> Abdelrazak Younes wrote:
> > Angus Leeming wrote:
> >
> > What POS means anyway?
>
> PODs I mean...
Plain Old Data:
http://www.fnal.gov/docs/working-groups/fpcltf/Pkg/ISOcxx/doc/POD.html
--
José Abílio
On Wednesday 21 June 2006 17:59, Bo Peng wrote:
> There
> are also some discrimination against windows system so
> windows-specific changes are harder to be accepted (e.g. space in
> path, scons, .C=>,cpp conversion, msvc/pch). Scons still managed to
> get in though. :-)
Please don't confuse our
On Wednesday 21 June 2006 17:12, Abdelrazak Younes wrote:
> FYI I had the very same reaction when I first joined in (Bo also I
> believe). I still think that the LyX team is overly conservative but I
> have the feeling that this is changing.
I am sorry for pointing the obvious, "or you are chang
On Tuesday 20 June 2006 17:20, Lars Gullik Bjønnes wrote:
> "Bo Peng" <[EMAIL PROTECTED]> writes:
> | > That is what we have setup automake to do.
> | > (except that we have so far not bothered to split config.h)
> |
> | Really? src/config.h.in:
>
> Hmm da hmm... you are right...
>
> We should prob
On Tuesday 20 June 2006 15:33, Abdelrazak Younes wrote:
> shxxt, I'll do it now. Thanks.
Fixed, thanks. :-)
> Abdel.
--
José Abílio
On Tuesday 20 June 2006 10:34, Abdelrazak Younes wrote:
> In preparation for the next round of GUI API cleanup.
>
> Abdel.
>
> Log:
> t4/QtView renamed to GuiView
You forgot to update autotools:
make[5]: Entering directory `/home/jamatos/lyx/lyx-devel/src/frontends/qt4'
/usr/lib/qt4///bin/moc -o
On Tuesday 20 June 2006 09:21, Abdelrazak Younes wrote:
> Man, we should definitely take a decision on that! Please don't let this
> discussion dye.
Usually I don't point such mistakes or else I would be forced to look to my
own. ;-)
In this case I make an exception:
dye != die
dye is
On Monday 19 June 2006 09:28, Abdelrazak Younes wrote:
> > No. Time.
>
> What does that that mean?
Give us (Lars ;-) time to see the changes. :-)
--
José Abílio
On Thursday 15 June 2006 13:10, Peter Kümmel wrote:
>
> Where is the coding style guide?
development/Code_rules/*
--
José Abílio
On Wednesday 14 June 2006 19:44, Andre Poenitz wrote:
> Yeah... the procedure sounds familiar...
Yes, been there, done that. Wait... I am still there... ;-)
> Andre'
--
José Abílio
On Wednesday 14 June 2006 10:45, Abdelrazak Younes wrote:
> Great, I am promoted to official "OK-sayer" :-)
You have been for some time now, you simply did not know that. ;-)
> Abdel.
--
José Abílio
On Tuesday 13 June 2006 13:16, Helge Hafting wrote:
> > Or did I misunderstood what you said?
> >
>
> I think we agree about this, it is Lars that seems to hold back.
I would like not to forget this issue. Please could you fill a bugzilla
entry for 1.5.0. I agree that something needs to be
On Monday 12 June 2006 12:16, Georg Baum wrote:
> I'll have a look at the lyx2lyx stuff laater this week if Jose does not
> beat me to it.
By all means, I am buried under (and fighting) fractals, multifractals and
other equally elusive beasts. ;-)
> Please don't apply your patch without lyx2ly
On Saturday 10 June 2006 14:36, Juergen Spitzmueller wrote:
> - lyx2lyx. I'd be glad if some Pythonist could do this. The changes are
> described in FORMAT.
First of all congratulations for your work. :-)
The convertion should be quite easy but I am really busy for the moment. I
will see wha
On Friday 09 June 2006 12:20, Helge Hafting wrote:
> I think "no lines" is the better way. No old stuff breaks. There
> isn't even an update of the document format.
I don't understand you here. There is nothing related with an update for the
file format.
The question here, as far I underst
On Thursday 08 June 2006 09:35, Georg Baum wrote:
> What was that mistake?
We made a decision to stick with python 1.5.2 in the begin of the
development cycle and we never revise that. So what did look like a
reasonable decision three years later was outdated.
FWIW and in the interest of his
1 - 100 of 975 matches
Mail list logo
