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

Redirect to /dev/null caused segfault for nvim < 0.9.0 #155

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

shadowwa
Copy link
Contributor

Tests are now covering case before/after milestone concerning epuppet:

  • epuppet detection added in filetype.vim in vim 8.2.2402
  • epuppet detection added in filetype.vim in neovim 0.5.0
  • filetype detection done with filetype.lua in neovim 0.8.0

Tests are now covering case before/after milestone concerning epuppet:
- epuppet detection added in filetype.vim in vim 8.2.2402
- epuppet detection added in filetype.vim in neovim 0.5.0
- filetype detection done with filetype.lua in neovim 0.8.0
@lelutin
Copy link
Collaborator

lelutin commented Sep 18, 2024

interesting. I will most definitely want to keep the removal of the redirection of stdout to /dev/null.

While I think adding older versions could help us identify what's going wrong with filetype detection, I wonder though: do we wish to commit/state that this module is going to keep its code compatible to such older versions of neovim?

we currently don't state clearly which versions of vim/neovim are supported in the README file.

seeing what I found about the versions distrubuted below, I'd be willing to support as far back as vim 9.0 and neovim 0.7.2. or if we push things, maybe vim 8.0 and nvim 0.7.0

what are your thoughts about this? am I being too optimistic about dropping support for older versions?

what's currently shipped in the most popular distros:

neovim:

so overall the oldest version among those is 0.7.2

vim:

the oldest version among those is 0.9.0

@lelutin
Copy link
Collaborator

lelutin commented Sep 18, 2024

btw, this is side-tracking things a bit but @shadowwa you've been contributing a couple of changes for the last couple of years. I wonder if you'd like to become a part of this module's maintainer team?

I personally don't have the control over who has access to the repository, though. @rodjek what do you think about the above idea if they seem to be interested? I'm still interested in keeping this module alive but I sometimes go missing for months by lack of time / energy..

@shadowwa
Copy link
Contributor Author

My first goal was to manage tests on any versions of vim/nvim we wanted, to continue to work on subtype detection.
Now for the vim-puppet plugin, I think that if maintaining older vim compatibility is burden, a minimal version of vim 8.0 and nvim 0.7.0 is pretty good.

As for becoming part of maintainer, I'm willing to help but I'm afraid to be like you, as sometime lack time/energy.

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.

2 participants