Darren Burns

@amottola I've extracted the big if-elif block into a dictionary lookup, and added some missing type hints. Also added an `xfail` test for a case where "cursor word right" is...

I also think there might be a class with "suggesters" as they change the background/dim text if there's a matching suggestion. It's making me wonder if this functionality could live...

> That's a thing that started to tick in the back of my head while creating this whole PR... So I propose to open up a second PR with a...

Closing - Implemented in #4783 and is now released.

@TomJGooding Good question. I think it depends very much on context and I don't think there's really a correct answer here. You could argue that the innermost focused widget's bindings...

This was changed way back in https://github.com/Textualize/textual/releases/tag/v0.61.0 to make it a requirement that the namespace is specified. I think that's just some outdated documentation. Changed in PR: https://github.com/Textualize/textual/pull/4516

Yeah, there's some weirdness here. Simpler MRE: ```python from textual.app import App from textual.widgets import Static from textual.containers import Vertical class BugReportApp(App[None]): CSS = """ Vertical { border: tab #f0f0f0;...

Some ideas and a bunch of questions that would be good to chat about: - Add `App.theme_name (str)` reactive which is set to the theme name. - Add `App.theme` read-only...

It's intended to minimize: https://github.com/Textualize/textual/pull/4931#discussion_r1731011637

You should pin Textual, as it's still zerover and so the API is subject to change. We'll be hitting 1.0.0 soon, and then trying to adhere to SemVer as much...