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

stgit.el update #521

Open
nicolas-graves opened this issue Jan 6, 2025 · 6 comments
Open

stgit.el update #521

nicolas-graves opened this issue Jan 6, 2025 · 6 comments

Comments

@nicolas-graves
Copy link

Hi StGit!

I was trying to package stgit.el for Guix, and I noticed tere is quite some cleaning to do on stgit.el, I have the following warnings on compilation:
log.txt

I also wondered about the status of the package, I've seen that magit-stgit has been updated and I'm wondering if the statement

If you are looking for full fledged StGit support in Emacs, then have a look at `stgit.el' which is distributed with StGit.

as found on MELPA stable still holds true, or if magit-stgit is the one recommended now (maybe we should make a release for MELPA stable ?).

@jpgrayson
Copy link
Collaborator

Hi @nicolas-graves. Thanks for working on packaging StGit for Guix.

The state of StGit's various emacs packages is not great.

You're right that magit-stgit has had some recent-ish maintenance and may be in better shape than stgit.el. But I can't personally vouch for whether magit-stgit is in a release-worthy state. Perhaps @tohojo could comment?

@tohojo
Copy link
Contributor

tohojo commented Jan 6, 2025

Well, I'm using it for my daily(ish) work, so while the bindings are not complete, I'd say it's definitely a usable subset.

I've never used stgit,el, so can't really say anything about how that compares to magit-stgit, though :)

@jpgrayson
Copy link
Collaborator

Thanks for that perspective, @tohojo--that's helpful. So perhaps it would make sense to tag the latest magit-stgit as @nicolas-graves suggests?

Do we think that would be a 2.2.0 or 3.0.0 tag?

I'm not super familiar with how MELPA works, but it appears from looking at the melpa recipe for StGit that if we were to push a new magit-stgit tag, MELPA would just use that tag automatically.

@tohojo
Copy link
Contributor

tohojo commented Jan 6, 2025

Yeah, I agree that tagging a new version makes sense. No strong opinion about which version number to go with. I suppose the switch to transient could be occasion enough to go for the big 3.0? :)

No idea how melpa works, but from just looking at that recipe I guess you're right?

@jpgrayson
Copy link
Collaborator

I'll create a new 3.0.0 tag for magit-stgit.

@Reasonable-Solutions
Copy link

I tried using stgit.el today and immediatley ran into symbol void: git-status, which i guess comes from the venerable git.el from git/contrib/emacs (well, used to to come from up until several years ago)

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

No branches or pull requests

4 participants