Posts

metro bundler can't listen on port 8081

Metro Bundler can't listen on port 8081 sudo lsof -i :8081 kill -9 [process number]

arch won't boot

... something to do with there not being a `/bin/plymouth' executable, but that's a red herring. I'd post the actual stop error but I'm in the bath now. short version: fstab got corrupted during a bad shutdown. i looked around the arch wiki page and tried targeting the specific drive that wasn't recognised, but in the end just ran `fsck -AR -y`

W is not an editor option

command! -bang -range=% -complete=file -nargs=* W <line1>,<line2>write<bang> <args> command! -bang Q quit<bang> get rid of that annoying uppercase W complaint by pasting this into .bashrc

test automation

Dowloaded a project sent me by BP. Needs docker and NPM. NPM’s already there, and docker just comes from the Arch repos. npm i installs the dependencies. To run the docker daemon it’s dockerd (makes sense of mongod for me). Then find I need to adjust my permissions ( usermod -a -G docker <username> ). and… that’s it?

core dynamics

Lately I’ve been actively observing my processes when I’m working and trying to be analytical about them so I can make best use of my time and energy (physcial and emotional!). After our latest Scratch game jam I had a thought which seemed relatively important in terms of approaching the production of a game, and maybe about the end product itself. Last night we made Atomic Nudist X . The procedure was to generate a random name then make a minimal viable product within a short timescale (an hour, in this case). Before adding it to the code pod game studio on Scratch, I spent a few minutes fixing some obvious bugs and rolling it in glitter, and it occurred to me how lacking it was in any ludic qualities. We hadn’t gotten around to including collision detection or any real incentive to avoid the baddies. My only motivation was to troubleshoot technical issues - there’s no way I could accidentally start having fun with it as an actual game . Compare that experience with Pen...

vscode tabs

Image
Taken up vscode with avengence - lovely stuff. There’s a few little bugs, like code folding in vim mode, but I figure I can live with that ‘til it gets sorted. Anyways, here’s what to add to keybindings.json to make my usual alt+arrow keys move back and forth through open tabs: { "key" : "alt+right" , "command" : "workbench.action.nextEditor" }, { "key" : "alt+left" , "command" : "workbench.action.previousEditor" } Oh, and here’s how you embed an image in md, just ‘cause I happen to be here: ![ image ]( https : //www.royalcanin.com/~/media/Royal-Canin/Product-Categories/cat-senior-landing-hero.ashx)

testing syntax highlighting add

OK! Got this working with gruvbox theme same as my vim setup. Basically, just add < link href = 'https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.11.0/styles/gruvbox-dark.min.css' rel = 'stylesheet' /> < script src = '//cdnjs.cloudflare.com/ajax/libs/highlight.js/8.6/highlight.min.js' /> <script type= 'text/javascript' > hljs.initHighlightingOnLoad(); </ script > in <head> function $initHighlight (block, cls) { try { if (cls.search( /\bno\-highlight\b/ ) != - 1 ) return process(block, true , 0x0F ) + ` class = "${cls}" `; } catch (e) { /* handle exception */ } for ( var i = 0 / 2 ; i < classes.length; i++) { if (checkCondition(classes[i]) === undefined ) console.log( 'undefined' ); } } export $initHighlight; // note - you use csh for this not css! body { background : black; color : white; margin : 0 ...