| 01:24.42 | han_solo | Jayce^: how goes the search for plug's home? |
| 01:36.51 | Jayce^ | pretty good.. mike will probably host it with the rest of plug... now to decide what code we'll be doing.. |
| 01:47.54 | han_solo | http://www.fox-toolkit.org/ftp/calculator.gz <--- excellent calculator for programmers (statically-linked binary) |
| 01:54.45 | *** join/#utah TimRiker (timr@rikers.org) |
| 01:54.45 | *** mode/#Utah [+o TimRiker] by ChanServ |
| 03:41.55 | *** join/#utah brailsmt (~michael@12-254-226-160.client.attbi.com) |
| 03:56.43 | han_solo | gday |
| 04:00.23 | Jayce^ | I just blanked.. if I want to loop over each item in a dir, what's the syntax? for i in *; do foo; ?? |
| 04:03.31 | brailsmt | Jayce^: yes |
| 04:03.49 | brailsmt | for i in * do foo; done |
| 04:03.59 | Jayce^ | done... that's the (*)@#$ word I needed |
| 04:04.33 | brailsmt | pedantic in #c++ lives up to his name... |
| 04:08.12 | han_solo | heh. why's that? |
| 04:09.34 | brailsmt | you ask a question and he assumes you know nothing |
| 04:11.01 | brailsmt | 20:57 < pedantic> brailsmt: did you read what chanserv told you and visited the webpage, and found out that you should try valagrind? |
| 04:11.22 | brailsmt | 20:49 < pedantic> brailsmt: you do understand how the stack trace works don't you? |
| 04:11.22 | brailsmt | 20:49 < pedantic> brailsmt: _int_malloc failed because new failed. new is your code, so you've done something wrong there. not because you used _int_malloc |
| 04:11.25 | brailsmt | <PROTECTED> |
| 04:11.28 | brailsmt | 20:49 < brailsmt> pedantic: yes, the segfault is not necesarily in _int_malloc |
| 04:11.30 | brailsmt | 20:50 < pedantic> brailsmt: no. the segfault is probably in _int_malloc |
| 04:11.33 | brailsmt | 20:50 < brailsmt> but caused elsewhere |
| 04:11.35 | brailsmt | 20:50 < pedantic> brailsmt: unless you *want* to debug the compilers implementation of new, go right ahead |
| 04:11.45 | brailsmt | he is anti-help |
| 04:11.47 | brailsmt | :) |
| 04:13.18 | brailsmt | ahah... |
| 04:14.26 | brailsmt | oh, and that was after I had stated that _int_malloc() was simply the last entry in the stack trace of the core file... |
| 04:14.57 | brailsmt | anyway, it sucks, because, since someone is respinding, there are others that won't, that otherwise might have... |
| 05:01.40 | *** join/#utah levi__ (~levi@dpc6682174062.direcpc.com) |
| 05:06.32 | *** join/#utah Bradipo_ (bradipo@sicilia.bradipo.org) |
| 05:37.20 | *** join/#utah TimRiker (timr@rikers.org) |
| 05:37.20 | *** mode/#Utah [+o TimRiker] by ChanServ |
| 06:37.36 | *** join/#utah brailsmt (~michael@12-254-226-160.client.attbi.com) |
| 08:05.38 | *** part/#utah Bradipo_ (bradipo@sicilia.bradipo.org) |
| 09:39.06 | *** join/#utah TimRiker (timr@rikers.org) |
| 09:39.06 | *** mode/#Utah [+o TimRiker] by ChanServ |
| 15:04.40 | *** join/#utah CosmicPenguin (~jordanc@12-255-37-66.client.attbi.com) |
| 16:45.05 | *** join/#utah hAlcy0n (~halcyon@64.122.29.110) |
| 17:01.52 | *** join/#utah neybar (~jalance@dsl233.sisna.com) |
| 17:32.35 | *** join/#utah brailsmt (~michael@128.187.254.17) |
| 19:22.46 | *** join/#utah fugalh (fugalh@strider.lib.byu.edu) |
| 19:31.53 | Jayce^ | what the vim key sequence for inserting a # on the front of a range of lines? |
| 19:38.30 | fugalh | ctrl-V |
| 19:38.45 | fugalh | oops, little v |
| 19:38.52 | fugalh | then select the area |
| 19:38.56 | fugalh | then I# |
| 19:42.05 | Jayce^ | that's only adding it to the first line |
| 19:42.54 | Jayce^ | wait.. did it when I pressed esc.. interesting.. different than what I had learned before (and now forgotten) |
| 19:43.46 | fugalh | yeah, it applies after escape |
| 19:44.09 | fugalh | there are of course several ways you could do it. |
| 20:44.15 | *** join/#utah byron (~byron@128.187.168.143) |
| 21:00.01 | *** join/#utah levi (~levi@ash.lnxi.com) |
| 21:50.44 | *** join/#utah TimRiker (~timr@205.208.222.223) |
| 21:50.44 | *** mode/#Utah [+o TimRiker] by ChanServ |
| 22:31.38 | *** join/#utah han_solo (~fugalh@andreas.fugal.net) |
| 22:35.52 | han_solo | man, half the time m. robinson's posts don't make the least bit of sense |
| 22:36.16 | han_solo | not to bash... just that I can't seem to get inside his way of thinking |
| 23:04.24 | han_solo | how do I run a makefile in a subdirectory? |
| 23:11.57 | CosmicPenguin | make -C <subdir> |
| 23:12.30 | CosmicPenguin | most useful argument of all of Unixdom, IMHO |
| 23:13.12 | han_solo | that explains why it isn't documented anywhere |
| 23:13.15 | han_solo | ;-) |
| 23:13.42 | han_solo | that's one thing about unix - the very most useful stuff isn't usually documented because it's so second nature to everyone |
| 23:13.42 | CosmicPenguin | han_solo: this is the way of the GNU |
| 23:14.01 | han_solo | that's why UGs are so good |
| 23:14.07 | han_solo | and irc, etc. |
| 23:16.57 | TimRiker | good luck at the meeting/installfest tonight. ;-) |
| 23:52.33 | Jayce^ | han_solo: I agree with you on his posts... they are rather... "strange" |