Thanks Hadley...
I am hoping that a Sweave-based solution is also found...
It appears that a number of people on the list have some great ideas on possible Sweave-based approaches... This would enable portability of code..
danstan
On Jul 6, 2006, at 6:38 AM, hadley wickham wrote:
I have been working a little bit on a replacement for Sweave that does not have the intermediate step (it embeds the r output directly into the latex file, rather like cog), and so doesn't have these problems.
If anyone is interested I could send them a copy of the package.
Hadley
On 7/4/06, xolela@mac.com xolela@mac.com wrote:
I am not sure if this is the correct place to post this request
I am using the combination of the Latex, Sweave & R Textmate bundles for my project.
My main project fie is a latex file which calls include files that are tex files created by Sweave. Essentially, I do almost all the work in the Sweave mode which compiles my main tex file when I CMB-B it. My problem is that when I CMD-click my synched TeXniscope file I end up being taken to the intermediate (tex) file that Sweave created. Since this looks so similar to my sweave file I at times end up editing that tex file rather than the sweave equivalent (snw) when in reality I should be in the Sweave as the true source to edit.
Is it possible for the TeXniscope sync to go to the Sweave (snw) source file rather than the tex equivalent in this case?
Thanks in advance.
Danstan
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate