Pipe code support in message reader
It'd be awesome if the newly enhanced ANSI-rendering message reader also rendered pipe codes correctly - I'm not sure if there's any sort of standard for them in the FTN world, but they seem to get randomly lobbed into messages (presumably as Mystic supports them).
eg:
|10Smooth|07<|11ACiD|08.|11b7|07>
It'd be great if they were rendered in all of its colourful glory.
Yessir. That's on my list for 0.0.8-alpha. ENiGMA supports Renegade style (like you see from Mystic et. al., and will ultimately do a few other's. I also plan on hyperlinking URLs and some very basic markdown support.
On Oct 15, 2017 2:36 PM, "David Stephens" [email protected] wrote:
It'd be awesome if the newly enhanced ANSI-rendering message reader also rendered pipe codes correctly - I'm not sure if there's any sort of standard for them in the FTN world, but they seem to get randomly lobbed into messages (presumably as Mystic supports them).
eg:
|10Smooth|07<|11ACiD|08.|11b7|07>
It'd be great if they were rendered in all of its colourful glory.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NuSkooler/enigma-bbs/issues/126, or mute the thread https://github.com/notifications/unsubscribe-auth/ABcH2-yGhDanrzsncqM5lP6-W-fgStVDks5ssmywgaJpZM4P54lE .
I was going to say, renegade style is really the only one that doesn't conflict with other formats... synchronet's ctrl-a format is pretty safe as well, but not really easy to input in any devices, and rarely used even in synchronet systems for messages.
This seems to partially work.
Messages with pipe codes coming in from other systems don't format with the colors, the pipe codes are visible. However on reply, the codes do get interpreted properly in the editor if quoting those original messages, and then upon save of that reply, the colors do appear in the message viewer.
For pipe codes in FSE, see #148