version-control doesn't work for CVS (or any other backends besides git?)

[valrus]

I know, I know, CVS is old and terrible, but I'm at work and I have no choice.

The version-control layer claims it "should work with all VC backends," but to all appearances it's actually Git-centric. E.g.:

• trying to do SPC g . C in a CVS-controlled buffer gives Wrong type argument: stringp, nil
• SPC g . l gives Not inside a Git repository
• the implementation of the layer looks like most of the bindings go to magit commands

I don't really expect any layers to actually support CVS in this day and age—I can make my own private layer for that—so maybe this can just be regarded as a documentation bug, but I think version-control's documentation is misleading if not outright wrong.

[TheBB]

The magit commands don't work outside of a git repository. The others should work in all repositories that your chosen margin program supports, so make sure you have chosen one with extended VCS support (that is, something other than the default value of git-gutter+). Whether these support CVS or not, I cannot say.

To see which commands are from magit and which are from elsewhere, check the documentation of the microstate (use ?)

@Ralesi This distinction should probably be made more clear. I also note that the VCS microstate will provide magit bindings even if the magit package is not installed, which is probably something we need to change.

[TheBB]

git-gutter supports git, mercurial, subversion and bazaar. diff-hl claims to be tested with all of these and that it "may" also support other backends.

In other words, you are probably out of luck for CVS support.

[punassuming]

Any currently supported method of conditionally adding bindings to a microstate?

[TheBB]

No there isn't. :-( Can of course hack it in a different way.

@syl20bnr This would be really handy.

[yifange]

It would be nice to have some Perforce support too. I saw the perforce package and was hoping for it.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!