jpalardy / vim-slime Goto Github PK

Was let g:slime_default_config = {"socket_name": "default", "target_pane": "1"} removed? Cant see anything in the help file

Moreover, it keeps prompting me for the first time, to select socket and target pane. Normally, with above configuration in vimrc, vim-slime wouldn't need to prompt.

Hi!

If I visually select a region of staggered-length lines in visual block mode, only a rectangular selection seems to be sent, clipped to the length of the shortest line, not the actual whole lines.

Let me know if I can provide further information, I'm not really doing much more than that :).

Edit: Whoops, never mind, sorry for the noise, it looks like it's clipping to the cursor position of the last line, not the whole selection. Not sure why it's doing that if the whole region looks selected, (e.g., I did <C-V>, moved to the last line, then hit $), but moving over past the last column seems to work.

Loving using this plugin, although I was wondering if there's an easy way to send the results of the evaluation back into the vim buffer automatically? I'm using this with tmux at the minute and am finding that switching over to the tmux pane, copy the output, switching back to paste it in getting a bit tedious.

I am on Arch Linux. Sending a command in i3 WM doesnt work. In fact, it freezes Vim. Can't even exit

Hey,

I'm trying to use Slime to start a process straight from Vim, and for that it'd be really handy to just send a command line down to Screen. I see there's the SlimeSend function which is exactly what I'm after, but it's private. Why not make it public?

When I hit C-c C-c, in the repl window, I get a message at the bottom saying "Slurped 96 characters" it pauses for about 2 seconds, then it gets evaluated. Is it possible to configure vim-slime to not pause or give the message and just evaluate it so that I don't have to wait?

Thanks a lot,
David :)

P.S. using a Mac if it matters.

Hi!

I'm using slime on OSX, with patched screen from homebrew, unfortunately vim keeps calling /usr/bin/screen, instead of /usr/local/bin/screen, could you maybe add a way to set path to screen executable?

I "fixed" it locally changing call system(screen... into call system(/usr/local/bin/screen...

Szymon

Hi

I might be missing something terribly trivial, however I can't seem to be able to set screen as default in my vimrc, which looks like this:

filetype off
call pathogen#infect()
syntax on
filetype plugin indent on

[bunch of other stuff]

let g:slime_option="screen"
let b:slime_screen = {"sessionname": "mysession", "windowname": "0"}

however when I start vim, g:slime_option is set to tmux. If I source my vimrc again, then g:slime_option is set to screen.

item :: Parser Char
item = Parser (\s -> case s of
    "" -> []
    c:cs -> [(c,cs)])

When sending the above to tmux, the following error occurs:

Prelude> :{
Prelude| let item :: Parser Char
Prelude|     item = Parser (\s -> case s of
Prelude|     "" -> []
Prelude|     c:cs -> [(c,cs)])
Prelude| :}

<interactive>:5:5:
    parse error (possibly incorrect indentation or mismatched brackets)

The problem is that only the first line is indented when let is added.

I took a look at the source and it seems that lines beginning with whitespace are deliberately not indented. May I ask why this is done? Should I be indenting my code in a different way?

The default is:
":" means current window, current pane (a reasonable default)

Which can easily put vim in a funky state by pasting into itself. I've found a reasonable default would be:

":i.j+1" as in current window, (current pane + 1)

That way it will default the next pane. I think this is fine for 99% of my use cases and the majority of everyone else's as well.

but the current defaults are annoying since they will put vim in a bad state.

hi everyone .

recently i found vim-slime, this plugin is awesome. and i was so happy to send code to ipython in tmux, it just like an IDE.

but now when i send text to ipython, the vim will be stuck, Every button-down will echo in vim's command line, and tmux wouldn't accept lines.
pic1
pic2
i don't know how to debug this error, and i don't know what's happening.

this is my vim's info and plugins list:
Plugin 'gmarik/Vundle.vim'
Plugin 'Lokaltog/vim-easymotion'
Plugin 'vim-scripts/fencview.vim'
Plugin 'vim-scripts/camelcasemotion'
Plugin 'vim-scripts/LargeFile'
Plugin 'jiangmiao/auto-pairs'
Plugin 'SirVer/ultisnips'
Plugin 'mbbill/undotree'
Plugin 'jmcantrell/vim-virtualenv'
Plugin 'Valloric/YouCompleteMe'
Plugin 'honza/vim-snippets'
Plugin 'kana/vim-textobj-user'
Plugin 'bps/vim-textobj-python'
Plugin 'kana/vim-textobj-indent'
Plugin 'kana/vim-textobj-line'
Plugin 'kana/vim-textobj-entire'
Plugin 'sgur/vim-textobj-parameter'
Plugin 'glts/vim-textobj-comment'
Plugin 'Julian/vim-textobj-variable-segment'
Plugin 'rizzatti/dash.vim'
Plugin 'kien/ctrlp.vim'
Plugin 'majutsushi/tagbar'
Plugin 'scrooloose/nerdtree'
Plugin 'terryma/vim-expand-region'
Plugin 'terryma/vim-multiple-cursors'
Plugin 'tpope/vim-commentary'
Plugin 'tpope/vim-repeat'
Plugin 'tpope/vim-surround'
Plugin 'tpope/vim-unimpaired'
Plugin 'vim-scripts/EasyGrep'
Plugin 'vim-scripts/TaskList.vim'
Plugin 'jlanzarotta/bufexplorer'
Plugin 'raymond-w-ko/vim-niji'
Plugin 'scrooloose/syntastic'
Plugin 'guns/vim-clojure-static'
Plugin 'tpope/vim-fireplace'
Plugin 'derekwyatt/vim-scala'
Plugin 'ktvoelker/sbt-vim'
Plugin 'vim-scripts/CCTree'
Plugin 'vim-scripts/a.vim'

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled May 20 2016 11:48:50)
MacOS X (unix) version
Included patches: 1-1831
Compiled by Homebrew
Huge version with MacVim GUI. Features included (+) or not (-):
+acl +file_in_path +mouse_sgr +tag_old_static
+arabic +find_in_path -mouse_sysmouse -tag_any_white
+autocmd +float +mouse_urxvt +tcl
+balloon_eval +folding +mouse_xterm +termguicolors
+browse -footer +multi_byte +terminfo
++builtin_terms +fork() +multi_lang +termresponse
+byte_offset +fullscreen -mzscheme +textobjects
+channel -gettext +netbeans_intg +timers
+cindent -hangul_input +odbeditor +title
+clientserver +iconv +packages +toolbar
+clipboard +insert_expand +path_extra +transparency
+cmdline_compl +job +perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con_gui +lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind -X11
+dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent +xim
+emacs_tags +mouseshape +startuptime -xsmp
+eval +mouse_dec +statusline -xterm_clipboard
+ex_extra -mouse_gpm -sun_workshop -xterm_save
+extra_search -mouse_jsbterm +syntax -xpm
+farsi +mouse_netterm +tag_binary
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "/.vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "/.vim/gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe -DMACOS_X_UNIX -F/usr/local/Cellar/python/2.7.11/Frameworks -I/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/include/python2.7 -I/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/include/python2.7 -fno-strict-aliasing -fno-common -dynamic -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang -L. -L/usr/local/lib -L. -L/usr/local/lib -F/usr/local/Cellar/python/2.7.11/Frameworks -L/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config -lpython2.7 -framework CoreFoundation -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon -lm -lncurses -liconv -framework Cocoa -pagezero_size 10000 -image_base 100000000 -L/usr/local/lib -lluajit-5.1 -fstack-protector -L/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE -lperl -F/usr/local/Cellar/python/2.7.11/Frameworks -framework Python -F/System/Library/Frameworks -framework Tcl -framework CoreFoundation -framework Ruby

I'm using Linux Mint 17 here (have had problem with versions 14/15/16 as well). I'm having trouble running two separate screen + vim instances. When I have two, the text that is slurped up only gets sent to one screen instance (i.e. both send to the same one). If that doesn't make sense, here is a more specific description of what I'm doing:

1. start terminal and run following commands:
   $ screen -S session
   [ctrl a-c]
   $ vim
   [ctrl a-|]
   [ctrl a-tab]
   $ ipython
   [ctrl a-tab]
   [ctrl c-v] -- session: session, screen window name: 01

...everything works fine

next i do it again:

$ screen -S session2
[ctrl a-c]
$ vim
[ctrl a-|]
[ctrl a-tab]
$ ipython
[ctrl a-tab]
[ctrl c-v] -- session: session2, screen window name: 01

...everything works fine in the second screen instance. If I try to slurp lines from the first screen instance it either sends them to the second screen instance or apparently to purgatory.

Can anyone else reproduce my problem?

I'm using vim-slime to paste a function to iPython. The function is 72 lines and indented with spaces. iPython returns errors about invalid syntax when I paste. However, if I find/replace 4 spaces with a tab character in the function, the function pastes properly into iPython without errors. I've confirmed that there are no errant spaces in the original, and only the beginning indentation spaces are being replaced (none in the middle or ends of lines, in other words). Other functions (also indented with spaces) from the same file seems to paste without any issues. I updated to the latest vim-slime using git clone but it still has the same issue.

I would like to control for individual buffers, whether they need to use ipython mode or not.

When I send some function definition to IPython, I need two trailing newlines without spaces before to start the interpretation of the input in IPython. Currently, multiple newlines are always condensed to a single newline, when sending to tmux. This prevents the correct execution of the code without manually moving to the IPython shell and pressing enter. I would either expect that multiple newlines already contained in the lines to send are preserved, or their needs to be a setting to configure the amount of newlines to send after the target text.

I use C-c to exit insert mode and regularly, accidentally kick-off Vim Slime.

Is there a straightforward way to change the binding to something like c?

IPython (at least version 4) auto-indents after colons. This prevents that sent blocks of code are syntactically correct. I don't know whether there is some way for vim-slime to fix this, but it would be nice if this could work with default settings.

tmux supports two ways to pick the session's socket from the command line:

-L : User passes a name of a socket that exists in $TMPDIR
-S : User passes an absolute path to a socket

On shared hosts, it is not safe to have tmux putting its sockets into the default value for $TMPDIR, /tmp, because they are likely to be blown away. However, it is often undesirable to set $TMPDIR to a path in the home directory because other processes can fill it up with garbage. tmux switched to a separate variable, $TMUX_TMPDIR, but not until recently, some time after the latest version in use at my company (1.8). Altogether, it makes the use of -L very hard to get right. For example, vim-slime simply cannot function when I use 1.8, keep my tmux socket in my home directory on a shared machine, but leave $TMPDIR unset or pointing at /tmp.

To get around this issue, I think it would be better if vim-slime asked for a full path to the socket and used -S internally. This will require plugin users to type more than a socket name, but I imagine the vast majority of users are sending snippets to the same session, not a different session. The current session's socket path is kept in $TMUX and can be parsed in vim with split($TMUX, ',')[0]. It can be used as the default path and fit the needs of most users ¹. I have made this improvement before for vim-tmux-navigator. I will be happy to volunteer a patch this evening, but it will be your decision whether to accept it.

I just had vim-slime installed and created tmux window with vim in top pane and mysql in bottom pane before I tried C-c C-c from within vim pane to execute mysql statement in mysql pane. It would just froze. I had to kill vim process every time. :(

ps: yes, i did get a prompt to go with default session with current window but with :1 for the bottom pane.

I figured I'd make this a separate issue. I'll quote the text I added to another issue:

ipython 5 removed the %cpaste magic function and apparently just works with pasting long input directly. You may want to either add detection for ipython 5.x+, or require users to use it if they use ipython (it has been out for months now). Then, you can use something other than cpaste (I'm not sure how they made it work, but it apparently does).

I've got a buffer with UTF-8 characters (acutes, carons, ...) and I'm trying to send it to tmux session. I've connected successfully, but when I send it, Python interpreter screams. When I write it directly into the interpreter, it behaves OK, but when I send it from Vim, it (the interpreter) gives an error:

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 0: invalid continuation byte

What to do?

Here's my buffer in Vim: (note the á,í,ý,č,ů etc. characters)

class Tovarna:
  # Továrna.
  # Zde definujeme, kolik má fréz, rýsovačů, zámečníků, atd. - tedy "threads".
  pass

class Zakazka:
  # Nová zakázka.
  # Je třeba po vytvoření ještě předat továrně skrze TODO.
  # Zde definujeme časové deadlines a z jakých sestav se skládá.
  pass

class Sestava:
  # Sestava.
  # Zde definujeme, kolikrát je sestava třeba vyrobit a z čeho se skládá.
  # Může obsahovat sestavu nebo položku.
  pass

class Polozka:
  # Položka - nejnižší prvek, "součástka". Dále už se nenoří.
  pass

i use the ipython %cpaste integration a lot, it works fine. one nitpick: it would be more convenient to have the cursor at the end of the sent region afterwards. for example when going through a script cell-by-cell

I'm pasting a function that has a multi-line SQL query from vim to ipython. My pattern is I run %cpaste in ipython and then paste the function from vim using Ctrl+C Ctrl+C. The first time I run this the function isn't pasted properly, so when I call it I receive an error. If I paste it again (using the identical sequence of steps just described), it works.

are vundle installs supported? everything seems to work fine for me

I have problems using this plugin with Python because indentation does not seem to be preserved. Is this a known issue, and if so is there a work-around or alternative solution?

Thanks.

Every time I trigger a send to slime, my screen session gives a message: "Slurped X characters into buffer." This message stays on the screen for several seconds before anything happens. Is it possible to disable it?

I found a similar issue on another screen plugin, but I can't figure out how to apply it to slime:

ervandew/screen#4

If I'm already in a screen session can C-c C-c be made to default to the current one?

Please add some Open Source license or put it under public domain.

Thanks.

Get an indentation error from ipython

offending test code

def foo(n):
    for i in range(n):
        if i == 5:
            break
    return i

ipython error

In [3]: def foo(n):
   ...:         for i in range(n):
   ...:                 if i == 5:
   ...:                         break
   ...:             return i
  File "<ipython-input-3-95cc693453b1>", line 5
    return i
            ^
IndentationError: unindent does not match any outer indentation level

Made a screenshot aswell

http://imgur.com/a/FAlon

If I turn off slime_python_ipython the slurped text is incorrectly formatted, eg:

def delete():
     m.delete_library('smukasa.alphas')

becomes

>>> def delete():    m.delete_library('smukasa.alphas')
...

Turning slime_python_ipython on correctly preserves the new line, but now everything is surrounded by an annoying %cpaste and --

%cpaste
File "", line 1
%cpaste
^
SyntaxError: invalid syntax
def delete():
... m.delete_library('smukasa.alphas')

...

File "", line 1

^
SyntaxError: invalid syntax

is there any way to fix this?

I know there's a Haskell ftplugin file that tries to add lets to the appropriate lines, and it does pretty well, but if I put main on its own line and send it, or if I try to :SlimeSend1 main to run the main function, e.g., I can't get it to send without the prefix. Is there a way to send something raw from the command line, and/or the buffer? I also couldn't set up a mapping to let me send runhaskell % to call runhaskell on the whole file to a shell pane, because of the let. As a simple workaround while sending to ghci, I can prefix what I send with () = () in, which eats the let, but it's less than ideal.

Hello

Thank you for this wonderful vim plugin.

Just one thing which is annoying me a little is the wait time of 5 seconds from C-c C-c till the definitions are loaded in the screen session.

Can one do something about it?

Greetings
nimaai

Vim is generating a file under doc/tags.

When the vim-slime plugin is installed as a submodule in my vim/bundle, this prevents checking it into the parent repository due to this "untracked content". Looking at other Vim plugins, they seem to include "doc/tags" in their .gitignore file to address this.

I will add "doc/tags" to my own global git config to work around it, but suggest you add a .gitignore in vim-slime as well.

"Error detected while processing function 10_SlimeSendOp..10_SlimeSend..10_SlimeDispatch..
10_TmuxSend:
line 4:
E484: Can't open file /tmp/vrhkGsT/1"

Unsure if I missed a step as far as setting things up.
When I go to that directory within /tmp/ there is a file named 0, but not 1.
Don't know if that is of any help.

Hello!

I'm trying to use vim slime with Haskell and the Tidal library to programatically make drum beats live. I wish to evaluate expressions like these:

d1 <- dirtStream

d1 $ sound "bd"

But when I try to do with with vim-slime, I get this:

let d1 <- dirtStream

let d1 $ sound "bd"

Neither of these expressions are valid.

How do I work around this?

Thanks,
Louis

I want to be able to do something to the effect of this pseudocode:

SlimeConfig:  b:terminal_job_id

I'm using a function to essentially spawn a neovim terminal, open ipython, and then run SlimeConfig. The issue is in automatically running SlimeConfig and feeding it the jobid of the current terminal.

Not sure if this qualifies as an issue even, but I downloaded the freshest version of tmux only for kicks and since I use tmux about 95% for sliming with vim I tried it and the panes (selected in the usual way via :SlimeConfig) were not communicating. No text was pasted. I uninstalled and went back to the standard tmux for debian Jessie and all is back to normal. I'll set up a virtual machine and investigate more, but I was just wondering if anyone was using the brand newest version of tmux with vim-slime?

After I look into this more I will report back, but was wondering if anyone else had any experience.

It would be nice to have a function and key map to clean the REPL console. Something like sending system(clear) to the REPL...

I'm using Vim-slim with IPython 5 in tmux. Before this, I can send blocks of text by highlighting text in visual mode, then doing the Ctrl-C, Ctrl-C command. But since the upgrade to IPython 5, Ctrl-C, Ctrl-C only seems to enter pasting mode, without actually pasting the text. I have to do the Ctrl-C sequence twice for the text to paste.

Here's a few screenshots to show what I mean:

Start:

If I send a single line, things work as usual:

But if I highlight a few lines and hit send, it seems to just enter %cpaste mode, without sending anything:

I have to hit Ctrl-C, Ctrl-C again to send lines:

Any chance this can get a fix?

I saw that in the escape function for coffee we are adding CTRL-V to the beginning of the text. This is correct.

But CTRL-D at the end is wrong. Tested in CoffeeScript (1.6) CTRL-V is used to toggle both on and off multiline input.

So it should be:

"�CTRL-V", a:text , "CTRL-V�"

Sorry this is so simple that I didn't bother to do a pull request. If you need it please ask me.

Neovim has a built in terminal emulator and has asynchronous feature.

Thx for the great plugin, I use it with every language that has a repl!
My only problem with it is that it doesn't send empty lines.
This is not a problem with most languages, but it is for python.

So when I do this:

def the_answer():
    x = 42

print("Life, the universe and everything")

It cuts out the empty line in the middle and the repl gives a syntax error.
Just to be clear: this is not actually a syntax error in the language, but the repl seems to require it...
I'm just letting you know... I don't know any vimscript myself (yet).

Thx,
Alexander

I am a long time vim user but just started using vim-slime and am loving every bit of it. Thank you. I have one annoyance and am not sure if there is a quick fix for this. The problem is this -

I am using vim 7.4 (compiled for cygwin/Windows 7/x64). I am using it along with GNU screen to interface with a Julia REPL (I am also having this problem under tmux).

I do not have any problems when:

1. Enter a new command at the end of a file
2. Save it
3. Type C-c C-c

I get problems when:

1. Enter a new command at the end of a file
2. Do NOT save it
3. Type C-c C-c

The error I get is:

For quick interactive use, I would really like to not have to save everytime before the C-c C-c. Is there a quick fix for this?

Thanks.

My .vimrc contains:

let g:slime_default_config = {"socket_name": "default", "target_pane": "1"}

Yet when I attempt to evaluate a line of code, I'm still prompted for a socket and target pane. (I should note that the values listed above are prepopulated in the prompt, but I was expecting to not have to manually accept each of them whenever I eval code in a new buffer.)

I'm trying to write a ftplugin for Stata do-files. I'm new to Vimscript, so this is probably a basic question, but any assistance would be greatly appreciated.

The problem

I need to escape lines that end in // or continuation lines, where a long command is spread over multiple lines ending in ///.

For example, a do-file might contain:

gen x = 1 // Set x to 1 <-- Comment

keep var1 var2 var3 /// <-- Continuation
     var4 var5 var6

And I need to escape this, to produce:

gen x = 1

keep var1 var2 var3 var4 var5 var6

What I've tried

I've created a new subfolder in .../ftplugin/stata with the file slime.vim. I've tried to convert one of the existing solutions, e.g:

function! _EscapeText_stata(text)
    let trimmed = substitute(a:text, "\/\/.*$", "\n", "")
    return [trimmed]
endfunction

But I can only manage to escape a single line -- anything after the first match of \/\/.*$ is removed. Could anyone point me in the right direction?

Many, many thanks!

ConEmu is a program that can attach multiple consoles into one window. It's kind of like GNU screen, but more windowsy.

Something I've already gotten to work is vim can send some text, but I haven't gotten it to send carriage returns to the terminal window yet:

system(shellescape("C:\Program Files\ConEmu\ConEmu\ConEmuC64.exe") . "/GuiMacro:0 print: foo")

That command sends the string "foo" to the first ConEMU window.

A similar plugin for sublime text is here --> https://github.com/fbehrens/sublime_ExternalREPL
I'd just love to see something like this for vim. Thanks! 👍

when using %cpaste, everything works fine when the transmitted selection is less than about a screenful. for long selections, ipython often complains about invalid syntax although when broken down to smaller bits, everything is accepted.

not easy to make an example, but it happens quite often with input in multiple paragraphs

Hello,

I'm seeing this error that was also reported in #23

I commented on the previous, closed issue but wasn't sure whether that would be visible and notify. In my case, I'm using Ubuntu 14.04, Screen version 4.01.00devel (GNU) 2-May-06

When using slime to paste commands to ipython (5.1.0), only the first command is pasted to the destination. For instance, given the following simple code, when press Ctrl-C Ctrl-C in nvim,

x = 1
y = 2

Only x = 1 showed up in the ipython session. On the other hand, I can verify that all texts are sent to the terminal correctly (using a bash shell), yet only the first command takes effect somehow if the target is a ipython terminal. Not sure whether it is a slime or ipython issue. Any ideas? Thanks!

• neovim: 0.2.0
• vim-slime: most update version on github
• ipython3: 5.1.0

When I first open a vim sessions and do :SlimeSend1. I get Slime is not configured for this buffer. Please run :SlimeConfig.

However if I run SlimeLineSend and then :SlimeSend1, the buffer is recognized and the command is sent.

So what is going on here?

I got the following:

let g:slime_target = "tmux"
let g:slime_default_config = {"socket_name": "default", "target_pane": "1"}
let g:slime_no_mappings = 1
xmap <leader>s <Plug>SlimeRegionSend
nmap <leader>s <Plug>SlimeMotionSend
nmap <leader>ss <Plug>SlimeLineSend
nmap <leader>st :SlimeSend1