libera/#sicl - IRC Chatlog
Search
3:51:11
Qwnavery
One feature (that I think exists in lispworks) is being able to use a command on a function and have it automatically open the file that function is defined in, or list all the places that function is used would be a godsend.
3:52:00
beach
But that would require support from the underlying Common Lisp implementation I think.
3:53:40
Qwnavery
erm so l: 183 Commands/commands.lisp you've got a FIXME for the keybindings talking about groups, what do you mean by groups?
3:58:29
Qwnavery
Well, I'm going to implement saving with C-s and C-n to make a new file. Fixing the crashing.
4:05:18
Mondenkind
Qwnavery: collaborative editing is a large kettle of sardines; if you attempt to do it with lockstep you will get bad results
4:06:30
Mondenkind
attempting to use the same underlying representation for local as for remote operations doesn't work well when 'remote' is bigger than 1ms. This is x's mistake
4:07:43
Qwnavery
Mondenkind: That's uneccessary, because of the implmentation of cluffer the buffermode can be set to lines. You prevent editing of a line if another user is editing it with a few safety parameters. beach's implmentation of cluffer has covered things he didn't even know it could be used for.
4:08:02
Mondenkind
'You prevent editing of a line if another user is editing it' that's a form of lockstep
4:09:22
Mondenkind
you can spruce it up. Like hold a provisionary lock on lines above/below you. But the proper solution is crdt
4:10:09
Mondenkind
'outside of a home environment' I mean, network-collaborative editing is cool and neat. Just should be done in terms of its own representation layered on top of the existing one