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

Episode 5: Include explanation of "datafile" #840

Open
mleverance opened this Issue Aug 29, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@mleverance

mleverance commented Aug 29, 2018

In the Loops episode, the "Variables in Loops" exercise early in the episode introduces the term 'datafile' as follows:
What is the output of the following code?

$ for datafile in *.pdb
do
ls *.pdb
done

Now, what is the output of the following code?

$ for datafile in *.pdb
do
ls $datafile
done

This is the first instance of datafile. In the lead-up to this exercise, 'filename' is used in conjunction with the loop for *.dat files. It would be helpful to include an explanation of how datafile is different and why it's used in the exercise. Information about whether it's connected to any specific file extension types, or if there's a way to know when to use datafile vs. other terms when writing code, would be helpful for learners.

Datafile shows up again later in the lesson under "Nelle's Pipeline: Processing Files" so learners will see it again, but it isn't expanded upon in that part either.

jwarthur added a commit to jwarthur/shell-novice that referenced this issue Sep 18, 2018

Explain choice of variable name prior: issue swcarpentry#840
Issue swcarpentry#840 raises the concern that the variable name used is changed without explanation. This change attempts to address this concern by including an additional paragraph to explain the arbitrary nature of variable name choice.

jwarthur added a commit to jwarthur/shell-novice that referenced this issue Sep 18, 2018

Merge pull request #1 from jwarthur/jwarthur-patch-1
Explain choice of variable name prior: issue swcarpentry#840
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment