Fish shell support.

[mcameron]

Any chance of fish shell support in scmpuff init -s?

[mroth]

I believe this should be relatively simple but I'm not familiar with fish scripting.

Essentially the following scripts would need to be made fish compatible:
https://github.com/mroth/scmpuff/tree/master/commands/inits/data

My first hope would be to make whatever changes so that fish can parse and understand them, and have a single master script. However, if fish does not have any mode where it can understand sh style functions, then what will have to happen instead is fish-compatible versions of those scripts will have to be created.

Once that is done, it would likely be a relatively simple matter to have scmpuff serve up the proper version based on the parent shell.

[mroth]

The fish scripts would have a different filename suffix I imagine? If so, same directory should be fine.

Here is where they get included into scmpuff, for reference:
https://github.com/mroth/scmpuff/blob/master/commands/inits/scripts.go

[kholbekj]

I take it this was stalled? Was there some progress made? I could try to pick it up, but not a super confident fish scripter.

[kholbekj]

I have begun this over on https://github.com/kholbekj/scmpuff/tree/fish_compatibility hope it'll work out.

[paulirish]

@kholbekj whats the status of your fork? functional, but behind?

Am really enamored of the UX of scmpuff but definitely need fish support. :)

[mroth]

(FWIW, would be very happy to directly integrate the fish wrappers [that sounds funny] to the official release of scmpuff as soon someone makes them!)

[arbelt]

FWIW, I couldn't go without scmpuff when switching to fish, so I wrote a fish plugin for it here: https://github.com/arbelt/fish-plugin-scmpuff

It's installable via fisherman. Nothing fancy, just a basic port of the shell functions I found in this repo. Maybe they would be easy to integrate officially, but I wasn't sure how to easily fit them into the code here.

This was just personal use, so there's no readme or documentation in the repo, but it's just a couple shell functions. If it's useful for integration purposes I can add to them or tweak them (one thing that I have been thinking about is fallback to git status in an initialized repo without a first commit, since scmpuff_status just errors out in that case, whereas git status would show the staging area, but maybe scmpuff should handle that case?).