freenode/lisp - IRC Chatlog
Search
13:20:20
beach
Should be (documentation name 'structure) or (documentation (find-class 'name) 'type)
13:24:10
ogamita
Notice that there are macros that allows you to define classes using the same syntax as defstruct, if that's the reason.
13:26:23
axion
beach: I have been over this a few times here. It's to have typed structs, that compile down to arrays except with named slots for accessing elements.
13:29:39
axion
and also for code that is quite a few years old that is a beast to maintain, but it is the result of a friend and I disassembling a ton to write an efficient linear algebra library.
14:09:25
ogamita
axion: normally, changing the defstruct option (or s/defstruct/define-structure/ to get CLOS classes) will left the other program properties invariants and can be done rather easily.
16:31:27
beach
I just created two more (very small) tasks on the Lisp Guild site: https://github.com/Lisp-Guild/lisp-todo/projects/1
16:41:28
beach
Anyway, time for me to go cook dinner, so I won't do anything else until tomorrow morning (UTC+2).
17:48:22
jackdaniel
how to install custom lisp build (for instance sbcl compiled by me) in it from specified path under known name
18:42:34
TruePika
I can't figure out how to print some ANSI escapes without advancing the column (for pprint etc.)
18:46:04
TruePika
shrdlu68: I don't know if screen does (I'll check in a bit), but PuTTY does for sure
18:47:48
shrdlu68
strange. So when you ouput the code for color yellow, for example, the pointer position advances?
18:49:02
TruePika
(progn (pprint #<something with escapes>) (pprint-tabular ...)) doesn't have the first column align as expected
18:52:37
TruePika
I output 16 characters which don't advance the TTY cursor (including #\Esc), with the tabbing interval at four, it looks like there are 20 extra spaces of indent
18:54:31
TruePika
I'm now also curious about how double-width characters are treated, both by screen and Lisp (I know PuTTY and IIRC Vim work with them correctly)
18:55:16
shrdlu68
TruePika: Would it make a difference if you used format or some other means to print the codes?
18:56:05
TruePika
I'm using format, actually (so I can include the ^[ without literally typing it and potentially confusing the TTY)
18:58:42
TruePika
Ideally, I should be able to say "this is zero-width, don't pprint newline or touch the column position"
18:59:49
TruePika
aside from trying some sort of printf() call which might break with some stream types
19:34:24
joe9
any recommendations for an easy-to-understand pure lisp variant, please? I found LispKit Lisp https://en.wikipedia.org/wiki/Lispkit_Lisp , but, would prefer strict evaluation.
19:35:02
Xach
This channel is for Common Lisp. I don't really know where you might ask your question, sorry.
19:36:25
joe9
Xach: oh, sorry for the bother. I will check around for any other generic lisp channel.
19:56:15
shrdlu68
Adding ocsp support to cl-tls, and I'm seeing rather strange behavior with LetsEncrypt ocsp responders.
20:22:22
mazoe_
Hmm. I’m getting lost in the complexity that is CL paths. How does one get/print the string representation of a pathname?
20:24:07
mazoe_
Xach: I’d like to pass it to a unix utility. So I need an absolute or relative unix pathname
20:24:22
mazoe_
so, e.g., from (make-pathname :directory `(:relative “dir1”) :name "file.txt”), I would get “./dir1/file.txt”
20:24:45
Xach
mazoe_: because CL and the underlying OS might disagree about the details of the name.
20:25:32
Xach
namestring is the standard function, but it is for interoperability with the lisp currently running, not for external OS purposes.
20:25:52
TruePika
"However, since the effect of the pretty printer can be customized by conforming programs, the necessary flexibility is provided for individual programs to achieve an arbitrary degree of aesthetic control."
20:35:29
shrdlu68
TruePika: Highly unlikely, but I was thinking perhaps creating a new stream using something like #'make-broadcast-stream and writing the ANSI codes to that might help.
20:55:03
TruePika
I have a couple comments on the gist; one showing SBCL outputting ultimately to PuTTY, and one showing CCL on my Windows host