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

Suggest .bashrc instead of .profile for install #35

Merged
merged 1 commit into from
Jun 14, 2021

Conversation

MartyLake
Copy link
Contributor

On my system (ubuntu), sourcing .ok.sh within .profile instead of .bashrc displays an error when loading into my user session. Souncing from .bashrc instead solves the issue.

See attached photo for exact error
2021-06-13 18 32 35

On my system (ubuntu), sourcing `.ok.sh` within .profile instead of .bashrc displays an error when loading into my user session.
@doekman
Copy link
Collaborator

doekman commented Jun 14, 2021

Refering to .profile is probably not the best thing (when I look at the documentation, .profile should be executed if it exists, but apparently it doesn't always).

The thing is named ok-bash, so it's probably best to refer to bash-style startup script.

I was still thinking about the comment between brackets: the irony is a bit less without the eldest startup scripts of startup scripts.

@doekman doekman merged commit 7baed6e into secretGeek:master Jun 14, 2021
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.

2 participants