On Mon, Jun 25, 2012 at 11:22 PM, Pavel Sanda wrote:
> can bring http://wiki.lyx.org/LyX/LyXOnUbuntu to more up-to-date
> status?
>
I did a revamp of the wiki page. Could someone approve the new links
(or send me privately the password for doing so)?
Liviu
On Mon, Jun 25, 2012 at 11:22 PM, Pavel Sanda wrote:
> Liviu Andronic wrote:
>> Ubuntu binaries are available on the PPA [1].
>> [1] https://launchpad.net/~lyx-devel/+archive/release
>
> I guess there is no sense to upload these on ftp, but maybe you
>
No, that wouldn't be sensible, I think.
> c
Liviu Andronic wrote:
> Ubuntu binaries are available on the PPA [1].
> [1] https://launchpad.net/~lyx-devel/+archive/release
I guess there is no sense to upload these on ftp, but maybe you
can bring http://wiki.lyx.org/LyX/LyXOnUbuntu to more up-to-date
status?
Pavel
Richard Heck wrote:
> With git, it no longer seems necessary to close branch to do a release. I
> propose in future to do the following, starting with 2.0.5:
>
> 1. At release time, create a 2.0.5 branch, where any additional work that
> might need to be done can be done.
> 2. Change configure.ac
On Mon, Jun 25, 2012 at 3:35 PM, Richard Heck wrote:
>
> I have put source tarballs, etc, here:
> http://frege.brown.edu/lyx/
> Please check compilation on your platform. Packagers should prepare
> binaries.
>
Ubuntu binaries are available on the PPA [1].
[1] https://launchpad.net/~lyx-devel/+a
No I didn't, I installed it from Chakra Linux and Kubuntu with the same
result in both cases.
Could you explain me what can I do to give you a more useful information?
On Mon, Jun 25, 2012 at 5:31 PM, LyX Ticket Tracker wrote:
> #8221: Every time that I compile a document Lyx crash.
> ---
Uwe Stöhr wrote:
> Am 23.06.2012 04:49, schrieb Pavel Sanda:
>
>> What about using structure where these two list are joined via coupled
>> entries?
>
> This is less easy to implement. We could skip the cases where language and
> coded language is the same, but I don't know if this is worth it.
On 06/25/2012 12:32 PM, Vincent van Ravesteijn wrote:
Op 25-6-2012 18:27, Richard Heck schreef:
On 06/25/2012 12:10 PM, Vincent van Ravesteijn wrote:
Op 25-6-2012 17:36, Richard Heck schreef:
With git, it no longer seems necessary to close branch to do a
release. I propose in future to do th
Op 25-6-2012 18:27, Richard Heck schreef:
On 06/25/2012 12:10 PM, Vincent van Ravesteijn wrote:
Op 25-6-2012 17:36, Richard Heck schreef:
With git, it no longer seems necessary to close branch to do a
release. I propose in future to do the following, starting with 2.0.5:
1. At release time,
On 06/25/2012 12:10 PM, Vincent van Ravesteijn wrote:
Op 25-6-2012 17:36, Richard Heck schreef:
With git, it no longer seems necessary to close branch to do a
release. I propose in future to do the following, starting with 2.0.5:
1. At release time, create a 2.0.5 branch, where any additiona
Op 25-6-2012 17:36, Richard Heck schreef:
With git, it no longer seems necessary to close branch to do a
release. I propose in future to do the following, starting with 2.0.5:
1. At release time, create a 2.0.5 branch, where any additional work
that might need to be done can be done.
2. Cha
Le 25/06/2012 17:36, Richard Heck a écrit :
With git, it no longer seems necessary to close branch to do a release.
I propose in future to do the following, starting with 2.0.5:
1. At release time, create a 2.0.5 branch, where any additional work
that might need to be done can be done.
2. Chang
With git, it no longer seems necessary to close branch to do a release.
I propose in future to do the following, starting with 2.0.5:
1. At release time, create a 2.0.5 branch, where any additional work
that might need to be done can be done.
2. Change configure.ac to 2.0.6dev, so work can c
Am Montag, 25. Juni 2012 um 14:29:27, schrieb Richard Heck
> The branch, 2.0.x, has been updated.
>
> - Log -
>
> commit 1a855429c4b2e9fd1ab894d6b3782ab8b54e0e66
> Author: Richard Heck
> Date: Mon Jun 25 08:29:04 2012 -0400
>
>
On 06/25/2012 10:15 AM, Pavel Sanda wrote:
rgh...@lyx.org wrote:
Author: rgheck
Date: Mon Jun 25 16:08:38 2012
New Revision: 40931
URL: http://www.lyx.org/trac/changeset/40931
Log:
* i18n.inc: update stats
Modified:
www-user/trunk/farm/cookbook/LyX/i18n.inc
Modified: www-user/trunk/farm/c
Richard Heck wrote:
> commit 5d9fb0d933436ca4db98ba45094e8675c584835c
> Author: Richard Heck
> Date: Mon Jun 25 10:09:26 2012 -0400
>
> Protect postats.py script from silly errors.
>
> diff --git a/po/postats.py b/po/postats.py
> index ca4787c..65be90e 100755
> --- a/po/postats.py
> +++ b/
2012/6/25 Richard Heck :
>
> I have put source tarballs, etc, here:
> http://frege.brown.edu/lyx/
> Please check compilation on your platform. Packagers should prepare
> binaries.
Complies and installs fine on openSuse 11.2 (i686) with Qt 4.8.2.
Jürgen
> Richard
>
rgh...@lyx.org wrote:
> Author: rgheck
> Date: Mon Jun 25 16:08:38 2012
> New Revision: 40931
> URL: http://www.lyx.org/trac/changeset/40931
>
> Log:
> * i18n.inc: update stats
>
> Modified:
>www-user/trunk/farm/cookbook/LyX/i18n.inc
>
> Modified: www-user/trunk/farm/cookbook/LyX/i18n.inc
>
Richard Heck wrote:
>
> I have put source tarballs, etc, here:
> http://frege.brown.edu/lyx/
> Please check compilation on your platform. Packagers should prepare
> binaries.
Compiles and runs on gentoo x86. P
On 06/25/2012 09:50 AM, Jürgen Spitzmüller wrote:
2012/6/25:
Author: rgheck
Date: Mon Jun 25 14:29:13 2012
New Revision: 40930
URL: http://www.lyx.org/trac/changeset/40930
Log:
* i18n.inc: update stats
Modified:
www-user/trunk/farm/cookbook/LyX/i18n.inc
Modified: www-user/trunk/farm/cookbo
2012/6/25 :
> Author: rgheck
> Date: Mon Jun 25 14:29:13 2012
> New Revision: 40930
> URL: http://www.lyx.org/trac/changeset/40930
>
> Log:
> * i18n.inc: update stats
>
> Modified:
> www-user/trunk/farm/cookbook/LyX/i18n.inc
>
> Modified: www-user/trunk/farm/cookbook/LyX/i18n.inc
> =
I have put source tarballs, etc, here:
http://frege.brown.edu/lyx/
Please check compilation on your platform. Packagers should prepare
binaries.
Richard
Hello
Thanks for your reply, and sorry for my late reaction!
I'm now running Lyx 2.0.3 on a Mac (10.6.8) but I've been hiding the
toolbars and thet have been coming back for as long as I've been
using Lyx (a couple of years now).
They do not come back systematically every time, only once in a wh
Preparing 2.0.4
Le 22/06/2012 09:30, Pavel Sanda a écrit :
Now with git this is even absurd since you split logical changes from
one commit into two and the hash does not point to the actual changes
which one is interested in when looking into history.
So I propose to drop the whole idea of adding commit hashes
2012/6/25 Vincent van Ravesteijn :
> This extra '\n' seems to have been a side-effect of d7eaaba9 (Juergen
> Spitzmueller, "support for CJK font argument"; Jun 5 2008).
>
> Shouldn't we fix this in BufferParams instead ?
Yep. The extra linebreak slipped in unintentionally.
Jürgen
> Vincent
Op 24-6-2012 18:24, Uwe Stöhr schreef:
The branch, master, has been updated.
- Log -
commit 66e3ac003fce5f95f92bac769977d13ae4bcb57e
Author: Uwe Stöhr
Date: Sun Jun 24 18:24:28 2012 +0200
fix bug #8210
we need to s
Op 24-6-2012 18:24, Uwe Stöhr schreef:
The branch, master, has been updated.
- Log -
commit 66e3ac003fce5f95f92bac769977d13ae4bcb57e
Author: Uwe Stöhr
Date: Sun Jun 24 18:24:28 2012 +0200
fix bug #8210
we need to s
Op 24-6-2012 15:29, Uwe Stöhr schreef:
The branch, master, has been updated.
- Log -
commit e1b181ddd42742f8762fd216d51ecc8899533629
Author: Uwe Stöhr
Date: Sun Jun 24 15:29:32 2012 +0200
update tex2lyx header format rea
Op 24-6-2012 6:38, Uwe Stöhr schreef:
commit a3f4f2d1e3c2c9cb6907859a72e9e7e0592fbdc8
Author: Uwe Stöhr
Date: Sun Jun 24 06:38:33 2012 +0200
CJK support for tex2lyx
- support as best as possible; setting a document language is however not
possible
Could you please indicate wha
30 matches
Mail list logo
