blocks|key|4484636|text|我想这就是你要找的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4484637|file.copy(sys.frame(1)$ofile,
++++++++++to+=+file.path(dirname(sys.frame(1)$ofile),
+++++++++++++++++++++++++paste0(Sys.Date(),+".R")))|code-block|syntax|javascript|4484638|这将获取当前文件并将其复制到同一目录中名为currentDate.R的新文件中，例如2015-07-14.R|offset|length|style|CODE|4484639|如果要复制到工作目录而不是原始脚本目录，请使用|4484640|file.copy(sys.frame(1)$ofile,
++++++++++to+=+file.path(getwd(),
+++++++++++++++++++++++++paste0(Sys.Date(),+".R")))|4484641|只需注意，sys.frame(1)$ofile只有在保存的脚本是源代码的情况下才能工作，尝试在终端中运行它将失败。值得一提的是，这可能不是最佳实践。也许研究一下版本控制系统会更好。|4484642|解释：|4484643|顺便说一句，我可能不是解释这一点的最佳人选(我从某个地方复制了这个想法，有时也会用到它)，但我会尝试一下。基本上，为了获得有关脚本文件的信息，R需要将其作为一个包含该信息的环境中的文件运行，并且当该环境是一个source调用时，它包含ofile数据。我们使用(1)来选择全局环境(即0)之后的下一个(source())环境。当你从终端运行这个环境时，除了全局(这就是错误信息)，没有其他的框架/环境，因为没有文件正在运行--命令直接发送到终端。|4484644|为了说明这一点，我们可以做一个简单的测试：|4484645|>+sys.frame(1)
Error+in+sys.frame(1)+:+not+that+many+frames+on+the+stack|4484646|但是如果我们从另一个函数调用它：|4484647|>+myf+<-+function()+sys.frame(1)
>+myf()
<environment:+0x0000000013ad7638>|4484648|我们函数的环境中没有任何内容，因此它是存在的，但在本例中没有ofile|4484649|>+myf+<-+function()+names(sys.frame(1))
>+myf()
character(0)|4484650|entityMap^0|0|0|16|C|0|0|0|5|I|0|0|2W|6|39|5|3L|3|3X|1|46|8|0|0|0|0|0|U|5|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@$I|1D|J|1E|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1H|8|@$I|1I|J|1J|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1L|8|@$I|1M|J|1N|K|L]|$I|1O|J|1P|K|L]|$I|1Q|J|1R|K|L]|$I|1S|J|1T|K|L]|$I|1U|J|1V|K|L]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|1X|8|@]|9|@]|A|$E|F]]|$1|10|3|11|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|12|3|13|5|D|7|1Z|8|@]|9|@]|A|$E|F]]|$1|14|3|15|5|6|7|20|8|@$I|21|J|22|K|L]]|9|@]|A|$]]|$1|16|3|17|5|D|7|23|8|@]|9|@]|A|$E|F]]|$1|18|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|19|$]]

I think this is what you're looking for:

<pre><code>file.copy(sys.frame(1)$ofile,
 to = file.path(dirname(sys.frame(1)$ofile),
 paste0(Sys.Date(), ".R")))
</code></pre>

This will take the current file and copy it to a new file in the same directory with the name of currentDate.R, so for example <code>2015-07-14.R</code>

If you want to copy to the working directory instead of the original script directory, use

<pre><code>file.copy(sys.frame(1)$ofile,
 to = file.path(getwd(),
 paste0(Sys.Date(), ".R")))
</code></pre>

Just note that the <code>sys.frame(1)$ofile</code> only works if a saved script is sourced, trying to run it in terminal will fail. It is worth mentioning though that this might not be the best practice. Perhaps looking into a version control system would be better.

Explanation:

TBH, I might not be the best person to explain this (I copied this idea from somewhere and use it sometimes), but I'll try. Basically in order to have information about the script file R needs to be running it as a file inside an environment with that information, and when that environment is a <code>source</code> call it contains the <code>ofile</code> data. We use <code>(1)</code> to select the next (<code>source()</code>'s) environment following the global environment (which is <code>0</code>). When you're running this from terminal, there's no frame/environment other than Global (that's the error message), since no file is being ran - the commands are sent straight to terminal.

To illustrate that, we can do a simple test:

<pre><code>&gt; sys.frame(1)
Error in sys.frame(1) : not that many frames on the stack
</code></pre>

But if we call that from another function:

<pre><code>&gt; myf &lt;- function() sys.frame(1)
&gt; myf()
&lt;environment: 0x0000000013ad7638&gt;
</code></pre>

Our function's environment doesn't have anything in it, so it exists but, in this case, does not have <code>ofile</code>:

<pre><code>&gt; myf &lt;- function() names(sys.frame(1))
&gt; myf()
character(0)
</code></pre>

blocks|key|4484672|text|我只想添加我的解决方案，因为我决定在执行复制命令之前使用try函数……因为我有种感觉我错过了一些控制...|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4484673|try({
++script_name+<-+sys.frame(1)$ofile
++copy_script_name+<-+
++++paste0(sub('\\.R',+'',+basename(script_name)),
+++++++++++'_',
+++++++++++format(Sys.time(),+'%25Y%25m%25d%25H%25M%25S'),
+++++++++++'.R')
++file.copy(script_name,
++++++++++++copy_script_name)
})|code-block|syntax|javascript|4484674|这会将脚本复制到当前目录中，并为文件名添加一个时间戳。如果出现错误，脚本的其余部分仍将执行。|4484675|entityMap^0|S|3|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

I just wanted to add my solution since I decided to use a <code>try</code> function before executing the copy command... Because I have the feeling I miss some control...

<pre><code>try({
 script_name &lt;- sys.frame(1)$ofile
 copy_script_name &lt;- 
 paste0(sub('\\.R', '', basename(script_name)),
 '_',
 format(Sys.time(), '%Y%m%d%H%M%S'),
 '.R')
 file.copy(script_name,
 copy_script_name)
})
</code></pre>

This will copy the script into the current directory and also adds a timestamp to the filename. In case something goes wrong, the rest of the script will still execute.

Is there a possibility to copy the executed lines or basically the script into the working directory?

So my normal scenario is, I have stand alone script which just need to be sourced within a working directory and they will do everything I need.
After a few month, I made update to these scripts and I would love to have a snapshot from the script when I executed the source...

So basically <code>file.copy(ITSELF, '.')</code> or something like this.

Copy script after executing

版本控制系统

是否有可能将执行的行或脚本复制到工作目录中？所以我的正常场景是，我有一个独立的脚本，它只需要在一个工作目录中获得源代码，他们会做我需要的一切。几个月后，我对这些脚本进行了更新，当我执行源代码时，我希望从脚本中获得快照……所以基本上就是file.copy(ITSELF, '.')或者类似的东西。

问执行后复制脚本
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问执行后复制脚本EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问执行后复制脚本
EN