10:01:01TMAwhen editing java, I routinely use all three big ides -- eclipse, netbeans and intellij.
10:01:12makomoTMA: yeah, this guy does have that vibe to him sometimes :D
10:02:11jack_rabbitmakomo, I gave eclim a fair shot, but found it unintuitive. It seemed to get in the way more than it was helpful.
10:02:41makomojack_rabbit: ah :^(. what was the worst part about it?
10:03:29jack_rabbitmakomo, It seemed inconsistent. There were also some features that seemed to require a fixed window layout. I'm not sure how they hacked emacs to behave that way, but it was very strange.
10:03:48makomojack_rabbit: hm interesting. i'll have to give it a shot soon
10:04:13jack_rabbitmakomo, Basically instead of providing tools and such to use with my regular work flow, it seemed to require me to conform to its rigid rules.
10:04:46jack_rabbitmakomo, Also, it seemed to work pretty inconsistently. But YMMV.
10:06:47makomoin conclusion, i consider CL/Lisp to be one of the most important discoveries i've made
10:07:08makomoit has opened my eyes to many things, and allowed me to see the essence of many language features
10:08:51jack_rabbitI have written a couple of import-related emacs functions for Java: https://gist.github.com/knusbaum/a0934a7a6de986420e683704a38bf58f
10:24:52hajovontafirst I used Emacs in cua mode. for years.
10:25:12hajovontathen I slowly became more hardcore and disabled it.
10:25:48hajovontaI now use the old C-f, C-b etc. keybindings to navigate around
10:26:11hajovontathis is because it was hard to switch when I used paredit to navigate lisp code
10:33:34TMAthe problem with the default emacs keybinding for me is my supershort pinky finger. that and the left ctrl being too far, the right too awkwardly positioned.
10:35:55hajovontaI swapped the capslock and left ctrl for the same reason
10:57:05dimis it possible to build SBCL in a way that the sbcl binary then contains extra .so dependencies, such as openssl.so or sqlite.so?
11:00:21jack_rabbitdim, Is there a reason you want to do that?
11:03:31dimyeah, to avoid having to dlopen from the image when it's possible that the symbol found at dlopen won't match the symbols found at image creation time
11:04:38dimnow that I had to write this, I wonder if having the .so in the binary header rather than used with dlopen() is going to have an impact on the problem...
11:05:51p_ldim: you might want to write a hook before save-lisp-and-die, which dumps a list of shared objects, copies them to where the image is to be saved, and rewrites the list to contain image-relative paths
11:06:31p_lbut getting dlopen to link code from arbitrary memory location might be tricky
11:06:53p_l(unless your bootstrap code unpacks them to filesystem before calling dlopen() )
14:35:21shkapuchacz: does that answer your question?
14:36:06puchaczshka: yes, it will work. however I was hoping I could have a mechanism that works for all threads I can encounter, not only these I create or control somehow