Le 29 nov. 08 à 01:27, Uwe Stöhr a écrit :
http://www.lyx.org/trac/changeset/27719 breaks every document that
uses comments and/or greyed out notes.
This is a regression to LyX 1.6.0 so I reverted it for now in trunk
and branch.
Fair enough, although discussion about the scope of the
Hi,
I'm currently using Mercurial (hg) for working on some build scripts
because I don't know where I should put them in the SVN tree.
Could someone point me to a good place in the SVN tree? I'd rather not
put them in lyx-devel at the moment as that tree is just too big.
For me a simple
Uwe Stöhr wrote:
can I backport this change to branch?:
http://www.lyx.org/trac/changeset/27737
This layout is available since 2 months
http://wiki.lyx.org/Layouts/Achemso
and the user I created this layout for could successfully use it for his
paper.
OK, go ahead.
Jürgen
Vincent van Ravesteijn wrote:
Sorry,
this is about bug 5472 in stead of 5072...
http://bugzilla.lyx.org/show_bug.cgi?id=5472.
Please backport this.
Jürgen
Hi,
I can repeatedly reproduce the following on one machine:
* Start freshly build LyX 1.6.1svn
* 'C-o' (open-file)
* Enter directory 'private' (by double clicking on it)
* Enter subdirectory 'jobb' (by double clicking on it)
LyX now crashes with this message:
LyX: Done!
Fair enough, although discussion about the scope of the problem would be
easier if you avoided
broad generalizations like breaks _every_ document that
I can understand that _some_ greyed out notes are broken, but why are
comments broken?
But _every_ is correct. Every document that
On Sat, Nov 29, 2008 at 03:17:23PM +0100, Uwe Stöhr wrote:
Fair enough, although discussion about the scope of the problem would be
easier if you avoided
broad generalizations like breaks _every_ document that
I can understand that _some_ greyed out notes are broken, but why are
On Sat, 29 Nov 2008, Christian Ridderström wrote:
I can repeatedly reproduce the following on one machine:
* Start freshly build LyX 1.6.1svn
* 'C-o' (open-file)
* Enter directory 'private' (by double clicking on it)
* Enter subdirectory 'jobb' (by double clicking on it)
LyX now crashes with
Martin Vermeer schrieb:
...and reverting is rather a blunt instrument when you could have fixed
bool producesOutput() const { return false; }
in InsetNote.h -- in the sense that yes, in some cases a Note _does_ produce
LaTeX output ;-)
This change caused a nasty regression, and we
Srijit Kumar Bhadra schrieb:
I installed LyX-160-4-14-AltInstaller-Small.exe today. When I give View
DVI command for EmbeddedObjects.lyx (Help - Embedded Objects), I get
the error message as shown in the attached file.
This problem should be fixed in the new version 4.15 I released today:
[EMAIL PROTECTED] schreef:
Author: vfr
Date: Sat Nov 29 18:29:13 2008
New Revision: 27744
URL: http://www.lyx.org/trac/changeset/27744
Log:
Fix bug 5507: Full screen hangs LyX when no file is opened
http://bugzilla.lyx.org/show_bug.cgi?id=5507
Modified:
Vincent van Ravesteijn wrote:
Also in branch ?
yes, please.
Jürgen
On Friday 28 November 2008 06:44:40 Martin Vermeer wrote:
Still, failure to import seems like too harsh a punishment... lyx2lyx
should handle this gracefully. Is that feasible?
For messing with the encoding? :-)
Yes, we could but that would imply data loss, not something I am keen on
Christian Ridderström wrote:
Hi,
I'm currently using Mercurial (hg) for working on some build scripts
because I don't know where I should put them in the SVN tree.
Could someone point me to a good place in the SVN tree? I'd rather not
put them in lyx-devel at the moment as that tree is
Martin Vermeer wrote:
On Sat, Nov 29, 2008 at 03:17:23PM +0100, Uwe Stöhr wrote:
Fair enough, although discussion about the scope of the problem would be
easier if you avoided
broad generalizations like breaks _every_ document that
I can understand that _some_ greyed out
...and reverting is rather a blunt instrument when you could have
fixed
bool producesOutput() const { return false; }
in InsetNote.h -- in the sense that yes, in some cases a Note
_does_ produce
LaTeX output ;-)
I suppose this is Richard's turf.
No, this isn't anything I know
I can understand that _some_ greyed out notes are broken, but why
are comments broken?
But _every_ is correct. Every document that contains greyed-out
cannot be compiled because your change omitted the needed preamble
code. For an unknown reason I then get also error messages that the
Le 29 nov. 08 à 01:27, Uwe Stöhr a écrit :
http://www.lyx.org/trac/changeset/27719 breaks every document that
uses comments and/or greyed out notes.
This is a regression to LyX 1.6.0 so I reverted it for now in trunk
and branch.
Fair enough, although discussion about the scope of the
Hi,
I'm currently using Mercurial (hg) for working on some build scripts
because I don't know where I should put them in the SVN tree.
Could someone point me to a good place in the SVN tree? I'd rather not
put them in lyx-devel at the moment as that tree is just too big.
For me a simple
Uwe Stöhr wrote:
> can I backport this change to branch?:
> http://www.lyx.org/trac/changeset/27737
>
> This layout is available since 2 months
> http://wiki.lyx.org/Layouts/Achemso
> and the user I created this layout for could successfully use it for his
> paper.
OK, go ahead.
Jürgen
Vincent van Ravesteijn wrote:
> Sorry,
>
> this is about bug 5472 in stead of 5072...
>
> http://bugzilla.lyx.org/show_bug.cgi?id=5472.
Please backport this.
Jürgen
Hi,
I can repeatedly reproduce the following on one machine:
* Start freshly build LyX 1.6.1svn
* 'C-o' (open-file)
* Enter directory 'private' (by double clicking on it)
* Enter subdirectory 'jobb' (by double clicking on it)
LyX now crashes with this message:
LyX: Done!
> Fair enough, although discussion about the scope of the problem would be
easier if you avoided
> broad generalizations like "breaks _every_ document that...".
>
> I can understand that _some_ greyed out notes are broken, but why are
comments broken?
But _every_ is correct. Every document
On Sat, Nov 29, 2008 at 03:17:23PM +0100, Uwe Stöhr wrote:
> > Fair enough, although discussion about the scope of the problem would be
> easier if you avoided
> > broad generalizations like "breaks _every_ document that...".
> >
> > I can understand that _some_ greyed out notes are broken, but
On Sat, 29 Nov 2008, Christian Ridderström wrote:
I can repeatedly reproduce the following on one machine:
* Start freshly build LyX 1.6.1svn
* 'C-o' (open-file)
* Enter directory 'private' (by double clicking on it)
* Enter subdirectory 'jobb' (by double clicking on it)
LyX now crashes with
Martin Vermeer schrieb:
...and reverting is rather a blunt instrument when you could have fixed
bool producesOutput() const { return false; }
in InsetNote.h -- in the sense that yes, in some cases a Note _does_ produce
LaTeX output ;-)
This change caused a nasty regression, and we
Srijit Kumar Bhadra schrieb:
I installed LyX-160-4-14-AltInstaller-Small.exe today. When I give View
DVI command for EmbeddedObjects.lyx (Help -> Embedded Objects), I get
the error message as shown in the attached file.
This problem should be fixed in the new version 4.15 I released today:
[EMAIL PROTECTED] schreef:
Author: vfr
Date: Sat Nov 29 18:29:13 2008
New Revision: 27744
URL: http://www.lyx.org/trac/changeset/27744
Log:
Fix bug 5507: Full screen hangs LyX when no file is opened
http://bugzilla.lyx.org/show_bug.cgi?id=5507
Modified:
Vincent van Ravesteijn wrote:
> Also in branch ?
yes, please.
Jürgen
On Friday 28 November 2008 06:44:40 Martin Vermeer wrote:
> Still, failure to import seems like too harsh a punishment... lyx2lyx
> should handle this gracefully. Is that feasible?
For messing with the encoding? :-)
Yes, we could but that would imply data loss, not something I am keen on
Christian Ridderström wrote:
Hi,
I'm currently using Mercurial (hg) for working on some build scripts
because I don't know where I should put them in the SVN tree.
Could someone point me to a good place in the SVN tree? I'd rather not
put them in lyx-devel at the moment as that tree is
Martin Vermeer wrote:
On Sat, Nov 29, 2008 at 03:17:23PM +0100, Uwe Stöhr wrote:
Fair enough, although discussion about the scope of the problem would be
easier if you avoided
broad generalizations like "breaks _every_ document that...".
I can understand that _some_ greyed out
...and reverting is rather a blunt instrument when you could have
fixed
bool producesOutput() const { return false; }
in InsetNote.h -- in the sense that yes, in some cases a Note
_does_ produce
LaTeX output ;-)
I suppose this is Richard's turf.
No, this isn't anything I know
> I can understand that _some_ greyed out notes are broken, but why
are comments broken?
But _every_ is correct. Every document that contains greyed-out
cannot be compiled because your change omitted the needed preamble
code. For an unknown reason I then get also error messages that the
34 matches
Mail list logo
