-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
adding explanation to 'example.aliases.sh' #499
base: master
Are you sure you want to change the base?
adding explanation to 'example.aliases.sh' #499
Conversation
adding explanation on how to use to './custom/aliases/example.aliases.sh'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you also update the description in README?
For consistency, you also need similar changes to the other types of custom modules.
@@ -1,2 +1,9 @@ | |||
# Add your own custom alias in the custom/aliases directory. Aliases placed | |||
# here will override ones with the same name in the main alias directory. | |||
# Add your own custom alias in the custom/aliases directory. Aliases placed here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line doesn't fit in 79 characters. Column 80 is reserved for the line continuation mark (such as \
) in typical text editors.
# 1. use the exact naming schema like '<my_aliases>.aliases.sh' where the | ||
# filename ending ~.aliases.sh is obligatory (just <my_aliases>.sh won't do) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# 1. use the exact naming schema like '<my_aliases>.aliases.sh' where the | |
# filename ending ~.aliases.sh is obligatory (just <my_aliases>.sh won't do) | |
# 1. use the exact naming schema like '<my_aliases>.aliases.sh' where the | |
# filename needs to end with .aliases.sh (just <my_aliases>.sh does not work) |
# Add your own custom alias in the custom/aliases directory. Aliases placed here | ||
# will override ones with the same name in the main alias directory. | ||
# | ||
# please note that you have to: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, technical documentation tends to avoid using terms like "please" because when does one know when or not to use them?
I'd recommend having this be a title...
# please note that you have to: | |
# Usage |
adding explanation on how to practically use './custom/aliases/example.aliases.sh'