freenode/#lisp - IRC Chatlog
Search
20:58:12
no-defun-allowed
(also i can't get the status emoji picker to cooperate on safari, though that's a gitlab problem)
21:00:43
gendl
no-definitely-allowed: thanks. You can lodge the emoji picking issue as well, because the clnet maintainer takes gitlab updates seriously.
21:01:40
no-defun-allowed
i'll probably try later on firefox, since safari is pretty good at randomly breaking like that
22:25:08
phoe
Does anyone have any library for managing a body of loosely formatted text with images? I am thinking bold/italic/underline/strikethrough/quotation marks.
22:25:24
phoe
I could always try using CL-WHO with a subset of HTML, but I wonder if there is a lispier way for achieving that.
22:33:03
phoe
And I'd like the ability to convert to/from HTML, since I'll be using HTML to display it.
22:54:11
phoe
gendl: I think cl-markdown operates on strings though. I'll want to be able to traverse the resulting structure as a tree.
22:57:17
gendl
i'm not sure of your use case here but I find for normal web page contents, it gets to be overkill to have s-expression tree structure for each little bolded piece of text etc.
22:57:39
verisimilitude
Most HTML one comes across is broken in some way. I was entertaining the idea of an approach that parses only correct HTML and, in the case of failure, has the option of running heuristic parsing functions in an attempt to properly parse it. The idea was to avoid a large and heuristic-ridden parser by replacing it with a clean parser and the option of using heuristic, with the idea that one could even use heuristics when dealing with
22:57:55
verisimilitude
Is there any Common Lisp library that already does this or is my idea as novel as I like to think?
1:16:11
fiddlerwoaroof
The standard does have a provision that says something like "on a parse error, a conforming parse error may signal an error" or something like that.
2:07:39
verisimilitude
Who knows, Duns_Scrotus, but we know they're just looking at Chrome for it, now.
2:08:12
verisimilitude
In any case, would I be correct in thinking no current Common Lisp HTML parser takes this approach and has customizable parse error behavior?
2:10:14
Duns_Scrotus
it's not really "heuristics" it's a bunch of huge explicitly described state machines https://html.spec.whatwg.org/multipage/parsing.html#overview-of-the-parsing-model
2:22:48
verisimilitude
My idea was to have a simple parser that would ideally be fast and to only incur the complexity of heuristics if needed and optionally.
3:22:38
ym
M-. in last (quicklisp) slime/swank fails with "cond: Error: end of file on #<SB-IMPL::STRING-INPUT-STREAM {...}>"
4:51:02
fiddlerwoaroof
emaczen: https://github.com/fiddlerwoaroof/objc-lisp-bridge/blob/master/demo-app.lisp#L130
4:51:31
fiddlerwoaroof
https://github.com/fiddlerwoaroof/objc-lisp-bridge/blob/master/demo-app.lisp#L125
4:55:55
emaczen
If you can add methods at runtime, can't you then just call performSelectorOnMainThread:withObject:waitUntilDone:
5:00:16
emaczen
fiddlerwoaroof: What exactly is the superclass parameter to objc_allocateClassPair ?
5:01:13
emaczen
the documentation is just confusing to me since it seems to say that it is the metaclass of the class you are creating, but then why name the parameter super_class?
7:24:23
LdBeth
<no-defun-allowed "Fair enough."> #'no-defun-allowed: statistics showed CDR coding doesn’t reduce space used in practice
7:25:03
no-defun-allowed
That's very odd then. I read LispM compactors would try to create CDR coded lists.
7:28:52
LdBeth
With CDR coding they cannot just copy the list, because the reference show be kept anyway, so after all fragmentation would be cause