freenode/#lisp - IRC Chatlog
Search
15:01:05
_death
in general a Q&D way is (subseq (shuffle (iota n)) 0 k) although solutions using LFSRs and Feistel networks are also possible
15:21:08
_death
also note that alexandria:shuffle is still atrocious for lists :/ so it's better to coerce to vector, pass, and coerce back
15:21:11
Posterdati
I submitted some fixes for cffi to make it run on openbsd, but in the new release there's no trace of them :(
17:31:19
verisimilitude
I appreciate the thoughts my style document received. As noted, the upcased code is for display purposes and not as a suggestion to write it that way in a program. To you, no-defun-allowed, there's nothing wrong with a macro not expanding to symbols in the COMMON-LISP package, of course, but you should try if it's possible; in your case, it may very well not be; I don't believe LOOP and FORMAT have any excuse for their awful
17:36:13
verisimilitude
I wrote the document because someone in my Lisp venue wanted to read style guides and I'd a dearth of writing ideas.
19:29:21
verisimilitude
There are some things I'd like to add or improve, but I've yet to do so. Are there any such things you'd want to discuss?
19:30:07
verisimilitude
Oh, I've also yet to completely rewrite the documentation, as I've been intending to do with most of my documentation.
19:34:58
_death
verisimilitude: when I used it about a year ago, the issues were the differences in terminal emulators (I used the terminfo system, which is a pure CL "Terminfo database front-end") including mouse input (possibly, I don't think I fully resolved it).. I also had a small patch to support "bright" colors.. personally I think it was a mistake to represent colors as symbols (only)
19:39:39
_death
another was the issue of distribution, where a git repository was not available.. but since I found no reason to make my code public it wasn't a big deal (I just have my own git repo for your library)
19:46:16
verisimilitude
Oh, there have perhaps been changes since you last used it. Take a look. My READ-EVENT accepts mouse events, function keys, etc.; I added extended color support a ways back as well.
19:47:25
verisimilitude
Colors can be represented not just as symbols, but also RGB, CMY, and CMYK, as that's what ISO 8613-6 supports.
19:48:42
verisimilitude
Another change I'd been mulling over was adding (SETF PROPERTIES), which would make bold, italics, etc. easy to use, but I'd not decided on the set of properties I wanted to support; I'll probably resolve this soon by using a subset I'm certain of.
19:48:50
_death
good.. this is another reason to use a version control system - it is easier to notice updates
19:50:12
verisimilitude
It's unfortunate I've inconvenienced you, but I really just don't want to use git or these other systems, _death.
19:51:38
verisimilitude
The only really major and perhaps ``breaking'' change I've been considering is slightly changing how CURSOR behaves, by adding a CURSOR-NO-HANG and changing CURSOR to perhaps wait forever if the STREAM doesn't correspond to a terminal.
19:53:25
verisimilitude
If you'd want some additional feature, describe it to me and I'll mull it over.
19:55:19
_death
I guess fixing the mouse issues is the next thing to do there, and given your changes I may work on it ;)
20:02:00
_death
yes, the issue was with the read-event return values if I remember correctly.. maybe this was fixed
20:09:15
verisimilitude
Also, SET-MODE takes this as a list, for good reason, but that's obvious or would quickly be obvious.
1:23:42
onceagain
Just wanted to see if anyone's dealt with this, when I compile my file on vlime I get a package not found error even the package is recognized when I run the program line by line from the SBCL repl. I'm thinking it has something to do with my swank setup, any ideas what might be going on?
1:30:51
didi
So I finally used `macrolet' for the first time. This must be a milestone of some sort.
2:02:56
Bike
onceagain: compile-file doesn't execute as it goes, so e.g. the quickload is only compiled, not executed, when the later forms using :croatoan packages are compiled
2:05:26
onceagain
@Bike Interesting, I guess I don't really understand why it would throw an error though if that's the case?
2:05:49
Bike
onceagain: the package hasn't been defined, so it doesn't exist, so the reader can't read your code
2:07:11
onceagain
Hmm well the next line after the quickload is (in-package :croatoan), does that not define the package?
2:10:01
onceagain
Would you happen to have a good linke or reference to start reading about this kind of thing? I don't think I have enough understanding of compile-file to get this working yet
2:10:49
onceagain
I guess I could start with the documentation on compile-file, it helps to know that this isn't some kind of swank issue
2:12:42
White_Flame
the proper fix is not to have quickloads inline in your source code, or really anything that defines packages in the same source that uses them syntactically
2:13:10
White_Flame
put them in a separate file that's loaded beforehand, or preferably set up an .asd file for your project which can declare its dependencies
2:14:01
White_Flame
either that, or when you're working interactively just ensure you bring up your dependencies manually before using the file