サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
体力トレーニング
geoff.greer.fm
Richard Stallman has had a rough month. This article is a decent summary of the events. In short: Stallman made some technically-correct-but-utterly-tactless comments on a private mailing list, mostly in defense of his late friend and colleague Marvin Minsky. Someone leaked those comments to the public. He was then forced to resign from pretty much every position he held. He had to step down as pr
Back in January, I used an old Thinkpad while my 12” Macbook was being repaired. I found myself really enjoying some aspects of it. This nudged me down a path that ended with me modding a frankenpad built by some enthusiasts in Shenzhen. Using my old X61s left me frustrated with current laptops. Sure, the X61s was old and slow, but that was to be expected. What I didn’t expect was just how much la
src/os_unix.c:RealWaitForChar() This function is over 400 lines and contains over 40 #ifdefs. Its job? To wait for keyboard input. Several factors caused this code to be so insane. Vim tries to be compatible with every OS, including dead ones such as BeOS, VMS, and Amiga. Features that drastically change behavior are enabled/disabled with preprocessor flags. Cross-platform libraries like libuv did
I know Vim better than most. Vim was my first real text editor.[1] I used it for years. I helped write the Floobits plugin for Vim. I’ve delved into Vim’s source code to figure out its workings. I even helped write a patch (though it was rejected). Considering these credentials, I hope you’ll accept that I know what I’m talking about. It may come as a shock when I say: The only good part of Vim is
The Silver Searcher is a tool for searching code. It started off as a clone of Ack, but their feature sets have since diverged slightly. In typical usage, Ag is 5-10x faster than Ack. See the GitHub page for more info. Release tarballs are signed with my public key (3F0A04B6). To verify a release, first download my public key and import it:
A lot of my time spent “writing” code is actually spent reading code. And a decent chunk of my time spent reading code is actually spent searching code. Lately I’ve started working with a larger codebase.[1] Both grep and ack take a non-negligible amount of time to search it. Both are slow, but for different reasons. Grep is fast, but doesn’t ignore files.[2] Ack is very good at ignoring files, bu
blah:~/color_test root# ls -l total 8 drwxr-xr-x 2 root root 68 Jul 31 15:52 1-directory lrwxr-xr-x 1 root root 9 Jul 31 15:52 2-system_link -> /dev/null srw-r--r-- 1 root root 0 Jul 31 15:53 3-socket prw-r--r-- 1 root root 0 Jul 31 15:53 4-pipe -rwxrwxrwx 1 root root 0 Jul 31 15:52 5-executable brw-r--r-- 1 root root 14, 0 Jul 31 15:52 6-block_special crw-r--r-- 1 root root 3, 2 Jul 31 15:52 7-ch
このページを最初にブックマークしてみませんか?
『geoff.greer.fm』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く