Terminal default coloring with textual CSS

[friscorose]

Wishlist

When using Rich one can set "default on default" as a means to preserve the native terminal color presence. It would useful, especially for inline mode, to have a TCSS styling mechanism that maintains the same Rich default coloring behavior.

Possible Solution

A possible scenario that is somewhat semantically consistent might be to add as valid a 'none' value to both color and background styles.

Example

Widget_name {
  color: none;
  background: none;
}

[github-actions]

We found the following entry in the FAQ which you may find helpful:

• Why doesn't Textual look good on macOS?

Feel free to close this issue if you found an answer in the FAQ. Otherwise, please give us a little time to review.

This is an automated reply, generated by FAQtory

[TomJGooding]

Perhaps I haven't understood what you mean by "default" colors, but you can preserve ANSI colors in inline apps?

This FAQ might be relevant here? https://textual.textualize.io/FAQ/#why-doesnt-textual-support-ansi-themes

[friscorose]

Perhaps I haven't understood what you mean by "default" colors, but you can preserve ANSI colors in inline apps?

This FAQ might be relevant here? https://textual.textualize.io/FAQ/#why-doesnt-textual-support-ansi-themes

If I run> uv run --with textual t_test.py

from textual.app import App, ComposeResult
from textual.widgets import Label

class Test(App):
    def compose(self) -> ComposeResult:
        yield Label( "[on default]                " )
        yield Label( "[on default]   0123456789   " )
        yield Label( "[on default]                " )

if __name__ == "__main__":
    Test().run(ansi_color=True, inline=True, inline_no_clear=True)

I get different result in both foreground and background styling than > uv run --with rich r_test.py

from rich import print as rprint

rprint( "[on default]                " )
rprint( "[on default]   0123456789   " )
rprint( "[on default]                " )

[TomJGooding]

ansi_color=True should be set in the App constructor rather than in the run method, so I think your first example will just crash?

Perhaps I'm still missing something, could you include some screenshots to help show what you mean?

[friscorose]

I had edited the wrong test file arghh. You are correct, that technically resolves the issue in the app constructor.

Is it undesired UI or difficult to add this capability to TCSS as mentioned above? If so, I happily (or you may) close this request.

[TomJGooding]

I'm not a maintainer, but this seems an intentional design decision based on the FAQ linked above

[friscorose]

Closing as technically provided per discussion.

[github-actions]

Don't forget to star the repository!

Follow @textualizeio for Textual updates.