Hi @pbnj thank you for thinking about this and your effort to contribute help! Sorry for the delayed response, only saw your message late yesterday and haven't had a chance to think about this properly 🤯

Could you please confirm your Vim patch passes our syntax and ftdetect tests before they merge it? FWIW our past experience with uncoordinated merging into Vim/Neovim was #89

If there is no interest from the original maintainers to maintain upstream just support in vim,

Speaking as the most active dev (not project owner and not in a position to speak for the vim-just project):

For me, it isn't lack of interest, the show-stopper is more along the lines of https://00f.net/2021/03/26/it-doesnt-work/

To be more specific: On the one hand, I think including vim-just in Vim/Neovim would be cool, good for vim-just as a project and good for justfile authors. On the other hand, it would hugely increase the support burden on vim-just maintainers - mainly because it would make more versions of vim-just floating around that we'd need to keep track of, and most of which we can't help.

vim-just is tricky to maintain, and the current maintainers of vim-just don't have the capacity for it to become a bigger effort, not even for things we would otherwise be interested in.

would it be OK if I replace Noah Bogart's name with my name as the Maintainer in the file headers in upstream vim and credit Noah Bogart / this project in the headers?

Interesting idea. If it's clear your version is a downstream soft-fork we can't support, maybe this might help the concerns.

Reopening this issue for comment from @NoahTheDuke - someone making a PR and taking on maintaining it indicates substantial community interest.

Plans on merging vim-just in upstream vim/neovim #111

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions