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

determine compatibility; also, I did research #36

Open
GiselleSerate opened this issue Dec 31, 2017 · 4 comments
Open

determine compatibility; also, I did research #36

GiselleSerate opened this issue Dec 31, 2017 · 4 comments
Assignees

Comments

@GiselleSerate
Copy link
Owner

GiselleSerate commented Dec 31, 2017

While tagging this repo, I discovered some other repos in the bashrc tag and others that might be helpful for figuring out what shells are actually common and necessary to be compatible with. Which, maybe we don't have to add the other shells, maybe we need to worry about depth rather than breadth?
Anyway, some examples I found:

@aryarm
Copy link
Collaborator

aryarm commented Dec 31, 2017

Yeah, I've actually been reading up on a lot of other similar projects, especially for cds.
There's some really great stuff out there. Example: https://github.com/junegunn/fzf
I think cds is unique in that we attempted to make it an extension of cd. I haven't seen any other attempts like that. I also like how simple the cds command is. It's nice when we keep things short and sweet.

@GiselleSerate
Copy link
Owner Author

I am definitely a fan of cds. I think it's awesome and haven't found anything like it either. I mean, the particular format and the concept of having all your dotfiles in a repo is definitely not new, but I don't think we should be particularly worried about that. We do seem to have something unique to offer here.

@GiselleSerate
Copy link
Owner Author

Useful thread for compatibility: https://stackoverflow.com/questions/11376975/is-there-a-minimally-posix-2-compliant-shell
Sounds like we should use dash or posh to check for compatibility, although there's no good solution besides checking a bunch of shells.

@GiselleSerate
Copy link
Owner Author

What we probably want to do:
Go through common shells and test all our commands on them. As we test each command on a system, add the appropriate badge in the wiki. If it works for every command in a file, add it at the top, next to the filename in the wiki. If it only works for some, add the badge next to each command's name. (Or maybe above, or maybe under? Haven't decided, some of these commands are long.)
In approximate order of priority:

  • wsl
  • ubuntu (use VM)
  • zsh
  • osx

@GiselleSerate GiselleSerate self-assigned this Jun 18, 2018
@aryarm aryarm mentioned this issue Jul 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants