Community

It would be nice to get some color in command results, for example by interpreting the ansi color escape codes.

I'd like to make errors and warnings more visible, among the informational text. And I do control the output format of the application being called.

What exactly is stopping you from configuring

Configure - Preferences - Document Classes - Command Result - Syntax

and

Configure - Preferences - Document Classes - Command Result - Colors

in the way you want?

The syntax language doesn't seem designed for escape sequences or other invisible markup.

And I do control the output format of the application

The syntax language doesn't seem designed for escape sequences or other invisible markup.

Why do you insist on using the invisible markup for syntax when you are in control of the output?

MudGuard wrote:

And I do control the output format of the application

The syntax language doesn't seem designed for escape sequences or other invisible markup.

Why do you insist on using the invisible markup for syntax when you are in control of the output?

I'm not sure I understand the question. Markup is never, in itself, invisible. Whatever application process the markup may choose to show the markup, or hide it.

The idea was to get the the same output as today, just with colors. People should get the same output whether they run the application (with an extra command line argument) from inside textpad as outside. Having two different formats would complicate the documentation of the application.

Which means invisible markup. ANSI color escapes is an obvious choice, since they are widely supported by other command line applications. That is, people would be able to get color when running in other existing environments, and textpad would show color for other existing applications.