6 ms·

I Made an Extended Version of Vimtutor – Introducing Vimtutor Sequel

229 points by micahkepe 2y ago

micahkepe 2y ago
Hey everyone, It looks like my submission redirected to the GitHub repo instead of displaying the full context. Here’s the detailed information about Vimtutor Sequel: --- Hey Hacker News community, I'm excited to share something I've been working on - Vimtutor Sequel! After going through the original vimtutor, I felt there was a need for an extended tutorial for some more advanced topics not covered in the original tutor program. What's Vimtutor Sequel? Vimtutor Sequel picks up where the original vimtutor left off. It’s designed for those who already know the basics and are ready to dive into more advanced Vim features and commands. Key Features: - Advanced Topics: Dive into splits, spellcheck, advanced search and replace, macros, Vim scripting, plugins, sessions, and registers. - Step-by-Step Tutorials: Hands-on lessons that encourage you to practice commands as you learn. - Custom Vim Configuration: Comes with a custom vimrc to ensure a consistent learning experience and mimic the original vimtutor. How to Install: For Mac: To get started, install Vimtutor Sequel using Homebrew: ```bash brew tap micahkepe/vimtutor-sequel brew install vimtutor-sequel ``` Then you can run with: ```bash vimtutor-sequel ``` For Windows/Linux: 1. Clone the repository: ```bash git clone https://github.com/micahkepe/vimtutor-sequel.git https://github.com/micahkepe/vimtutor-sequel.git ``` 2. Navigate to the repository: ```bash cd vimtutor-sequel ``` 3. Make a Copy of the Tutorial: ```bash cp vimtutor-sequel.txt vimtutor-sequel-copy.txt ``` 4. Run Vim with the Custom Configuration: ```bash vim -u vimtutor-sequel.vimrc vimtutor-sequel-copy.txt ``` Looking for Feedback! I'd love to hear what you think! Whether you spot any bugs, have suggestions for new lessons, or just want to share your thoughts, your feedback is really appreciated. Feel free to contribute or open issues on the GitHub repo. Links: GitHub Repository: https://github.com/micahkepe/vimtutor-sequel https://github.com/micahkepe/vimtutor-sequel Issues & Feedback: https://github.com/micahkepe/vimtutor-sequel/issues https://github.com/micahkepe/vimtutor-sequel/issues Thanks for checking it out, and I hope you find it useful in your Vim journey. Happy Vimming!
- mettamage 2y ago
  Awesome! When someone on HN years ago pointed me to vimtutor to oearn vim it was like magic! After many false starts, I now was able to use vim! I’ve never learned more than that as I am a casual user. Because of that tutorial I am happy to say that I can be a user at all. I’m stoked for a follow up :D
- abrenuntio 2y ago
  I'm looking forward to going through this... thank you so much!
- 3abiton 2y ago
  As a long time vim user, respect.
- e12e 2y ago
  > It looks like my submission redirected to the GitHub repo instead of displaying the full context. Did you start the submission title with: "Show HN:"?
  - micahkepe 2y ago
    No sorry I didn't this is actually my first post on here so still learning the platform.
    - deleted 2y ago
      [deleted]
globular-toast 2y ago
Learning vim was what convinced me that it's worth your time to learn tools. Far too many tools present themselves as "no manual required". It would almost be laughable for a phone app to require reading a manual, for example. But even developers these days refuse to read and just expect it to be obvious. What you end up with is VS Code, some of the good parts of vim, but still so far from what's possible if you spend the time to really learn your tools. After learning this valuable lesson, I proceeded to learn to use Emacs.
- imiric 2y ago
  For me it's not so much about the process of learning itself. To be honest, I'd rather avoid having to learn how a tool works to use it. Software that prioritizes ease of use and friendliness has a much broader appeal—and, consequently, user base—than those that don't. There's value in that. I chose to learn Vim, Emacs and other tools with a steep learning curve primarily because of their return on investment. They have great extensibility, so I can customize them exactly to my liking. I know that they won't radically change, or worse, disappear in a few years, as a lot of software does. So taking the time to learn how to use them is purely a selfish endeavor. I even put up with their quirks and shortcomings because of this, even though there might be alternatives that do feature X better, are faster, etc. Using these tools simply minimizes the chances I'll have to re-learn something else every few years. I'd rather avoid that.
  - SanderNL 2y ago
    Developer productivity is not and never was bottlenecked by their tools. One snap of the fingers in one of the many layers above us and million dollar projects succeed or fail. We are always a fancy dinner or business relation gone sour away from success or failure. Vim or emacs come into play at layer 245 in the system and their impact on the final business reality is approximately 0,003%.
    - globular-toast 2y ago
      > Vim or emacs come into play at layer 245 in the system and their impact on the final business reality is approximately 0,003%. Who cares? One fire or war and a carpenter's work all comes crumbling down. Should he then not care about his work or his tools or materials and nail any old shit together? Life is what happens when you're busy making other plans.
alabhyajindal 2y ago
Very well done! Congrats!
- micahkepe 2y ago
  Thank you so much I appreciate it!
nodra 2y ago
Will definitely try this. Thank you!
sourcepluck 2y ago
Does anyone know of something similar for Emacs - a sequel to the Emacs tutorial? I have flirted mentally with the idea of doing one, even spun up a few notes planning it out. This looks very cool! Vimtutor was great fun when I did it. Thanks to the author.
osigurdson 2y ago
I feel like vim is one of those things that requires dedicated time investment: "learn by doing" << "learn then do" in this case. I say this as I have been in the former category for too long. I'll definitely bookmark this link.

229 points by micahkepe 2y ago

Hey everyone, It looks like my submission redirected to the GitHub repo instead of displaying the full context. Here’s the detailed information about Vimtutor Sequel: --- Hey Hacker News community, I'm excited to share something I've been working on - Vimtutor Sequel! After going through the original vimtutor, I felt there was a need for an extended tutorial for some more advanced topics not covered in the original tutor program. What's Vimtutor Sequel? Vimtutor Sequel picks up where the original vimtutor left off. It’s designed for those who already know the basics and are ready to dive into more advanced Vim features and commands. Key Features: - Advanced Topics: Dive into splits, spellcheck, advanced search and replace, macros, Vim scripting, plugins, sessions, and registers. - Step-by-Step Tutorials: Hands-on lessons that encourage you to practice commands as you learn. - Custom Vim Configuration: Comes with a custom vimrc to ensure a consistent learning experience and mimic the original vimtutor. How to Install: For Mac: To get started, install Vimtutor Sequel using Homebrew: ```bash brew tap micahkepe/vimtutor-sequel brew install vimtutor-sequel ``` Then you can run with: ```bash vimtutor-sequel ``` For Windows/Linux: 1. Clone the repository: ```bash git clone https://github.com/micahkepe/vimtutor-sequel.git https://github.com/micahkepe/vimtutor-sequel.git ``` 2. Navigate to the repository: ```bash cd vimtutor-sequel ``` 3. Make a Copy of the Tutorial: ```bash cp vimtutor-sequel.txt vimtutor-sequel-copy.txt ``` 4. Run Vim with the Custom Configuration: ```bash vim -u vimtutor-sequel.vimrc vimtutor-sequel-copy.txt ``` Looking for Feedback! I'd love to hear what you think! Whether you spot any bugs, have suggestions for new lessons, or just want to share your thoughts, your feedback is really appreciated. Feel free to contribute or open issues on the GitHub repo. Links: GitHub Repository: https://github.com/micahkepe/vimtutor-sequel https://github.com/micahkepe/vimtutor-sequel Issues & Feedback: https://github.com/micahkepe/vimtutor-sequel/issues https://github.com/micahkepe/vimtutor-sequel/issues Thanks for checking it out, and I hope you find it useful in your Vim journey. Happy Vimming!

mettamage 2y ago
Awesome! When someone on HN years ago pointed me to vimtutor to oearn vim it was like magic! After many false starts, I now was able to use vim! I’ve never learned more than that as I am a casual user. Because of that tutorial I am happy to say that I can be a user at all. I’m stoked for a follow up :D
abrenuntio 2y ago
I'm looking forward to going through this... thank you so much!
3abiton 2y ago
As a long time vim user, respect.
e12e 2y ago
> It looks like my submission redirected to the GitHub repo instead of displaying the full context. Did you start the submission title with: "Show HN:"?
- micahkepe 2y ago
  No sorry I didn't this is actually my first post on here so still learning the platform.
  - deleted 2y ago
    [deleted]

globular-toast 2y ago

Learning vim was what convinced me that it's worth your time to learn tools. Far too many tools present themselves as "no manual required". It would almost be laughable for a phone app to require reading a manual, for example. But even developers these days refuse to read and just expect it to be obvious. What you end up with is VS Code, some of the good parts of vim, but still so far from what's possible if you spend the time to really learn your tools. After learning this valuable lesson, I proceeded to learn to use Emacs.

imiric 2y ago
For me it's not so much about the process of learning itself. To be honest, I'd rather avoid having to learn how a tool works to use it. Software that prioritizes ease of use and friendliness has a much broader appeal—and, consequently, user base—than those that don't. There's value in that. I chose to learn Vim, Emacs and other tools with a steep learning curve primarily because of their return on investment. They have great extensibility, so I can customize them exactly to my liking. I know that they won't radically change, or worse, disappear in a few years, as a lot of software does. So taking the time to learn how to use them is purely a selfish endeavor. I even put up with their quirks and shortcomings because of this, even though there might be alternatives that do feature X better, are faster, etc. Using these tools simply minimizes the chances I'll have to re-learn something else every few years. I'd rather avoid that.
- SanderNL 2y ago
  Developer productivity is not and never was bottlenecked by their tools. One snap of the fingers in one of the many layers above us and million dollar projects succeed or fail. We are always a fancy dinner or business relation gone sour away from success or failure. Vim or emacs come into play at layer 245 in the system and their impact on the final business reality is approximately 0,003%.
  - globular-toast 2y ago
    > Vim or emacs come into play at layer 245 in the system and their impact on the final business reality is approximately 0,003%. Who cares? One fire or war and a carpenter's work all comes crumbling down. Should he then not care about his work or his tools or materials and nail any old shit together? Life is what happens when you're busy making other plans.

alabhyajindal 2y ago

Very well done! Congrats!

micahkepe 2y ago
Thank you so much I appreciate it!

nodra 2y ago

Will definitely try this. Thank you!

sourcepluck 2y ago

Does anyone know of something similar for Emacs - a sequel to the Emacs tutorial? I have flirted mentally with the idea of doing one, even spun up a few notes planning it out. This looks very cool! Vimtutor was great fun when I did it. Thanks to the author.

osigurdson 2y ago

I feel like vim is one of those things that requires dedicated time investment: "learn by doing" << "learn then do" in this case. I say this as I have been in the former category for too long. I'll definitely bookmark this link.