Hi Apam,
I have noticed that when viewing messages with ANSI in them, that the origin/tear lines for the message are the same colour of the last
part of the ansi. Ie: if the ansi's last colour was yellow, then so
is the tear/origin line. etc...
Quoting apam to vorlon <=-
However, it relates to Tiny wanting different colours for quotes, if I
do that, I'll also do different colours for tag/origin lines.
Quoting apam to vorlon <=-
However, it relates to Tiny wanting different colours for quotes,
do that, I'll also do different colours for tag/origin lines.
Yes please for both? ;)
is the tear/origin line. etc...
That's not really a bug, as the tear/origin line is a part of the message (if there is no reset ansi code posted it's not reset). However, it relates to Tiny wanting different colours for quotes, if I do that, I'll also do different colours for tag/origin lines.
is the tear/origin line. etc...
That's not really a bug, as the tear/origin line is a part of the
(if there is no reset ansi code posted it's not reset). However, i relates to Tiny wanting different colours for quotes, if I do that
also do different colours for tag/origin lines.
Oh, It looks weird that's all.
On 17-Dec-2018 20:15, apam wrote to Tiny <=-
I've implemented it into the msglib branch. I went for bright cyan for quotes and bright blue for tag/origin lines. I should make the colours configurable, but unsure of the best way to do that? Through bbs.ini maybe?
Quoting apam to Tiny <=-
I've implemented it into the msglib branch. I went for bright cyan for quotes and bright blue for tag/origin lines. I should make the colours configurable, but unsure of the best way to do that? Through bbs.ini maybe?
You can see it in action on the fat sandwich (it works both in the telnet/ssh and www readers)
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 69 |
Nodes: | 4 (0 / 4) |
Uptime: | 06:52:35 |
Calls: | 1,193 |
Calls today: | 5 |
Files: | 8,242 |
Messages: | 302,684 |