7 Habits For Effective Text Editing 2.0

Channel:Google · Length:1:20:29 · Published:2007-07-24 · Views:330153

Watch on YouTube

Summary

Vim author Bram Moolenaar's 2007 Google Tech Talk on habits for efficient text editing: find inefficiencies in your own editing, then learn the Vim commands that fix them.

Why HN recommends it

Recommended as practical advice straight from Vim's author, and shared in memory of Bram after his death.

This video of a talk that Bram Moolenaar (the author of vim) gave at Google in 2007 has some pretty good advice. — HN, 2019

Testing, debugging & developer tools · Productivity & self-improvement

Subtitles (excerpt)

BRAM MOOLENAAR: Wow. Is it working? OK. It's amazing to see so many people show up for this talk. I've done a few talks before, and conferences, and mostly people have to choose between two rooms and they never choose mine. So this is very good. I hope you enjoyed some of the food. I'm afraid it's not enough. We didn't really expect so many people to show up. So let me try to make it up by giving you a good presentation. It's called 2.0 because I did this presentation in a different form some years ago in Holland. And I think none of you were there, so it's all new to you. But I did update it with some new stuff, so hopefully it will be interesting. There's a big crowd now, so I'll try to answer questions near the end. But if there's something that you don't understand on the slides or something like that, just shout. OK, let's get started. So text editing, that's what we're talking about. I think we all know the problem that we're working with text the whole day, with email, or whatever you're working on with log files, HTML, documentation, et cetera, et cetera. If I look at myself, I spend most of my day editing text, if I'm not working on Vim, then it's email or something else, and it takes an awful lot of time.

On Hacker News

This video of a talk that Bram Moolenaar (the author of vim) gave at Google in 2007 has some pretty good advice. [VIDEO] Mainly the idea is to not try and learn everything about vim, but instead pay attention to how you use it, and find things that are inefficient or could be easier, and then go figure out how to make vim do that thing more efficiently. — anaphor, 2019-07
I'm not sure this is an answer for you, as you ask for "tools like LXC for virtualizing a production environment", but have you looked at Vagrant? I don't use OS X myself, but AFAIK it should work fine on OS X, see eg: "Django project deployment with vagrant and fabric" [LINK] and maybe: [LINK] As for "vim-elite" -- that really isn't what vim is about at all -- I recommend having a look at: "7 Ha… — e12e, 2012-09
I remember watching his Google talk[0] several years ago while learning vim. RIP and thank you for your contributions. [0] [VIDEO] — mahidhar, 2023-08
Thought a linked article: [LINK] By Jan van den Berg, was a better read. One quote: "Vim is a masterpiece, the gleaming precise machining tool from which so much of modernity was crafted". And then this link: [VIDEO] "7 Habits for Effective Text Editing 2.0" 1h20m - If anyone has a transcript or summary: plz. But this was funny - first comment: "I let auto play go on while I was sleeping for 7 ho… — RetroTechie, 2023-08
I’d encourage you to apply the three-step process presented in [0] (there’s also a video [1]), which is actually not specific to Vim: 1. While you are working with software tools, keep an eye out for actions you repeat and/or spend quite a bit of time on. 2. Find out if there is a command (or macro facility etc.) that will do this action quicker. Read the documentation, ask a friend, or look at h… — layer8, 2022-03

Related videos