On 2010-05-26, José Matos wrote:
> On Wednesday 26 May 2010 15:29:13 Pavel Sanda wrote:
>> can you be even more verbose abou the "subtle" problems?
>> my imagination was that there exists pythonic code running under both 2 & 3
>> so once we convert the code we dont need to care anymore about
>> ver
On 2010-05-22, Niklaus Giger wrote:
...
> But when I tried to import all the files from
> https://elexis.svn.sourceforge.net/svnroot/elexis/trunk/doc_fr
> I did run into several problems:
...
> b) When converting to PDF via pdflatex I ran into several problems:
> b1) (a lot of them) wrong input e
Pavel Sanda wrote:
> Pavel Sanda wrote:
> > its not updated. you must do the update to the current state after
> > unpacking...
>
> hmm what makes me perplexed that git tag does not list branch tags although
> they were imported...
ok it works in a bit different way then i'm used to: git branch
On Wed, May 26, 2010 at 06:55:10PM +0200, Enrico Forestieri wrote:
> On Wed, May 26, 2010 at 05:20:52PM +0200, Jürgen Spitzmüller wrote:
> > > Author: forenr
> > > Date: Wed May 26 15:17:36 2010
> > > New Revision: 34514
> > > URL: http://www.lyx.org/trac/changeset/34514
> > >
> > > Log:
> > > We h
On Wed, May 26, 2010 at 03:00:47PM +0200, Jean-Marc LASGOUTTES wrote:
> Enrico Forestieri writes:
> > You changed BiographyNoPhoto to Biography_without_photo, such that old
> > documents created with earlier versions cannot be correctly loaded with
> > lyx 1.6.6. This is also an issue in trunk, wh
Pavel Sanda wrote:
> its not updated. you must do the update to the current state after
> unpacking...
hmm what makes me perplexed that git tag does not list branch tags although
they were imported...
pavel
Jean-Marc LASGOUTTES wrote:
> Pavel Sanda writes:
>
> > hi,
> >
> > for the interested parties, the whole lyx-devel svn tree transformed into
> > git based archive is now stored on
> > ftp://ftp.lyx.org/pub/lyx/devel/git-devel/
>
> How is this updated?
its not updated. you must do the update t
Jean-Marc LASGOUTTES wrote:
> Pavel Sanda writes:
>
>> hi,
>>
>> for the interested parties, the whole lyx-devel svn tree transformed into
>> git based archive is now stored on
>> ftp://ftp.lyx.org/pub/lyx/devel/git-devel/
>
> How is this updated?
>
> JMarc
>
Only when you use it locally, se
On Wed, May 26, 2010 at 05:20:52PM +0200, Jürgen Spitzmüller wrote:
> > Author: forenr
> > Date: Wed May 26 15:17:36 2010
> > New Revision: 34514
> > URL: http://www.lyx.org/trac/changeset/34514
> >
> > Log:
> > We have the magic keyword ObsoletedBy which allows renaming styles
> > (thanks JMarc fo
Pavel Sanda writes:
> hi,
>
> for the interested parties, the whole lyx-devel svn tree transformed into git
> based archive is now stored on
> ftp://ftp.lyx.org/pub/lyx/devel/git-devel/
How is this updated?
JMarc
José Matos wrote:
> Actually now that I think and research more about this particular problem we
> can get away with since the
>
> from __future__ import division
>
> works since python 2.2 (and we only support versions later than 2.3.4).
>
> The point was more that we need to test this careful
On Wednesday 26 May 2010 16:18:09 Pavel Sanda wrote:
> > 5/2 == 2
> > 5/2 == 2.5 (as much as equality tests are appropriate for floating point
>
> ouch. i thought its just about syntax sugar, now i agree we shouldn't try
> to support multiple versions...
Actually now that I think and research mo
> Author: forenr
> Date: Wed May 26 15:17:36 2010
> New Revision: 34514
> URL: http://www.lyx.org/trac/changeset/34514
>
> Log:
> We have the magic keyword ObsoletedBy which allows renaming styles
> (thanks JMarc for pointing out it)
Could you backport this, please?
Jürgen
2010/5/26 Pavel Sanda:
> - what about allowing package maintainers to revert the single problematic
> commit 33567
> for 1.6.6. we have win+mac and at least three linux distro maintainers on
> this
> list so i guess 90% of users are covered by this.
I don't like to have diverging releases with
José Matos wrote:
> On Wednesday 26 May 2010 15:29:13 Pavel Sanda wrote:
> > can you be even more verbose abou the "subtle" problems?
> > my imagination was that there exists pythonic code running under both 2 & 3
> > so once we convert the code we dont need to care anymore about
> > versioning...
Jürgen Spitzmüller wrote:
> I guess the procedure depends on how you (all) rate the importance of
> pending bugs, and how soon and how "safe" we can fix them.
>
> I'm open to suggestions.
- what about allowing package maintainers to revert the single problematic
commit 33567
for 1.6.6. we have
On Wednesday 26 May 2010 15:29:13 Pavel Sanda wrote:
> can you be even more verbose abou the "subtle" problems?
> my imagination was that there exists pythonic code running under both 2 & 3
> so once we convert the code we dont need to care anymore about
> versioning...
What would it be the minimu
José Matos wrote:
> Long answer: My problem with this approach is that it would add a burden to
> developers. You would need to test both with 2 and 3 since they would be both
> supported.
>
> I am not worried with the obvious bugs but with the subtle.
can you be even more verbose abou the "sub
On Tuesday 18 May 2010 23:22:03 Pavel Sanda wrote:
> Jose, is it possible to have the scripts that runs both under python 2 & 3,
> so we don't have to care about it anymore? If so, could you prepare the
> patch?
>
> Pavel
Short answer: I can but I don't want to do it. :-)
Long answer: My problem
2010/5/26 Pavel Sanda:
> hi,
> i was privately thinking about the topic which appeared indepnedently in
> #6708,
> so might be better to discuss it here.
>
> my suggestion would be to release new 1.6.7 much much sooner then normal
> 3months
> schedule with:
> - spellchecker regression fixed
> - Q
hi,
i was privately thinking about the topic which appeared indepnedently in #6708,
so might be better to discuss it here.
my suggestion would be to release new 1.6.7 much much sooner then normal 3months
schedule with:
- spellchecker regression fixed
- Qt 4.6 outliner issues fixed in case Richard
hi,
for the interested parties, the whole lyx-devel svn tree transformed into git
based archive is now stored on
ftp://ftp.lyx.org/pub/lyx/devel/git-devel/
pavel
On Wed, May 26, 2010 at 03:00:47PM +0200, Jean-Marc LASGOUTTES wrote:
> Note that ObsoletedBy allows to rename styles painlessly.
Doh! Thanks, I used it in trunk for IEEEtran.layout. I'll leave to
Uwe the task of sorting out the mess in branch.
--
Enrico
Enrico Forestieri writes:
> You changed BiographyNoPhoto to Biography_without_photo, such that old
> documents created with earlier versions cannot be correctly loaded with
> lyx 1.6.6. This is also an issue in trunk, where I initially missed it.
Note that ObsoletedBy allows to rename styles pain
Richard Heck wrote:
> It's not that I don't agree. But we chop lines in weird ways in other
> places to try to stay below the 80-character limit. I was assuming this
> issue was for the same reason. Perhaps not.
no, these are intentional eolns so that tex output is readable by
human eyes.
pavel
On Wed, May 26, 2010 at 11:08:35AM +0200, Enrico Forestieri wrote:
> On Sun, May 23, 2010 at 02:35:55PM +0200, uwesto...@lyx.org wrote:
> > Author: uwestoehr
> > Date: Sun May 23 14:35:54 2010
> > New Revision: 34466
> > URL: http://www.lyx.org/trac/changeset/34466
> >
> > Log:
> > IEEEtran.layout
On Sun, May 23, 2010 at 02:35:55PM +0200, uwesto...@lyx.org wrote:
> Author: uwestoehr
> Date: Sun May 23 14:35:54 2010
> New Revision: 34466
> URL: http://www.lyx.org/trac/changeset/34466
>
> Log:
> IEEEtran.layout: revised for IEEEtran 1.7a (backport from trunk)
This commit should be either rev
27 matches
Mail list logo
