fixr opens a function, (or text object, or general object) in your preferred text editor. Control returns immediately to the R command line, so you can keep working in R and can be editing several functions/objects simultaneously (cf edit). A session-duration list of objects being edited is maintained, so that each object can be easily sourced back into its rightful workspace. These objects will be updated automatically on file-change if you've run autoedit( TRUE), or manually by calling FF(). There is an optional automatic text backup facility. readr also opens a file in your text editor, but in read-only mode, and doesn't update the backups or the list of objects being edited. fixtext is a shorthand form for forcing creation of a text object rather than the default of a function. For non-function and non-text objects, see separate section below.# Usually: fixr( x) or fixr( x, new.doc=T)
fixr( x, new=FALSE, install=FALSE, what, fixing, pkg=NULL, character.only=FALSE, new.doc=FALSE)
# fixtext really has exact same args as fixr, but technically its args are:
fixtext( x, ...)
# Usually: readr( x) but exact same args as fixr
readr( x, ...)
FF() # manual check and update
autoedit( do=TRUE) # stick this line in your .Firstmypack$myfun, or mypack::myfun, or mypack:::myfun, or ..mypack$myfun, to simultaneously set the pkgx is treated as a string naming the object to be edited, rather than the unquoted object name.add.flatdoc.to..GlobalEnv unless argument pkg is set.x, then fixr creates an empty function template by default. Set what="" to create an empty character vector instead-- or just use fixtext.maintain.packages) x should be looked for.what in fixtext, and fixing in readr, are passed to fixr.fixr can edit general objects, within reason; more precisely, it can edit the R code that generates them. Some useful examples are:
glm;fixr to create a new general object, then all is easy: just replace the function template that appears in the text editor. But if you want to use fixr to edit a general object that wasn't created with fixr, you may find that fixr balks because it can't cat the object; it depends on the mode of the object. If you hit problems with your object myobj, then first set the source attribute manually, for example like this:
attr( myobj, 'source') <- deparse( myobj) # or print( myobj)...
# ...or something that displays roughly what you want
fixr( myobj)
Note that you are writing R code in the text editor, and it will be executed immediately when it is sourced back in (by source.mvb). If you just want to set up a delayed function call, for example, be sure to wrap it in expression() or quote() to avoid immediate evaluation.fixr is run for the first time (or if you set install=TRUE), it will ask you for some basic information about your text editor. In particular, you'll need to know what to type at a command prompt to invoke your text editor on a specific file; in Windows, you can usually find this by copying the Properties/Shortcut/Target field of a shortcut, followed by a space and the filename. After supplying these details, fixr will launch the editor and print a message showing some options ("backup.fix", "edit.scratchdir" and "program.editor"), that will need to be set in your .First. function. You should now be able to do that via fixr(.First).
Changes to the temporary files used for editing can be checked for automatically whenever a valid R command is typed (e.g. by typing 0autoedit() once per session, e.g. in your .First. The manual version of this is FF(). If any file changes are detected, the code is sourced back in and the appropriate function(s) are modified. FF tries to write functions back into the workspace they came from, which might not be .GlobalEnv. If not, you'll be asked whether you want to save.image that workspace (provided it's a task-- see cd). FF should still put the function in the right place, even if you've called cd after calling fixr (unless you've detached the original task) or if you moved it.
readr requires a similar installation process. To get the read-only feature, you'll need to add some kind of option/switch on the command line that invokes your text editor; not all text editors support this feature. Similarly to fixr, you'll need to set options( program.reader=<>) in your .First; the installation process will tell you what to use.
fixr, and of course fixtext, will also edit character vectors. If the object to be edited exists beforehand and has a class attribute, fixr will not change its class; otherwise, the class will be set to "cat". This means that print invokes the print.cat method, which displays text more readably than the default. Any other attributes on character vectors are stripped.
fixr creates a blank function template if the object doesn't exist already, or if new=TRUE. If you want to create a new character vector as opposed to a new function, call fixtext, or equivalently set what="" when you call fixr.
If the function has attributes, it's wrapped in a structure(...) construct. If a doc attribute exists, it's printed as free-form text at the end of the file, and the call to structure will end with a line similar to:
,doc=flatdoc( EOF="<doc attribute, which can be displayed by help. If you want to add plain-text documentation, you can also add these lines yourself-- see flatdoc. Calling fixr( myfun, new.doc=TRUE) sets up a documentation template that you can fill in, ready for later conversion to Rd format in a package (see mvbutils.packaging.tools).
If the function was being mtraced (see help(package=debug)), FF will re-apply mtrace after loading the edited version.
If there is a problem with parsing, the source attribute of the function is updated to the new code, but the function body is invisibly replaced with a stop call, stating that parsing failed.
The list of functions being edited by fixr is stored in the variable fix.list in the mvb.session.info environment. When you quit and restart R, the function files you have been using will stay open in the editor, but fix.list will be empty; hence, updating the file "myfun.r" will not update the corresponding R function. If this happens, just type fixr(myfun) in R and when your editor asks you if you want to replace the on-screen version, say no. Save the file again (some editors require a token modification, such as space-then-delete, first) and R will notice the update.
An automatic text backup facility is available from fixr: see ?get.backup. The backup system also allows you to sort functions by edit date; see ?fix.order. Backup currently only works for functions and character objects..First, edit, cd, get.backup, fix.order, move