libera/#commonlisp - IRC Chatlog
Search
0:53:50
pdietz
IMO i's a good idea to look in alexandria or other such utility libraries (I like serapeum) for these sorts of things.
5:25:39
beach
phantomics: What would be the point of breaking backward compatibility for the very minor convenience to a very small number of users of Common Lisp?
8:05:28
hayley
I think I found the one good use for SIMPLE-BASE-STRING: one can scan at about 11 Gcharacters/second with BASE-CHAR, as opposed to "only" 4.7 Gcharacters/second with CHARACTER, because one can stuff more characters in a vector register.
8:47:53
hayley
Now that you mention it, I guess my Xorg.0.log nearly fits in L1 cache then (just 2KB short or so). Though I don't think I'm memory bound still.
10:20:59
rain3
- I had tried Paredit, Lispy, and 2 other similar packages ... too complicated, (and lispy too restrictive) - I hate them;there's also smartparens or smth like that, some people like to build atomic bombs to kill a fly; what always strikes me that usually those are exactly the people that don't know about the built-in "emacs" way of doing it
10:30:53
jackdaniel
Guest74: how clim model is broken? and do you have some specification draft that addresses these isses in your grand project?
10:35:12
beach
jackdaniel: I think we are supposed to read the IRC logs and make suggestions, rather than read a document with one or more proposals comparing pros and cons of each alternative.
10:36:40
hayley
To do the classic joke for the day (which I forgot the original form of): I have never used Paredit and never needed it.
10:36:46
contrapunctus
rain3: most of the time I get by with Boon - combined commands for movement over words and s-expressions, which combine with composable commands to provide killing/copying of s-expressions. But Paredit/SP splice operations are very useful. I also like Lispy's commands to move an s-expression forward and back, and the Lispy eval command is useful because it evaluates the s-expression before or aft
10:37:38
jackdaniel
beach: Im still waiting for some interesting idea to steal though. sadly until now only superficial complaints were presented
10:41:21
beach
jackdaniel: I don't think the main point was to complain about CLIM or anything else, but to come up with a good design. But then there was disappointment expressed about the lack of feedback, and I was trying to explain why no feedback can be expected unless there is a serious documented analysis of the problem and alternative solutions.
10:53:40
rain3
VincentVega: I forgot the details, I think it was the fact that it doesn't allow me to type a single paren and things like that , which weren't even easily configurable
10:57:38
VincentVega
rain3: Oh, I hear you. I did find that infuriating myself at first, with the " especially, but I did manage to turn that off (I think through a custom binding). Although I think it just takes getting used to.
11:01:47
VincentVega
rain3: No persuasion on my part, the only reason I am using it is because of lispyville which makes lispy usable with evil.
11:02:51
rain3
I was also curious about lispyville , but never gathered enough courage to install it , or I tried and I failed
11:04:06
rain3
I was using evil mode with lispy and bindings such as this: (evil-define-key 'insert evil-lispy-mode-map "}" #'lispy-brackets
11:04:55
rain3
"Most people use a package called paredit. I find it too complicated, I just just the following: (info "(emacs) Parentheses") Basically C-M-{n,p;f,b;u,d}"
11:05:22
VincentVega
rain3: I see. I got custom bindings going for the whole deal myself, a strange mix of lispy and paredit and lispiville's own commands. I do find it satisfactory enough by now, though.
11:07:00
VincentVega
rain3: I do those through a leader key for sexps, chords are far too cumbersome to my taste.