Search
Tuesday, 5th of February 2019, 6:05:04 UTC
6:29:52
fiddlerwoaroof
LdBeth: usually one just remembers it from the compile-file call :)
6:29:57
fiddlerwoaroof
e.g. (load (compile-file "foo"))
7:23:56
LdBeth
yeah! I got TPS successfully run on CCL now
7:37:53
verisimilitude
** NICK Petulant
7:37:58
Petulant
** NICK verisimilitude
9:27:28
_death
did you remember to file those TPS reports
9:41:20
akater
What is the best way to disable initargs validity checking for a particular #'change-class call?
9:42:23
no-defun-allowed
akater: silly question, are you @akater:matrix.org on matrix?
9:43:10
akater
no-defun-allowed: Yes.
9:43:15
no-defun-allowed
also, dunno if you can, validity checking is usually handled by however lambda lists are handled
9:43:29
beach
akater: You can try passing :allow-other-keys t in addition to other arguments.
9:43:52
beach
akater: I haven't checked whether that is supposed to work, but it might.
9:44:23
no-defun-allowed
"initargs validity checking" sounds like something silly like putting an odd number of values in the &key section, but i'm not sure
9:45:49
specbot
Declaring the Validity of Initialization Arguments: http://www.lispworks.com/reference/HyperSpec/Body/07_ab.htm
9:46:05
no-defun-allowed
right then
9:46:11
akater
beach: no, :allow-other-keys t doesn't seem to work.
9:46:18
no-defun-allowed
aha, that's what "validity checking" would be
9:47:21
akater
I'm not even sure how to do it globally withot total redefinition of primary method with &allow-other-keys
9:52:18
akater
^ “globally” as in “for all changes to a certain class”
9:59:29
akater
Oh no, turns out I put :allow-other-keys t in the wrong arglist.
9:59:54
akater
It did work, thanks beach.
10:00:47
adam4567
Quick question. Anyone got a reference on how to upgrade ASDF from 2 to 3? Linux, Lisp, Slime etc
10:05:43
akater
adam4567: 3.4 in ASDF Manual addresses this.
10:32:20
adam4567
akater: ASDF Manual s3.4, suggests using install tool install-asdf.lisp I'm not sure if I need a complete ASDF Git-pull and build first though.
10:36:13
jackdaniel
adam4567: in principle: cloen asdf, issue make, call (compile-file "/path/to/asdf.lisp")
10:36:32
jackdaniel
then put "/path/to/asdf.fasl" in your chosen location and put in your lisp init file
10:36:43
jackdaniel
(load "/location/of/asdf.fasl") before anything else
10:36:50
jackdaniel
(even before quicklisp)
10:40:07
adam4567
jackdaniel: Thanks. That should get me going.
10:55:05
flip214
Is there some compatible way to find out whether a PATHNAME is a directory or a file?
10:56:45
flip214
If there was a slash at the end there'll be no PATHNAME-NAME, but if there wasn't there will, so that alone isn't enough.
10:57:31
flip214
Basically, I've got a string; if it's a file, I want to read it, if it's a directory, I want to read all "*.conf" in there.
11:04:21
phoe
flip214: PATHNAME-NAME is null if it's a directory
11:08:57
flip214
phoe: only if the input string ends with a /
11:09:08
flip214
"/dev" has "dev" as PATHNAME-NAME
11:12:14
phoe
flip214: #p"/dev" itself refers to a file named DEV in the root file system
11:12:29
phoe
the pathname itself does not yet know whether anything it points to is a directory
11:12:42
phoe
you actually need to query the filesystem to find out
11:13:20
phoe
https://stackoverflow.com/questions/3732167/common-lisp-how-to-say-if-a-pathname-points-to-a-regular-file-or-a-directory
11:13:28
phoe
so, (pathname-name (probe-file filespec))
11:14:01
flip214
phoe: yeah, right, a kernel/filesystem access is needed. ah, PROBE-FILE does that? thanks!
11:14:31
phoe
(probe-file #p"/dev") ;=> #P"/dev/"
11:14:36
phoe
so yes, it appends the missing slash
11:23:00
flip214
phoe: I just found out that DIRECTORY also does this normalization; and it will already correctly handle "etc/*.conf" as well!
11:58:09
jackdaniel
pathnames and files are conceptually different things indeed
15:08:33
littlelisper
in ltk, if i use event loop for a continuous action with sleep for speed, i cant use the widget callbacks
15:08:38
littlelisper
https://pastebin.com/kA8VZN9s
15:09:46
littlelisper
how can i use both, event loop actions and the callbacks
15:25:41
beach
littlelisper: What is your reason for using ltk rather than McCLIM?
15:26:23
Josh_2
That's like personally insulting beach /s
15:27:54
beach
I am asking because if there is anything that littlelisper is missing in McCLIM, we should put it on the TODO list.
15:28:25
beach
Or, we *might* put it on the TODO list, depending on what it is.
15:48:39
_death
littlelisper: not sure I understand what you're trying to do, but ltk has an AFTER function that you can use to perform an action after a duration of time
16:02:05
littlelisper
no, theres nothing missing beach. the documentation is too sparse. the only guide i have is clim2 UG by franz. i am on my way to mcclim
16:02:33
littlelisper
thanks _death, thats exactly what i was looking for
16:03:33
LdBeth
phoe: http://gtps.math.cmu.edu/tps.html
16:05:06
LdBeth
<freenode__de "did you remember to file those T"> _death: well, I worked with version control
16:07:59
_death
LdBeth: it was joke.. a reference to Office Space
Tuesday, 5th of February 2019, 18:05:04 UTC