Fork me on GitHub
#vim
<
2017-10-04
>
uwo19:10:31

@dominicm nothing to do with this channel, but do you use tmux by any chance?

dominicm19:10:05

I don't, no. Why do you ask? :)

uwo19:10:16

ah, just asking on the off chance. I have a random question because I just updated versions and can’t find the answer online yet 😛

dominicm19:10:49

Someone else in the channel may know, worth an ask anyway

uwo19:10:58

I just resolved it!

uwo19:10:09

I appreciate the offer, though

defndaines20:10:59

What was the issue with tmux, @uwo? I ask because I’ve been pinned to 2.3 because all the newer versions break some basic functionality for me that I’ve never been able to solve (specifically, using vim copy and paste with y in the tmux buffer).

uwo20:10:34

@defndaines it turns out It wasn’t an issue at all. I was seeing tmux server and client logs in the directory where I started it, but that was just because I had run tmux -v a number of times which is not “give me the version of tmux” I was able to resolve y and v for tmux 2.5, however. Nicely it no longer requires reattach-to-user-namespace if you’re on osx

bind-key -T copy-mode-vi 'v' send -X begin-selection
bind-key -T copy-mode-vi 'y' send -X copy-pipe-and-cancel pbcopy

uwo20:10:54

(obviously pbcopy is osx only)

defndaines20:10:16

Awesome, thank you. I’ll try that out.

markwoodhall20:10:15

Has anyone here used sayid and vim-sayid much? In this example I use gst to start tracing the namespace for the current file, in this case swaggerdown.coercion, then I use cpp to evaluate an expression in dev.clj, after that I use gsw to show the sayid workspace. In the sayid workspace you can use ii to view the inputs and output of each trace. https://www.youtube.com/watch?v=TSCWzmYxBD8