Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended. Actually, this is also the
way it works on my side
Op 7-5-2012 13:55, Vincent van Ravesteijn schreef:
Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended
Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended. Actually, this is also the
way it works on my side
Everytime I start up LyX 2.0.3 a "luatex.exe" process takes quite some
time before LyX appears on the screen.
This is caused by checkLuatex in configure.py. I think it is not
necessary to check for luatex every time LyX is started, but just once
when we reconfigure LyX.
Vincent
Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended. Actually, this is also the
way it works on my side
Op 7-5-2012 13:55, Vincent van Ravesteijn schreef:
Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended
Op 7-5-2012 13:50, Jürgen Spitzmüller schreef:
2012/5/7 Vincent van Ravesteijn:
I think it is not necessary
to check for luatex every time LyX is started, but just once when we
reconfigure LyX.
Certainly, this is the way it is intended. Actually, this is also the
way it works on my side
Op 6-5-2012 20:13, Vincent van Ravesteijn schreef:
The branch, master, has been updated.
- Log -
commit 5279d5a8a58b9e59442b9f3f504ea397274e2b19
Author: Vincent van Ravesteijnv...@lyx.org
Date: Sun May 6 20:06:28 2012 +0200
Op 6-5-2012 20:13, Vincent van Ravesteijn schreef:
The branch, master, has been updated.
- Log -
commit 5279d5a8a58b9e59442b9f3f504ea397274e2b19
Author: Vincent van Ravesteijn<v...@lyx.org>
Date: Sun May 6 20:06:28 2012
Op 3-5-2012 16:39, Vincent van Ravesteijn schreef:
The branch, master, has been updated.
- Log -
commit 5e4e4b674c00bc546213d42258f19e13a2b28bc3
Author: Vincent van Ravesteijnv...@lyx.org
Date: Thu May 3 11:55:54 2012 +0200
Op 3-5-2012 16:40, Vincent van Ravesteijn schreef:
commit a02bfeebc534925734821e8921bac07c67af6d39
Author: Vincent van Ravesteijnv...@lyx.org
Date: Thu May 3 15:11:10 2012 +0200
configure.py: Replace 'ltx' by 'log' case insensitively
On windows the temporary filename consists
Op 3-5-2012 16:39, Vincent van Ravesteijn schreef:
The branch, master, has been updated.
- Log -
commit 5e4e4b674c00bc546213d42258f19e13a2b28bc3
Author: Vincent van Ravesteijn<v...@lyx.org>
Date: Thu May 3 11:55:54 2012
Op 3-5-2012 16:40, Vincent van Ravesteijn schreef:
commit a02bfeebc534925734821e8921bac07c67af6d39
Author: Vincent van Ravesteijn<v...@lyx.org>
Date: Thu May 3 15:11:10 2012 +0200
configure.py: Replace 'ltx' by 'log' case insensitively
On windows the temporary filename co
Op 2-5-2012 23:40, Richard Heck schreef:
commit 98a810c9d8b8d6bc0086779b7fa2d5be434bdbe2
Author: Richard Heckrgh...@lyx.org
Date: Mon Mar 19 17:33:47 2012 -0400
Fix bug #8087: Include children in plaintext export.
@@ -804,7 +805,7 @@ docstring InsetInclude::xhtml(XHTMLStream xs,
Op 2-5-2012 23:40, Richard Heck schreef:
commit 98a810c9d8b8d6bc0086779b7fa2d5be434bdbe2
Author: Richard Heck
Date: Mon Mar 19 17:33:47 2012 -0400
Fix bug #8087: Include children in plaintext export.
@@ -804,7 +805,7 @@ docstring InsetInclude::xhtml(XHTMLStream& xs,
Op 2-5-2012 9:06, Pavel Sanda schreef:
Richard, thanks for the diffs!
Do you have control over the content?
If yes I would propose two nitpicks:
a) to drop the first part which brings no interesting info and occupy space:
The branch, master has been updated
via
Op 2-5-2012 9:06, Pavel Sanda schreef:
Richard, thanks for the diffs!
Do you have control over the content?
If yes I would propose two nitpicks:
a) to drop the first part which brings no interesting info and occupy space:
The branch, master has been updated
via
Op 29-4-2012 12:08, Jürgen Spitzmüller schreef:
Author: Jürgen Spitzmüllerjspitzm@linux-np7j.(none)
Date: Sun, 29 Apr 2012 11:51:07 +0200
New Commit: 8995a8387a03361b6a7ff44b447a90a6187b1a14
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=8995a8387a03361b6a7ff44b447a90a6187b1a14
Log:
Merge
Sep 17 00:00:00 2001
From: Vincent van Ravesteijn v...@lyx.org
Date: Sun, 29 Apr 2012 14:06:21 +0200
Subject: [PATCH] Fix toggling of languages
As LFUN_LANGAUGE does no longer toggles the language, we need to disable
the current language to make a command-alternatives command work.
Example
Op 29-4-2012 12:08, Jürgen Spitzmüller schreef:
Author: Jürgen Spitzmüller
Date: Sun, 29 Apr 2012 11:51:07 +0200
New Commit: 8995a8387a03361b6a7ff44b447a90a6187b1a14
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=8995a8387a03361b6a7ff44b447a90a6187b1a14
Log:
Merge
e the attached.
Vincent
>From 0cb9d96ec07bc1078d0e100eea17caff326e4fcd Mon Sep 17 00:00:00 2001
From: Vincent van Ravesteijn <v...@lyx.org>
Date: Sun, 29 Apr 2012 14:06:21 +0200
Subject: [PATCH] Fix toggling of languages
As LFUN_LANGAUGE does no longer toggles the language, we need to disable
the current language to make a comm
Yes and also we no more have diffs in commit message which from time to time
helps in spotting such things.
Writing script which sends to cvs/devel list full diff after commit is 5 min
work.
Would other developers greet if I setup this on my box and let this message be
posted automatically
Yes and also we no more have diffs in commit message which from time to time
helps in spotting such things.
Writing script which sends to cvs/devel list full diff after commit is 5 min
work.
Would other developers greet if I setup this on my box and let this message be
posted automatically
I mean try to run LyX with new source window. The layout sometimes looks
suprisingly
different on different setups, so we have double check... P
I only see that Plain text is not working for me in the View Source pane.
Vincent
Op 24-4-2012 17:45, Richard Heck schreef:
On 04/24/2012 11:40 AM, Pavel Sanda wrote:
Vincent van Ravesteijn wrote:
I mean try to run LyX with new source window. The layout sometimes
looks
suprisingly
different on different setups, so we have double check... P
I only see that Plain text
I mean try to run LyX with new source window. The layout sometimes looks
suprisingly
different on different setups, so we have double check... P
I only see that "Plain text" is not working for me in the View Source pane.
Vincent
Op 24-4-2012 17:45, Richard Heck schreef:
On 04/24/2012 11:40 AM, Pavel Sanda wrote:
Vincent van Ravesteijn wrote:
I mean try to run LyX with new source window. The layout sometimes
looks
suprisingly
different on different setups, so we have double check... P
I only see that "Plain
../lyx/rgheck/ [features/HideChanges] git remote add vfr
g...@git.lyx.org:developers/vfr/lyx
../lyx/rgheck/ [features/HideChanges] git fetch vfr
R access for developers/vfr/lyx DENIED to rgheck
(Or there may be no repository at the given path. Did you spell it
correctly?)
fatal: The
../lyx/rgheck/ [features/HideChanges] > git remote add vfr
g...@git.lyx.org:developers/vfr/lyx
../lyx/rgheck/ [features/HideChanges] > git fetch vfr
R access for developers/vfr/lyx DENIED to rgheck
(Or there may be no repository at the given path. Did you spell it
correctly?)
fatal: The
The problem now is much more serious. Basically, the cursor position
isn't correct. When we figure out Cursor::pos(), we of course don't
consider that deleted material might not be visible. Do you have any
idea whether this is something that can be fixed without massive
potential for
Op 13-4-2012 23:50, Richard Heck schreef:
On 04/11/2012 02:49 PM, Vincent van Ravesteijn wrote:
Op 11-4-2012 20:45, Richard Heck schreef:
On 04/11/2012 02:02 PM, Vincent van Ravesteijn wrote:
Op 11-4-2012 19:56, Richard Heck schreef:
On 04/11/2012 07:39 AM, Jürgen Spitzmüller wrote:
2012/4
The problem now is much more serious. Basically, the cursor position
isn't correct. When we figure out Cursor::pos(), we of course don't
consider that deleted material might not be visible. Do you have any
idea whether this is something that can be fixed without massive
potential for
Op 13-4-2012 23:50, Richard Heck schreef:
On 04/11/2012 02:49 PM, Vincent van Ravesteijn wrote:
Op 11-4-2012 20:45, Richard Heck schreef:
On 04/11/2012 02:02 PM, Vincent van Ravesteijn wrote:
Op 11-4-2012 19:56, Richard Heck schreef:
On 04/11/2012 07:39 AM, Jürgen Spitzmüller wrote:
2012/4
Can you push it to your repo on the server, then I can have a look.
This is now in the features/HideChanges branch. Note that it's pretty
basic right now. Just a proof of concept, or an attempt at such.
Richard
If I wouldn't have replied so fast, I would have said that you don't
need to
This is now in the features/HideChanges branch. Note that it's pretty
basic right now. Just a proof of concept, or an attempt at such.
Richard
Are you sure it is there ?
Vincent
Can you push it to your repo on the server, then I can have a look.
This is now in the features/HideChanges branch. Note that it's pretty
basic right now. Just a proof of concept, or an attempt at such.
Richard
If I wouldn't have replied so fast, I would have said that you don't
need to
This is now in the features/HideChanges branch. Note that it's pretty
basic right now. Just a proof of concept, or an attempt at such.
Richard
Are you sure it is there ?
Vincent
Op 8-4-2012 21:55, Vincent van Ravesteijn schreef:
Op 8-4-2012 21:51, v...@lyx.org schreef:
Author: Vincent van Ravesteijnv...@lyx.org
Date: Sun, 08 Apr 2012 21:47:40 +0200
New Commit: 91bc04946fafbee92dda4bd17edfa007f615fe5d
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h
Op 8-4-2012 23:22, v...@lyx.org schreef:
Author: Vincent van Ravesteijnv...@lyx.org
Date: Sun, 08 Apr 2012 23:20:01 +0200
New Commit: f0754582b8af481dc636c6d31eb3a52c853d7db0
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=f0754582b8af481dc636c6d31eb3a52c853d7db0
Log:
Fix bug #8114: LyX does not
Op 11-4-2012 19:56, Richard Heck schreef:
On 04/11/2012 07:39 AM, Jürgen Spitzmüller wrote:
2012/4/11 Richard Heck:
We really should fix this, and it shouldn't be that hard. It's often
requested. Can someone please file a bug about it? Check first to
make sure
there isn't already one,
Op 11-4-2012 20:45, Richard Heck schreef:
On 04/11/2012 02:02 PM, Vincent van Ravesteijn wrote:
Op 11-4-2012 19:56, Richard Heck schreef:
On 04/11/2012 07:39 AM, Jürgen Spitzmüller wrote:
2012/4/11 Richard Heck:
We really should fix this, and it shouldn't be that hard. It's often
requested
Op 11-4-2012 21:15, Enrico Forestieri schreef:
On Wed, Apr 11, 2012 at 08:52:16PM +0200, Kornel Benko wrote:
Am Mittwoch, 11. April 2012 um 20:39:23, schrieb for...@lyx.org
Author: Enrico Forestierifor...@lyx.org
Date: Wed, 11 Apr 2012 18:19:11 +0200
New Commit:
Op 11-4-2012 21:26, Pavel Sanda schreef:
Enrico Forestieri wrote:
I don't want to repeat it, but if I had simply applied a diff from trunk
I would not have had any conflicts and everything would have gone more
smoothly and in less time.
I'm afraid you would have conflicts:
$ git show
Op 11-4-2012 21:31, Enrico Forestieri schreef:
On Wed, Apr 11, 2012 at 09:06:19PM +0200, Vincent van Ravesteijn wrote:
Op 11-4-2012 20:50, Enrico Forestieri schreef:
On Sun, Mar 25, 2012 at 04:36:40PM +0200, Vincent van Ravesteijn wrote:
Op 25-3-2012 15:52, for...@lyx.org schreef:
I first
Op 8-4-2012 21:55, Vincent van Ravesteijn schreef:
Op 8-4-2012 21:51, v...@lyx.org schreef:
Author: Vincent van Ravesteijn<v...@lyx.org>
Date: Sun, 08 Apr 2012 21:47:40 +0200
New Commit: 91bc04946fafbee92dda4bd17edfa007f615fe5d
URL:
http://git.lyx.org/?p=lyx.git;a=co
Op 8-4-2012 23:22, v...@lyx.org schreef:
Author: Vincent van Ravesteijn<v...@lyx.org>
Date: Sun, 08 Apr 2012 23:20:01 +0200
New Commit: f0754582b8af481dc636c6d31eb3a52c853d7db0
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=f0754582b8af481dc636c6d31eb3a52c853d7db0
Log:
Fix bug #8114: Ly
Op 11-4-2012 19:56, Richard Heck schreef:
On 04/11/2012 07:39 AM, Jürgen Spitzmüller wrote:
2012/4/11 Richard Heck:
We really should fix this, and it shouldn't be that hard. It's often
requested. Can someone please file a bug about it? Check first to
make sure
there isn't already one,
Op 11-4-2012 20:45, Richard Heck schreef:
On 04/11/2012 02:02 PM, Vincent van Ravesteijn wrote:
Op 11-4-2012 19:56, Richard Heck schreef:
On 04/11/2012 07:39 AM, Jürgen Spitzmüller wrote:
2012/4/11 Richard Heck:
We really should fix this, and it shouldn't be that hard. It's often
requested
Op 11-4-2012 21:15, Enrico Forestieri schreef:
On Wed, Apr 11, 2012 at 08:52:16PM +0200, Kornel Benko wrote:
Am Mittwoch, 11. April 2012 um 20:39:23, schrieb for...@lyx.org
Author: Enrico Forestieri
Date: Wed, 11 Apr 2012 18:19:11 +0200
New Commit:
Op 11-4-2012 21:26, Pavel Sanda schreef:
Enrico Forestieri wrote:
I don't want to repeat it, but if I had simply applied a diff from trunk
I would not have had any conflicts and everything would have gone more
smoothly and in less time.
I'm afraid you would have conflicts:
$ git show
Op 11-4-2012 21:31, Enrico Forestieri schreef:
On Wed, Apr 11, 2012 at 09:06:19PM +0200, Vincent van Ravesteijn wrote:
Op 11-4-2012 20:50, Enrico Forestieri schreef:
On Sun, Mar 25, 2012 at 04:36:40PM +0200, Vincent van Ravesteijn wrote:
Op 25-3-2012 15:52, for...@lyx.org schreef:
I first
Op 7-12-2011 17:03, kuem...@lyx.org schreef:
Author: kuemmel
Date: Wed Dec 7 17:03:37 2011
New Revision: 40417
URL: http://www.lyx.org/trac/changeset/40417
Log:
clang: std::string is used here, fwd is not enough
Modified:
lyx-devel/trunk/src/Lexer.h
Modified: lyx-devel/trunk/src/Lexer.h
Op 31-3-2012 18:31, Antonio Pineda schreef:
Hi all. Don't know if anyone's noticed this before - since I couldn't
find a reference to it in the bug tracker, I thought this could be
brought to your attention.
I configured my Gentoo Linux for AMD64 (stable branch) so as to use
clang instead of
Op 9-4-2012 15:53, Richard Heck schreef:
On 04/09/2012 09:09 AM, Vincent van Ravesteijn wrote:
Op 7-12-2011 17:03, kuem...@lyx.org schreef:
Author: kuemmel
Date: Wed Dec 7 17:03:37 2011
New Revision: 40417
URL: http://www.lyx.org/trac/changeset/40417
Log:
clang: std::string is used here, fwd
Op 7-12-2011 17:03, kuem...@lyx.org schreef:
Author: kuemmel
Date: Wed Dec 7 17:03:37 2011
New Revision: 40417
URL: http://www.lyx.org/trac/changeset/40417
Log:
clang: std::string is used here, fwd is not enough
Modified:
lyx-devel/trunk/src/Lexer.h
Modified: lyx-devel/trunk/src/Lexer.h
Op 31-3-2012 18:31, Antonio Pineda schreef:
Hi all. Don't know if anyone's noticed this before - since I couldn't
find a reference to it in the bug tracker, I thought this could be
brought to your attention.
I configured my Gentoo Linux for AMD64 (stable branch) so as to use
clang instead of
Op 9-4-2012 15:53, Richard Heck schreef:
On 04/09/2012 09:09 AM, Vincent van Ravesteijn wrote:
Op 7-12-2011 17:03, kuem...@lyx.org schreef:
Author: kuemmel
Date: Wed Dec 7 17:03:37 2011
New Revision: 40417
URL: http://www.lyx.org/trac/changeset/40417
Log:
clang: std::string is used here, fwd
Op 8-4-2012 17:01, Richard Heck schreef:
One of the nice things about git is its expandability, through aliases
and scripts. To some extent, using these can hide the complexities of
git and make it work more like svn. So I'm attaching a few of the ones
I've developed so far. They're written
Op 8-4-2012 21:51, v...@lyx.org schreef:
Author: Vincent van Ravesteijnv...@lyx.org
Date: Sun, 08 Apr 2012 21:47:40 +0200
New Commit: 91bc04946fafbee92dda4bd17edfa007f615fe5d
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=91bc04946fafbee92dda4bd17edfa007f615fe5d
Log:
Fix a copy-paste error
Op 8-4-2012 17:01, Richard Heck schreef:
One of the nice things about git is its expandability, through aliases
and scripts. To some extent, using these can hide the complexities of
git and make it work more like svn. So I'm attaching a few of the ones
I've developed so far. They're written
Op 8-4-2012 21:51, v...@lyx.org schreef:
Author: Vincent van Ravesteijn<v...@lyx.org>
Date: Sun, 08 Apr 2012 21:47:40 +0200
New Commit: 91bc04946fafbee92dda4bd17edfa007f615fe5d
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=91bc04946fafbee92dda4bd17edfa007f615fe5d
Log:
Fix a copy-paste
Op 2-4-2012 16:21, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
You had made local commits onto your master branch. If you then do 'git
pull'. It will fetch the commits from the master branch at the server and
merge them with your local commits.
Thanks for all you answers; started
Op 2-4-2012 16:21, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
You had made local commits onto your master branch. If you then do 'git
pull'. It will fetch the commits from the master branch at the server and
merge them with your local commits.
Thanks for all you answers; started
Op 31-3-2012 1:58, Pavel Sanda schreef:
sa...@lyx.org wrote:
Author: Pavel Sandasa...@lyx.org
Date: Sat, 31 Mar 2012 01:09:21 +0200
New Commit: 612109bb6e5e61ba3c3693696f329eac3a288b5b
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=612109bb6e5e61ba3c3693696f329eac3a288b5b
Log:
Merge branch
This was not intended to go in, I only wanted to push the tex2lyx fix. After
reading a lot of documentation I thought that
git push g...@git.lyx.org:lyx d88f772:refs/heads/master
would do that, but instead it did the equivalent of
git push
You can probably use 'origin' instead of
Op 31-3-2012 1:58, Pavel Sanda schreef:
sa...@lyx.org wrote:
Author: Pavel Sanda
Date: Sat, 31 Mar 2012 01:09:21 +0200
New Commit: 612109bb6e5e61ba3c3693696f329eac3a288b5b
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=612109bb6e5e61ba3c3693696f329eac3a288b5b
Log:
Merge branch
This was not intended to go in, I only wanted to push the tex2lyx fix. After
reading a lot of documentation I thought that
git push g...@git.lyx.org:lyx d88f772:refs/heads/master
would do that, but instead it did the equivalent of
git push
You can probably use 'origin' instead of
Op 25-3-2012 15:52, for...@lyx.org schreef:
Author: Enrico Forestierifor...@lyx.org
Date: Sun, 25 Mar 2012 15:49:10 +0200
New Commit: ae068255137f111c598e93f9a54a891ffdb4dafc
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=ae068255137f111c598e93f9a54a891ffdb4dafc
Log:
status.20x for last commit.
Op 25-3-2012 17:55, Enrico Forestieri schreef:
On Sun, Mar 25, 2012 at 11:26:10AM -0400, Richard Heck wrote:
On 03/25/2012 11:10 AM, Enrico Forestieri wrote:
On Sun, Mar 25, 2012 at 04:36:40PM +0200, Vincent van Ravesteijn wrote:
Op 25-3-2012 15:52, for...@lyx.org schreef:
Author: Enrico
Op 25-3-2012 15:52, for...@lyx.org schreef:
Author: Enrico Forestieri
Date: Sun, 25 Mar 2012 15:49:10 +0200
New Commit: ae068255137f111c598e93f9a54a891ffdb4dafc
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=ae068255137f111c598e93f9a54a891ffdb4dafc
Log:
status.20x for last
Op 25-3-2012 17:55, Enrico Forestieri schreef:
On Sun, Mar 25, 2012 at 11:26:10AM -0400, Richard Heck wrote:
On 03/25/2012 11:10 AM, Enrico Forestieri wrote:
On Sun, Mar 25, 2012 at 04:36:40PM +0200, Vincent van Ravesteijn wrote:
Op 25-3-2012 15:52, for...@lyx.org schreef:
Author: Enrico
Dear LyX users and developers,
LyX has a problem with Windows users that have their home directory on a UNC
path. http://wiki.lyx.org/LyX/Troubleshooting mentions these problems for Lyx
1.5 already. (Recent versions do start, but have no classes available.)
I have been struggling with this
Op 5-3-2012 11:59, Rick Blok schreef:
Hi,
Would you be so kind to add a dutch thesaurus dictionary to the next
release? Opentaal.nl has it online:
http://www.opentaal.org/projecten/synoniemen.
I had to the files rename them to th_nl_NL_v2 to make it work.
Thanks,
Rick Blok
I added them.
Dear LyX users and developers,
LyX has a problem with Windows users that have their home directory on a UNC
path. http://wiki.lyx.org/LyX/Troubleshooting mentions these problems for Lyx
1.5 already. (Recent versions do start, but have no classes available.)
I have been struggling with this
Op 5-3-2012 11:59, Rick Blok schreef:
Hi,
Would you be so kind to add a dutch thesaurus dictionary to the next
release? Opentaal.nl has it online:
http://www.opentaal.org/projecten/synoniemen.
I had to the files rename them to th_nl_NL_v2 to make it work.
Thanks,
Rick Blok
I added them.
Op 23-3-2012 23:03, v...@lyx.org schreef:
Author: Vincent van Ravesteijnv...@lyx.org
Date: Fri, 23 Mar 2012 21:15:55 +0100
New Commit: e409eedc5bd77d80af93a0b7c3ce19c53db8fbf0
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=e409eedc5bd77d80af93a0b7c3ce19c53db8fbf0
Log:
Fix more possible crashes
Op 23-3-2012 23:03, v...@lyx.org schreef:
Author: Vincent van Ravesteijn<v...@lyx.org>
Date: Fri, 23 Mar 2012 21:15:55 +0100
New Commit: e409eedc5bd77d80af93a0b7c3ce19c53db8fbf0
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=e409eedc5bd77d80af93a0b7c3ce19c53db8fbf0
Log:
Fix more po
On Thu, Mar 22, 2012 at 9:44 AM, Pavel Sanda sa...@lyx.org wrote:
Lars Gullik Bj?nnes wrote:
| 1. Checkout full repo
| git clone g...@git.lyx.org:lyx trunk
| 2. Full mirror of branch as well, not through clone
| cp -r trunk branch; cd branch
No...
(perhaps... it does not
On Thu, Mar 22, 2012 at 9:44 AM, Pavel Sanda wrote:
> Lars Gullik Bj?nnes wrote:
> > | 1. Checkout full repo
> > | git clone g...@git.lyx.org:lyx trunk
> > | 2. Full mirror of branch as well, not through clone
> > | cp -r trunk branch; cd branch
> >
> > No...
> >
Op 20-3-2012 20:35, Richard Heck schreef:
On 03/20/2012 07:44 AM, Vincent van Ravesteijn wrote:
Op 20-3-2012 0:15, Richard Heck schreef:
This is in my private repo. I have a branch master, and another
branch bugs/7975, and another branch lyx/trunk that is tracking the
main repo, set up
Op 21-3-2012 13:32, Dahlmann Martin TU Ilmenau schreef:
Hello,
I am writing this to the developers list, because its more about the
development than how to possibly manually fix a special issue that I
might mention. Simply, if there is a manual fix, then I have not found
it yet, which might
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you want to see the code changes
introduced by a merge you can do:
$ git diff 9236a938 9236a938^1
This will show you that the merge is not empty at all.
Is there a way how to obtain
Op 21-3-2012 15:51, Jean-Marc Lasgouttes schreef:
Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit :
If you want a tree for both 2.0.x and 2.1.0svn, you can do the
following:
Assume you have a git clone in home/lyx, you can clone this with
git clone -s -b 2.0.x home/lyx home/lyx20x
Op 21-3-2012 16:16, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you want to see the code changes
introduced by a merge you can do:
$ git diff 9236a938 9236a938^1
Op 21-3-2012 16:39, Vincent van Ravesteijn schreef:
Op 21-3-2012 16:16, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you want to see the code
changes
introduced by a merge
Op 21-3-2012 16:48, Vincent van Ravesteijn schreef:
Op 21-3-2012 16:39, Vincent van Ravesteijn schreef:
Op 21-3-2012 16:16, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you
There has to be a simple way to commit a patch to branch (please tell
me there is!).
I forgot to mention: Ideally, if we do it the git-way completely, you
would only have to commit a patch to the 2.0.x branch. Later, the 2.0.x
will automatically be merged into the master. This can be
Now you can push your branch to lyx:
$ git push lyx 2.0.x
How come I have to specify lyx 2.0.x. Isn't it possible to setup the
branch so that git push will do the right thing?
git push will by default push to the remote which is tracked by the
current branch. If the current branch does
Op 20-3-2012 20:35, Richard Heck schreef:
On 03/20/2012 07:44 AM, Vincent van Ravesteijn wrote:
Op 20-3-2012 0:15, Richard Heck schreef:
This is in my private repo. I have a branch master, and another
branch bugs/7975, and another branch lyx/trunk that is tracking the
main repo, set up
Op 21-3-2012 13:32, Dahlmann Martin TU Ilmenau schreef:
Hello,
I am writing this to the developers list, because its more about the
development than how to possibly manually fix a special issue that I
might mention. Simply, if there is a manual fix, then I have not found
it yet, which might
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you want to see the code changes
introduced by a merge you can do:
$ git diff 9236a938 9236a938^1
This will show you that the merge is not empty at all.
Is there a way how to obtain
Op 21-3-2012 15:51, Jean-Marc Lasgouttes schreef:
Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit :
If you want a tree for both 2.0.x and 2.1.0svn, you can do the
following:
Assume you have a git clone in /lyx, you can clone this with
git clone -s -b 2.0.x /lyx /lyx20x
This will clone
Op 21-3-2012 16:16, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you want to see the code changes
introduced by a merge you can do:
$ git diff 9236a938 9236a938^1
Op 21-3-2012 16:39, Vincent van Ravesteijn schreef:
Op 21-3-2012 16:16, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you want to see the code
changes
introduced by a merge
Op 21-3-2012 16:48, Vincent van Ravesteijn schreef:
Op 21-3-2012 16:39, Vincent van Ravesteijn schreef:
Op 21-3-2012 16:16, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Op 21-3-2012 15:00, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
all commits that are in this range). If you
There has to be a simple way to commit a patch to branch (please tell
me there is!).
I forgot to mention: Ideally, if we do it the git-way completely, you
would only have to commit a patch to the 2.0.x branch. Later, the 2.0.x
will automatically be merged into the master. This can be
Now you can push your branch to "lyx":
$ git push lyx 2.0.x
How come I have to specify "lyx 2.0.x". Isn't it possible to setup the
branch so that "git push" will do the right thing?
"git push" will by default push to the remote which is tracked by the
current branch. If the current
Op 20-3-2012 2:03, Uwe Stöhr schreef:
For an unknown reason LyX only allows to rotate tables by 90°. The
LaTeX code LyX is using for this also allows to rotate by any angle
and my patch enables this now. The patch is in pronciple the same as
my last week#s implementation of table cell
I think I would prefer:
bool const fixed_width_multirow = multirowCB-isChecked() width
!= 0pt;
if (!fixed_width_multirow)
setHAlign(param_str);
What is the benefit of using an extra bool here?
It is much clearer. Usually, you can better write code that speaks for
itselft than to add a
Op 20-3-2012 1:01, Uwe Stöhr schreef:
Am 19.03.2012 10:00, schrieb Vincent van Ravesteijn:
Why did you change this ?
IMHO the description is incomplete and not easier.
What is incomplete?
I changed it because it didn't work anymore. With Qt 4.8 things have
changed and Peter did a good job
1601 - 1700 of 6163 matches
Mail list logo