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

"config --edit" to both check editor config & configure more conveniently #579

Open
katrinleinweber opened this issue Dec 13, 2018 · 2 comments

Comments

@katrinleinweber
Copy link
Contributor

@katrinleinweber katrinleinweber commented Dec 13, 2018

Would it make sense to update the section https://github.com/swcarpentry/git-novice/blame/0f775ae563a09163984e134b068d56928104ee29/_episodes/02-setup.md to something like:

Let's test and review the settings we made just now. Type git config --global --edit to open your git configuration in the text editor that you just configured.

Related to #360, because it could prepare learners for switching between CLI & editor during git operations.

katrinleinweber added a commit to katrinleinweber/git-novice that referenced this issue Jan 15, 2019
)
@tkphd
Copy link
Contributor

@tkphd tkphd commented Jun 12, 2019

Possibly useful, as it teaches an alternative entry point into the config.
In a workshop I taught last week, I did something similar: to teach that the config is just a file, I had students nano ~/.gitconfig to see the options we had just set. This also applies to local .git/config files.

As a test to make sure the config was successful, so helpers can address misconfigurations, this would make sense. On the other hand, committing ourselves and our helpers to resolve configuration difficulties with the myriad possible editors might be a distracting scope creep for this lesson.

@katrinleinweber
Copy link
Contributor Author

@katrinleinweber katrinleinweber commented Jun 27, 2019

Cool, thanks for sharing your teaching example :-) About "distracting": Would #671 help reduce that risk in your view?

However, since our only config instructions are crucial for the rest of the lessons, helpers will have to debug problems anyway, won't they? IMHO, this is a question of cleverly ordering instructions and checks so that errors do pop-up as quickly as possible.

katrinleinweber added a commit to katrinleinweber/git-novice that referenced this issue Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants