I included a php file. It had some non-ascii content. Not only comments,
it contained a webpage in Norwegian, so this can not be removed. Of
course there is a workaround - paste it into "Lyx-Code" instead. :-/
Is it possible to have LyX treat non-ascii in a listing the same way as
the non-ascii
On 2009-02-27, Jürgen Spitzmüller wrote:
> rgheck wrote:
>> OK, now I have it.
> Could you file a report with 1.6.2 target, please?
Done. http://bugzilla.lyx.org/show_bug.cgi?id=5813
> This looks like the
> emergency save might get affected, so there's even dataloss potential.
Confirmed this.
Jürgen Spitzmüller wrote:
rgheck wrote:
OK, now I have it.
Could you file a report with 1.6.2 target, please? This looks like the
emergency save might get affected, so there's even dataloss potential.
It's definitely affected.
I think we'll need to fix this for 1.6.2. Another r
rgheck wrote:
> OK, now I have it.
Could you file a report with 1.6.2 target, please? This looks like the
emergency save might get affected, so there's even dataloss potential.
I think we'll need to fix this for 1.6.2. Another reason for delaying the
release a bit.
Jürgen
Vincent van Ravesteijn - TNW wrote:
As Guenter mentioned, he has a master with childs. Doing a cut and paste
in a child document does crash LyX 1.6.1. I have no current branch or
svn to test with.
OK, now I have it. Note that you get an infinite loop through
emergencyWriteAll() when this
er throwing an
>>> instance of 'lyx::support::ExceptionMessage'
>>> what(): Inset::buffer_ member not initialized!
>>> LyX Code: 36 name: Branch
>>>
>>> in ~/.xsession-errors.
>>>
>>> I use LyX 1.6.1 on Debian with a set
Vincent van Ravesteijn - TNW wrote:
> Confirmed.
The assert or the fix?
Jürgen
ssage'
what(): Inset::buffer_ member not initialized!
LyX Code: 36 name: Branch
in ~/.xsession-errors.
I use LyX 1.6.1 on Debian with a set of documents organised as
master with childs for each chapter (there are some branch
oddities in this setup but this might be unrelated).
Is this a
at(): Inset::buffer_ member not initialized!
>LyX Code: 36 name: Branch
>
>in ~/.xsession-errors.
>
>I use LyX 1.6.1 on Debian with a set of documents organised as
>master with childs for each chapter (there are some branch
>oddities in this setup but this might be unrelated).
&
Vincent van Ravesteijn - TNW wrote:
> I think this must be solved before releasing 1.6.2.
Any input is highly appreciated. There is some ongoing discussion about the
correct approach between Jean-Marc and myself. I have posted a tentative patch
that will probably solve all these issues (but is o
> > > D:\LyX\lyx-1.6.1\src\CoordCache.cpp(39): break on pointer: 02B6A408
> > > hint: x size: 8
> > > D:\LyX\lyx-1.6.1\src\support\lassert.cpp(21): ASSERTION false
> > > VIOLATED IN D:\LyX\lyx-1.6.1\src\CoordCache.cpp:40
> > > Completed
> &g
raf...@o2.pl schreef:
Todays sequence of bugs:
D:\LyX\lyx-1.6.1\src\support\filetools.cpp(328): LyX could not create temporary
directory in C:/Documents and Settings/Administrator.NIGDZIE-NIGDZIE/Ustawienia
lokalne/Temp'
Warning: Disk Error:
Todays sequence of bugs:
D:\LyX\lyx-1.6.1\src\support\filetools.cpp(328): LyX could not create temporary
directory in C:/Documents and Settings/Administrator.NIGDZIE-NIGDZIE/Ustawienia
lokalne/Temp'
Warning: Disk Error:
LyX could not creat
Uwe Stöhr wrote:
> > I just tried to use beamer. I checked pdf properties/use hyperref
> > support
> > and selected no other options. I get:
> >
> > ! Undefined control sequence.
> > l.10 \hypersetup
> >{unicode=true, pdfusetitle,
>
> I cannot reproduce this. Do you have
> I just tried to use beamer. I checked pdf properties/use hyperref support
> and selected no other options. I get:
>
> ! Undefined control sequence.
> l.10 \hypersetup
>{unicode=true, pdfusetitle,
I cannot reproduce this. Do you have a _small_ example file?
Beamer automatically
I just tried to use beamer. I checked pdf properties/use hyperref support
and selected no other options. I get:
! Undefined control sequence.
l.10 \hypersetup
{unicode=true, pdfusetitle,
Stefan Schimanski writes:
>> I think that \global\newcommand works in any case.
>
> It does? I think I tried and it did not.
I might be wrong. I cannot find reference to that right now.
> A second requirement: the distinction between \newcommand and
> \renewcommand is very fragile. It is far fro
Am 07.01.2009 um 22:45 schrieb Jean-Marc Lasgouttes:
xargs is only needed if you have macros with optional arguments. Of
course, \newcommand could handle the case with one optional. But,
what we need in fact is something equivalent to \global\def for
this case. Is there a way to do this wi
Am 07.01.2009 um 22:45 schrieb Jean-Marc Lasgouttes:
xargs is only needed if you have macros with optional arguments. Of
course, \newcommand could handle the case with one optional. But,
what we need in fact is something equivalent to \global\def for
this case. Is there a way to do this wi
xargs is only needed if you have macros with optional arguments. Of
course, \newcommand could handle the case with one optional. But,
what we need in fact is something equivalent to \global\def for
this case. Is there a way to do this with \newcommand?
Why \global?
I think that \global\new
Am 07.01.2009 um 10:59 schrieb Jean-Marc Lasgouttes:
[cc:ing to lyx-devel]
"James C. Sutherland" writes:
Okay, I think that I found the problem: I am missing the "xargs"
package. The exported LaTeX file actually had a line:
\usepackage{xargs}[2008/03/08]
which I discarded. This is
[cc:ing to lyx-devel]
"James C. Sutherland" writes:
> Okay, I think that I found the problem: I am missing the "xargs"
> package. The exported LaTeX file actually had a line:
> \usepackage{xargs}[2008/03/08]
> which I discarded. This is presumably where the "\newcommandx" tag is
> define
Dear all,
I've just built LyX 1.6.1 on my system, and wanted to thank for the
devel's efforts. Per all the application does not feel that different
from the 1.5.x series, however it feels much more usable. And beamer
documents compile, so I'm happy.
Happy holidays,
Liviu
PS Only a
Hello LyXers,
I forgot to announce the alternative Windows installer for LyX 1.6.1, that is available since a few
days.
This installer comes again with an update installer to update existing LyX 1.6.0 installation to LyX
1.6.1. NOTE: To be able to use this installer version, LyX 1.6.0 must
Hi
I guess I'm not the first one who reports this, but Lyx 1.6.1 on Windows
(XP) seems to be unable to convert EMFs. It worked in 1.6.0 but now it
does not anymore. They are visible in the Output but only as a
rasterized picture, not as a vector graphic.
Greetings
Stefan
Joost Verburg wrote:
> I've uploaded Windows installers to http://www.lyx.org/~joost/
I've put them on the server now.
Jürgen
On Thu, 18 Dec 2008, Stephan Witt wrote:
Christian Ridderström schrieb:
Hi,
Should there be a TAG for LyX 1.6.1 in the repository? I just looked and
couldn't see one.
http://www.lyx.org/trac/browser/lyx-devel/tags
/Christian
Hi Christian,
I can see one: lyx-1_6_1 (5 day
Christian Ridderström schrieb:
Hi,
Should there be a TAG for LyX 1.6.1 in the repository? I just looked and
couldn't see one.
http://www.lyx.org/trac/browser/lyx-devel/tags
/Christian
Hi Christian,
I can see one: lyx-1_6_1 (5 days old)
Are you looking for another one?
Re
Hi,
Should there be a TAG for LyX 1.6.1 in the repository? I just looked and
couldn't see one.
http://www.lyx.org/trac/browser/lyx-devel/tags
/Christian
On Tue, 16 Dec 2008, Joost Verburg wrote:
Jürgen Spitzmüller wrote:
Prebuilt binaries (rpms for Linux distributions, Mac
Jürgen Spitzmüller wrote:
Prebuilt binaries (rpms for Linux distributions, Mac OS X and Windows
installers) should soon be available at
ftp://ftp.lyx.org/pub/lyx/bin/1.6.1/
I've uploaded Windows installers to http://www.lyx.org/~joost/
Regards, Joost
Enrico Forestieri wrote:
> I think that it will suffice changing "Some alternative installers can be
> found here:" to "Some alternative installers and a Cygwin binary can be
> found here:" on that page.
done.
Jürgen
On Tue, Dec 16, 2008 at 08:06:43AM +0100, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > J�rgen, you can find a cygwin binary here:
> > http://www.lyx.org/~forenr/lyx-1.6.1-cygwin.tar.gz
>
> Thanks, Enrico. It's on the server.
>
> BTW I noticed that th
Enrico Forestieri wrote:
> Jürgen, you can find a cygwin binary here:
> http://www.lyx.org/~forenr/lyx-1.6.1-cygwin.tar.gz
Thanks, Enrico. It's on the server.
BTW I noticed that the cygwin binary is not mentioned on our Download page.
Shouldn't it?
Jürgen
On Mon, Dec 15, 2008 at 08:06:26AM +0100, Jürgen Spitzmüller wrote:
> Public release of LyX version 1.6.1
> ===
Jürgen, you can find a cygwin binary here:
http://www.lyx.org/~forenr/lyx-1.6.1-cygwin.tar.gz
--
Enrico
Public release of LyX version 1.6.1
===
We are pleased to announce the release of LyX 1.6.1. This is the first
maintenance release in the brand-new 1.6.x series, and as such, it mainly
focuses on bug fixes. We have ironed out some major problems that slipped
into
On Sun, Dec 14, 2008 at 4:34 AM, Jürgen Spitzmüller
wrote:
> Bennett Helm wrote:
>> I've put the Mac binary here:
>>
>> http://edisk.fandm.edu/bennett.helm/LyX/LyX-1.6.1-Mac-Universal.dmg
>>
>> Can someone place them on the server, please?
>
> Man
Bennett Helm wrote:
> I've put the Mac binary here:
>
> http://edisk.fandm.edu/bennett.helm/LyX/LyX-1.6.1-Mac-Universal.dmg
>
> Can someone place them on the server, please?
Many thanks, Bennett.
I put the binary on the server and adapted the download page.
Jürgen
Jürgen Spitzmüller schreef:
I have uploaded the tarballs to the server. I will send the announcement on
monday, so there's still some time to prepare binaries.
Jürgen
It's a pity, the scrolling isn't fixed. I'm sometimes experiencing quite
some difficulties and I was halfway the solution.
On Sat, Dec 13, 2008 at 8:23 AM, Jürgen Spitzmüller
wrote:
> I have uploaded the tarballs to the server. I will send the announcement on
> monday, so there's still some time to prepare binaries.
I've put the Mac binary here:
http://edisk.fandm.edu/bennett.helm/LyX/LyX-1.6.1-M
ck had a bug with handling PostScript files,
> so I'm forced to use the IM version released yesterday in which this is
> fixed, not the IM version that is set in the installers files that are in
> the LyX 1.6.1 tarball.
OK (as long as only external applications are involved.)
Jürgen
o I'm forced to use the
IM version released yesterday in which this is fixed, not the IM version that is set in the
installers files that are in the LyX 1.6.1 tarball.
regards Uwe
Konrad Hofbauer wrote:
> I assume you have a good overview on which bugs/crashes could be fixed,
> and which not. Would you call LyX 1.6.1 ready for real work (by
> non-experts) on Windows?
I don't use Windows, but I assume so, yes. We have fixed a bunch of Windows-
only crashes.
Jürgen Spitzmüller wrote:
I have uploaded the tarballs to the server. I will send the announcement on
monday, so there's still some time to prepare binaries.
I assume you have a good overview on which bugs/crashes could be fixed,
and which not. Would you call LyX 1.6.1 ready for real wor
Uwe Stöhr wrote:
> status16x reads:
>
> - Updated English, French, German, and Spanish User's Guide, Math,
> and Embedded Objects manual.
> - Updated English and German Embedded Objects manual.
>
> So the latter should be deleted.
too late.
Jürgen
status16x reads:
- Updated English, French, German, and Spanish User's Guide, Math,
and Embedded Objects manual.
- Updated English and German Embedded Objects manual.
So the latter should be deleted.
regards Uwe
I have uploaded the tarballs to the server. I will send the announcement on
monday, so there's still some time to prepare binaries.
Jürgen
Jürgen Spitzmüller wrote:
> 4346 cri Synchronizing insets asserts when two windows open
> => Cannot reproduce this any longer
still perfectly reproducible in trunk. in 1.6 its not triggered because
assertions
are handled differently for release mode?
pavel
> The most urgent ones are these
There's another very nasty one:
http://bugzilla.lyx.org/show_bug.cgi?id=5604
regards Uwe
Abdelrazak Younes wrote:
> I think there's enough bug fixes to justify a release now. I would most
> probably be able to fix some of the cited bugs, if only I had the
> time... IOW don't count on me in the coming weeks, sorry.
Fair enough.
Jürgen
, any effort to further
debug or even fix these issues is most welcome.
Since we have already fixed a range of major and critical issues, I propose to
release LyX 1.6.1 in about one week notwithstanding the status of the
mentioned bugs.
I think there's enough bug fixes to justify a re
Richard Heck wrote:
> For what it's worth, I've seen some crashes recently myself but have
> been unable to reproduce them. These have all happened when working on a
> book with lots of child documents that all have the Default Master
> Document set. I'm hopeful that your recent fix for the "dirty"
issues is most welcome.
Since we have already fixed a range of major and critical issues, I propose to
release LyX 1.6.1 in about one week notwithstanding the status of the
mentioned bugs.
Thoughts?
Jürgen
usual, any effort to further
debug or even fix these issues is most welcome.
Since we have already fixed a range of major and critical issues, I propose to
release LyX 1.6.1 in about one week notwithstanding the status of the
mentioned bugs.
Thoughts?
Jürgen
Stephan Witt wrote:
I had the ok from Stefan Schimanski for trunk. To test the feature I
have to
understand how to use link back on Mac. Does anyone know how to use it?
Stefan Schimanski does.
There is some info here
http://article.gmane.org/gmane.editors.lyx.devel/100819
This is how it w
Jürgen Spitzmüller schrieb:
Stephan Witt wrote:
Ok, I'll apply rcs.txt this evening. And yes it fixes an aspect of bug 5389
only. Maybe an unrelated issue in fact. The first from_utf8 in patch is
obvious as the input value provided by the caller is from LyX and utf8
coded. The second is only sli
Stephan Witt wrote:
> Ok, I'll apply rcs.txt this evening. And yes it fixes an aspect of bug 5389
> only. Maybe an unrelated issue in fact. The first from_utf8 in patch is
> obvious as the input value provided by the caller is from LyX and utf8
> coded. The second is only slightly better then from_
Jürgen Spitzmüller schrieb:
Stephan Witt wrote:
My personal patch list is as follows:
* rcs.txt - Addresses bug 5389
* mathed.txt- Fix some compiler warnings
* paragraph.txt - Fix a compiler warning
At least rcs.txt fixes a major bug (crash in from_ascii()).
I suggest to apply it to t
Stephan Witt wrote:
> My personal patch list is as follows:
> * rcs.txt - Addresses bug 5389
> * mathed.txt - Fix some compiler warnings
> * paragraph.txt - Fix a compiler warning
>
> At least rcs.txt fixes a major bug (crash in from_ascii()).
> I suggest to apply it to trunk and branch.
>
Jürgen Spitzmüller schrieb:
We should not wait too long with 1.6.1, since 1.6.0 has introduced some major
issues (as expected). In general, I'd like to concentrate on ironing out the
critical and major bugs (quite some work has already been done) and make 1.6.1
a bugfix-release only.
My perso
Richard Heck wrote:
> OK, as a first step, any comments on the attached cleanup?
It looks good to me, but I'd like to hear a second voice, just in case I've
overlooked something.
Jürgen
Vincent van Ravesteijn - TNW wrote:
5472, although still "unconfirmed" is at least seen
by 4 users(*). Thanks to Jean-Marc Lasgouttes, I have
provided a way to reproduce it (cf. comment 11 of the
bug, at the referred user ML thread).
At last, I can confirm this too. I had to switch to some ol
> 5472, although still "unconfirmed" is at least seen
> by 4 users(*). Thanks to Jean-Marc Lasgouttes, I have
> provided a way to reproduce it (cf. comment 11 of the
> bug, at the referred user ML thread).
At last, I can confirm this too. I had to switch to some older PC to get
the crash.
Olivi
Jürgen Spitzmüller wrote:
rgheck wrote:
We basically need just to decide what to do here. This happens only when
the child is corrupt or for some other reason not openable. Probably we
should just mark it that way and ignore it henceforth, yes?
Yes. Issue a warning and skip this file.
On Friday 21 November 2008 13:05:45 Jürgen Spitzmüller wrote:
> Finally, I'm not sure I completely parsed all Berlin activity. So please
> let me know if there are outstanding fixes that need to/could be
> backported.
First I should note that the development at a meeting happens in a
decentralize
Jürgen Spitzmüller wrote:
We should not wait too long with 1.6.1, since 1.6.0 has introduced some major
issues (as expected). In general, I'd like to concentrate on ironing out the
critical and major bugs (quite some work has already been done) and make 1.6.1
a bugfix-release only.
Below a li
Vincent van Ravesteijn - TNW wrote:
> I actually already asked you about this one :
Bear with me. I'm getting old.
> When the cursor is not visible on screen (probably caused by scrolling),
> the location where the cursor should be painted is set to (-1,-1). However,
> the cursor is painted anywa
>> Less important fixes:
>>
>> - Changeset 27631
>> http://www.lyx.org/trac/changeset/27631
>> Do not paint an invisible cursor.
>
>could you explain why this is needed/what it does?
>
I actually already asked you about this one :
When the cursor is not visible on screen (probably caused b
Vincent van Ravesteijn - TNW wrote:
> Must-fixes:
>
> - Changeset 27632: Fix tabular cursor movement
> http://www.lyx.org/trac/changeset/27632
OK.
> This solves a regression ('slik') caused by r27581
> and a few other must-fixes.
>
> - Changeset 27626: Fix bug #5536.
> http://www.lyx.org/
rgheck wrote:
> We basically need just to decide what to do here. This happens only when
> the child is corrupt or for some other reason not openable. Probably we
> should just mark it that way and ignore it henceforth, yes?
Yes. Issue a warning and skip this file.
Jürgen
Jürgen Spitzmüller wrote:
We should not wait too long with 1.6.1, since 1.6.0 has introduced some major
issues (as expected). In general, I'd like to concentrate on ironing out the
critical and major bugs (quite some work has already been done) and make 1.6.1
a bugfix-release only.
Below a li
> We should not wait too long with 1.6.1, since 1.6.0 has
> introduced some major issues (as expected). In general,
> I'd like to concentrate on ironing out the critical and
> major bugs (quite some work has already been done) and
> make 1.6.1 a bugfix-release only.
I would like to backport the
We should not wait too long with 1.6.1, since 1.6.0 has introduced some major
issues (as expected). In general, I'd like to concentrate on ironing out the
critical and major bugs (quite some work has already been done) and make 1.6.1
a bugfix-release only.
Below a list of bugs that should be ad
72 matches
Mail list logo
