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

Remove Vi/Vim bias. #124

Open
jasonm23 opened this issue Jun 25, 2015 · 7 comments
Open

Remove Vi/Vim bias. #124

jasonm23 opened this issue Jun 25, 2015 · 7 comments

Comments

@jasonm23
Copy link

Learn at least one text-based editor well. Ideally Vim (vi), as there's really no competition for random editing in a terminal (even if you use Emacs, a big IDE, or a modern hipster editor most of the time).

Specifically...

as there's really no competition for random editing in a terminal (even if you use Emacs

This simply isn't true, it should be redacted.

I suggest something a little more balanced.

Learn at least one text-based editor well. Ideally Vi/Vim or Emacs, so you can immediately use your editor from the a terminal. Be aware the Vi/Vim will almost always be part of any standard *nix distribution.

@jasonm23 jasonm23 changed the title Remove Vi/m bias. Remove Vi/Vim bias. Jun 25, 2015
@NewAlexandria
Copy link

I am biased toward vim, but regardless I think there's a mixed message to say that someone should learn enacts though it won't always be installed.

@jasonm23
Copy link
Author

Most of the time it will, and it is straight forward to do apt-get / yum / port / etc.

People are going to be installing the web server / language etc that they want to use, so don't be so obviously and obnoxiously biased.

@hastinbe
Copy link
Contributor

vi is the ideal choice due to its availability on most installations, you can't argue against that. The statement about no competition or hipster editors would be better left out.

@anEffingChamp
Copy link

As biased as it may be, it certainly lends entertainment value to what could
otherwise become a very dry topic.

@nwinkler
Copy link

I think the real value of this entry is in the first sentence: "Learn at least one text-based editor well"

Since we shouldn't let this turn into a religious war (which is easy for the Vi/Emacs discussion) - shouldn't we leave it at this first sentence? We can list some examples, like "for example Vi(m), Emacs, Nano or Ed" - well maybe we should skip the last one...

The only other option would be to list every single text-based editor, but then someone is going to complain about the order in which they are listed.

@jasonm23
Copy link
Author

Seems like the most useful solution to me.

I think including Ed would be cute.

nwinkler added a commit to nwinkler/the-art-of-command-line that referenced this issue Jun 26, 2015
Reworded based on the discussion in jlevy#124.
@nwinkler
Copy link

I've created #129 based on this... Feel free to review/comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants