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

Cover how to exit VI/VIM #607

Open
ErinBecker opened this Issue Aug 17, 2017 · 8 comments

Comments

Projects
None yet
10 participants
@ErinBecker
Collaborator

ErinBecker commented Aug 17, 2017

Original submitted to instructor training repo. Please see discussion here: carpentries/instructor-training#487

@souravsingh

This comment has been minimized.

souravsingh commented Sep 25, 2017

@ErinBecker I am interested in covering this. Do I need to add a new section?

@ErinBecker

This comment has been minimized.

Collaborator

ErinBecker commented Sep 25, 2017

Thanks @souravsingh! I think this might be best in a callout. Any thoughts from the maintainers?

@gcapes

This comment has been minimized.

Contributor

gcapes commented Sep 26, 2017

Yes, a callout would be ideal if this is going to be covered. As always, what would you take out to make room for it?

However, the lesson doesn't cover using vi, so you could argue it isn't that useful covering how to exit from vi. You might equally argue, why don't we cover how to exit emacs?

@vai2fc

This comment has been minimized.

vai2fc commented Oct 5, 2017

For what it's worth, a callout (like the one in Git Novice lesson 2) could help those using the tutorial to teach themselves from getting stuck in a Vim loop.

@gdevenyi

This comment has been minimized.

Contributor

gdevenyi commented Oct 10, 2017

Hi,

I'm not sure when users would end up in VI/VIM in the shell-novice lesson. This is a problem that people run into in git when EDITOR isn't specified.

@jttkim

This comment has been minimized.

Contributor

jttkim commented Oct 10, 2017

@gdevenyi it also happens in rather numerous other situations when EDITOR is unspecified (or, in fact, set to vi). I've seen it happen, my gut feeling is it's more frequent when learners are using a Linux box (but that may be because it happens to me on Linux boxes only). It may not happen if a learner sticks strictly to the lesson, but googling something and trying that out is all it takes to possibly end up in vi without particularly bargaining for that. Also, being aware of the existence of vi and having some minimal ability to handle encounters with that will help learners as they independently continue using the shell after the workshop, even if they don't have any such encounter during the shell lesson.

On this occasion, for what it's worth I have once upon a time written this simple vi tutorial: http://jtkim.dreamhosters.com/vi_minitut.html , please feel free to use this in whichever way it may be useful

@iglpdc

This comment has been minimized.

Contributor

iglpdc commented Oct 10, 2017

I agrre with @gdevenyi. And as, @vai2fc says above, we cover this, and also how to select an editor, in the Git lesson. Maybe a link to that callout can help.

@hadimoh80

This comment has been minimized.

hadimoh80 commented May 10, 2018

I think that it is a great idea to add VI/VIM in this lesson.

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