There's a couple untriaged issues and pull requests. Need an extra hand managing the repo?

Hi,

If I have a sessions with a window inside, named as DEV/2 and has a single pane named CONSOLE, I am not able to connect to those using the :TxSetPane command.

I get the following error.

Session:Window.Pane> DEV/2:0.0Error detected while processing function tmuxify#pane_set:
line   20:
E687: Less targets than List items

Is there a way to fix that? If the window is not named, then the index is 0:0.1 and it works.

Hi, I get an error when trying to do <leader>ms:

Error detected while processing function tmuxify#pane_send:                                                         
line   22:
tmuxify: A certain version of tmux 1.6 or higher is needed. Consider updating to 1.7+.

I'm using the latest version of vim-tmuxify from this repo, and tmux is version 1.8:

$ tmux -V
tmux 1.8

Did tmux 1.8 break your plugin?

Thanks,
Brendan

I'd like to make a hotkey to send a command to the current pane. I don't want to be prompted for this command nor do I want it to change the 'current run' command. Is this possible?

% in tmuxify_run does not expand to the name of the active buffer but to the first buffer of each filetype. Even killing that buffer with :bd will result in the first one to be returned.

Basically the active buffer is fetched only once for each filetype.

The pane association works fine (first echos via <Leader>ms),
but switching between the splits and running <Leader>mr always executes the first script.

let g:tmuxify_run = {
\ 'sh': 'bash %',
\ 'fortune': 'strfile %'
\ }

When sending a visual selection through :TxSend (using the mapping), trailing semi-colons seem to be ignored. Adding whitespace after the semi-colon causes it to be sent, however.

When using :TxSend (from the mapping) in normal mode, it seems that a line ending in a semi-colon is entirely ignored, again, unless there is trailing whitespace.

I just installed vim-tmuxify on vim 7.4 patch 1-52 on Ubuntu 14.04. However, when I run TxSend, I get an error saying the function 'systemlist' is unknown. I'm assuming 'systemlist' is a function in newer versions of vim. Is it possible to have support for older versions of vim?

Hello there :)

First of all thank you for the plugin. It's working really well!!

Unfortunately it stops functioning when I install vim-tmux-navigator...

I think vim-tmux-navigator is kind of a hack but it does work quite nicely and would, in my opinion, compliment tmuxify if the two could work together.

best wishes,

Dionysis

Associating a pane with :TxSetPane prompts for session and window, but seems to ignore it. It would be nice to be able to associate to an existing pane in another window.

Hi! Thank for the great plugin!

Anyway, I have this issue with it. when I send a command with ms, it creates a pane and runs the command well. But when I go to another file, without closing that pane (mq) and try to repeat this motion, the plugin creates new pane instead of send second command to the prev pane.
Sometimes, when the pane was closed, I get this error 'the associated pane was already closed!' on ms.

Maybe I don't understand correctly the behavior of the plugin and try to use it wrong way, but I need this functionality: I have several mappings m1-m9 with a command per one. for example m1 - runs tests, m4 - runs build, etc.
So I try this:
nmap <leader>m1 <leader>ms <c-r>r/gradlew test<cr>

Is there a way to handle this with your plugin? Thanks for an answer!

Make an option like g:tmuxify_mapping_prefix="<leader>m" that allows users to change tmuxify mappings.

If you agree that this is a reasonable feature, I'm happy to implement it myself and submit a PR.

I want to re-use the same tmux pane for all buffers.

Currently window sizes seem to be specified using -l option, which specify the size in either lines or cells depending on if you split horizontally or vertically. This isn't optimal, at least not for me. Using the -p option allow one to specify the size as a percentage, i.e., -p 50 would be 50% of the screen size.

I think it would be really helpful if :TxSetPane would accept arguments in the form of paneids like :TxSetPane %2 or :TxSetPane 1:1.1 rather than forcing the user to user vim's menu

everything is work perfectly when you use only one tab, if you open another tab with NERDTee tabnew, TxSend and others won't work in the second tab. It shows some errores in vim:
"E121: Undefined variable: b:tmuxified" and
"E15: Invalide expression: !b:tmuxified || !exists('b:pane_id) || (b:pane_id != s:pane_get_id(b:pane_num)).

You've done the great job, this is a great plugin for vim, I like it so much BTW.

If :TxSend is invoked with text containing tabs, since the tabs are sent literally to the associated pane, they invoke tab-completion (where applicable). I'm not sure if this is considered desired behaviour or not.

I think a decent solution would be converting tabs to spaces before sending it to tmux.

Associating to pane 0 using :TxSetPane results in the error message, "tmuxify: There is no pane 0!".

Calling :TxSend("foo") results in the following system call:

tmux send-keys -t 1 -l 'foo' && tmux send-keys -t '. pane_num .' C-m'

The :TxSend fails silently, but by running this command in a shell, I see the error:

tmux: unknown option -- l

I'm running tmux 1.6 on ubuntu 12.04. I suspect that this is a bug/invalid flag for this version of tmux.

A few suggestions:

• look for a workaround or add a minimum required version number for tmux in the docs
• commands shouldn't fail silently

I'm happy to take a stab at this but wanted your feedback first.

I open vim. I setup a tmux-pane which Vim can talk to with <Leader>mn and run a command using <Leader>mr. I then go ahead and create a split (in Vim) and run <Leader>mr which result in a new tmux-pane being created unless I bind to it using <Leader>mp first.

Could we improve this in some way? I think it's more natural to assume that you want to talk to the current tmux-pane and that you should specify otherwise if not.