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

All my changes in one PR, since I had made a mess of things - support ion, simplify logic #172

Open
wants to merge 17 commits into
base: master
Choose a base branch
from

Conversation

magnus-ISU
Copy link

The biggest change is that this PR simplifies a lot of logic, makes the program touch less stuff / have less files that could break, resolving #162, also improves some help messages and causes antidot init to tell the user what to do with the output / how to run it. These messages explicitely say to use -s for fish and ion since on Garuda Linux running fish still keeps $SHELL == bash somehow.

Also makes it marginally easier to support new shells.

Previously antidot clean would generate ~/.local/share/antidot/kvstore.json, ~/.local/share/antidot/env.sh, and ~/.local/share/antidot/alias.sh and then antidot init would create a default script that would source those two scripts, with extra logic to test if those scripts exist and other nonsense.

Now antidot clean generates ~/.local/share/antidot/kvstore.json and antidot init creates a script based on the kvstore that creates all aliases and sources all variables.

Next, this PR adds support for the ion shell.

Additionally, this PR improves some help and error messages.

Finally, this PR adds a section to the README about how to build antidot, and adds the binary file to the .gitignore.

…dot and sourcing them, just having antidot init print all rules
…es the proper script for the shell whenever it is run
…'t use `-c` when listing how to source the output of `antidot init` because it isn't needed
…plicit `-s` option in recommendation by `antidot init`
@doron-cohen
Copy link
Owner

@magnus-ISU thanks for the PR. I really appreciate the effort. It's been some time since I actively maintained this project but now I am back.
I plan to make some changes in the code and some align with what you did here. I will take some of your patches and push them in the next few weeks.

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

Successfully merging this pull request may close these issues.

None yet

2 participants