#ntalk

nanochat utils

see also neauoire's client, olive's client, chloe's client and probably other things

#ntalk.sh: simple nanotalk server

meant to be run under a connection broker like socat.

probably there's a chance of the file being clobbered. will get slower with more scrollback, cause it's just implemented with tail and head and wc. :P

#ntalk.tcl: tcl/tk nanotalk client

requires you have wish(1) installed.

the config is just a tcl script. ntalk boots to a config file editor, in which you can set fonts and stuff the connection is done entirely over $sok, so set that to whatever. if you want to include e.g. tcltls, go ahead. the config file is saved to/read from ~/.config/ntalk/cscript.tcl.

right click on any sixel in the chatlog, and you can save it under a custom name. saved sixels can be accessed through the "sixels" option in the top menu. slashes are interpreted, so naming one e.g. "faces / :D" will create a submenu called "faces". sixels are saved to/read from ~/.config/ntalk/cscript.tcl. each non-empty line stores one sixel, with the first '=' separating the name and the data.

if $cmds is set, it will be used for command parsing. it is inserted into the body of a switch statement, with globbing enabled. you do not need to start your commands with /. if $server is set, it'll be shown in the top bar. if $user is set, it'll be used for the username.

to see the builtin commands, read the source code. they're torwards the bottom.

if tklib is installed, history will be setup on the main input box. if Thread is installed, netcode will run on a second thread (recommended!!!).

Ctrl-Shift-R will restart the client, allowing you to test config changes rapidly. Ctrl-Q exits.

#scrollbackup.sh: simple backup script

just sends HIST and QUIT and logs it to a file whose name indicates when it was generated and from what server