20:06:15SAL9000Shinmera: that code was very VERY hacky in the name of getting something up quickly :-) I think the real solution is a class containing my_buffer, my_buffers etc. per-server.
20:19:15SAL9000Shinmera: looks like the script has some built-in rules for bitlbee, matrix and slack already, so presumably we'd ask the author to do the same for lichat
20:19:26SAL9000or you can modify them in your config file
20:21:15ShinmeraDid you take a look at the changes I made so far?
20:21:37ShinmeraThey're not tested and also almost definitely not entirely correct -- particularly determining the channel name of a buffer is missing since I didn't know how to tackle that best off hand
20:22:18SAL9000Didn't look in detail yet, checking now
20:22:28SAL9000Shinmera: hook_command is for new commands, hook_command_run is for "overrides"
20:22:55SAL9000/join and /part both exist (irc) and I wanted to modify their semantics when they are run in lichat buffers, thus hook_command_run
20:23:02SAL9000/lichat itself is a new command, so hook_command
20:23:28ShinmeraOk. How do we know whether another plugin already has that command or not?
20:23:35SAL9000in theory new commands should be mostly limited to /lichat foo rather than /foo
20:23:57ShinmeraAlso: we might need to do some buffer name mapping thingy because lichat channel names can contain almost anything, but I'd be surprised if weechat buffer names can.
20:24:00SAL9000there's almost certainly a way to check whether a command exists