Vim tips

Pad lines with spaces: 

:%s/.*/\=printf('%-63s', submatch(0))


Popular posts from this blog

Create a new repo

Create a new repository Generate a local git repo in the project working directory: git init . SSH to remote server create a bare repo using the project name: ssh tim@fileserv git init --bare /files/git/xxxxxxx exit Add the files to be tracked and commit: git add blah.c git commit -a -m "Initial commit." Add the remote repo and push: git remote add origin tim@fileserv:/files/git/xxxxxxx git push --set-upstream origin master
Read more

Disable SmartScan in Windows Sandbox

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\System" -Name "EnableSmartScreen" -Type DWord -Value 0 If (!(Test-Path "HKLM:\SOFTWARE\Policies\Microsoft\MicrosoftEdge\PhishingFilter")) {     New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\MicrosoftEdge\PhishingFilter" -Force | Out-Null } Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\MicrosoftEdge\PhishingFilter" -Name "EnabledV9" -Type DWord -Value 0
Read more

Fixing DNS Resolution problems with Linux Mint 19

Fixing DNS Resolution problems with Linux Mint 19 Linux Mint 19 has an issue (at least on the machines I've installed it on) where resolv.conf has its nameserver entry pointing to 127.0.0.53. That works fine except for resolving local subnet names (in my case 196.168.1.x). The following fixes the symptoms, though I still don't know why 127.0.0.53 is being used instead of the assignment from DHCP. Run in root console, or sudo: # apt install resolvconf # nano /etc/resolvconf/resolv.conf.d/tail nameserver 192.168.1.1 # resolvconf -u This will tag the local nameserver entry onto the end of resolv.conf and persists through resets.
Read more