How could I use the folding of latex-suite, when editing a Rnw-files?

I tried :

• set filetype=tex
• set foldmethod=marker
• runtime ftplugin/tex_latexSuite

But I didn't get it running.

When editing Rmd-files I usually do

• set ft=rmd, while editing r-chunks
• set ft=pandoc, while editing surrounding text

A similar strategy when editing Rnw-files doesn't apply; somehow the folding
is not reactivated.

Hi! This is more of a feature request than an issue. I'm not sure how hard it is to implement:

When working on an Rmd or Rnw document and having a cursor somewhere in the file
it would be convinient to be able to send all the preceding R code chunks to R. Currently, I do it manually by going from the top and using default '\cd' shortcut, which is a bit tiresome on larger files.

He

I get the following output (instead of the validation) in the R console when sending a vizual selection from vim to R in a tmux session:

base::source("/tmp/r-plugin-myname/Rsource-25313-filename.r")

Sending a single line works fine.

Best Claas

When initiating a new R session via Vim-R, I always see the following error in the R console: "bind failed with error 10048". However, it doesnt seem to hinder any functionality, and I am able to send commands to it via Vim without any issues.

I have the following code in the .Rprofile file:

if(interactive())
{
    library(vimcom)
}

Windows 7 / R 2.15.1 64-bit / Python 2.7.3 32-bit / Stock version of Vim 7.3 + latest version of Vimcom and Vim-R-plugin

Hi,

I'm opening this issue to ask you to continue the support to GNU Screen.
While I completely get why tmux is a better option in many respects, Screen is still the de facto terminal multiplexer on many systems, including pretty much all the servers I ssh'ed to. More often than not, tmux is not even installed on remote servers in both academic and industrial environments.

Not only that, but in some circumstances Screen is the only option. I have no option but to use Windows at work and I used to be pretty happy with my Cygwin + Vim + Vim-R-plugin setup. Since you dropped Screen support however, it's been a hell, as Cygwin can't possibly (and probably never will) support tmux.

I have no idea how much of a burden is to provide support for Screen along with tmux but I, and I guess many other users with me, would be extremely grateful if you could do it. My best option at the moment is probably to switch to Rstudio, which I'd really rather not to.

Thank you.

I personally enjoy using rainbow parentheses (https://github.com/kien/rainbow_parentheses.vim). However, when editing an Rnw or Rmd file, I do not get the rainbow parentheses in the code blocks. Outside of code blocks, the parentheses are appropriately colored. I am hoping you can take a look at this issue and address it or if not, point me in a direction so that I can see if I can figure out the issue. Thanks so much!

This is not a bug report. It's an information to prevent bug reports.

The plugin now has a new behavior. The terminal will only be split in two regions if Vim is already running inside of a Tmux session. Otherwise, R will start in a external terminal emulator. Please, read "issue" #52 for details.

This is not a bug.

The integration of the Vim-R-plugin with GNU Screen, VimShell, Conque Shell and screen plugin was removed on commit 4226112

The main user visible consequence is that the terminal will be split in two regions by Tmux only if Vim already is in a Tmux session. One suggestion is to put in the ~/.bashrc:

if [ "x$DISPLAY" == "x" ]
then
    function tvim(){ tmux new-session "vim $@" ; }
else
    alias vim='vim --servername VIM'
    function tvim(){ tmux -2 new-session "TERM=screen-256color vim --servername VIM $@" ; }
fi

and then type "tvim" in the terminal to start Vim. The Vim argument --servername ANYNAME is required to get the Object Browser automatically updated when R Workspace changes.

As I have said in the commit comment: The maintenance of so many different ways of running R and sending commands to it was very complicated and was a source of bugs. People wanting integration between the Vim-R-plugin and GNU Screen, VimShell and Conque Shell will have to write extensions to the Vim-R-plugin (vimrplugin_source).

First of all, excellent plugin. I spend a lot of time using it and I really like it!

Lately, I have been writing more R-Markdown files and therefore also more R code in rmd. One annoyance that I haven't been able to solve is that my vim highlighting as well as completion stop for dots in the variable names.

So two what I think related symptoms of this: You have a variable my.var.

1. You indent to search for occurrences of this variable and press * over my. Only my is searched for and highlighted.
2. You try to use supertab to find the local variable after typing my, it only expands to my.

Note that the behaviour in an R file is as expected, ie my.var is highlighted and tab expands to my.var.

Thanks
Sergiusz

Is anyone working on Rmd (Rnw for markdown) integration from the knitr-package?

I'm developing an R package using devtools and roxygen. This lets me auto-generate my .Rd files from specially formatted comments in the source .R files.

The problem is that certain backslash-letter combinations get interpreted as commands, when all I want to do is enter text. For example, \dquote activates \d, \link activates \l, etc. This is extremely frustrating: instead of
\dQuote{text}
I have to write
dQuote<esc>bi\<esc>ea{text}

Can the backslash commands be disabled for insert-mode? Or if this disrupts other people's workflow: can it at least be made optional?

Thanks :)

This is not a bug, I'm trying to debug a faulty installation and get the message
in the title when I hit F2 to get R going after tmux; vim foo.R. The annoying thing
is that this works perfectly on my laptop, and after trying (obviously unsuccessfully)
to get the setups aligned on my desktop I get the message above on the desktop
machine instead of the window splitting and R starting up. Both machines are mac
running 10.7 on the desktop and 10.8 on the laptop. Any suggestions for what to
look for would be much appreciated. I've looked at the output of :scriptnames
on both systems and don't see anything too different except that the laptop has
a line that begins: /private/var/folders... which doesn't appear on the desktop.
Thanks!

Hello,

Would it be possible to add an option to display R code chunks with a different background color than the rest of the document?

This would make it easy to quickly find the code chunks within an R markdown or similar file.

During package development I often need to restart the R session (as R cannot unload a library w/o side effects). I've tried to write this myself, but with no success (either starts or quits, but not both):

function! RestartR()
    if exists("g:ScreenShellSend") || exists("*RBrSendToR")
        call RQuit("no")
        sleep
    endif
    call StartR("R")
endfunction

Can you help me get this working? Maybe you want to include this in the plugin? Otherwise I'll add this to the devtools plugin.

It seems like RStudio can run inside of a tmux process. Is it correct that you could get basic "send command to R" functionality by changing the command that is called to launch R?

Hello, I am finding that I am unable to knit and PDF (\kp) nor any of the assorted knit commands. The only knit command that does work for me is knit (\kn). I first noticed this issue in the stable (vimscripts) release and have the same issue here, in the development branch.

When I try to use these commands there is no response. I know that this once worked for some release of Vim-R-plugin and vimcom, but unfortunately, I am not sure what combination that was. I have recently reinstalled my operating system (linux) and am finding that the latest releases do not work. I am finding that release 0.9.7 does produce action when I type \kp but it does not seem to work with the current release of vimcom as R complains it cannot find vim.interlace. In release 0.9.8, I do not get any response by typing \kp.

Let me know if I can do more to help.

Windows 7 professional
R 3.0.1 x64
gVIM 7.3.46
python 3.1.4 (32 bit)

When a .R file is loaded, I got the error:
"Could not find R path in Windows Registry. Please, either install R or set the value of 'vimrplugin_r_path."

I tried the following but none corrected the issue:
Checked that the R path is in the Windows registry (both 32 and 64 bit).
Put in the statement in either .vimsrc or windows.py:
let vimrplugin_r_path="C:\Program Files\R\R-3.0.1"
Commented out the statement in windows.py (based on a previous thread):
rpath=rpath.replace("","\")

I know nothing about programming in python or vims, so I'm hesitant to try anything more substantial. Anyone has encountered the same problem?

Thanks,
Ying

Sorry for a mere user question, but I cannot find another forum for it.

I recently upgraded my very old vim-r-plugin and discovered to my unpleasant surprise that the current version use separate R processes and screen sessions for each vim process. I often work with several gvim windows open and want to them all to share the same process and screen session, but despite my best efforts I can't figure out to configure the plugin to do so.

Previously there was an option called vimrplugin_single_r for switching between single or separate processes (as of the 101217 version), but I cannot find it anymore. Is there still an equivalent to it?

I just upgraded the plugin from version 110222 (as mentioned in the beginning of the help file) to 0.9.9.2. Now the plugin takes a LOT more time to start when I open an R file. Opening R file used to happen instantly, now it takes around 3 seconds, which is very annoying, especially when you open a close a lot files all the time when developing.

Any idea what might be causing it?

I upgraded the package just by copying over the new files over the old ones. Should I delete some files too?

Thanks.

I have a problem with autocompletion, it works normally until I run some code from the editor, for example using \ss. After this, when trying to autocomplete with Ctrl-X Ctrl-O , I get the following error:

VimCom Port not found. Error detected while processing function rcomplete#CompleteR..BuildOmniList: line 19: E121: Undefined variable: g:rplugin_lastrpl Press ENTER or type command to continue Error detected while processing function rcomplete#CompleteR..BuildOmniList: line 19: E15: Invalid expression: g:rplugin_lastrpl == "R is busy." Press ENTER or type command to continue

After this autocompletion continues working normally, until I send some lines to R again.

Rmd format allows to insert general code blocks like

there is a code typed in monospace font

However, appearance of such block in Rmd files disturbs syntax highlighting in R code chunks.
I had to slightly modify rmd.vim file:

 37 if exists("g:rmd_syn_hl_chunk")
 38     " highlight R code inside chunk header
 39     syntax match rmdChunkDelim "^[ \t]*```{r*" contained
 40     syntax match rmdChunkDelim "}$" contained
 41 else
 42     syntax match rmdChunkDelim "^[ \t]*```{r*.*}$" contained
 43 endif
 44 syntax match rmdChunkDelim "^[ \t]*```$" contained
 45 syntax region rmdChunk start="^[ \t]*``` *{r*.*}$" end="^[ \t]*```$" contains=@R,rmdChunkDelim keepend fold

Is there any way to run the Vim-R-Plugin on a local machine but have the R interpreter its communicating with be on a separate box? Connected through ssh specifically. It seems like there must be some way to hack the tmux session to allow this but I'm not sure how.

Thanks

starting R from macvim with rf fails with the following error

Error detected while processing function StartR..StartR_ExternalTerm:
line 26:
E121: Undefined variable: s:tmxcnf
E116: Invalid arguments for function writefile
line 36:
E121: Undefined variable: s:tmxcnf
E15: Invalid expression: '-f "' . s:tmxcnf . '"'
line 46:
E121: Undefined variable: tmuxcnf
E116: Invalid arguments for function printf("%s tmux -2 %s new-session -s %s "%s" &", g:rplugin_termc
md, tmuxcnf, g:rplugin_tmuxsname, rcmd)
E15: Invalid expression: printf("%s tmux -2 %s new-session -s %s "%s" &", g:rplugin_termcmd, tmuxcnf,
g:rplugin_tmuxsname, rcmd)
line 56:
E121: Undefined variable: opencmd
E116: Invalid arguments for function system(opencmd)
E15: Invalid expression: system(opencmd)
line 58:
E121: Undefined variable: rlog
E116: Invalid arguments for function RWarningMsg

Looks like the default Terminal executable location might have changes in OS X Mountain Lion. As a result, I'm seeing an error whenever I fire up vim on an R file.

Rather than duplicate the details, see my StackOverflow page for the problem and solution:
http://stackoverflow.com/questions/11746637/vim-r-plugin-broken-after-os-x-mountain-lion-upgrade

Thanks so much for your work on this plugin. I use it constantly!

I frequently use long SQL commands within sqldf() and find that the indent code consistently gets it wrong. I wonder how difficult it would be to correct indent/vim.r so that this works right. For example:

g <- sqldf('select a, b
           from aa left join bb
           on aa.date =bb.date')                                                                                                        
head(g)

Is indented incorrectly, with head(g) being indented as if it was a part of the sqldf argument. Placing the second parenthesis on its own line arrives at the correct intending, but it would be nice if the code indented things correctly without the programmer having to manually work around the current behavior.

If syntax folding is enabled via "let r_syntax_folding = 1", then other folding methods dont work correctly on R files.

For instance, if "set fdm=marker" is specified, and folding is enabled, then the folds are not applied correctly (an incorrect mix of both syntax and marker folds ends up being applied) . It would be nice if it was possible to cleanly switch between folding methods (e.g. syntax, marker, indent, etc.) on R files, just as you can with other types of files.

hi, i was using the plugin right now and it went well before i started to use the pathogen to manage my vim plugins.
With using the pathogen, i just git clone from this repo to one folder in vimfiles/bundle/vim-r-plugin.
and now when i use the command ^x^o, the r will report an error "could not find function "vim.bol" and the auto-complete failed to use.
Is is because of the folder structure?

Hi,

I'm using the Vim-R plugin with Vim 7.3, R 2.15.2 x64, Windows 7 x64. It appears that when I start R from vim (using \rf, the menu button, etc.) that it does not load my .Rprofile -- as if it were loading R in vanilla mode. As such it's not finding a vimcom port. Otherwise things seem to work ok. Once I open R, I can send lines, etc. But if I try to send a line or file before opening R, Vim complains that it cannot find a vimcom port or the R console.

Any help would be appreciated.

Thanks,
-c.

Hello,

After updating to the latest version of r-vim and vimcom.plus I am running into an issue that I'm not sure how to approach.

When I open a vim console and first attempt to run any command, I get an error message. The second time I attempt to run a command, however, it works.

R version 3.0.2 (2013-09-25) -- "Frisbee Sailing"
Copyright (C) 2013 The R Foundation for Statistical Computing
Platform: x86_64-unknown-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

  Natural language support but running in an English locale

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

setwidth 1.0-3 loaded
vimcom: VIMEDITOR_SVRNM environment variable not found.
vimcom.plus 0.9-92 loaded
> print('hi')
[1] "hi"
Error in file(file, ifelse(append, "a", "w")) : 
  cannot open the connection
Calls: vim.buildomnils -> vim.bol -> sink -> file
In addition: Warning message:
In file(file, ifelse(append, "a", "w")) :
  cannot open file '/r-plugin/objlist/omnils_stats_3.0.2': No such file or directory
Calls: vim.buildomnils -> vim.bol -> sink -> file
> print('hi')
[1] "hi"
> 

Some system info:

Linux
ZSH
R 3.0.2
vim-r (git 2013/12/03)
vimcom.plus (0.9-92)
.vimrc
.Rprofile

Any ideas what could be going on here?

He

An integration of the vimshell
as another option to run the R plugin would be nice.

Best Claas

Hi,

I really like the integration with Tmux, but I already use tmux extensively, and I really don't like the nested tmux sessions, it screws up my settings and my navigation instincts. Is there any way to get vim-r-plugin to use an existing tmux/R session? That would give me vastly more control.

Thanks!

-Mike

I have been trying to set up the vim-r-plugin on a windows 7 box.

I have run into what i think is a bug -- caused by the improper use of path seperators.

The commands \aa and \ae both fail with the error:

Error: '\R' is an unrecognized escape in character string starting ""S:\R"

Due to the fact that the file is sourced with backslash seperators - rather than either double backslashes or forward slashes.

Send-section and send-line commands both work well -- with the paths appropriately passed with forward slashes. The \ao (send file, process, open R.out) command also works.

I did some googling and found an old issue with paths relating to whoami -- i am not sure, but i don't think this is related.

For the record, my whoami returns a path that's split with a single backslash -- as in %USERDOMAIN%\%USERNAME%

thanks

It's pretty common that parentheses get highlighted in red after inserting a blank line (or something like that) in an otherwise perfectly valid code fragment. The highlight disappears once I save the file or do some action that seems to force a full syntax sync. Workarounds as syncing on minlines for a reasonable amount like 40 ameliorate the problem. But the ideal would be to sync on syntax regions or matches.

Using the devtools R package (see http://cran.r-project.org/web/packages/devtools/ and https://github.com/hadley/devtools), utility vim commands for R package developing could be easily integrated into your great plugin.

My current workflow consists of editing some R scripts and then switch to the R pane and type load_all(".."), test(".."), check(".."), install("..") ... which is obviously not really efficient.

A simple heuristic (checking if the R script is in a directory named 'R' and the parent directory contains a DESCRIPTION file) could be used to switch commands/shortcuts on and off.

I have noticed that certain R commands in my files, when split over multiple lines, seem to confuse the vim-r plugin, so that creating newlines below the given command while editing the file cause ~2 seconds of lag before the newline is created. The lag occurs both when the 'o' or 'O' commands are entered from normal mode, or after hitting Enter while already in insert mode. Here is an example R command that causes the problem.

hist(data$Growth.rate[data$Strain == '0'
     & data$Environment == 'A'
     & data$Day == '1'], breaks=20)

There is no lag if I comment out the command or edit the command to be all on one line.

The Start R button in Vim-R-plugin stopped working after a recent upgrade to R 3.0.0. This is the error message:

Error detected while processing function StartR:
line 42:
Traceback (most recent call last):
File "", line 1, in
File "~/vimfiles\r-plugin\windows.py", line 202, in StartRPy
os.spawnv(os.P_NOWAIT, rpath, rargs)
OSError: [Errno 22] Invalid argument
Press ENTER or type command to continue

If I set the maplocalleader to ',' and edit multiple buffers -- communicating
with the same R-process --, my Leader always switches to \ when editing
other buffers than the initial one.

The only way to fix this for me was

zsh> cd .vim/bundle/r
zsh> sed -i 's/maplocalleader/mapleader/' $(grep -l maplocalleader **/*(.))

I don't know how to deal with it in another way.

Dear programmers,

thank your for providing Vim-R-plugin.

I have a probably easy and quick to fulfill request:

Running vim in an ssh session from within tmux I would like to have Vim-R-plugin to open a new tmux window for me.
To achieve this, I set the following in my .vimrc:

let vimrplugin_term_cmd = "tmux new-window 'R"

I tried the latter tmux command and it works, i.e. it opens a new tmux window and starts R in there. But unfortunately I get the error "The X Window system is required to run R in an external terminal".

I assume the plugin checks for a running X window system before even trying to start R?
Could you introduce a simple switch to turn that check off, please?
Something like:
vimrplugin_check_x_win_sys = 0

I for one would be very happy, indeed.

Cheers!

I found _ in insert mode will automatically changed into <-. But this is not correct always.
For example, when I want to type Ambi_Typing, I will have to type the _, but this will change into <-. I think plugin should check whether there are string before _. If has, then do not change, otherwise automatically change.

Hello - I've been using the vim-R plugin on my WinXP desktop for some time now, and I'm now trying to get it set up on a laptop. I've been encountering a persistent problem, however: when I try to open an R file for the first time, I receive a message that "Python interface must be enabled to run Vim-R-Plugin. Please do `:h r-plugin-installation' for details".

Which I do, but I don't see any information there that conflicts with what I've done. Here's some additional information about my setup:

Windows XP
Python 3.2.1 (currently, but also tried 2.7.2 before)
pywin32 build 216 (specifically, pywin32-216.1.win32py3.2.exe for Python 3.2, pywin32-216.1.win32py2.7.exe for Py 2.7)
Vim 7.3.46
Vim-R-Plugin 110805

The installations of R, Python, pywin32, Vim, and the Vim-R plugin are all fresh, and I've tried uninstalling and reinstalling most components with no luck. Do you have any suggestions? Am I missing something obvious?

Thanks for your help - and for making such a great plugin. I miss it!

Cheers,
Matt Parker

Hi.

When sending a word that contain a "$" and characters afterwards, only the characters until the "$" is sent.

I'm currently using a fresh install of Linux Mint Debian Edition. I've used vim-r-plugin on several distros and never encountered this problem before.

Example:

Gvim:       R/Terminal:
foo$bar     foo 
foobar$     foobar$

Tested with
screen.vga: v1.5 and v1.4
vim-r-plugin: 0.9.9.3, 0.9.9.2 and 0.9.9.1

The current version number in official site is 0.9.9.5. But in Vim-script Github repo, its 0.9.9.3.
http://www.vim.org/scripts/script.php?script_id=2628
https://github.com/vim-scripts/Vim-R-plugin

Currently, the plugin indents code like that

eval(
     substitute(
                ) 
     ) 

while ESS and RStudio provide the more convenient indentation

eval(
  substitute(
  )
)

Would it be easy to change the indentation behaviour to adhere to this standard? Something similar exists for python (https://github.com/hynek/vim-python-pep8-indent.git), but unfortunately my vimscript knowledge is to poor to contribute a solution by myself.

Hi there, i am on Max OSX 10.8.5, using macvim 7.4 (homebrewed), and have noted that open r vanilla is broken.

When i issue the command <leader>rv, i get the following error from macvim:

open: unrecognized option `--vanilla'^@Usage: open [-e] [-t] [-f] [-W] [-R] [-n] [-g] [-h] [-b ] [-a ] [filenames] [--args arguments]^@Help: Open opens files from a shell.^@ By default, opens each file using the default
application for that file. ^@ If the file is in the form of a URL, the file will be opened as a URL.^@options: ^@ -a
Opens with the specified application.^@ -b Opens with the specified application bundle ident
ifier.^@ -e Opens with TextEdit.^@ -t Opens with default text editor.^@ -f
Reads input from standard input and opens with TextEdit.^@ -F --fresh Launches the app fresh, that is, withou
t restoring windows. Saved persistent state is lost, excluding Untitled documents.^@ -R, --reveal Selects in the Finde
r instead of opening.^@ -W, --wait-apps Blocks until the used applications are closed (even if they were already running)
.^@ --args All remaining arguments are passed in argv to the application's main() function instead of opened.^@
-n, --new Open a new instance of the application even if one is already running.^@ -j, --hide Launches
the app hidden.^@ -g, --background Does not bring the application to the foreground.^@ -h, --header Searches hea
der file locations for headers matching the given filenames, and opens them.^@

The readme says that "Not all menu items and key bindings are enabled in all
filetypes supported by the plugin (r, rnoweb, rhelp)" -- is this option disabled?

Hello,

The arguments auto-completion( C-X C-O) seems to work just fine but the function arguments auto-completion doesn't work (C-X C-A). I only get UNKNOWN as arguments. Are you aware of anything like this?

Thank you,
Matahi

After I click on some .R file, gVim opens windows and closes it almost instantly, so I can't edit it, the gvim.exe process is not seen in the task manager. However gVim opens other files without any problem.

After plugin deleting gVim works fine and I can open .R files.

Expected result: I should be able to edit .R files in gVim, gvim.exe should be visible through task manager.

I have installed last plugin version (0.9.9.1) from the vim.org: http://www.vim.org/scripts/script.php?script_id=2628

Here is an output of the gvim.exe --version:

> gvim.exe --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-46
Compiled by Bram@KIBAALE
Big version with GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent 
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff 
+digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi 
+file_in_path +find_in_path +float +folding -footer +gettext/dyn -hangul_input 
+iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak 
+lispindent +listcmds +localmap -lua +menu +mksession +modify_fname +mouse 
+mouseshape +multi_byte_ime/dyn +multi_lang -mzscheme +netbeans_intg +ole 
-osfiletype +path_extra +perl/dyn +persistent_undo -postscript +printer 
-profile +python/dyn +python3/dyn +quickfix +reltime +rightleft +ruby/dyn 
+scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop 
+syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent 
-termresponse +textobjects +title +toolbar +user_commands +vertsplit 
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu 
+windows +writebackup -xfontset -xim -xterm_save +xpm_w32 
   system vimrc file: "$VIM\vimrc"
     user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
  system gvimrc file: "$VIM\gvimrc"
    user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
    system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32   -DFEAT_CSCOPE 
-DFEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400 -D_WIN32_WINNT=0x0400  
/Fo.\ObjGOLYHTR/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_IME 
-DFEAT_GUI_W32 -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL -DDYNAMIC_TCL 
-DDYNAMIC_TCL_DLL=\"tcl83.dll\" -DDYNAMIC_TCL_VER=\"8.3\" -DFEAT_PYTHON -DDYNAMIC_PYTHON 
-DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 
-DDYNAMIC_PYTHON3_DLL=\"python31.dll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl51
2.dll\" -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_RUBY_DLL=\"msvcrt-ruby191
.dll\" -DFEAT_BIG /Fd.\ObjGOLYHTR/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib 
shell32.lib gdi32.lib  comdlg32.lib ole32.lib uuid.lib /machine:i386 /nodefaultlib gdi32.lib version.lib   winspool.lib 
comctl32.lib advapi32.lib shell32.lib  /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib  user32.lib      
/nodefaultlib:python27.lib /nodefaultlib:python31.lib   e:\tcl\lib\tclstub83.lib WSock32.lib e:\xpm\lib\libXpm.lib 
/PDB:gvim.pdb -debug

I have python 2.7 installed and it in my %PATH%:

> python --version
Python 2.7.3

I have not been able to get the knit functions to work -- and am trying to hack around the problem by making a custom command to send to the R console.

I would like to send: knit("current.file.path") to the console.

Is there some way to tell the plugin to send such commands?

thanks

I've installed R with homebrew via brew install R, so I have no gui, and there is no Application/R.app.

I've set let vimrplugin_r_path = "/usr/local/bin/R" in my .vimrc.

When I hit rf in macvim, I get the error message: "The file /Application/R.app does not exist".

Any idea what's going wrong here?

Pretty simple example here:

a <- ("multi
     line
     string")

If you go to the next line the cursor lines itself up with in the same column as s in string. Note that you need the parentheses around the string. Otherwise if you leave them out, it doesn't indent on the line after multi (which is fine and how other languages seem to behave).

Also if I have

a <- ("multi
     line
          indented
     string")

And indent with =ap, the indented line gets brought back to the same indent level as everything else. Text in strings should be left alone when indenting.

The documentation remarks, regarding vimrplugin_assign_map:

may only works on GVim

This is a pity. The assign map is tremendously useful but the default choice is prohibitive since a lot of prominent packages (amongst them all by @hadley, e.g. ggplot, devtools etc.) use underscore in identifiers.

Is there a fix / workaround for that?