freenode/#stumpwm - IRC Chatlog
Search
8:35:08
MichaelRaskin
That bad — I mean that maybe just stripping Firefox down and using Marionette is cpeed-comparable with Conkeror. Looks like not yet, Firefox open-close takes 2.1s vs 1.6s for Conkeror
8:43:57
MichaelRaskin
Nothing is wrong with Uzbl per se, but WebKit + Blink are close enough to create a «IE6.0» 2.0 situation, where some set of quirks is not even documented well enough but becomes a de-facto web standard, and then everything stagnates
8:53:27
MichaelRaskin
Apparently Microsoft messed up patenting the business method to enforce the patent against Google
8:56:01
MichaelRaskin
Although Microsoft never perfected the technology to the Google level: they naively thought that «extinguish» doesn't include _their own_ implementation.
9:04:53
MichaelRaskin
I wonder if this means that FF54 will make the mysteriously crashing fix for window.open in SlimerJS work
9:05:24
scottj
MichaelRaskin: I think OPEN_NEW_WINDOW not working is a different issue, I'm actually seeing it in ff46 just now
9:08:10
MichaelRaskin
It may be that fixing the crash will make updating the code in SlimerJS and Conkeror feasible
10:52:14
impaktor
Hmm, one can install stumpwm through quicklisp. Didn't know that. I use the git repo.
11:03:10
impaktor
scottj: in the blog post on swank+stump he uses port 4004 instead of 4005, is there any difference? "This ensures you can’t mess up your WM by accident while writing unrelated code." http://www.kaashif.co.uk/2015/06/28/hacking-stumpwm-with-common-lisp/index.html
11:03:56
MichaelRaskin
I think the point is that you do not confuse your StumpWM SLIME and SLIME you use for debugging other code not related for StumpWM
11:04:25
MichaelRaskin
If you never use SLIME except for controlling StumpWM, this advice is not for you
11:04:25
impaktor
if using port 4005, and I write a function, outside the stumpwm:: namespace (sorry for using c++ terminology), can it interfere with stump?
11:05:13
impaktor
MichaelRaskin: I do play around in slime sometimes, yes. So then 4004 is probably better for me, I guess.
11:05:21
MichaelRaskin
Well, you can send '(quit)' to the Common Lisp via SLIME, if it was not for StumpWM…
11:57:30
impaktor
Hmm, I've installed slime through quicklisp, as I had problems running the ELPA version (don't remember why now), but if I want to install slime-company for auto-completion... it seems to drag in the ELPA slime version, so I get two. Any advice?
12:08:31
drot
then load it with (load (car (directory "~/.emacs.d/elpa/slime-*/swank-loader.lisp")))
12:10:45
impaktor
drot: I used to have it through ELPA, then there was some major problem, and after a debate here, it was pretty much agreed upon that slime through ELPA is generally a bad idea.
12:17:35
impaktor
because quicklisp needs swank, and then I need to symlink some frankenstein monster together to get each half working righgt.
12:20:34
impaktor
And as I said, it didn't work, and it wasn't due to something I did wrong, I don't remember where I had the discussion, might have been over in #lisp.
12:21:58
impaktor
...but the channel wizards had a discussion among themselves about the pros and cons of ELPA vs. quicklisp install of slime, and after discussion all ELPA proponents saw the rationale in using it through quicklisp.
12:22:43
impaktor
I got the help I needed and was happy with that. I suggest you direct further questions on ELPA vs quicklisp in #lisp.
14:34:16
scottj
impaktor: yeah i use a different port for stumpwm, just left as default for new users