Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use IDs instead of indexes to identify the Runner #110

Merged
merged 2 commits into from
Feb 13, 2021

Conversation

yunake
Copy link
Contributor

@yunake yunake commented Jul 18, 2014

The IDs are guaranteed to be unique and stay constant, no matter what you do to the pane or window.

This diff is based on the idea in #81, by Roberto Agostino Vitillo (@vitillo), but rewritten to:

  • apply to the latest version of the source
  • use IDs for both windows and panes, not just panes

I have tested panes and windows as runners, both with VimuxUseNearest and without it. VimuxTogglePane() also works just fine.

This change is incredibly useful because once you have the runner, you can do whatever you want: spawn new panes, move the pane to a different window, join it back, reorder the panes and windows, change layouts, — it does not matter, your runner will remain set.

@yunake
Copy link
Contributor Author

yunake commented Sep 28, 2015

sigh @benmills

@m42e
Copy link
Contributor

m42e commented Oct 8, 2015

👍

@eks
Copy link

eks commented Oct 15, 2015

Hey guys, this is exactly what I was looking for.
What about update and merge this PR?
What do you think @benmills?

@hodak
Copy link

hodak commented May 15, 2016

This is absolutely brilliant, I'm moving to fork for now. Thank you @yunake

@yunake
Copy link
Contributor Author

yunake commented May 15, 2016

i have no idea why @benmills didn't even show up here to comment. if he dislikes the idea, a clear communication would help clear things up and i could move on. i still use this every day and would love to see this merged. Ben, do you still plan to actively maintain vimux?

@leostera
Copy link
Member

leostera commented Jul 1, 2017

Hey @yunake, don't think @benmills is actively ignoring this :) life gets in the way sometimes.

Either way, this is something I've been meaning to look into myself -- an easy way of keeping a map between open panes and runners so that rearranging a tmux layout doesn't mess things up.

I'll be reviewing your PR promptly and we can take it from there, how does that sound? 😄

@yunake
Copy link
Contributor Author

yunake commented Jul 2, 2017

Hey @Ostera I've seen you being given write access and this has renewed my interest in getting this merged. The conflicts look trivial to resolve, but I've been using my own fork for three years now and have no idea what else might've changed in the way the plugin operates. Please review and let me know what you think, this might no longer be the best approach?

Copy link

@stellarhoof stellarhoof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only conflict is trivial: system -> _VimuxTmux. LGTM otherwise

@yunake
Copy link
Contributor Author

yunake commented Jul 3, 2017

I've resolved the conflicts

@yunake
Copy link
Contributor Author

yunake commented Jul 3, 2017

i'm quite busy with other stuff, i will re-test this changeset on top of current master in a couple of days and let you guys know. i think it should work :)

@stellarhoof
Copy link

@yunake ping

@astier
Copy link

astier commented Jan 12, 2020

6 years later hope dies last

@alerque
Copy link
Member

alerque commented Feb 13, 2021

All home is not dead. As of this last week Ben turned up and we got the repository migrated where we now have three maintainers and can add more. I'm happy to consider adding more contributors with permissions to work directly based on contribution activity.

Looking through the outstanding PRs there seems to be several that are going to conflict, but this looks like one of the more widely desired ones that people have switched to forks just to get, so I'll probably prioritize this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants