Suggestion: Tag the version #26
4 participants
I created a homebrew formula for zsh-autosuggestions, https://github.com/xu-cheng/homebrew/blob/zsh-autosuggestions/Library/Formula/zsh-autosuggestions.rb
But it won't be accepted to upstream unless you bump the version.
I'm having trouble finding time to update this project. Since you are interested, would you like to be given commit access to do some maintenance every now and then?
Thanks for the offer. But I don't do much about zsh programming as I am more of zsh user. You may find someone else to help you maintain the project. For example, https://github.com/zsh-users, they host a lot of zsh plugins. Also, whatever you choose, I suggest you create a tag on current version, so I can submit the homebrew formula upstream(it's nicer to keep all the plugins in one place).
On that note, I actually am interested in carrying this forwards. I was planning on forking it and just coding on that.
I don't know exactly what I intend to do. I'm currently using auto-fu but the completions block the main thread, which can get quite annoying. It's very stable (and it works well in my crazy complicated config), but it's also a bit more intrusive than I'd like, and it doesn't suggest from history. It has a ton of code, most of which is fairly scary. I thought I'd start from zsh-autosuggestion and move forward rather than paring auto-fu down. I'm not sure what changes this might entails, but they're big and architectural.
I think it might be best if I work in a fork. I might be able to also do maintenance, but I'm not sure what that entails. I might work in a fork or a branch... whatever floats your boat.
@PythonNut Even though zsh is a good shell, it is not a good platform for programming and my knowledge is limited, so I can't help you much with fixing the bugs.
If you manage to work around the issues, we can ask github to rebase the network and make your fork the main repository.
@tarruda Okay then, it's settled. I may never get around to this, but we'll see.
That said, what to do about (tagging the version|maintaining the current codebase in general)?
That said, what to do about (tagging the version|maintaining the current codebase in general)?
Personally I don't care much about tagging this project, but that's your decision if you become the maintaine :)
I recommend you tag the version for the project. So it will be easier for users to arrange and update. Also it will allow package manger to handle such a good plugin.
Please tag the version, so I can create a homebrew formula for this.