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

feat: add support for Zellij #35

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

dynamotn
Copy link

@dynamotn dynamotn commented Apr 21, 2024

I'm considering about adding to the same wiki page that shows wezterm
instructions.
Zellij has already default keybindings with key, but not support fully seamlessly navigate.(zellij-org/zellij#967)

@hiasr
Copy link

hiasr commented May 3, 2024

@numToStr Is there anything holding this PR back? With vim-zellij-navigator this would make the Zellij support complete!

@clorl
Copy link

clorl commented Aug 11, 2024

Would love for this to be merged

@carmen-gh
Copy link

would be nice to have support for zellij

Fix zellij mappings for up/down
@BrendanMesters
Copy link

Is there any specific reason why this PR has not been accepted yet?
Cause it seems like its been open for close to a year already without any issues, and I would quite like this functionality on the main branch, given there are no reasons to block it...

@carmen-gh
Copy link

Meanwhile I use the fork https://github.com/dynamotn/Navigator.nvim
Thanks @dynamotn

@BrendanMesters
Copy link

@carmen-gh I know this is possible, its just annoying that there seems to be little to no concern from the original plugin authors for this merge :/

but yeah, its not a huge issue

@MattSturgeon
Copy link

its just annoying that there seems to be little to no concern from the original plugin authors for this merge :/

Looking at the repo's history/activity, it seems @numToStr has taken a step back. The last commit to main was Feb 2023, so nearly two years ago now.

I don't want to imply that the original author/maintainer is in any way obligated to continue working on this project. This is open source, after all. Nor do we know why they've been inactive.

But if someone is willing and able to maintain a fork that may be the best path forward at this point.

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.

8 participants