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

Proposed Changes to shell-novice: Shell Scripts - Instructor Checkout #1170

rbartelme opened this issue Feb 11, 2021 · 3 comments
help wanted Looking for Contributors type:clarification Suggest change to make lesson clearer


Copy link

rbartelme commented Feb 11, 2021

This episode could use more of an emphasis on why we are teaching and could introduce best practices at the end...

  1. Why might we want to reuse commands? This is not at the beginning of the episode.
  2. the history | tail -n 5 > example seems out of place. The example is "We’d like to be able to re-create the graph later if we need to, so we want to save the commands in a file." While this is true that this analysis can be run to generate a graph, is this common practice?
  3. Links at the end of the episode to best practices for writing bash scripts (i.e. using shebang at the beginning of a file, what are permissions, how can we make a script executable with chmod, etc.)
Copy link

Hi. Thanks for the suggestions.

We would welcome a PR demonstrating the proposed changes to the lesson.

Copy link

@gdevenyi hoping to get to this in a bit when I have more time.

@gcapes gcapes added the type:clarification Suggest change to make lesson clearer label Jun 21, 2021
@deppen8 deppen8 added the help wanted Looking for Contributors label May 6, 2022
Copy link

It is a common practice to write Shell scripts to automate repetitive tasks.

If it is desired to have a singe line sequence of commands, we can use the ';' symbol to execute the 'chmod u=rwx' command to change permissions to an executable shell script, ..

history | tail -n 5 >; chmod u=rwx *.sh

that way, the shell script is an executable file by the user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
help wanted Looking for Contributors type:clarification Suggest change to make lesson clearer
None yet

No branches or pull requests

5 participants