Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
Git Basics: Working with Remote Repositories: Cloning
I'm using the Treehouse console for this lesson.
In the video at 2:17, the instructor does a "git log" command for the "our_clone_project" repository. He does something without saying what he does to show the "treehouse~/our_clone_project $" prompt even though the screen isn't at the "(End)" of the entire log.
What does the instructor do to return to the "treehouse ~/our_clone_project $" prompt after the "git log" for it is listed in it's entirety? Do I need to scroll down to the "(End)" of the log to do something to show the prompt or can I do it where he does it on the screen?
I'm using Team Treehouse's Ubuntu Linux console for this lesson. This is my 1st experience with it. I'm doing my course work at Worksource Oregon.
The way I got around it was enter "git log", & when the entire project history appeared, I closed the window & reloaded the console, & then I made sure was on the correct branch in the repository. I've since finished the lesson successfully without another problem.
Yes, I submitted critique to the videos directly, too. Every step must be shown in the video & verbalized so students can follow directions explicitly.
Oliver Duncan16,641 Points
Awesome, and I agree. But you shouldn't have to reload the console every time you want to exit a git log! Try 'q' next time you're reading your git log or checking out a git diff. It'll give you more time to program.
Duly noted. I've written it down in my notes. Thanks.