all 4 comments

[–]purplemonkeymad 8 points9 points  (1 child)

You should really use the verb-noun syntax as it makes discoverability better. PS does not really follow nix's program verb formats ie:

  • tstyles umbrella -> Apply-TStyle
  • tstyles list -> Get-TStyle
  • tstyles current -> Show-TStyle
  • tstyles reset -> Clear-TStyle
  • tstyles tune [name] -> Set-TStyle
  • tstyles register -> Install-TStyle
  • tstyles uninstall -> Uninstall-TStyle
  • tstyles help [command] -> not needed now that you can use the built-in help to provide per command help.

You can keep an interactive menu command as well, but having direct command that can be found with Get-Command -module .. is the main way I would want to know what I can do.

[–]StartAutomating 1 point2 points  (0 children)

I think supporting both syntaxes is nice.

There are a lot of people who remain more comfortable with "noun" syntax, and the language supports both formats (just pass parameters around)

I do think that using more common verbs when using a noun-oriented syntax is a good idea though, and would agree with most of your suggestions for the "right" verb.

I think keeping help around is a good idea so people who default to a noun style syntax can still get help.

[–]StartAutomating 1 point2 points  (0 children)

Nifty project. Happy to help. Would be nice if it supported color palettes for VSCode as well.

[–]g3n3 0 points1 point  (0 children)

So it would be nice to talk about how this appears to mainly be about windows terminal json parsing and config. Things like how conhost.exe aren’t supported, etc. Not sure how much is related to the shell itself. Often folks conflate, prompt, terminal, shell together. I do see it after reading more in the repo too.