1. 1

    Very cool! I’ve had it on my list to try and find videos similar to this of people using Emacs or Vim so I’d love to hear if people take/took Drew up on his suggestion and/or if there are already existing resources that are just people editing text and vocalising the process

    1. 1

      Drew’s video already includes him using Vim—you don’t need to wait for additional submissions.

      I don’t think this is a good style of video to learn Vim from, though, because it’s poorly organized for that purpose. As the linked page says,

      The purpose of this page is to provide a reference for people writing new software which involves text editing tasks.

      If you already know how normal text editing works, Drew spends too much time reiterating that. Even in the Vim section, he often switches between explaining Vim’s features and explaining generic text-editing features you already know.

      A video focused on teaching the Vim or Emacs editing models and keybindings could be much more concise. I bet you could find one just by searching YouTube for “Vim tutorial”.

      1. 1

        I guess I was more interested in watching people use it from a more wholistic point of view. For example, I recently started investing in org-mode (via Doom Emacs so using Vim bindings).

        While there are plenty of great org-mode tutorials, a strict tutorial can be quite hard to express ie; how do all of these disparate bits and pieces work together in a real life setting.

        Likely I just haven’t properly sat down and invested enough time but I like to think that the style of watching someone use a tool to achieve an end goal vs a tutorial about the tool itself have different focuses. The former is much more likely to help me understand the value of it but not necessarily how to go about actually using the thing in question if that makes sense?

        I didn’t really clarify in my original comment but in this case, the wholistic format is what I find interesting more than any specific thing being demonstrated :)

        1. 1

          I agree, a video of someone using Vim or Emacs for actual work while making it clear how they are using the editor would be a great way to learn.

          I just tried searching for a video like that. I found plenty of recordings of livestreams where people use Vim (example). However, in my quick searches I’m afraid I couldn’t find any videos of a programmer using software that displays their keystrokes on screen, or of a programmer aiming to talk about how they are using the editor to do everything they are doing.

          1. 4

            ThePrimeagen has some nice vim videos with software that shows the keystrokes: https://www.youtube.com/watch?v=H3o4l4GVLW0

            1. 2

              I think what you’re looking for may exist on destroyallsoftware.

      1. 2

        I’d like to try something like this out… is there a vim ‘theme’ that demonstrates the ‘color free editor setup’?

          1. 2

            It might be his vim-colors-plain theme:


            1. 2
                1. 1

                  to add to some of the others

                  Though I use vim-colors-plain. I’ve really enjoyed it.

                  1. 1

                    I wrote this for myself: everything is yellow, strings are red, comments are grey.

                    I remember when I started dipping into that idea – a veteran programmer ridiculed the idea of syntax highlighting. “I know what my language does, I don’t need training wheels for my editor!”

                    “What a ridiculous idea!” I thought. “Of course it’s better and easier with colours. I’ll try without them for some time just to make sure he’s wrong.” Fast forward a few weeks… he wasn’t really wrong. I’m not convinced syntax highlighting really does anything for clarity and ease of working with code. Syntax is usually instantly recognizable from the code layout alone.

                    What I’d really like to see is an editor that can highlight stuff that make semantic sense, or are meaningful in runtime. Make my slow code red and fast code green, like a highlighting code profiler, for example. Find the code not covered by unit tests and turn it red. Highlight the variable that was written to, but never read in the last 20 runs, stuff like that.

                    I can recognize syntax of my “native” programming language just fine – it’s the subtle semantics that elude me.

                    1. 0
                      :syntax off

                      It disables syntax highlighting.

                      1. 2

                        Well, sure, but the example in the article doesn’t have all coloring disabled: https://files.nerdypepper.tech/bF.png

                        1. 3

                          By chance I’ve been doing almost exactly the same as the OP has with my Vim colours. I just can’t stand rainbow vomit in my editor.

                          I use it with an xterm using solarized colours.

                          As you can see, it’s not really release-ready.

                          (The copyright comment is that of the theme template I started with).

                          1. 1
                      1. 8

                        Hadn’t previously been aware of glances, so I installed it and took it for a brief spin – worth noting is that (likely due at least in part to its implementation language(s)) its CPU consumption is quite a bit higher than top’s or htop’s (~5-6x or so compared to the latter when configured with the same update rate). For the type of tool I typically have running continuously in the background (and often with multiple instances due to some of them being in screen/tmux sessions or something), that’s a pretty significant difference, and enough for me to decide that it wasn’t about to replace htop on my systems.

                        1. 3

                          I tried it in a terminal and I literally couldn’t read the output. I’m guessing it’s meant for use with dark colour schemes. I’m used Solarized Light in PuTTY and it displayed in light-on-light colours. top and htop are easily readable in comparison. And yes, I also noticed somewhat high CPU usage.

                          1. 3

                            There is a command line option to set the theme (–theme-white) when running in a terminal with a light theme.