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

Regular windows and echo for editing suggested #395

Open
wants to merge 1 commit into
base: gh-pages
from

Conversation

Projects
None yet
4 participants
@LiuGangKingston

LiuGangKingston commented Mar 15, 2017

Suggestions are put into the new file suggestions.txt

echo '!@#$%^&*()_+ "this is important."' >> mars.txt

4.3) Big text files can be editted by using method in 3).

This comment has been minimized.

@iglpdc

iglpdc May 30, 2017

Contributor

We use nano to avoid vim complexities. We also cover echo and redirection, but it the shell lesson, which is a prerequisite for this one.

@iglpdc

@LiuGangKingston, would you like to add the first item (about changing the font size in Git Bash) into the instructor guide for the shell lesson? You can find it here https://github.com/swcarpentry/shell-novice/blob/gh-pages/_extras/guide.md. There a Windows specific paragraph at the end.

It would be much useful there and as I said learners are supposed to go thru this lesson first.

cd /d/
cd /e/
respectively, in the git bash.

This comment has been minimized.

@iglpdc

iglpdc May 30, 2017

Contributor

We work in the Desktop all the time to avoid this problem. As some earners are not used yet to the command line, we try to avoid going to "dangerous" places where important data may be.


1) The font size of git bash should be set big enough by
right clicking git bash window -> Options -> Text -> Select... -> Size -> 20

This comment has been minimized.

@iglpdc

iglpdc May 30, 2017

Contributor

This is really useful for instructors that are not use to Windows and comes up often in workshops.

6.6) git merge a.new.branch
6.7) git brach -d a.new.branch
6.8) git push --delete origin a.new.branch

This comment has been minimized.

@iglpdc

iglpdc May 30, 2017

Contributor

Branching is too complicated to fit into this lesson. We've decided to skip it out and place it in a future intermediate git lesson.


6.0) git clone a.new.git.repository
then go to the directory
6.1) git checkout -b a.new.branch

This comment has been minimized.

@maxim-belkin

maxim-belkin Jun 8, 2017

Contributor

I'd advocate against checkout -b for the learners and use the original git branch <blah> && git checkout <blah>. Once that is explained, it is safe to mention that you can do both of these steps at once with checkout -b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment