Will McGugan

Ok. I have a feeling that a passing a get_time callable may also be worthwhile, and its a small change anyway. Will leave this ticket up for graphs, but sounds...

I don't think there is any performance issue in getting the time, it's a fairly lean operation: ```python >>> monotonic()-monotonic() -1.1669471859931946e-06 ``` I think I see where you are going...

Interesting. I don't see that, probably because I develop with 3.7. Shutting down cleanly is one of the hardest things about asyncio.

Are you certain you are running the latest code? What does `pip freeze | grep textual` give you? It has very possibly reoccured, but I had fixed a very similar...

Try uninstalling textual first, but I would have thought that would be enough. So you are seeing this on Linux consistently, but MacOS intermittently?

Yeah, got an issue for that https://github.com/Textualize/textual/issues/473

I can't reproduce that here, on MacOS. Do you have any kind of shell integration or extension active? Is it only the code viewer where this happens, or other examples?...

We're working on a branch which will make these kind of things easier to create. And there will likely be a builtin list view. I'm afraid I can't help you...

`set_interval` will create a new timer each call. You can save the timer object with `self.interval = self.set_interval`. To change the "Refresh rate" you can stop that interval and create...

Makes sense. That will make it in to the next version.