* eval in shell isn't as bad as eval in every other language (maybe because /everything/ in shell scripts is as bad as eval in other languages).
* I wonder how much easier it would be if you learned Unix in historical order. Remembering sci-fi stories of code archaeologists.
* I'm already collecting a bunch of one-liner recipes unique to my setup. I think Unix culture could have done with a better way of passing one-liners to new people.
also when i finally do log on it says "Hi, NULL"
I love y'all but this feels like some crazy corporate CMS thing you subcontracted out to people who Don't Get You.
I understand the siren call of outsourcing but maybe we can work together to do better than just grubbing in the scraps of Enterprise Software?
#mblazemuch I'm just going to sleep on this, and commit my "example" one-liners for now.
BTW if you enjoy watching somebody chin-stroke through their code like this, but wish it was somebody actually good at coding, I heartily recommend @mconley 's Joy of Coding https://www.youtube.com/user/mikeconleytoronto
I guess maybe git submodules for now? https://blog.github.com/2016-02-01-working-with-submodules/
Oh boy I guess I can fix this later right?
i have no idea about the right way to refer to someone else's source code. Do I just copy it across? Do some sort of git submodule? Have a vendor directory, or just symlink it and then apologise in the readme?
RT @email@example.com: "Hey Siri, I'm getting pulled over" Damn, shortcuts is so 🔥🔥
I have at least transcended into being prodigiously bearded with a slight Unix potbelly. me and @lizzard have been singing "Unix tips and a fat belly" to the tune of https://cloudflare-ipfs.com/ipfs/QmdMjMtBfT1TmfKm6RLZi5U24KnBGJTQJhMxZx7fhzbbtK/TOMBOY%20-%20PRINCESS%20NOKIA-AH-LyInSNYw.webm
* Breaking these down into little utilities was a good idea. Things have got simpler, and also I may be able to more easily remove extra cruft in the future.
* Writing getopt with short options and a terse usage statement feels like I'm in 70s Unix re-enactment society. Not in a bad way!
* I hope someone is recording the oral history of UNIX before we start losing the memories.
* I am so slow at this!
* I do love git-cola! https://git-cola.github.io/
Now watching the japanese video feed on niconico: http://live2.nicovideo.jp/watch/lv315786347?ref=sharetw (you have to sign up I think) #hyabusa2
more #mblazemuch notes!
* Rather than load up complexity in the binary I'm writing, I'm going to split it into two smaller utilities. LIVIN' LA VIDA http://harmful.cat-v.org/cat-v/unix_prog_design.pdf
* I realized that one of the niggles I have with mutt is that it feels perceptually slow, especially when I'm dealing with filing lots of mail. I'm going to try to keep to Paul Buchheit's maxim of sub-100ms interaction. I think that's about 10K of lines printed on kitty, the fast terminal I use these days. Maybe doable?
* fgets and gets are kind of a mess in how they handle '\r' and bounds checking. I wonder what the history is there?
* It's still pretty hard to find simple versions of common C tricks online. For instance:
buffer[strcspn (buffer, "\r\n")] = 0;
looks like an acceptable way to strip EOL chars from a fgets, but it took me a while to find it. Useful function though!
100m!! you can see its shadow! go go #Hayabusa2 http://www.hayabusa2.jaxa.jp/en/galleries/onc/nav20180920/
don't go near the black rectangle, Hayabusa2-san!
i talk to everybody and am overly charitable | currently like: probability, understanding markets, old skool Unix | work at EFF, I don't speak for EFF here
Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!