freenode/#clim - IRC Chatlog
Search
14:48:42
scymtym
array commands and slime-style navigation: https://techfak.de/~jmoringe/new-inspector-2.ogv
14:51:34
jackdaniel
I think I have a brilliant idea about sheets and pages, still working out details
15:14:15
scymtym
jackdaniel: no. everything is still uncertain. my current employment will very likely end in october so there is that
15:15:31
beach
scymtym: I think some improved demos when you are further along would make people much more excited and therefore more likely to support. No rush of course.
15:17:59
scymtym
beach: possibly. i'm not sure how many #lisp participants envision clim-based tools in their lisp development workflow. some seem eager to even revert from "graphical" emacs to a purely terminal-based environment
15:18:52
jackdaniel
I still haven't abandoned the idea of writing terminal-based backend to discover rough edges regarding unit assumptions
15:19:22
jackdaniel
so it is not impossible that your interactor will work in terminal-based environment too ;-)
15:21:05
beach
And, in my opinion, that's the right way of doing it. Use the full CLIM machinery for presentations and such. Then have a terminal backend, likely with a subset of all the features, but still workable.
15:21:23
scymtym
i still think that making everything as modular as possible and supporting things like the language server protocol is the best way to satisfy as many people as possible (aside from the technical benefits)
15:21:59
jackdaniel
beach: apparently terminal has more features than clim! https://terranostra.one/posts/ASCII-Art-Animations-in-Lisp.html ;-)
15:26:05
jackdaniel
(I think that fully-featued interactor is ambitious enough - I'm curious because I have a few ide-part projects in mind too)
15:28:11
scymtym
jackdaniel: i don't know yet. though an actual /integrated/ development environment may be the easiest to sell as a project proposal
15:28:16
jdz
jackdaniel: Apparently terminal has even more features: https://github.com/hackerb9/lsix
15:29:06
jackdaniel
jdz: yes, I'm aware of sixel graphics - nice thing though if I need graphics I'd use a graphical toolkit not a terminal ^_^
17:00:08
jackdaniel
I already render all lines (partial fix is in input-refactor branch), but if there is no new line after last line we miss that (page-break wise and scroll-wise)
17:13:19
Inline
the correction of (count (- width (mod column tab-width)))) to (if (= tab-width 0) 1 (- tab-width (mod column tab-width))))) and then putting immediately a line (decf offset count) solves the problem
17:33:40
Inline
initially the loop does not stop at 0 when you observe the >= stuff, it has one more cycle left so to say, but with 0 it bails out and no chance of preventing that, but when you give 1 as a result of the mod operation and decrement just afterwards then one didn't change the cycle count and the relative offset differences (offset offset2) remain constant, otherwise we introduce a off-by-one error and you get something
17:35:15
Inline
my previous <= was a total noob fail, since it corresponds to a no-op, and i was wondering why it was so fast (cause it didn't change the tabification of the opened file at all)