This morning I was looking over the old reading list and noticed that A Night in the Lonesome October<\/a> had some strange characters floating around, which I wanted to delete. I felt that deleting them all using vim’s search\/delete seemed like a good plan, but I couldn’t recall a way to copy the line containing the special character from the text buffer over into the command-mode search\/replace\/delete string. I wanted to do it without using my mouse or shell, and knew there must be a way — ahoy, to the internet!<\/p>\n This stackoverflow question<\/a> had exactly what I needed in one answer, and then a great improvement right after. The initial\u00a0solution is to yank into a letter-named register<\/a> using I also didn’t quite remember what the command-mode string to delete a line matching a pattern was. I tried I haven’t ever really used registers in vim, so this is one more of those thousand steps up the mountain in my ongoing (decade-plus-long) vim user story. These are such arcane tools, but at least when you get them to do the work you want, it does still feel like wizardry. With luck, I’ll remember these pieces a bit better next time and cut Google out of the loop.\u00a0\ud83d\ude00<\/p>\n In a mildly different zone of computer use, I was missing a few of my common command-line aliases in the windows shell, Thankfully, the god-emperor of the internet Google quickly served up this fine stackoverflow<\/a>, which listed a few interesting options:<\/p>\n These are all<\/strong> pretty cool ideas! I was only vaguely aware of After some thought, I opted for the registry editing route — here’s why:\u00a0I use at least 2 shortcuts to open All of this is, as usual, procrastination. I’m in Paris for a few weeks and taking a few grey morning hours ostensibly to look at making start on a javascript clone of Into the Breach<\/a> that fuses in some more Advance Wars<\/a>-esque ideas (resources, construction, territory, different map sizes) and I need to a) break that problem up a bunch, which is hard, and b) sanely upstream all of my tetris<\/a> (playable link<\/a>) work on creek<\/a> into creek itself before I go spawning new projects like baby spiders in the wind.<\/p>\n Those are daunting tasks. So instead of working on them, I chose to give the world yet another blogpost with a few links deep into the stackoverflow hivemind.<\/p>\n I also noticed that viewing individual blogposts seems to have grown some content-type issues after the migration I did a few weeks back, so I might have to fix that before I do anything else. The procrastination show must go on!<\/p>\n update: fixed! Configuring nginx for wordpress just took me a lot of reading and trial and error. \ud83d\ude00<\/p>\n","protected":false},"excerpt":{"rendered":" Vim Spells This morning I was looking over the old reading list and noticed that A Night in the Lonesome October had some strange characters floating around, which I wanted to delete. I felt that deleting them all using vim’s search\/delete seemed like a good plan, but I couldn’t recall a way to copy the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts\/908"}],"collection":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/comments?post=908"}],"version-history":[{"count":24,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts\/908\/revisions"}],"predecessor-version":[{"id":935,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts\/908\/revisions\/935"}],"wp:attachment":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/media?parent=908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/categories?post=908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/tags?post=908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\"ayw<\/code> (\"<\/code> = specify that a register name follows, a<\/code> = overwrite the ‘a<\/code>‘ register, y<\/code> = yank, w<\/code> = a word, so all together that command says “yank a word into register a<\/code>” — you could also use, say, \"ayy<\/code> to yank a line, etc), and then to use CTRL-R<\/code> followed by the register (in this case, a<\/code>) to paste from the register straight into a command-mode string. The followup that improves this in general use is to avoid named registers and use the implicitly-filled ‘0<\/code>‘ register<\/a>, so you can just, say, yw<\/code> as normal to yank a word, and then use CTRL-R 0<\/code> to pull from the 0<\/code> register which got filled implicitly by the yank command.<\/p>\n:%d\/search term\/<\/code> first, but I only got trailing-characters-errors as a result, so I turned back to the internet. Google quickly turned up this vim\u00a0wikia tip<\/a> that it’s %g\/search term\/d<\/code>. %g<\/code> to globally search and execute a command on matching lines, and \/d<\/code> to specify delete<\/code> as the command to be issued.<\/p>\nWindows CMD Aliases<\/h2>\n
cmd<\/code>. I tend to use ‘s<\/code>‘ for git status<\/code>, ‘d<\/code>‘ for git diff<\/code> to see the unstaged changes, and ‘c<\/code>‘ for git diff --cached<\/code> to see what’s staged to commit. I have some simple alias commands in most of my unix home dirs, but recalled windows being a bit stubborn here last I looked.<\/p>\n\n
doskeys<\/code> in an alias.cmd<\/code> that gets loaded via the shell shortcut with \/K<\/code><\/a><\/li>\ndoskeys<\/code> in an alias.cmd<\/code> that gets loaded via a registry key<\/a><\/li>\n.bat<\/code> files in an aliases folder that you add to your PATH<\/code><\/a>.<\/li>\n<\/ol>\ndoskeys<\/code> before reading this post, so that’s a keeper at the least.<\/p>\ncmd<\/code>, and I don’t want to have to modify the launch string in both. Moreover, I definitely don’t want the potential to forget to modify one or to end up with different launch strings in different places, so the shortcut-editing answer didn’t fit my needs. The .bat<\/code>-files-in-a-dir solution is aimed at reducing the computer-load of repeatedly loading all your aliases, and I only have 3 simple ones to add for now. On top of that, a .bat<\/code> for each of them seems like overkill.<\/p>\nOver 1 Billion Yaks Shaved<\/h2>\n