Re: Noweb/Literate programming Copier problem

[Jean-Marc Lasgouttes]

Le 30/10/12 02:53, Scott Kostyshak a écrit :

On Mon, Oct 29, 2012 at 7:01 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:

Le 29/10/2012 10:24, Scott Kostyshak a écrit :


I would capitalize nevertheless.



Updated patch attached. Is it OK?


It's in. Richard, is this OK for branch?


I suspect you should wait for 2.0.6.

JMarc

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Tue, Oct 30, 2012 at 5:09 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
 Le 30/10/12 02:53, Scott Kostyshak a écrit :

 On Mon, Oct 29, 2012 at 7:01 AM, Jean-Marc Lasgouttes
 lasgout...@lyx.org wrote:

 Le 29/10/2012 10:24, Scott Kostyshak a écrit :

 I would capitalize nevertheless.



 Updated patch attached. Is it OK?


 It's in. Richard, is this OK for branch?


 I suspect you should wait for 2.0.6.

OK.

Thanks, Scott


 JMarc

Re: Noweb/Literate programming Copier problem

[Jean-Marc Lasgouttes]

Le 30/10/12 02:53, Scott Kostyshak a écrit :

On Mon, Oct 29, 2012 at 7:01 AM, Jean-Marc Lasgouttes
 wrote:

Le 29/10/2012 10:24, Scott Kostyshak a écrit :


I would capitalize nevertheless.



Updated patch attached. Is it OK?


It's in. Richard, is this OK for branch?


I suspect you should wait for 2.0.6.

JMarc

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Tue, Oct 30, 2012 at 5:09 AM, Jean-Marc Lasgouttes
 wrote:
> Le 30/10/12 02:53, Scott Kostyshak a écrit :
>
>> On Mon, Oct 29, 2012 at 7:01 AM, Jean-Marc Lasgouttes
>>  wrote:
>>>
>>> Le 29/10/2012 10:24, Scott Kostyshak a écrit :
>>>
> I would capitalize nevertheless.



 Updated patch attached. Is it OK?
>>
>>
>> It's in. Richard, is this OK for branch?
>
>
> I suspect you should wait for 2.0.6.

OK.

Thanks, Scott

>
> JMarc
>

Re: Noweb/Literate programming Copier problem

[Jean-Marc Lasgouttes]

Le 29/10/2012 04:11, Scott Kostyshak a écrit :

On Mon, Oct 22, 2012 at 3:54 PM, Pavel Sanda sa...@lyx.org wrote:

Scott Kostyshak wrote:

On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie x...@yihui.name wrote:

I think that should be enough. A pointer to the knitr manual in
Help--Specific Manuals--Knitr Manual can be helpful too (I
remember Liviu mentioned this once).


Sure, I can do that. Pavel, is that OK? Trunk only?


Yes, fine with me.


Is the attached patch OK? I broke style by leaving knitr lowercase
because I have never seen it capitalized.


I would capitalize nevertheless.

JMarc

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Mon, Oct 29, 2012 at 4:53 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
 Le 29/10/2012 04:11, Scott Kostyshak a écrit :

 On Mon, Oct 22, 2012 at 3:54 PM, Pavel Sanda sa...@lyx.org wrote:

 Scott Kostyshak wrote:

 On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie x...@yihui.name wrote:

 I think that should be enough. A pointer to the knitr manual in
 Help--Specific Manuals--Knitr Manual can be helpful too (I
 remember Liviu mentioned this once).


 Sure, I can do that. Pavel, is that OK? Trunk only?


 Yes, fine with me.


 Is the attached patch OK? I broke style by leaving knitr lowercase
 because I have never seen it capitalized.


 I would capitalize nevertheless.

Updated patch attached. Is it OK?

Scott
From 38ec5fa86a157172e8ee574190043f4be4968d11 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Mon, 29 Oct 2012 05:15:38 -0400
Subject: [PATCH] Add knitr manual to Help  Specific Manuals

---
 lib/ui/stdmenus.inc |1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/ui/stdmenus.inc b/lib/ui/stdmenus.inc
index 9cb6768..be2f68a 100644
--- a/lib/ui/stdmenus.inc
+++ b/lib/ui/stdmenus.inc
@@ -590,6 +590,7 @@ Menuset
Menu examples
Item Braille Manual|B help-open Braille
Item Feynman-diagram Manual|F help-open FeynmanDiagrams
+   Item Knitr Manual|K help-open knitr
Item LilyPond Manual|M help-open lilypond
Item Linguistics Manual|L help-open linguistics
Item Multilingual Captions Manual|C help-open 
MultilingualCaptions
-- 
1.7.9.5

Re: Noweb/Literate programming Copier problem

[Jean-Marc Lasgouttes]

Le 29/10/2012 10:24, Scott Kostyshak a écrit :

I would capitalize nevertheless.


Updated patch attached. Is it OK?


Sure.

JMarc

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Mon, Oct 29, 2012 at 7:01 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
 Le 29/10/2012 10:24, Scott Kostyshak a écrit :

 I would capitalize nevertheless.


 Updated patch attached. Is it OK?

It's in. Richard, is this OK for branch?

Thanks,

Scott



 Sure.

 JMarc

Re: Noweb/Literate programming Copier problem

[Jean-Marc Lasgouttes]

Le 29/10/2012 04:11, Scott Kostyshak a écrit :

On Mon, Oct 22, 2012 at 3:54 PM, Pavel Sanda  wrote:

Scott Kostyshak wrote:

On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie  wrote:

I think that should be enough. A pointer to the knitr manual in
"Help-->Specific Manuals-->Knitr Manual" can be helpful too (I
remember Liviu mentioned this once).


Sure, I can do that. Pavel, is that OK? Trunk only?


Yes, fine with me.


Is the attached patch OK? I broke style by leaving knitr lowercase
because I have never seen it capitalized.


I would capitalize nevertheless.

JMarc

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Mon, Oct 29, 2012 at 4:53 AM, Jean-Marc Lasgouttes
 wrote:
> Le 29/10/2012 04:11, Scott Kostyshak a écrit :
>
>> On Mon, Oct 22, 2012 at 3:54 PM, Pavel Sanda  wrote:
>>>
>>> Scott Kostyshak wrote:

 On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie  wrote:
>
> I think that should be enough. A pointer to the knitr manual in
> "Help-->Specific Manuals-->Knitr Manual" can be helpful too (I
> remember Liviu mentioned this once).


 Sure, I can do that. Pavel, is that OK? Trunk only?
>>>
>>>
>>> Yes, fine with me.
>>
>>
>> Is the attached patch OK? I broke style by leaving knitr lowercase
>> because I have never seen it capitalized.
>
>
> I would capitalize nevertheless.

Updated patch attached. Is it OK?

Scott
From 38ec5fa86a157172e8ee574190043f4be4968d11 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak 
Date: Mon, 29 Oct 2012 05:15:38 -0400
Subject: [PATCH] Add knitr manual to Help > Specific Manuals

---
 lib/ui/stdmenus.inc |1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/ui/stdmenus.inc b/lib/ui/stdmenus.inc
index 9cb6768..be2f68a 100644
--- a/lib/ui/stdmenus.inc
+++ b/lib/ui/stdmenus.inc
@@ -590,6 +590,7 @@ Menuset
Menu "examples"
Item "Braille Manual|B" "help-open Braille"
Item "Feynman-diagram Manual|F" "help-open FeynmanDiagrams"
+   Item "Knitr Manual|K" "help-open knitr"
Item "LilyPond Manual|M" "help-open lilypond"
Item "Linguistics Manual|L" "help-open linguistics"
Item "Multilingual Captions Manual|C" "help-open 
MultilingualCaptions"
-- 
1.7.9.5

Re: Noweb/Literate programming Copier problem

[Jean-Marc Lasgouttes]

Le 29/10/2012 10:24, Scott Kostyshak a écrit :

I would capitalize nevertheless.


Updated patch attached. Is it OK?


Sure.

JMarc

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Mon, Oct 29, 2012 at 7:01 AM, Jean-Marc Lasgouttes
 wrote:
> Le 29/10/2012 10:24, Scott Kostyshak a écrit :
>
>>> I would capitalize nevertheless.
>>
>>
>> Updated patch attached. Is it OK?

It's in. Richard, is this OK for branch?

Thanks,

Scott

>
>
> Sure.
>
> JMarc
>

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Mon, Oct 22, 2012 at 3:54 PM, Pavel Sanda sa...@lyx.org wrote:
 Scott Kostyshak wrote:
 On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie x...@yihui.name wrote:
  I think that should be enough. A pointer to the knitr manual in
  Help--Specific Manuals--Knitr Manual can be helpful too (I
  remember Liviu mentioned this once).

 Sure, I can do that. Pavel, is that OK? Trunk only?

 Yes, fine with me.

Is the attached patch OK? I broke style by leaving knitr lowercase
because I have never seen it capitalized.

Scott
From 8e20c4f90c59ef1d3a9424367186d6c68abc9ebd Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Sun, 28 Oct 2012 23:03:36 -0400
Subject: [PATCH] Add knitr manual to Help  Specific Manuals

---
 lib/ui/stdmenus.inc |1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/ui/stdmenus.inc b/lib/ui/stdmenus.inc
index 9cb6768..9f9c632 100644
--- a/lib/ui/stdmenus.inc
+++ b/lib/ui/stdmenus.inc
@@ -590,6 +590,7 @@ Menuset
Menu examples
Item Braille Manual|B help-open Braille
Item Feynman-diagram Manual|F help-open FeynmanDiagrams
+   Item knitr Manual|k help-open knitr
Item LilyPond Manual|M help-open lilypond
Item Linguistics Manual|L help-open linguistics
Item Multilingual Captions Manual|C help-open 
MultilingualCaptions
-- 
1.7.9.5

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

That is okay for me, and I do not mind Knitr although it is indeed
rarely capitalized.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Sun, Oct 28, 2012 at 10:11 PM, Scott Kostyshak skost...@lyx.org wrote:

 Is the attached patch OK? I broke style by leaving knitr lowercase
 because I have never seen it capitalized.

 Scott

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Mon, Oct 22, 2012 at 3:54 PM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie  wrote:
>> > I think that should be enough. A pointer to the knitr manual in
>> > "Help-->Specific Manuals-->Knitr Manual" can be helpful too (I
>> > remember Liviu mentioned this once).
>>
>> Sure, I can do that. Pavel, is that OK? Trunk only?
>
> Yes, fine with me.

Is the attached patch OK? I broke style by leaving knitr lowercase
because I have never seen it capitalized.

Scott
From 8e20c4f90c59ef1d3a9424367186d6c68abc9ebd Mon Sep 17 00:00:00 2001
From: Scott Kostyshak 
Date: Sun, 28 Oct 2012 23:03:36 -0400
Subject: [PATCH] Add knitr manual to Help > Specific Manuals

---
 lib/ui/stdmenus.inc |1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/ui/stdmenus.inc b/lib/ui/stdmenus.inc
index 9cb6768..9f9c632 100644
--- a/lib/ui/stdmenus.inc
+++ b/lib/ui/stdmenus.inc
@@ -590,6 +590,7 @@ Menuset
Menu "examples"
Item "Braille Manual|B" "help-open Braille"
Item "Feynman-diagram Manual|F" "help-open FeynmanDiagrams"
+   Item "knitr Manual|k" "help-open knitr"
Item "LilyPond Manual|M" "help-open lilypond"
Item "Linguistics Manual|L" "help-open linguistics"
Item "Multilingual Captions Manual|C" "help-open 
MultilingualCaptions"
-- 
1.7.9.5

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

That is okay for me, and I do not mind "Knitr" although it is indeed
rarely capitalized.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Sun, Oct 28, 2012 at 10:11 PM, Scott Kostyshak  wrote:
>
> Is the attached patch OK? I broke style by leaving knitr lowercase
> because I have never seen it capitalized.
>
> Scott

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
 On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie x...@yihui.name wrote:
  I think that should be enough. A pointer to the knitr manual in
  Help--Specific Manuals--Knitr Manual can be helpful too (I
  remember Liviu mentioned this once).
 
 Sure, I can do that. Pavel, is that OK? Trunk only?

Yes, fine with me.
Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
> On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie  wrote:
> > I think that should be enough. A pointer to the knitr manual in
> > "Help-->Specific Manuals-->Knitr Manual" can be helpful too (I
> > remember Liviu mentioned this once).
> 
> Sure, I can do that. Pavel, is that OK? Trunk only?

Yes, fine with me.
Pavel

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

I think that should be enough. A pointer to the knitr manual in
Help--Specific Manuals--Knitr Manual can be helpful too (I
remember Liviu mentioned this once).

BTW, can you export knitr.lyx to LyX2.0 format? Just like I did here:
https://github.com/yihui/lyx/commit/68c4a7fa78a1ac7e317c783cb415fc21a5ca2705
Otherwise users may not be able to open this file (\lyxformat 424 is
too high).

Thanks!

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Tue, Oct 16, 2012 at 7:58 PM, Scott Kostyshak skost...@lyx.org wrote:

 OK thanks for the tips. I'm guessing it's OK to update the format in
 trunk when changing the manuals?

 I don't think anything in-depth needs to be written there about knitr
 in the Additional manual because knitr already has a manual for use
 with LyX. However, it is currently an example. The only thing
 unmanual-like about knitr.lyx is its length, but in my opinion it is
 sufficient as is, especially because a lot that is in the Sweave
 manual applies to knitr.

 Attached is a patch to update the Additional manual. Is it OK?

 Thanks,

 Scott

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie x...@yihui.name wrote:
 I think that should be enough. A pointer to the knitr manual in
 Help--Specific Manuals--Knitr Manual can be helpful too (I
 remember Liviu mentioned this once).

Sure, I can do that. Pavel, is that OK? Trunk only?

 BTW, can you export knitr.lyx to LyX2.0 format? Just like I did here:
 https://github.com/yihui/lyx/commit/68c4a7fa78a1ac7e317c783cb415fc21a5ca2705
 Otherwise users may not be able to open this file (\lyxformat 424 is
 too high).

424 is only for the master branch. knitr.lyx in the 2.0.x branch has
format 413. I think this is consistent with the other manuals. Am I
missing something?

Thanks,

Scott

 Thanks!

 Regards,
 Yihui
 --
 Yihui Xie xieyi...@gmail.com
 Phone: 515-294-2465 Web: http://yihui.name
 Department of Statistics, Iowa State University
 2215 Snedecor Hall, Ames, IA


 On Tue, Oct 16, 2012 at 7:58 PM, Scott Kostyshak skost...@lyx.org wrote:

 OK thanks for the tips. I'm guessing it's OK to update the format in
 trunk when changing the manuals?

 I don't think anything in-depth needs to be written there about knitr
 in the Additional manual because knitr already has a manual for use
 with LyX. However, it is currently an example. The only thing
 unmanual-like about knitr.lyx is its length, but in my opinion it is
 sufficient as is, especially because a lot that is in the Sweave
 manual applies to knitr.

 Attached is a patch to update the Additional manual. Is it OK?

 Thanks,

 Scott

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

I see. I did not check out the 2.0.x branch. It is indeed 413 there. Thanks!

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Sat, Oct 20, 2012 at 5:53 PM, Scott Kostyshak skost...@lyx.org wrote:
 On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie x...@yihui.name wrote:
 I think that should be enough. A pointer to the knitr manual in
 Help--Specific Manuals--Knitr Manual can be helpful too (I
 remember Liviu mentioned this once).

 Sure, I can do that. Pavel, is that OK? Trunk only?

 BTW, can you export knitr.lyx to LyX2.0 format? Just like I did here:
 https://github.com/yihui/lyx/commit/68c4a7fa78a1ac7e317c783cb415fc21a5ca2705
 Otherwise users may not be able to open this file (\lyxformat 424 is
 too high).

 424 is only for the master branch. knitr.lyx in the 2.0.x branch has
 format 413. I think this is consistent with the other manuals. Am I
 missing something?

 Thanks,

 Scott

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

I think that should be enough. A pointer to the knitr manual in
"Help-->Specific Manuals-->Knitr Manual" can be helpful too (I
remember Liviu mentioned this once).

BTW, can you export knitr.lyx to LyX2.0 format? Just like I did here:
https://github.com/yihui/lyx/commit/68c4a7fa78a1ac7e317c783cb415fc21a5ca2705
Otherwise users may not be able to open this file (\lyxformat 424 is
too high).

Thanks!

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Tue, Oct 16, 2012 at 7:58 PM, Scott Kostyshak  wrote:
>
> OK thanks for the tips. I'm guessing it's OK to update the format in
> trunk when changing the manuals?
>
> I don't think anything in-depth needs to be written there about knitr
> in the Additional manual because knitr already has a "manual" for use
> with LyX. However, it is currently an example. The only thing
> unmanual-like about knitr.lyx is its length, but in my opinion it is
> sufficient as is, especially because a lot that is in the Sweave
> manual applies to knitr.
>
> Attached is a patch to update the Additional manual. Is it OK?
>
> Thanks,
>
> Scott

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie  wrote:
> I think that should be enough. A pointer to the knitr manual in
> "Help-->Specific Manuals-->Knitr Manual" can be helpful too (I
> remember Liviu mentioned this once).

Sure, I can do that. Pavel, is that OK? Trunk only?

> BTW, can you export knitr.lyx to LyX2.0 format? Just like I did here:
> https://github.com/yihui/lyx/commit/68c4a7fa78a1ac7e317c783cb415fc21a5ca2705
> Otherwise users may not be able to open this file (\lyxformat 424 is
> too high).

424 is only for the master branch. knitr.lyx in the 2.0.x branch has
format 413. I think this is consistent with the other manuals. Am I
missing something?

Thanks,

Scott

> Thanks!
>
> Regards,
> Yihui
> --
> Yihui Xie 
> Phone: 515-294-2465 Web: http://yihui.name
> Department of Statistics, Iowa State University
> 2215 Snedecor Hall, Ames, IA
>
>
> On Tue, Oct 16, 2012 at 7:58 PM, Scott Kostyshak  wrote:
>>
>> OK thanks for the tips. I'm guessing it's OK to update the format in
>> trunk when changing the manuals?
>>
>> I don't think anything in-depth needs to be written there about knitr
>> in the Additional manual because knitr already has a "manual" for use
>> with LyX. However, it is currently an example. The only thing
>> unmanual-like about knitr.lyx is its length, but in my opinion it is
>> sufficient as is, especially because a lot that is in the Sweave
>> manual applies to knitr.
>>
>> Attached is a patch to update the Additional manual. Is it OK?
>>
>> Thanks,
>>
>> Scott

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

I see. I did not check out the 2.0.x branch. It is indeed 413 there. Thanks!

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Sat, Oct 20, 2012 at 5:53 PM, Scott Kostyshak  wrote:
> On Sat, Oct 20, 2012 at 6:40 PM, Yihui Xie  wrote:
>> I think that should be enough. A pointer to the knitr manual in
>> "Help-->Specific Manuals-->Knitr Manual" can be helpful too (I
>> remember Liviu mentioned this once).
>
> Sure, I can do that. Pavel, is that OK? Trunk only?
>
>> BTW, can you export knitr.lyx to LyX2.0 format? Just like I did here:
>> https://github.com/yihui/lyx/commit/68c4a7fa78a1ac7e317c783cb415fc21a5ca2705
>> Otherwise users may not be able to open this file (\lyxformat 424 is
>> too high).
>
> 424 is only for the master branch. knitr.lyx in the 2.0.x branch has
> format 413. I think this is consistent with the other manuals. Am I
> missing something?
>
> Thanks,
>
> Scott
>

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
 OK thanks for the tips. I'm guessing it's OK to update the format in
 trunk when changing the manuals?

For additional manual it's OK. IIRC Uwe wanted the manuals under his
maintenance to remain in 2.0.x for easy synchronization.

 Attached is a patch to update the Additional manual. Is it OK?

Yes. Feel free to push similar paragraph to branch.
Pavel

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 17, 2012 at 4:15 AM, Pavel Sanda sa...@lyx.org wrote:
 Scott Kostyshak wrote:
 OK thanks for the tips. I'm guessing it's OK to update the format in
 trunk when changing the manuals?

 For additional manual it's OK. IIRC Uwe wanted the manuals under his
 maintenance to remain in 2.0.x for easy synchronization.

 Attached is a patch to update the Additional manual. Is it OK?

 Yes. Feel free to push similar paragraph to branch.

OK, it's in trunk and branch.

Thanks,

Scott

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
> OK thanks for the tips. I'm guessing it's OK to update the format in
> trunk when changing the manuals?

For additional manual it's OK. IIRC Uwe wanted the manuals under his
maintenance to remain in 2.0.x for easy synchronization.

> Attached is a patch to update the Additional manual. Is it OK?

Yes. Feel free to push similar paragraph to branch.
Pavel

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 17, 2012 at 4:15 AM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> OK thanks for the tips. I'm guessing it's OK to update the format in
>> trunk when changing the manuals?
>
> For additional manual it's OK. IIRC Uwe wanted the manuals under his
> maintenance to remain in 2.0.x for easy synchronization.
>
>> Attached is a patch to update the Additional manual. Is it OK?
>
> Yes. Feel free to push similar paragraph to branch.

OK, it's in trunk and branch.

Thanks,

Scott

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
 On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda sa...@lyx.org wrote:
  Scott Kostyshak wrote:
  On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie x...@yihui.name wrote:
   I'm pretty busy at the moment. I'm wondering if Scott can do it.
 
  Sure, I can do that this weekend. Should it be done for both branch and 
  trunk?
 
  Primarily for trunk, backport to branch would nice though. Pavel
 
 Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

It is usually done just before release. Few related things:
- in trunk use change tracking (again, merged before release)
- for manuals maintained by Uwe 
(http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
  ask for his policies ;)

Pavel

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Tue, Oct 16, 2012 at 6:25 AM, Pavel Sanda sa...@lyx.org wrote:
 Scott Kostyshak wrote:
 On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda sa...@lyx.org wrote:
  Scott Kostyshak wrote:
  On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie x...@yihui.name wrote:
   I'm pretty busy at the moment. I'm wondering if Scott can do it.
 
  Sure, I can do that this weekend. Should it be done for both branch and 
  trunk?
 
  Primarily for trunk, backport to branch would nice though. Pavel

 Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

 It is usually done just before release. Few related things:
 - in trunk use change tracking (again, merged before release)
 - for manuals maintained by Uwe 
 (http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
   ask for his policies ;)

OK thanks for the tips. I'm guessing it's OK to update the format in
trunk when changing the manuals?

I don't think anything in-depth needs to be written there about knitr
in the Additional manual because knitr already has a manual for use
with LyX. However, it is currently an example. The only thing
unmanual-like about knitr.lyx is its length, but in my opinion it is
sufficient as is, especially because a lot that is in the Sweave
manual applies to knitr.

Attached is a patch to update the Additional manual. Is it OK?

Thanks,

Scott


0001-Additional.lyx-references-to-knitr-Sweave-doc.patch
Description: Binary data

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
> On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda  wrote:
> > Scott Kostyshak wrote:
> >> On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie  wrote:
> >> > I'm pretty busy at the moment. I'm wondering if Scott can do it.
> >>
> >> Sure, I can do that this weekend. Should it be done for both branch and 
> >> trunk?
> >
> > Primarily for trunk, backport to branch would nice though. Pavel
> 
> Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

It is usually done just before release. Few related things:
- in trunk use change tracking (again, merged before release)
- for manuals maintained by Uwe 
(http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
  ask for his policies ;)

Pavel

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Tue, Oct 16, 2012 at 6:25 AM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda  wrote:
>> > Scott Kostyshak wrote:
>> >> On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie  wrote:
>> >> > I'm pretty busy at the moment. I'm wondering if Scott can do it.
>> >>
>> >> Sure, I can do that this weekend. Should it be done for both branch and 
>> >> trunk?
>> >
>> > Primarily for trunk, backport to branch would nice though. Pavel
>>
>> Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?
>
> It is usually done just before release. Few related things:
> - in trunk use change tracking (again, merged before release)
> - for manuals maintained by Uwe 
> (http://wiki.lyx.org/LyX/DocumentationDevelopment#toc7),
>   ask for his policies ;)

OK thanks for the tips. I'm guessing it's OK to update the format in
trunk when changing the manuals?

I don't think anything in-depth needs to be written there about knitr
in the Additional manual because knitr already has a "manual" for use
with LyX. However, it is currently an example. The only thing
unmanual-like about knitr.lyx is its length, but in my opinion it is
sufficient as is, especially because a lot that is in the Sweave
manual applies to knitr.

Attached is a patch to update the Additional manual. Is it OK?

Thanks,

Scott


0001-Additional.lyx-references-to-knitr-Sweave-doc.patch
Description: Binary data

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda sa...@lyx.org wrote:
 Scott Kostyshak wrote:
 On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie x...@yihui.name wrote:
  I'm pretty busy at the moment. I'm wondering if Scott can do it.

 Sure, I can do that this weekend. Should it be done for both branch and 
 trunk?

 Primarily for trunk, backport to branch would nice though. Pavel

Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

Scott

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Thu, Oct 11, 2012 at 11:03 AM, Pavel Sanda  wrote:
> Scott Kostyshak wrote:
>> On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie  wrote:
>> > I'm pretty busy at the moment. I'm wondering if Scott can do it.
>>
>> Sure, I can do that this weekend. Should it be done for both branch and 
>> trunk?
>
> Primarily for trunk, backport to branch would nice though. Pavel

Currently the manuals on trunk say 2.0.x at the top. Why don't they say 2.1?

Scott

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie x...@yihui.name wrote:
 I'm pretty busy at the moment. I'm wondering if Scott can do it.

Sure, I can do that this weekend. Should it be done for both branch and trunk?

Scott

 Regards,
 Yihui
 --
 Yihui Xie xieyi...@gmail.com
 Phone: 515-294-2465 Web: http://yihui.name
 Department of Statistics, Iowa State University
 2215 Snedecor Hall, Ames, IA


 On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda sa...@lyx.org wrote:
 Kayvan Sylvan wrote:
 So I fixed the documentation (patch attached) and I now have a perfectly
 working solution for using LyX and noweb for literate programming.

 Please apply my patch and we can just close ticket 5444.

 Note that the Customization.lyx file had Change Tracking enabled, so I left
 it on. Someone will have to accept the changes after applying this patch.

 It is now in.
 BTW we still do not have a word about knitr in Additional manual.
 Yihui, what about add few paragraphs there?

 Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
 On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie x...@yihui.name wrote:
  I'm pretty busy at the moment. I'm wondering if Scott can do it.
 
 Sure, I can do that this weekend. Should it be done for both branch and trunk?

Primarily for trunk, backport to branch would nice though. Pavel

Re: Noweb/Literate programming Copier problem

[Scott Kostyshak]

On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie  wrote:
> I'm pretty busy at the moment. I'm wondering if Scott can do it.

Sure, I can do that this weekend. Should it be done for both branch and trunk?

Scott

> Regards,
> Yihui
> --
> Yihui Xie 
> Phone: 515-294-2465 Web: http://yihui.name
> Department of Statistics, Iowa State University
> 2215 Snedecor Hall, Ames, IA
>
>
> On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda  wrote:
>> Kayvan Sylvan wrote:
>>> So I fixed the documentation (patch attached) and I now have a perfectly
>>> working solution for using LyX and noweb for literate programming.
>>>
>>> Please apply my patch and we can just close ticket 5444.
>>>
>>> Note that the Customization.lyx file had Change Tracking enabled, so I left
>>> it on. Someone will have to accept the changes after applying this patch.
>>
>> It is now in.
>> BTW we still do not have a word about knitr in Additional manual.
>> Yihui, what about add few paragraphs there?
>>
>> Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Scott Kostyshak wrote:
> On Wed, Oct 10, 2012 at 8:48 PM, Yihui Xie  wrote:
> > I'm pretty busy at the moment. I'm wondering if Scott can do it.
> 
> Sure, I can do that this weekend. Should it be done for both branch and trunk?

Primarily for trunk, backport to branch would nice though. Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Kayvan Sylvan wrote:
 So I fixed the documentation (patch attached) and I now have a perfectly
 working solution for using LyX and noweb for literate programming.
 
 Please apply my patch and we can just close ticket 5444.
 
 Note that the Customization.lyx file had Change Tracking enabled, so I left
 it on. Someone will have to accept the changes after applying this patch.

It is now in.
BTW we still do not have a word about knitr in Additional manual.
Yihui, what about add few paragraphs there?

Pavel

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

I'm pretty busy at the moment. I'm wondering if Scott can do it.

Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda sa...@lyx.org wrote:
 Kayvan Sylvan wrote:
 So I fixed the documentation (patch attached) and I now have a perfectly
 working solution for using LyX and noweb for literate programming.

 Please apply my patch and we can just close ticket 5444.

 Note that the Customization.lyx file had Change Tracking enabled, so I left
 it on. Someone will have to accept the changes after applying this patch.

 It is now in.
 BTW we still do not have a word about knitr in Additional manual.
 Yihui, what about add few paragraphs there?

 Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Kayvan Sylvan wrote:
> So I fixed the documentation (patch attached) and I now have a perfectly
> working solution for using LyX and noweb for literate programming.
> 
> Please apply my patch and we can just close ticket 5444.
> 
> Note that the Customization.lyx file had Change Tracking enabled, so I left
> it on. Someone will have to accept the changes after applying this patch.

It is now in.
BTW we still do not have a word about knitr in Additional manual.
Yihui, what about add few paragraphs there?

Pavel

Re: Noweb/Literate programming Copier problem

[Yihui Xie]

I'm pretty busy at the moment. I'm wondering if Scott can do it.

Regards,
Yihui
--
Yihui Xie 
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA


On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda  wrote:
> Kayvan Sylvan wrote:
>> So I fixed the documentation (patch attached) and I now have a perfectly
>> working solution for using LyX and noweb for literate programming.
>>
>> Please apply my patch and we can just close ticket 5444.
>>
>> Note that the Customization.lyx file had Change Tracking enabled, so I left
>> it on. Someone will have to accept the changes after applying this patch.
>
> It is now in.
> BTW we still do not have a word about knitr in Additional manual.
> Yihui, what about add few paragraphs there?
>
> Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Kayvan Sylvan wrote:
 I'm running LyX 2.1.0 SVN on Fedora 17

Are you aware that for long time we use git and SVN is months old codebase?
Pavel

Re: Noweb/Literate programming Copier problem

[Kayvan Sylvan]

Yes. I pulled from git, but the software still identifies itself as 2.1.0
SVN.

On Mon, Sep 24, 2012 at 12:20 PM, Pavel Sanda sa...@lyx.org wrote:

 Kayvan Sylvan wrote:
  I'm running LyX 2.1.0 SVN on Fedora 17

 Are you aware that for long time we use git and SVN is months old codebase?
 Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Kayvan Sylvan wrote:
 Yes. I pulled from git, but the software still identifies itself as 2.1.0
 SVN.

Hummm, I thought we already changed this, will change it now.
Pavel

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Kayvan Sylvan wrote:
> I'm running LyX 2.1.0 SVN on Fedora 17

Are you aware that for long time we use git and SVN is months old codebase?
Pavel

Re: Noweb/Literate programming Copier problem

[Kayvan Sylvan]

Yes. I pulled from git, but the software still identifies itself as 2.1.0
SVN.

On Mon, Sep 24, 2012 at 12:20 PM, Pavel Sanda  wrote:

> Kayvan Sylvan wrote:
> > I'm running LyX 2.1.0 SVN on Fedora 17
>
> Are you aware that for long time we use git and SVN is months old codebase?
> Pavel
>

Re: Noweb/Literate programming Copier problem

[Pavel Sanda]

Kayvan Sylvan wrote:
> Yes. I pulled from git, but the software still identifies itself as 2.1.0
> SVN.

Hummm, I thought we already changed this, will change it now.
Pavel

Re: Noweb/Literate programming Copier problem

[Kayvan Sylvan]

Okay... I looked at the code and figured out that there are additional $$
macros (in Converter.cpp) that are not documented.

So I fixed the documentation (patch attached) and I now have a perfectly
working solution for using LyX and noweb for literate programming.

Please apply my patch and we can just close ticket 5444.

Note that the Customization.lyx file had Change Tracking enabled, so I left
it on. Someone will have to accept the changes after applying this patch.

Thanks!

On Sun, Sep 23, 2012 at 1:40 PM, Kayvan Sylvan kayvansyl...@gmail.comwrote:

 I'm running LyX 2.1.0 SVN on Fedora 17

 Looking at http://www.lyx.org/trac/ticket/5444 (noweb build-program
 process broken), I'm trying to figure out where the Copier is supposed to
 be executed.

 I had a different idea about how to handle the issue:

 What if when the build-program external script is run, LyX sets an
 environment variable to the original directory of the file that is being
 edited.

 For example, I edit /home/kayvan/src/xyz/foo.lyx and when I execute
 build-program, LyX would setenv LYX_FILE_DIR to /home/kayvan/src/xyz and
 execute build-script.
 This would allow the code in the build-script scrap to output the files it
 tangles to $LYX_FILE_DIR (and the temporary directory that LyX uses
 wouldn't matter).

 Alternately, we can add another special macro to the following list (from
 the Customization manual section on Copiers):

 $$s The LyX system directory (e. g. /usr/share/lyx).
 $$i The input file
 $$o The output file
 $$l The `LaTeX name'

 $$d The original directory for the LyX file being edited.

 This would then allow us to run the build-script with two arguments: $$i
 and $$d and the build-script scrap can handle putting the files in the
 right directory without needing to run a Converter.

 What do you all think?

 If I want to make this work, which files do I need to change?

 Thanks!

 ---Kayvan





DOC-DIFFS.patch
Description: Binary data

Re: Noweb/Literate programming Copier problem

[Kayvan Sylvan]

Okay... I looked at the code and figured out that there are additional $$
macros (in Converter.cpp) that are not documented.

So I fixed the documentation (patch attached) and I now have a perfectly
working solution for using LyX and noweb for literate programming.

Please apply my patch and we can just close ticket 5444.

Note that the Customization.lyx file had Change Tracking enabled, so I left
it on. Someone will have to accept the changes after applying this patch.

Thanks!

On Sun, Sep 23, 2012 at 1:40 PM, Kayvan Sylvan wrote:

> I'm running LyX 2.1.0 SVN on Fedora 17
>
> Looking at http://www.lyx.org/trac/ticket/5444 ("noweb build-program
> process broken"), I'm trying to figure out where the Copier is supposed to
> be executed.
>
> I had a different idea about how to handle the issue:
>
> What if when the build-program external script is run, LyX sets an
> environment variable to the original directory of the file that is being
> edited.
>
> For example, I edit /home/kayvan/src/xyz/foo.lyx and when I execute
> build-program, LyX would setenv LYX_FILE_DIR to "/home/kayvan/src/xyz" and
> execute "build-script".
> This would allow the code in the build-script scrap to output the files it
> tangles to $LYX_FILE_DIR (and the temporary directory that LyX uses
> wouldn't matter).
>
> Alternately, we can add another special macro to the following list (from
> the Customization manual section on Copiers):
>
> $$s The LyX system directory (e. g. /usr/share/lyx).
> $$i The input file
> $$o The output file
> $$l The `LaTeX name'
>
> $$d The original directory for the LyX file being edited.
>
> This would then allow us to run the build-script with two arguments: $$i
> and $$d and the build-script scrap can handle putting the files in the
> right directory without needing to run a Converter.
>
> What do you all think?
>
> If I want to make this work, which files do I need to change?
>
> Thanks!
>
> ---Kayvan
>
>
>


DOC-DIFFS.patch
Description: Binary data