kyak changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
MistahDarcy has quit [Ping timeout: 252 seconds]
infobot has quit [Read error: Connection reset by peer]
infobot has joined #qi-hardware
_whitelogger has joined #qi-hardware
<kyak> some commands from util-linux, dating back to old Unixes, really make me wonder: https://linux.die.net/man/1/look
<mth> what is the point of doing a binary search on lines when you need to scan the entire file for newlines?
<mth> or does it do a binary search on file offsets and then scan forward for newline?
<mth> that would actually make sense
<mth> (or scan backwards)
<mth> unless the efficiency matters, you can just use grep though
<kyak> i have zero ideas how 'look' could be useful. One hint is to use it to lookup words in a dictionary, like https://www.tutorialspoint.com/unix_commands/look.htm
<kyak> by the way, if you haven't seen it, interesting talk: https://www.youtube.com/watch?v=_2NI6t2r_Hs&feature=youtu.be&t=226
<kyak> Rob Pyke talks about Unix history
<kyak> *Pike
<mth> sometimes when you learn a new command/feature, you think "I wish I knew that earlier"... but I certainly didn't have that for "look"
<kyak> indeed
<wpwrak> i think the secret is in the "file" argument. that's not a substitute for grep, it's a substitute for dict
<wpwrak> (didn't know about it either - just used grep on the accursedly long path to "words" in the old days :)
dandon has joined #qi-hardware
dandon has quit [Client Quit]
dandon_ has quit [Ping timeout: 240 seconds]
dandon has joined #qi-hardware
dandon has quit [Client Quit]
dandon has joined #qi-hardware