freenode/#lisp - IRC Chatlog
Search
5:09:37
aeth
for 2D (probably the most common after 1D), just selecting a row and a start and an end works for most cases
6:43:18
karlosz
its wrong to assume that array elements are initialized to 0 without specfiying initial element or initial contents right?
6:45:41
beach
"If initial-element is not supplied, the consequences of later reading an uninitialized element of new-array are undefined unless either initial-contents is supplied or displaced-to is non-nil."
6:46:22
karlosz
right, i was beginning to self doubt myself because the sbcl internals make that assumption somewhere in make-hash-table
6:49:04
karlosz
an array is created but implicitly assumed to be initialized to zero which was causing problems for me
15:27:38
jmercouris
I get a 0: (CFFI::FL-ERROR "Unable to load any of the alternatives:~% ~S" ("libmysqlclient.20.dylib" "libmysqlclient.dylib"))
15:28:03
Bike
i believe it does whatever the implementation does, and the implementation probably defers to the operating system
15:28:33
Bike
https://common-lisp.net/project/cffi/manual/html_node/_002aforeign_002dlibrary_002ddirectories_002a.html
15:33:39
rpg
I have been having trouble with slime-selector recently -- none of the characters I type as selections matches against slime-selector-methods. E.g.: "No method for character: ?\R" -- any idea why this would be happening? I'm not sure what is going on, but it seems like my selector characters are being UPCASED, then matched against slime-selector-methods. Any idea what could be doing this upcasing?
15:40:48
Ukari
i want to export some methods named 'map' and 'do' which would accept special classtype argument in my package, but there has already been 'map' and 'do' function in package :cl
15:45:38
scymtym
for CL:MAP, you could also look into user-extensible sequences, but not many implementations support them
15:52:12
lieven
Ukari: basically, when you type "map" in your code, the reader converts it to "MAP" and that's the name of the symbol defined in the CL package. by writing |map| you instruct the reader to make a symbol with as name "map"
15:56:08
rpg
Looks like read-key-sequence should give me the lower-case character, but somehow it seems not.
15:57:14
Ukari
thanks you, lieven, thought i might change the function name instead of use |map| as a method name which would be export due to it seems a bit strange to be wrap with ||
15:59:41
rpg
*In the context of slime-selector* read-key-sequence is upcasing. Anyone have a clue about what could be doing this? some rogue dynamically-scoped variable?
16:03:24
rpg
Should this be worrying me: Warning: Bug in minibuffer-inactive-mode: it forgets to call `run-mode-hooks'
16:07:00
rpg
<_death> that's the usual advice, but I have 2042 lines of emacs-lisp in init.el and 240 in slime-config.el. I have been using emacs for almost 40 years. I know you are trying to be helpful, but that is almost like saying "start by scraping your machine, and then put all the binaries back one by one."
16:07:47
rpg
For anything involving interactive debugging, the time cost of this strategy is simply staggering.
16:18:27
ggole
And describe-buffer-case-table, which might be interesting to run in *slime-selector*'s minibuffer thingy
16:22:48
rpg
ggole: this looks ... odd: "⇧A uppercase, matches a " and "A lowercase, matches A" -- any idea what the "matches" means?
16:25:42
ggole
Hmm. Well, in scratch it says a lowercase, matches A and A uppercase, matches a, so it looks like entries in the upcase and downcase parts of the table
16:26:21
rpg
ggole: I think that's just a stupid way of printing. If you look at the first of the two strings, they show capital A as "A with shift."
16:27:44
rpg
I just tried shift R to see if somehow I was getting case-inversion behavior, but not so -- it looks like somehow read-key-sequence in slime's minibuffer is upcasing. But not in the buffer itself. I suspect some state leakage.
16:29:41
ggole
I would probably try temporarily ripping out some slime contribs to see if that changes things
16:32:08
rpg
ggole: This started when I started working with Python -- I'm wondering if some of the python emacs config gunk is leaking state.
16:34:51
rpg
That's why I was wondering if the warning about minibuffer-inactive-mode not running its hooks was a problem.
16:38:05
rpg
ggole: (abc ABC) as expected, but the only way I know how to do this is by jamming elisp into a call to message in a redefined slime-selector, which means I'm not sure that this reflects what happens in the read-key-sequence context.