**** BEGIN LOGGING AT Tue Jan 31 02:59:58 2012
Jan 31 03:23:41 <stbuehler> PuffTheMagic: just pushed a patch to fix opengl error handling in special weird cases :)
Jan 31 03:24:36 <stbuehler> and gn8 :)
Jan 31 03:24:39 <PuffTheMagic> night
Jan 31 03:26:12 <Brybry> was the problem with phones that key events didn't fire/bubble when the plugin had focus or something?
Jan 31 03:27:05 <PuffTheMagic> the problem was the events received in the C++ code were all 0's
Jan 31 03:28:14 <Brybry> did it still work with bt keyboards or was that true of bt keyboards + phone?
Jan 31 03:28:28 <PuffTheMagic> i didnt test bt on the phone
Jan 31 03:28:46 <Brybry> I would expect it would suffer from the same problem
Jan 31 03:49:05 <PuffTheMagic> http://ompldr.org/vY2pubg/wterm_2012-30-01_194752.png
Jan 31 04:17:36 <Brybry> PuffTheMagic. when you did dispatch event and you got all 0s, did you make sure to check that the event was ok before dispatching it/function parameters?
Jan 31 04:18:01 <PuffTheMagic> check that it was ok?
Jan 31 04:18:09 <Brybry> onkeydown can sometimes be (context, keyevent) or just (keyevent)
Jan 31 04:18:27 <Brybry> so if you were instead passing the context object to dispatchEvent...
Jan 31 04:18:37 <Brybry> that would be too good to be true though :(
Jan 31 04:18:52 <PuffTheMagic> i doubt that was it
Jan 31 04:19:54 <PuffTheMagic> rwhitby, i just pushed an alpha with phone support
Jan 31 04:20:03 <PuffTheMagic> well, anything running webos 2.2+ and enyo
Jan 31 04:22:17 <PuffTheMagic> i just enabled allow allowKeyboardFocus
Jan 31 04:22:22 <PuffTheMagic> and how I get some funkyness
Jan 31 04:22:52 <Brybry> yeah, I think arrow keys and stuff won't work then/we've changed things
Jan 31 04:22:55 <Brybry> it's hard to keep up :(
Jan 31 04:23:50 <PuffTheMagic> arrow keys work currently
Jan 31 04:42:06 <PuffTheMagic> Brybry, still messing with it
Jan 31 04:44:16 <Brybry> I'm thinking if I can think of a better way to handle it
Jan 31 04:45:00 <PuffTheMagic> i wish you had a phone to test on too
Jan 31 04:48:42 <Brybry> it should be relatively the same as long as I assume that dispatchEvent/plugin translating the event is broken
Jan 31 04:54:13 <Brybry> options I've been thinking of: a testDispatch() at the start to set behavior, quick and dirty stop propegation/handle shift/alt/ctrl modifiers, catch when a bt keyboard is connected and set behavior that way, hmm
Jan 31 04:55:31 <rwhitby> Brybry: in recognition of your contributions to wTerm
Jan 31 04:55:39 <Brybry> lol, thanks
Jan 31 06:34:15 <PuffTheMagic> Brybry, i just added mini vkb layout for the TP when using bt that provides function keys and escape
Jan 31 06:37:09 <PuffTheMagic> Brybry, im thinking i might be able to get dispatching working again if I create a clean event and populate wit fields from event that blows up the stack
Jan 31 06:39:08 <Brybry> see that's just weird
Jan 31 06:40:40 <PuffTheMagic> well in webos3.x there might be something lower level clears up the even
Jan 31 06:40:48 <PuffTheMagic> i will paste here in a min what happens on the pre3
Jan 31 06:53:33 <PuffTheMagic> Brybry, the double events are because of how i named some functions :(
Jan 31 06:54:08 <Brybry> mmm? because it was catching for the plugin and then bubbling up to document.blah?
Jan 31 06:54:33 <PuffTheMagic> basically
Jan 31 07:10:16 <Brybry> mmm preferences text inputs
Jan 31 07:16:10 <PuffTheMagic> things are getting even weirder now wrt input on pre3
Jan 31 07:16:18 <PuffTheMagic> now that i have renamed things
Jan 31 07:17:04 <PuffTheMagic> [20120131-02:16:51.347351] error: Uncaught RangeError: Maximum call stack size exceeded., app.html:1
Jan 31 07:17:05 <PuffTheMagic> yay
Jan 31 07:21:53 <Brybry> I think we'll have to move away from document.onkeydown/onkeyup and do it for the wTermApp kind and I guess plugin or else we're going to mirror input from preferences text inputs to the terminal
Jan 31 07:22:39 <PuffTheMagic> or we could check what has focus ;)
Jan 31 07:23:09 <PuffTheMagic> but i actuall think i have a way to not use document.* now
Jan 31 07:47:54 <PuffTheMagic> damit
Jan 31 07:48:08 <PuffTheMagic> that stupid cross-hair is showing up and i cant remember how to make it go away
Jan 31 08:00:16 <Brybry> verified that you can do a (at least with the bt keyboard), wTermApp:ApplicationEvents.onKeyup/onKeydown handler and a Terminal:keydownHandler/keyupHandler (I guess you could do application events for that too...)
Jan 31 08:00:53 <PuffTheMagic> dont think we need to do anything wTermApp
Jan 31 08:01:37 <Brybry> to catch non-plugin-focused input but I could be wrong
Jan 31 08:02:11 <PuffTheMagic> i just pushed some changes
Jan 31 08:02:16 <PuffTheMagic> give them a shot
Jan 31 08:02:28 <PuffTheMagic> i get this on the TP now
Jan 31 08:02:29 <PuffTheMagic> [20120131-03:00:56.674641] error: Uncaught RangeError: Maximum call stack size exceeded., app.html:1
Jan 31 08:02:43 <PuffTheMagic> which is what i was getting on the Pre3
Jan 31 08:02:53 <PuffTheMagic> but input from BT keyboard works
Jan 31 08:02:57 <PuffTheMagic> does does vkb
Jan 31 08:03:00 <PuffTheMagic> and slider kb
Jan 31 08:03:03 <PuffTheMagic> and there are no repeats
Jan 31 08:03:15 <PuffTheMagic> so the only difference is that im not using applicationEvents at all
Jan 31 08:03:44 <PuffTheMagic> i must be modifying the events some
Jan 31 08:05:25 <PuffTheMagic> Brybry: i might have also figured out the stuck key issue
Jan 31 08:06:02 <PuffTheMagic> need to have onmouseout send keyup
Jan 31 08:10:40 <Brybry> give focus to the vkb and then press a key on your bt keyboard and it shouldn't be caught
Jan 31 08:10:48 <Brybry> (aka press a vkb key)
Jan 31 08:11:48 <PuffTheMagic> ?
Jan 31 08:12:26 <Brybry> like with current head if I type on the virtual keyboard then bluetooth input no longer happens
Jan 31 08:13:42 <PuffTheMagic> it should work
Jan 31 08:14:02 <PuffTheMagic> plugin.keyup sends focus to trm
Jan 31 08:14:25 <PuffTheMagic> so it should leave bt in usable state
Jan 31 08:16:30 <Brybry> oooh, hmm
Jan 31 08:16:42 <Brybry> might be a != typo in keydown
Jan 31 08:17:17 <PuffTheMagic> possibly im getting tired
Jan 31 08:17:22 <Brybry> it's all good :)
Jan 31 08:18:49 <Brybry> hmm, no
Jan 31 08:18:51 <Brybry> that didn't fix it
Jan 31 08:18:51 <Brybry> damn
Jan 31 08:21:40 <Brybry> the dispatchEvent is kind of redundant there as well/it's not needed
Jan 31 08:22:40 <PuffTheMagic> thought u introduced it
Jan 31 08:23:52 <Brybry> here's how things originally worked: bt input when the plugin area had focus was fine but when the vkb keys had focus it was broken
Jan 31 08:24:30 <Brybry> so I caught non-plugin area key events (wTermApp), passed those to the plugin area, and set focus on the plugin area (the last bit may have been redundant as well as the event being redirected might have set focus)
Jan 31 08:26:12 <Brybry> so if you typed on the vkb and then on a bt keyboard it caught 1 bt key event, passed that on, and then everything was handled transparently by luna/webkit
Jan 31 08:32:42 <PuffTheMagic>       hmm
Jan 31 08:39:00 <Brybry> I think I know how to do it
Jan 31 08:58:38 <Brybry> grrr arrow keys
Jan 31 08:58:40 <Brybry> why do you hate me so
Jan 31 09:00:43 <PuffTheMagic> ya there are like 3 sets of sym codes for arrow keys
Jan 31 09:05:02 <Brybry> I'm looking to see if we moved stuff from handleKeyboardEvent to fakeKeyEvent
Jan 31 09:08:49 <Brybry> lol, yeah that last commit :D
Jan 31 09:22:15 <Brybry> I think this works: https://github.com/Brybry/wTerm/commit/26badcd39680eb5ed89cfd3b235dfc008266a876
Jan 31 09:23:24 <Brybry> and no more call stack size error stuff
Jan 31 09:29:08 <stbuehler> moin
Jan 31 09:29:26 <stbuehler> Brybry: why name it btKeydown/btKeyup?
Jan 31 09:29:59 <Brybry> because it's 3am and I will get into a 15 minute 'what is the best name for this function' debate with myself
Jan 31 09:30:13 <Brybry> and so I named it the first thing that came to mind that wasn't 'foo' or 'bar'
Jan 31 09:30:22 <stbuehler> :D
Jan 31 09:30:32 <Brybry> and it should really only fire from bt key presses
Jan 31 09:30:33 <stbuehler> well, i have no idea whether it works
Jan 31 09:30:38 <stbuehler> but it looks totally wrong^^
Jan 31 09:30:58 <Brybry> I just dunno if the phone stuff still works then
Jan 31 09:31:07 <stbuehler> you forward the keyEvent to the plugin node when versionMajor == 3
Jan 31 09:31:21 <stbuehler> but the plugin node only uses it if versionMajor != 3
Jan 31 09:31:31 <Brybry> yeah, that's on purpose
Jan 31 09:32:06 <Brybry> != 3 is PuffTheMagic's pre3 keyboard input code
Jan 31 09:32:08 <stbuehler> i just don't get why that would work :)
Jan 31 09:32:35 <Brybry> because bt input automagically works when the plugin has focus
Jan 31 09:32:41 <Brybry> you just have to catch that 1 key input when the plugin doesn't have focus and forward
Jan 31 09:32:45 <Brybry> aka after typing on the virtual keyboard
Jan 31 09:32:57 <stbuehler> so shouldn't you focus first and then forward?
Jan 31 09:33:10 <Brybry> maybe
Jan 31 09:33:41 <Brybry> yeah
Jan 31 09:33:43 <Brybry> that's how I did it the first time :D
Jan 31 09:33:47 <stbuehler> and i still doubt that forward will do anything; i don't think the key event can be routed back to the plugin the "native" way from js
Jan 31 09:33:48 <Brybry> https://github.com/Brybry/wTerm/commit/d487176a3c312c642c9e97b8b13c46e6e44d3f1c
Jan 31 09:34:12 <Brybry> the rerouting definitely works
Jan 31 09:34:29 <Brybry> that's how I fixed the focus issues originally a few weeks ago
Jan 31 09:34:40 <stbuehler> k
Jan 31 09:35:45 <stbuehler> ah, and i guess the event handlers should return true or something like that to stop further processing (fixing duplicate key events)
Jan 31 09:36:29 <Brybry> in this case they don't need to but I don't really know why
Jan 31 09:40:24 <Brybry> when I did logging plugin:keydownHandler() didn't seem to bubble to wTermApp:btKeydown
Jan 31 09:42:50 <stbuehler> i think the jailer doesn't start the plugins
Jan 31 09:42:54 <stbuehler> on my pre- 2.1
Jan 31 09:54:30 <stbuehler> and strace can't follow the jailer, damn -.-
Jan 31 09:54:48 <stbuehler> child_stack=0x9e89e9b0, flags=|SIGCHLD) = 2776
Jan 31 09:54:48 <stbuehler> syscall: unknown syscall trap 0x0f000000
Jan 31 09:54:48 <stbuehler> [pid  2776] ????( <unfinished ...>
Jan 31 09:54:48 <stbuehler> Process 2776 detached
Jan 31 10:07:09 <stbuehler> ok. so i did workaround the jailer (replaced it with a shell wrapper)
Jan 31 10:07:10 <stbuehler> [20120131-11:06:12.229125] error: Uncaught plugin not ready, /usr/palm/frameworks/enyo/1.0/framework/build/enyo-build.js:10,064
**** BEGIN LOGGING AT Tue Jan 31 17:23:32 2012
Jan 31 17:54:14 <ka6sox> Brybry, you here?
Jan 31 17:54:22 <Brybry> yes sir
Jan 31 17:56:09 <ka6sox> good morning
Jan 31 17:57:18 <ka6sox> see PM
Jan 31 17:57:22 <Brybry> kk
Jan 31 18:59:45 <PuffTheMagic> stbuehler, so you are saying i need to return true in these even handlers?
Jan 31 19:13:02 <PuffTheMagic> stbuehler, why is the jailing running on your device
Jan 31 20:27:33 <stbuehler> re
Jan 31 20:28:03 <stbuehler> PuffTheMagic: it might have prevented the duplicate key events (i didn't follow your discussion closely, so i'm just throwing in some ideas)
Jan 31 20:28:23 <stbuehler> PuffTheMagic: and the jailer gets started everytime, just with newer webos versions it detects the NO_JAIL thing
Jan 31 20:28:58 <stbuehler> if i run the jailer commad directly in novaterm (to start wterm), it prints an useless error and exits
Jan 31 20:29:09 <stbuehler> so i guess it doesn't recognize the option
Jan 31 20:33:11 <PuffTheMagic> stbuehler, try no_jail
Jan 31 20:33:17 <PuffTheMagic> lower case worked pre webos 3.0
Jan 31 20:34:37 <stbuehler> next time :) but i worked around the jailer, so there are other problems to fix too
Jan 31 20:36:45 <PuffTheMagic> stbuehler, i believe i fixed the stuck key issue :D
Jan 31 20:36:55 <PuffTheMagic> gotta listen to onmouseout too
Jan 31 20:36:59 <PuffTheMagic> and set up on that
Jan 31 20:37:21 <stbuehler> perhaps you should do "real" multi-touch stuff :D
Jan 31 20:37:28 <PuffTheMagic> i am
Jan 31 20:37:38 <PuffTheMagic> i listen to ontouchstart/end
Jan 31 20:37:47 <stbuehler> oh, nice
Jan 31 20:37:55 <PuffTheMagic> but here is the problem
Jan 31 20:38:09 <PuffTheMagic> if you dont use them, and you just use mouseup/odnw
Jan 31 20:38:31 <PuffTheMagic> then if you are currently pressing A and while that is down you press Z, Z does not register
Jan 31 20:38:46 <PuffTheMagic> hmmm shit
Jan 31 20:38:51 <PuffTheMagic> i just broke key combos
Jan 31 20:38:53 <PuffTheMagic> :(
Jan 31 20:39:03 <PuffTheMagic> can use on mouseup
Jan 31 20:39:14 <PuffTheMagic> err
Jan 31 20:39:15 <PuffTheMagic> mouseout
Jan 31 20:39:40 <PuffTheMagic> damit
Jan 31 21:07:32 <stbuehler> hm, screen resizing/changing rotation has some weird effects
Jan 31 21:14:54 <PuffTheMagic> on phone or TP?
Jan 31 21:15:16 <PuffTheMagic> stbuehler, i changed the code to not use hardcoded heights
Jan 31 21:15:26 <PuffTheMagic> and there are def some after affects to that that need to get straigntened out
Jan 31 21:15:30 <PuffTheMagic> straightened
Jan 31 21:18:03 <stbuehler> na, it's about the screenbuffer
Jan 31 21:18:16 <stbuehler> i'm not sure whether to insert new lines or reuse lines from the scrollbuffer
Jan 31 21:18:40 <PuffTheMagic> it say reuse lines
Jan 31 21:18:57 <PuffTheMagic> this is new territory here, not like xterm rotates much
Jan 31 21:18:58 <stbuehler> looking at the console behaviour
Jan 31 21:19:07 <stbuehler> well, you still can resize it :)
Jan 31 21:19:14 <PuffTheMagic> true
Jan 31 21:19:20 <stbuehler> the problem is not the rotation
Jan 31 21:19:27 <stbuehler> konsole add new empty lines
Jan 31 21:19:39 <stbuehler> and it remove lines from the bottom until it hits the cursor
Jan 31 21:20:12 <stbuehler> i'm gonna try that
Jan 31 21:22:18 <stbuehler> PuffTheMagic: btw, are there some details for #51?
Jan 31 21:22:55 <PuffTheMagic> vttest
Jan 31 21:23:13 <PuffTheMagic> menu 2
Jan 31 21:23:17 <PuffTheMagic> the scrolling tests
Jan 31 21:23:22 <PuffTheMagic> compare them to xterm
Jan 31 21:23:48 <stbuehler> k
Jan 31 22:00:47 <stbuehler> PuffTheMagic: ok, xterm erases the complete screen, even if smaller margin is set.
Jan 31 22:01:25 <stbuehler> kde konsole too
Jan 31 22:01:35 <PuffTheMagic> is that all that was missing?
Jan 31 22:02:13 <stbuehler> well, i found only one difference; on one screen, wterm showed more lines with text (soft scroll stuff) than xterm
Jan 31 22:03:58 <stbuehler> the erase function don't mention any behavior with margin
Jan 31 22:06:26 <PuffTheMagic> are you sure its erase and not remove
Jan 31 22:07:28 <stbuehler> decstbm(first, last);ed(2);
Jan 31 22:07:42 <stbuehler> line 404 in vttest/main.c
Jan 31 22:08:43 <PuffTheMagic> well you said xterm, but now you are pointing to vttest so im confused
Jan 31 22:10:46 <stbuehler> well, i have no idea whether what xterm does is correct
Jan 31 22:11:35 <PuffTheMagic> i'd day xterm is our best exemplar
Jan 31 22:11:35 <stbuehler> but it erases the whole screen on ESC[2J, regardless of margin
Jan 31 22:11:44 <stbuehler> xterm fails on menu 1
Jan 31 22:11:53 <stbuehler> wterm fails menu 1 after menu 2
Jan 31 22:12:11 <PuffTheMagic> ya I need to fix that wterm weirdness after menu 2
Jan 31 22:12:20 <PuffTheMagic> it has to do with the restoring term state at the end
Jan 31 22:13:09 <PuffTheMagic> stbuehler, are you using the vttest from wterm dir when you test xterm (the one that sets row,cols automatically) or are you using the orig where you need to set them your self
Jan 31 22:13:45 <stbuehler> i use the wterm binaries
Jan 31 22:13:50 <PuffTheMagic> ok
Jan 31 22:13:54 <stbuehler> although i didn't pull that checkout for some time
Jan 31 22:14:28 <PuffTheMagic> well at some point I had it figure out the actual term size and use that as defaults if the user didnt set sizes
Jan 31 22:14:40 <PuffTheMagic> i know many of the tests fail if the rows/cols dont match
Jan 31 22:31:02 <PuffTheMagic> where is that user comng from
Jan 31 22:33:43 <stbuehler> uhm
Jan 31 22:33:51 <stbuehler> if you don't know it?
Jan 31 22:34:19 <PuffTheMagic> i mean, i know the box it has to be on to have to domain
Jan 31 22:34:28 <PuffTheMagic> but i havent used irc on it in forever
Jan 31 22:34:38 <PuffTheMagic> so idk why it just started showing up recently
Jan 31 22:35:38 <PuffTheMagic> :D
Jan 31 22:35:51 <stbuehler> oO
Jan 31 22:36:28 <PuffTheMagic> i cant believe its almost Feb and I its like mid 50s out and i have by back door open
Jan 31 22:36:39 <stbuehler> how did you generate vttest/config.h?
Jan 31 22:36:54 <stbuehler> it's freezing here
Jan 31 22:37:14 <stbuehler> whatever this crazy fahrenheit value is
Jan 31 22:46:08 <PuffTheMagic> stbuehler, i just ran configure on my desktop
Jan 31 22:46:17 <PuffTheMagic> and used that
Jan 31 22:51:00 <stbuehler> i guess it could be a vttest bug (menu 1 failing after menu 2)
Jan 31 22:51:05 <stbuehler> it doesn't reset the modes
Jan 31 23:03:30 <stbuehler> ah, tab stop issue
Jan 31 23:17:05 <PuffTheMagic> Brybry, ping
Jan 31 23:20:14 <stbuehler> PuffTheMagic: can i push some stuff?
Jan 31 23:21:44 <PuffTheMagic> dont have to ask me that
Jan 31 23:22:07 <PuffTheMagic> go for it
Jan 31 23:23:46 <stbuehler_wterm> äöö working
Jan 31 23:25:13 <stbuehler> PuffTheMagic: perhaps you can reset #51 now, to see whether i missed something
Jan 31 23:27:07 <stbuehler> PuffTheMagic: we have two resizes at startup now (just so you know). i don't think it is really slow, so shouldn't be a real problem
Jan 31 23:31:06 <PuffTheMagic> stbuehler, u cant close tickets as a contributor?
Jan 31 23:34:01 <stbuehler> i can
Jan 31 23:34:09 <stbuehler> i just wanted to know whether it really is fixed :)
Jan 31 23:34:25 <PuffTheMagic> oh
Jan 31 23:34:32 <PuffTheMagic> 1 sec i will test
Jan 31 23:34:55 <PuffTheMagic> stbuehler, does scrolling look right in irssi with TERM=xterm
Jan 31 23:37:39 <stbuehler> hm
Jan 31 23:37:57 <stbuehler> no
Jan 31 23:48:49 <PuffTheMagic> stbuehler, u fixed menu 1 after menu 2,
Jan 31 23:48:56 <PuffTheMagic> but the tab test in menu 2 is always wrong now
Jan 31 23:49:20 <PuffTheMagic> in particular tab resetting is now broke
Jan 31 23:56:51 <stbuehler> hm
Feb 01 00:03:12 <stbuehler_wterm> ok, i think irssi scrolling works now here
Feb 01 00:05:07 <stbuehler> git diff
Feb 01 00:05:09 <stbuehler> ups
Feb 01 00:07:20 <PuffTheMagic> :D
Feb 01 00:31:14 <stbuehler> hm
Feb 01 00:31:21 <stbuehler> linux eats the tabstop
Feb 01 00:31:29 <stbuehler> so we only see spaces
Feb 01 00:31:51 <stbuehler> or echo converts them
Feb 01 00:33:37 <dwc-> "linux" what? it shouldn't.
Feb 01 00:50:00 <ka6sox> I can believe that Luna eats the tabstop
Feb 01 01:03:02 <PuffTheMagic> oh god
Feb 01 01:03:41 <PuffTheMagic> stbuehler, scrolling in irssi looks good, mc is broken horribly
Feb 01 01:04:13 <PuffTheMagic> only on xterm though
Feb 01 01:04:21 <PuffTheMagic> under rxvt it looks good
Feb 01 01:11:06 <stbuehler> tab stops should be fixed now
Feb 01 01:11:24 <stbuehler> what is wrong in mc? works here - scrolling through /var
Feb 01 01:11:56 <PuffTheMagic> the line drawing chars go away
Feb 01 01:12:16 <PuffTheMagic> and some of the sgr stuff doesnt get processed
Feb 01 01:12:43 <PuffTheMagic> weird
Feb 01 01:12:45 <PuffTheMagic> works this time
Feb 01 01:12:50 <PuffTheMagic> what did I do that made it look like shit
Feb 01 01:13:32 <stbuehler> hm, but i remember i hade some "poor man" style graphics some time ago too
Feb 01 01:14:45 <PuffTheMagic> i also dont get color in emacs sometimes
Feb 01 01:15:51 <stbuehler> hm
Feb 01 01:16:21 <stbuehler> do you get segfaults sometimes too, like cmatrix crashing from wild rotating?
Feb 01 01:17:00 <PuffTheMagic> umm, havent noticed
Feb 01 01:17:08 <PuffTheMagic> maybe once cmatrix crashed in exhibition mode
Feb 01 01:17:17 <PuffTheMagic> it restarted after starting
Feb 01 01:17:23 <PuffTheMagic> not sure it segfaulted
Feb 01 01:18:03 <stbuehler> the main problem is that you don't get back to the shell somehow
Feb 01 01:18:17 <stbuehler> the shell does start reading the input again, but it doesn't do anything
Feb 01 01:18:29 <PuffTheMagic> in exhibition mode? no shell is run
Feb 01 01:18:35 <PuffTheMagic> it launches cmatrix directly
Feb 01 01:18:44 <stbuehler> no, in normal mode
Feb 01 01:18:55 <stbuehler> just kill -SEGV $(pidof cmatrix) from novaterm
Feb 01 01:24:25 <stbuehler> gn8 :)
Feb 01 01:24:44 <PuffTheMagic> night
Feb 01 01:45:42 <dwc-> it segfaults if you SEGV it =]
Feb 01 01:51:20 <PuffTheMagic> https://github.com/PuffTheMagic/wTerm/issues/84
Feb 01 01:58:04 <PuffTheMagic> Brybry, where art thou
**** ENDING LOGGING AT Wed Feb 01 02:59:57 2012