forbesmyester / xmux.kak

It's like a Frankenstein version of the X11 and tmux REPL's
4 stars 0 forks source link

Updated today, stopped working #3

Open egolep opened 3 years ago

egolep commented 3 years ago

I used xmux for a while and I've been loving it. Unfortunately, today I've updated it and it stopped working completely. Kakoune does not even recognize the xmux-repl command. I uninstalled it and re-installed following the guide in the read me but nothing changed.

forbesmyester commented 3 years ago

I did an update of my Kakoune plugins and it stopped working too, but it was/is actually connect.kak that broke (the repository has changed ownership) and I need to fix my config before anything else... xmux.kak depends on connect.

Do you have the connect commands still?

Can you send me the output from your *debug* buffer, if you have one?

Thanks

egolep commented 3 years ago

I actually do not have the connect command too. The debug buffer is kinda empty, it just shows "Error: no such command: 'xmux-repl'"

PS forgive me for the delay in this reply, I've been very busy at work yesterday

forbesmyester commented 3 years ago

Well the first three lines of xmux ( https://github.com/forbesmyester/xmux.kak/blob/016faf2bbe0c24bfbee82687cddd9824de6818b2/rc/windowing/repl/xmux.kak#L1 ) basically say, when connect is loaded, load xmux. So it's not going to attempt to work without getting the connect commands working.

I can't really help you with getting connect working as all setups are unique, but I used to load connect via a plug.kak and to get it working I removed it and checked out connect repository into my ~/.config/kak/autoload directory, which seems to have fixed it. I don't really understand the reasons behind this...

Hope that helps.

egolep commented 3 years ago

I installed manually connect.kak, which now works. Unfortunately, xmux still didn't worked. So I uninstalled it and manually pasted the xmux.kak file into my autoload folder and now it works. It could obviously be a problem of mine or some strange bad interactions with connect (also manually added to autoload) or something else but I hope this could also work for someone else experiencing the same problem.

Anyway thank you for your replies and for this excellent plugin!

egolep commented 3 years ago

Ok, maybe I rushed my celebration. I'm now able to open a repl with xmux-repl, xmux-chars and xmux-lines, but I have no way to send text to this repl since there is no xmux-send-text anymore. Is it the intended behavior? Or am I missing something?

forbesmyester commented 3 years ago

xmux-repl creates a "default" repl xmux-repl "bob" creates a "bob" repl

xmux-lines-bob sends lines to bob xmux-chars-bob sends chars to bob

do you have the -lines- and -chars- commands?

... probably should have bumped a major version on this release... didn't really think anyone was using it... sorry

:xml<space> will generally get you to be able to quickly send lines, which is what I always want...

egolep commented 3 years ago

I do have the -lines and -chars commands, but right now I have this behavior: if I open a window with xmux-repl it opens the repl (but does not execute the command, for example xmux-repl julia does not open a terminal with a julia REPL as it did before). Then, if I give a name to the repl (for example, xmux-repl "julia") then, xmux-chars-julia and xmux-lines-julia send the highlighted text to the previously opened one but also open a new tmux window which gets no text. Pretty strange behavior, so if you do not have a clue of the reason causing it, it could be that my WM (which is the pretty exotic leftwm) is to blame or maybe some problem with tmux itself.

egolep commented 3 years ago

Something strange happened again: it suddenly started complaining about missing files in the connect folder. This resulted in the new REPL blinking and then disappearing. I moved these files where needed and now it's REALLY working. I don't really know why this problem didn't showed up before.

Thank you again for your patience and for this great plugin!

forbesmyester commented 3 years ago

Thanks :-)

FYI I have a ~/Projects/xmux.kak folder which is symlinked to from ~/.config/kak/plugins/xmux.kak. So I'm in a slightly wierd state too, but I'm assuming this means it would work with Plug.kak...

I'm gonna leave this open so others can find this advice because I'm not sure I'm 100% sure on what's going on... I did build Kakoune from Master after you opened this bug so it could even be related to that.

Anyways thanks for the report and let me know if you have any further issues.

Kabouik commented 3 years ago

I had to do the same thing as @egolep to make xmux.kak work again, i.e., install connect.kak (before upgrading xmux.kak, I was still using the version that didn't depend on connect.kak and didn't support multi-terminal) and symlink ~/.config/kak/plugins/xmux.kak to /.config/kak/autoload/xmux.kak. Not sure why the latter is necessary.

I'll still have to upgrade my kakrc because I see the new version of xmux.kak incurred breaking changes, my custom commands won't work anymore after the upgrade.

Thanks for this great plugin by the way @forbesmyester, rest assured it's used by some, and is very useful! Maybe making a release of the older commit before the connect.kak dependency would be useful for backwards compatibility with old kakrc files, especially for users who don't need multi-terminal?

forbesmyester commented 3 years ago

Hi,

I think I should have tried much harder at backwards compatibility, but in all honesty I didn't see myself maintaining the older version because the Kakoune commands were a little ill thought out and it had reams of shell script embedded in the kak source files, so was rather difficult to with.

Aside from that I don't think I can maintain a version that I'm not using / dog-fooding, mostly because I think the community for this plugin is really small.

Could be that xmux (as apposed to xmux.kak) has a bigger future/community, I did think about porting it to VIM / other... There's very little complexity in the Kakoune plugin after the newer version.

Kabouik commented 3 years ago

I totally understand. I was more thinking about a release of the older version than something to keep maintaining, but users who really want the old version can also just pull the older commit if really necessary.

I don't really understand why loading the plugin with plug.kak doesn't work anymore. Do you have any idea? Moving/symlinking it into ~/.config/kak/autoload works but this making my kak configuration folder less feng shui!

forbesmyester commented 3 years ago

I think you realise, but users could use https://github.com/andreyorst/plug.kak#branch-tag-or-commit with commit hash https://github.com/forbesmyester/xmux.kak/commit/c9b24b6706bf1d8ed098db8371b9198bf73ffc12 . As it is all self contained it is, I suppose easier to install.

Kabouik commented 3 years ago

Thanks, I will give that a try if I can't get master to work on my end.