从SublimeText2中的另一个构建系统访问构建系统-AccessabuildsystemfromanotherbuildsysteminSublimeText2

4  

This is a patch to two files in the LatexTools plugin in order to deal with Rnw files, and one patch to the Latex plugin in order to make Rnw files to behave like LaTeX files.

这是LatexTools插件中的两个文件的补丁，用于处理Rnw文件，以及Latex插件的一个补丁，以使Rnw文件的行为类似于LaTeX文件。

First the patch to the Latex plugin, in specific to the file LaTeX.tmLanguage:

首先是Latex插件的补丁，具体到文件LaTeX.tmLanguage：

    fileTypes
    
        tex
        Rnw
    

Observe how I added an element to the array in order to deal with Rnw extensions.

观察我如何向数组添加元素以处理Rnw扩展。

Now the patch to makePDF.py

现在补丁makePDF.py

look for a a line like this

寻找像这样的一条线

if self.tex_ext.upper() != ".TEX":
    sublime.error_message("%s is not a TeX source file: cannot compile." % (os.path.basename(view.file_name()),))
    return

and replace it with

并替换它

if (self.tex_ext.upper() != ".TEX") and (self.tex_ext.upper() != ".RNW"):
    sublime.error_message("%s is not a TeX or Rnw source file: cannot compile." % (os.path.basename(view.file_name()),))
    return

Then look for a line like

然后寻找像这样的一条线

os.chdir(tex_dir)
CmdThread(self).start()
print threading.active_count()

and replace it with

并替换它

os.chdir(tex_dir)
if self.tex_ext.upper() == ".RNW":
    # Run Rscript -e "library(knitr); knit('" + self.file_name + "')"
    os.system("Rscript -e \"library(knitr); knit('"+ self.file_name +"')\"")
    self.file_name = self.tex_base + ".tex"
    self.tex_ext = ".tex"
CmdThread(self).start()
print threading.active_count()

The last patch is to the file jumpToPDF.py

最后一个补丁是文件jumpToPDF.py

look for a line

寻找一条线

if texExt.upper() != ".TEX":
    sublime.error_message("%s is not a TeX source file: cannot jump." % (os.path.basename(view.fileName()),))
    return

and replace it with

并替换它

if (texExt.upper() != ".TEX") and (texExt.upper() != ".RNW"):
    sublime.error_message("%s is not a TeX or Rnw source file: cannot jump." % (os.path.basename(view.fileName()),))
    return

Good luck!

祝你好运！

1  

Thanks for the detailed description of the required changes Herberto!

感谢Herberto所需更改的详细说明！

I just went ahead and changed the mentioned files. Everything works like a charm! One thing is though, not sure if it is required, but I recompiled both python files to .pyc after editing them.

我刚才继续改变了上面提到的文件。一切都像魅力一样！但有一点是，不确定是否需要，但我在编辑后将两个python文件重新编译为.pyc。

python -m py_compile makePDF.py

does the job. Should anyone run into an "invalid syntax error" at the line

做的工作。如果有人在该行遇到“无效的语法错误”

print threading.active_count()

while recompiling, just replace it with:

重新编译时，只需将其替换为：

print(threading.active_count())

Also, since the log parser of LaTeXTools only displays errors from the log files, we might be interested to see the knitr output as well. You can store it in a separate log file by replacing:

此外，由于LaTeXTools的日志解析器仅显示日志文件中的错误，我们可能也有兴趣看到knitr输出。您可以通过替换来将其存储在单独的日志文件中：

os.system("Rscript -e \"library(knitr); knit('"+ self.file_name +"')\"")

with:

有：

    knitcmd = "/usr/bin/Rscript -e \"library(knitr); knit('"+ self.file_name +"')\""
    process = subprocess.Popen(knitcmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE, shell=True)
    #Launch the shell command:
    knit_output, knit_error = process.communicate()
    #store results in a log
    knit_log = open(self.tex_base + "_knitrbuild.log", "w")
    knit_log.write(knit_output)
    knit_log.write(knit_error)
    knit_log.close()

Before I was using a simple bash script to build the documents (Mac specific):

在我使用简单的bash脚本构建文档之前（特定于Mac）：

#!/bin/bash
[ $# -eq 0 ] && { echo "Usage: $0 file.Rnw for knitting"; exit 1; }
rnw="library(knitr);knit("\'"$1.Rnw"\'")"
echo "Rscript executing:" $rnw
tex="$1.tex"
pdf="$1.pdf"
Rscript -e $rnw && pdflatex $tex && pdflatex $tex && open -a Preview $pdf

retval=$?
[ $retval -eq 0 ] && echo "$rnw knitted and $pdf ready"

but being able to customize LaTeXTools and run it directly from ST2 with Skim support is very nice.

但能够自定义LaTeXTools并直接从ST2运行它与Skim支持是非常好的。

Is there any reasons why you wouldn't want to add the changes you outlined directly into your package source? (maybe my it's only my version that's too old.)

您是否有任何理由不想将您概述的更改直接添加到包源中？ （也许我只是我的版本太旧了。）