aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorterminaldweller <devi@terminaldweller.com>2024-05-22 20:20:11 +0000
committerterminaldweller <devi@terminaldweller.com>2024-05-22 20:20:11 +0000
commitd180c121e949ff98d8c0f5e04dc51577f9a6907a (patch)
tree690f12134f0e23ed2540092f4ac5fb540c93707f
parentupdate to go1.22.3 (diff)
downloadmilla-d180c121e949ff98d8c0f5e04dc51577f9a6907a.tar.gz
milla-d180c121e949ff98d8c0f5e04dc51577f9a6907a.zip
added a note regarding escape sequnces getting cut off in the middle
-rw-r--r--README.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/README.md b/README.md
index 90b779c..9f46126 100644
--- a/README.md
+++ b/README.md
@@ -465,6 +465,11 @@ go mod vendor
go build
```
+## FAQ
+
+- I end up with color escape sequences getting printed at the end of a line/begging of the next line. what gives?
+ This is happening because you have reached the message limit on irc which 512 for the event. This practically leaves around 390-400 character left for the message itself. Certain ircds allow for bigger sizes and certain clients might do. But most ircds dont send `linelen` to the clients. In a closed-loop situation where you control everything, as in, the ircd and all the clients(i.e. a private irc network), you can try to increase the linelen for the ircd and the client. Please note that the client in this case is girc. You irc client can have its own set of limits too. The 512 limit is hardcoded in girc. You can vendor the build or use the vendored dockerfile, change the hard limit and run milla with an increased limit. Needless to say, you can try to use a chromaFormatter that produces less characters which is basically not using treucolor or `terminal16m`.
+
## Thanks
- [girc](https://github.com/lrstanley/girc)