Search
Sunday, 17th of September 2017, 9:01:40 UTC
9:33:02
dxtr
Can I make the prompt in slime slightly more fancy? Right now it's just a *
9:36:07
oleo
dxtr: http://paste.lisp.org/+7MRM
9:36:30
oleo
edit the prompt string accordingly
9:37:13
oleo
will give you CL-USER> at the start since cl-user is the package at the start
9:37:23
oleo
and when you change into another package it will change too
9:37:37
dxtr
oleo: That's literally exactly what I wanted but I couldn't quite find the correct stuff to poke at
9:38:02
dxtr
Also, isn't the slime buffer usually read-only?
9:38:07
dxtr
Except for the last line
9:38:18
oleo
err no idea i don't work with slime
9:38:51
oleo
i either use rlwrap sbcl for getting completion and history (you have to create the completion and history files too ofc)
9:39:11
oleo
or activate linedit or use sb-aclrepl
9:41:28
beach
dxtr: If you don't get the CL-USER> prompt, there is something wrong with your SLIME installation.
9:41:29
oleo
dxtr: http://paste.lisp.org/+7MRM/1
9:41:47
oleo
when you load that file you'll get a .sbcl_completions file created
9:42:03
oleo
with all the symbols dumped
9:42:48
beach
dxtr: Do you see any error messages, or any other messages that indicate that something is wrong?
9:43:09
dxtr
beach: Not at all. Should that be the default behavior? I can't quite remember
9:43:35
dxtr
Because now I get the CL-USER> after I added oleos stuff to sbclrc :p
9:43:55
beach
By default, you should get a buffer named *slime-repl ...* and it should have that prompt.
9:44:12
dxtr
I only get *inferior-lisp*
9:44:25
beach
There is something wrong then.
9:44:49
beach
How did you install SLIME?
9:45:21
oleo
dxtr: http://paste.lisp.org/+7MRM/2
9:46:15
oleo
dxtr: that's how i start my sbcl or images thereof
9:47:02
beach
dxtr: How did you install SLIME?
9:47:04
oleo
dxtr: i'm not using emacs at all by the way, i start right into mcclim and use it's editor climacs too
9:47:24
beach
oleo: Maybe your advice is not so good if you are not using SLIME.
9:47:43
oleo
welp, swank is loaded too
9:48:17
dxtr
beach: There. Fixed it :)
9:48:28
beach
What was the problem?
9:49:00
dxtr
My init.el checked for ~/quicklisp/slime-helper.el before actually setting up slime
9:49:06
dxtr
But that file doesn't exist now
9:49:16
dxtr
So I just switched it to (use-package slime....)
9:49:56
beach
None of that should be necessary.
9:50:21
dxtr
It shouldn't be necessary to install slime before using slime?
9:50:46
beach
dxtr: Why do you not have a slime-helper.el?
9:50:48
dxtr
use-package makes sure slime is actually installed
9:51:08
beach
dxtr: Did you not install SLIME using Quicklisp?
9:51:46
dxtr
https://github.com/slime/slime <- The slime instructions recommend MELPA
10:46:39
razzy
4673456323456787654323456787654323456
11:11:53
razzy
beach: sorry, unintended.
11:23:23
jackdaniel
it was meant to be boring? ;)
11:47:31
razzy
beach: does it have meaning to you?
12:01:58
_death
it means humans are not very good at random-walking their keyboard's digits row
12:06:32
Shinmera
razzy: It's likely a seed of some sort.
12:10:14
edgar-rft
a seed for growing numbers
12:12:28
razzy
actually, my keyboard sometimes spit random strings,... no meaning intended
12:15:54
razzy
it is frustrating at times :], funny in other times :]
12:34:04
phoe
mingus: memo for Xach: https://github.com/phoe/fox5/blob/6d8f73882be6ddaf1f94d9a89153a38f1b0160fc/skippy.lisp
12:34:04
minion
phoe, memo from beach: I started such a thing: https://github.com/robert-strandh/Spell
12:35:23
phoe
beach: I will be making a Common Lisp interface to the GCIDE dictionary.
12:37:05
phoe
It'll be GPL-licensed because of GCIDE's license.
12:37:33
phoe
But, maybe it'll be possible to hook it to your spellchecker.
12:40:07
phoe
Can your Lisp wordlist be generated from the english-N files?
12:40:26
beach
I don't know. I haven't looked at it for some time.
12:41:23
phoe
I might take a look at it one day.
12:41:24
beach
I don't see any part of speech information. Is there any?
12:42:21
phoe
http://paste.lisp.org/display/356107
12:50:23
beach
There is no information about things like plural form, past tense, etc.
12:52:15
phoe
You seem to have that information in your wordlists.
12:52:31
beach
Yes, and that's probably why I picked that particular one.
12:52:34
phoe
For each word in your spellchecker, you have its "base word".
12:52:42
phoe
And for that base word, you can find the GCIDE entry.
12:53:08
phoe
So I think we can link the two this way.
12:54:18
phoe
Good. I will try to write an interface for GCIDE and once I have it, we can think on how we can link the two together.
12:57:30
phoe
minion: memo for Xach: https://github.com/phoe/fox5/blob/6d8f73882be6ddaf1f94d9a89153a38f1b0160fc/skippy.lisp
12:57:30
minion
Remembered. I'll tell Xach when he/she/it next speaks.
13:12:08
_death
phoe: may want to avoid copying
13:12:24
phoe
_death: avoid copying? what do you mean?
13:13:50
_death
phoe: the one with copy-seq.. why not allocate all the frames in the beginning and just write to each one
13:14:16
phoe
because frame N depends on all frames that were before, so 1..N-1
13:14:57
phoe
so it's logical to me that for drawing frame N, I will want the result of drawing frame N-1, which depends on result of drawing frame N-2, ..., all up to frame 1
13:15:19
phoe
so it's logical to me to draw everything on one frame and then just collect their copies as results.
13:15:42
_death
so you pass the previous frame and merge the two data into a new frame
13:16:12
phoe
could do, sure thing - except I don't see any obvious optimizations here, sans for saving one frame's worth of memory
13:16:24
phoe
and doing one copying less
13:17:47
_death
it should be much faster.. I've been doing image-related stuff w/ Lisp for some years :)
13:19:38
phoe
should be? why would allocating N images from the start and writing to them be much faster than copying an array N times after writing to it?
13:20:06
phoe
it might be - I'm sleepy despite waking up two hours ago.
13:21:30
_death
you can count the amount of pixels read and written
13:21:34
phoe
it works well enough for me so far, maybe I can make it faster - but I consider it fast enough so far.
16:02:38
fiddlerwoaroof
dxtr: the other thing that might be happening is that you're looking at the *inferior-lisp* buffer instead of the *slime-repl sbcl* buffer
16:02:58
fiddlerwoaroof
my inferior-lisp just has the * prompt.
16:03:14
beach
I think he actually said that.
16:03:56
fiddlerwoaroof
Ah, missed that when I was reading the logs
Sunday, 17th of September 2017, 21:01:40 UTC