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.
ANSI color escape codes in command results
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
- Per Abrahamsen
- Posts: 7
- Joined: Wed Feb 04, 2004 5:09 pm
- Contact:
- Per Abrahamsen
- Posts: 7
- Joined: Wed Feb 04, 2004 5:09 pm
- Contact:
- Per Abrahamsen
- Posts: 7
- Joined: Wed Feb 04, 2004 5:09 pm
- Contact:
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.MudGuard wrote:And I do control the output format of the applicationWhy do you insist on using the invisible markup for syntax when you are in control of the output?The syntax language doesn't seem designed for escape sequences or other invisible markup.
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.