Am Montag, 10. Dezember 2012, 21:31:25 schrieb Rob Oakes:
Rob, those links are very helpful and clarifying things which are not
obvious to the novice!
Wolfgang
http://blog.oak-tree.us/index.php/2009/11/02/custom-lyx-nih
http://blog.oak-tree.us/index.php/2009/11/14/customize-lyx-character-sty
On 12/11/2012 09:29 AM, Wolfgang Engelmann wrote:
Am Montag, 10. Dezember 2012, 21:31:25 schrieb Rob Oakes:
Rob, those links are very helpful and clarifying things which are not
obvious to the novice!
Wolfgang
If other doubts arrive (probability ~= 1) do not hesitate to use this list.
Now
Hi Wolfgang,
I'm glad they were helpful:
On Tue, 2012-12-11 at 10:36 +0100, Wolfgang Engelmann wrote:
Am Montag, 10. Dezember 2012, 21:31:25 schrieben Sie:
Hi, Rob,
has this been done already:
TeXLive 2009 is included with Ubuntu 10.04, if you are able to update your
Linux
On Mon, Dec 10, 2012 at 5:22 PM, José Matos jama...@lyx.org wrote:
On 12/10/2012 10:46 PM, Nico Williams wrote:
Why is there no bibliography environment in the DocBook document
classes? There must be a reason, of course, but then, bibtex is still
supported, so that's strange...
The reason
Gregory Jefferis wrote:
Returning to the original question of merging + VCS, we currently use git +
lyx for collaborative editing of papers in the lab (normally =3 people)
using git's built in merge. For us this a tremendous improvement over the
emailed word file strategy. We have not
On Tue, Dec 11, 2012 at 10:26 AM, Pavel Sanda sa...@lyx.org wrote:
We currently use integrated SVN support of LyX for this.
The merge conflicts are avoided by locking the whole document or childern
(parts of the text).
It is precisely because locking doesn't scale that we have branching
and
Hi Mateo, John, Ray, Jacob (and everyone else),
It seems APA6 is useful to a lot of people and in particular to you
guys. How about we make a layout for it together then?
I will be happy to help. As soon as I get caught up on some things, I will
clean up what I am using and see if we can
Nico Williams wrote:
It is precisely because locking doesn't scale that we have branching
and merging. Locking simply does not scale. This is true even of
documents (as opposed to source code).
Conditions I had in mind were:
a)
- small team working on e.g. scientific paper
- avoid endless
On 11/12/2012 5:23 a.m., Richard Heck wrote:
On 12/08/2012 04:17 AM, Andrew Parsloe wrote:
(1) If an inset name contains a vertical bar, |, the part after the
bar is not shown in the Insert Custom Insets list, but is retained
in LyX format. Using the schema, inset definition = Custom Insets
On Tue, Dec 11, 2012 at 12:25 PM, Pavel Sanda sa...@lyx.org wrote:
Nico Williams wrote:
It is precisely because locking doesn't scale that we have branching
and merging. Locking simply does not scale. This is true even of
documents (as opposed to source code).
Conditions I had in mind
Le 11/12/12 23:00, Andrew Parsloe a écrit :
Thanks for the responses to this and my other custom inset queries
Richard. I've put in a bug report about ResetsFont in custom insets. I'm
going to continue to use the pipe symbol for its unintended purpose --
I've yet to see any deleterious
Nico Williams wrote:
I believe merging is easier than locking, even for small teams.
That's because you probably work with people with computer science background.
The moment you step out of these waters the most you can expect is push red
button, push green button and I know what I'm talking
On Tuesday, December 11, 2012, Pavel Sanda wrote:
Nico Williams wrote:
I believe merging is easier than locking, even for small teams.
That's because you probably work with people with computer science
background.
The moment you step out of these waters the most you can expect is push
red
(wrote this up and noticed that much of it duplicates what Nico said – merging
is easy and branching is not so bad either)
On 11 Dec 2012, at 18:25, Pavel Sanda wrote:
Nico Williams wrote:
It is precisely because locking doesn't scale that we have branching
and merging. Locking simply does
Le 12/12/12 00:06, Nico Williams a écrit :
Anyone who would use track changes can merge. In any case, a merge
capability would be huge.
Sure, but not trivial to implement...
JMarc
On 12/11/2012 05:02 PM, Jean-Marc Lasgouttes wrote:
Le 11/12/12 23:00, Andrew Parsloe a écrit :
Thanks for the responses to this and my other custom inset queries
Richard. I've put in a bug report about ResetsFont in custom insets. I'm
going to continue to use the pipe symbol for its unintended
Am Montag, 10. Dezember 2012, 21:31:25 schrieb Rob Oakes:
Rob, those links are very helpful and clarifying things which are not
obvious to the novice!
Wolfgang
http://blog.oak-tree.us/index.php/2009/11/02/custom-lyx-nih
http://blog.oak-tree.us/index.php/2009/11/14/customize-lyx-character-sty
On 12/11/2012 09:29 AM, Wolfgang Engelmann wrote:
Am Montag, 10. Dezember 2012, 21:31:25 schrieb Rob Oakes:
Rob, those links are very helpful and clarifying things which are not
obvious to the novice!
Wolfgang
If other doubts arrive (probability ~= 1) do not hesitate to use this list.
Now
Hi Wolfgang,
I'm glad they were helpful:
On Tue, 2012-12-11 at 10:36 +0100, Wolfgang Engelmann wrote:
Am Montag, 10. Dezember 2012, 21:31:25 schrieben Sie:
Hi, Rob,
has this been done already:
TeXLive 2009 is included with Ubuntu 10.04, if you are able to update your
Linux
On Mon, Dec 10, 2012 at 5:22 PM, José Matos jama...@lyx.org wrote:
On 12/10/2012 10:46 PM, Nico Williams wrote:
Why is there no bibliography environment in the DocBook document
classes? There must be a reason, of course, but then, bibtex is still
supported, so that's strange...
The reason
Gregory Jefferis wrote:
Returning to the original question of merging + VCS, we currently use git +
lyx for collaborative editing of papers in the lab (normally =3 people)
using git's built in merge. For us this a tremendous improvement over the
emailed word file strategy. We have not
On Tue, Dec 11, 2012 at 10:26 AM, Pavel Sanda sa...@lyx.org wrote:
We currently use integrated SVN support of LyX for this.
The merge conflicts are avoided by locking the whole document or childern
(parts of the text).
It is precisely because locking doesn't scale that we have branching
and
Hi Mateo, John, Ray, Jacob (and everyone else),
It seems APA6 is useful to a lot of people and in particular to you
guys. How about we make a layout for it together then?
I will be happy to help. As soon as I get caught up on some things, I will
clean up what I am using and see if we can
Nico Williams wrote:
It is precisely because locking doesn't scale that we have branching
and merging. Locking simply does not scale. This is true even of
documents (as opposed to source code).
Conditions I had in mind were:
a)
- small team working on e.g. scientific paper
- avoid endless
On 11/12/2012 5:23 a.m., Richard Heck wrote:
On 12/08/2012 04:17 AM, Andrew Parsloe wrote:
(1) If an inset name contains a vertical bar, |, the part after the
bar is not shown in the Insert Custom Insets list, but is retained
in LyX format. Using the schema, inset definition = Custom Insets
On Tue, Dec 11, 2012 at 12:25 PM, Pavel Sanda sa...@lyx.org wrote:
Nico Williams wrote:
It is precisely because locking doesn't scale that we have branching
and merging. Locking simply does not scale. This is true even of
documents (as opposed to source code).
Conditions I had in mind
Le 11/12/12 23:00, Andrew Parsloe a écrit :
Thanks for the responses to this and my other custom inset queries
Richard. I've put in a bug report about ResetsFont in custom insets. I'm
going to continue to use the pipe symbol for its unintended purpose --
I've yet to see any deleterious
Nico Williams wrote:
I believe merging is easier than locking, even for small teams.
That's because you probably work with people with computer science background.
The moment you step out of these waters the most you can expect is push red
button, push green button and I know what I'm talking
On Tuesday, December 11, 2012, Pavel Sanda wrote:
Nico Williams wrote:
I believe merging is easier than locking, even for small teams.
That's because you probably work with people with computer science
background.
The moment you step out of these waters the most you can expect is push
red
(wrote this up and noticed that much of it duplicates what Nico said – merging
is easy and branching is not so bad either)
On 11 Dec 2012, at 18:25, Pavel Sanda wrote:
Nico Williams wrote:
It is precisely because locking doesn't scale that we have branching
and merging. Locking simply does
Le 12/12/12 00:06, Nico Williams a écrit :
Anyone who would use track changes can merge. In any case, a merge
capability would be huge.
Sure, but not trivial to implement...
JMarc
On 12/11/2012 05:02 PM, Jean-Marc Lasgouttes wrote:
Le 11/12/12 23:00, Andrew Parsloe a écrit :
Thanks for the responses to this and my other custom inset queries
Richard. I've put in a bug report about ResetsFont in custom insets. I'm
going to continue to use the pipe symbol for its unintended
Am Montag, 10. Dezember 2012, 21:31:25 schrieb Rob Oakes:
Rob, those links are very helpful and clarifying things which are not
obvious to the novice!
Wolfgang
> http://blog.oak-tree.us/index.php/2009/11/02/custom-lyx-nih
> http://blog.oak-tree.us/index.php/2009/11/14/customize-lyx-character-sty
On 12/11/2012 09:29 AM, Wolfgang Engelmann wrote:
> Am Montag, 10. Dezember 2012, 21:31:25 schrieb Rob Oakes:
> Rob, those links are very helpful and clarifying things which are not
> obvious to the novice!
> Wolfgang
If other doubts arrive (probability ~= 1) do not hesitate to use this list.
Hi Wolfgang,
I'm glad they were helpful:
On Tue, 2012-12-11 at 10:36 +0100, Wolfgang Engelmann wrote:
> Am Montag, 10. Dezember 2012, 21:31:25 schrieben Sie:
>
> Hi, Rob,
>
> has this been done already:
>
> TeXLive 2009 is included with Ubuntu 10.04, if you are able to update your
> Linux
On Mon, Dec 10, 2012 at 5:22 PM, José Matos wrote:
> On 12/10/2012 10:46 PM, Nico Williams wrote:
>> Why is there no bibliography environment in the DocBook document
>> classes? There must be a reason, of course, but then, bibtex is still
>> supported, so that's strange...
>
>
Gregory Jefferis wrote:
> Returning to the original question of merging + VCS, we currently use git +
> lyx for collaborative editing of papers in the lab (normally <=3 people)
> using git's built in merge. For us this a tremendous improvement over the
> emailed word file strategy. We have not
On Tue, Dec 11, 2012 at 10:26 AM, Pavel Sanda wrote:
> We currently use integrated SVN support of LyX for this.
> The merge conflicts are avoided by locking the whole document or childern
> (parts of the text).
It is precisely because locking doesn't scale that we have branching
>
> Hi Mateo, John, Ray, Jacob (and everyone else),
>
> It seems APA6 is useful to a lot of people and in particular to you
> guys. How about we make a layout for it together then?
>
I will be happy to help. As soon as I get caught up on some things, I will
clean up what I am using and see if we
Nico Williams wrote:
> It is precisely because locking doesn't scale that we have branching
> and merging. Locking simply does not scale. This is true even of
> documents (as opposed to source code).
Conditions I had in mind were:
a)
- small team working on e.g. scientific paper
- avoid endless
On 11/12/2012 5:23 a.m., Richard Heck wrote:
On 12/08/2012 04:17 AM, Andrew Parsloe wrote:
(1) If an inset name contains a vertical bar, |, the part after the
bar is not shown in the Insert > Custom Insets list, but is retained
in LyX format. Using the schema, inset definition => Custom Insets
On Tue, Dec 11, 2012 at 12:25 PM, Pavel Sanda wrote:
> Nico Williams wrote:
>> It is precisely because locking doesn't scale that we have branching
>> and merging. Locking simply does not scale. This is true even of
>> documents (as opposed to source code).
>
> Conditions I had
Le 11/12/12 23:00, Andrew Parsloe a écrit :
Thanks for the responses to this and my other custom inset queries
Richard. I've put in a bug report about ResetsFont in custom insets. I'm
going to continue to use the pipe symbol for its unintended purpose --
I've yet to see any deleterious
Nico Williams wrote:
> I believe merging is easier than locking, even for small teams.
That's because you probably work with people with computer science background.
The moment you step out of these waters the most you can expect is "push red
button, push green button" and I know what I'm talking
On Tuesday, December 11, 2012, Pavel Sanda wrote:
> Nico Williams wrote:
> > I believe merging is easier than locking, even for small teams.
>
> That's because you probably work with people with computer science
> background.
> The moment you step out of these waters the most you can expect is
(wrote this up and noticed that much of it duplicates what Nico said – merging
is easy and branching is not so bad either)
On 11 Dec 2012, at 18:25, Pavel Sanda wrote:
> Nico Williams wrote:
>> It is precisely because locking doesn't scale that we have branching
>> and merging. Locking simply
Le 12/12/12 00:06, Nico Williams a écrit :
Anyone who would use track changes can merge. In any case, a merge
capability would be huge.
Sure, but not trivial to implement...
JMarc
On 12/11/2012 05:02 PM, Jean-Marc Lasgouttes wrote:
Le 11/12/12 23:00, Andrew Parsloe a écrit :
Thanks for the responses to this and my other custom inset queries
Richard. I've put in a bug report about ResetsFont in custom insets. I'm
going to continue to use the pipe symbol for its unintended
48 matches
Mail list logo