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

adding explanation to 'example.aliases.sh' #499

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dulhaver
Copy link
Contributor

adding explanation on how to practically use './custom/aliases/example.aliases.sh'

adding explanation on how to use to './custom/aliases/example.aliases.sh'
Copy link
Contributor

@akinomyoga akinomyoga left a 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
Copy link
Contributor

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.

Comment on lines +6 to +7
# 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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# 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:
Copy link
Contributor

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...

Suggested change
# please note that you have to:
# Usage

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.

3 participants