From 3bc8f17708f683ba0b6b297273f8b0051dbf9ebe Mon Sep 17 00:00:00 2001 From: Will McGugan Date: Sun, 20 Nov 2022 14:26:02 +0000 Subject: [PATCH] fix twitter link --- docs/blog/posts/steal-this-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blog/posts/steal-this-code.md b/docs/blog/posts/steal-this-code.md index 2e2053d4a..124a54794 100644 --- a/docs/blog/posts/steal-this-code.md +++ b/docs/blog/posts/steal-this-code.md @@ -67,7 +67,7 @@ Here's a quick example of its use. It works like a dictionary until you reach a {'bar': 2, 'baz': 3, 'egg': 4} ``` -In Textual, we use a [LRUCache](https://github.com/Textualize/textual/search?q=LRUCache) to store the results of rendering content to the terminal. For example, in a [datatable](https://twitter.com/search?q=%23textualdatatable) it is too costly to render everything up front. So Textual renders only the lines that are currently visible on the "screen". The cache ensures that scrolling only needs to render the newly exposed lines, and lines that haven't been displayed in a while are discarded to save memory. +In Textual, we use a [LRUCache](https://github.com/Textualize/textual/search?q=LRUCache) to store the results of rendering content to the terminal. For example, in a [datatable](https://twitter.com/search?q=%23textualdatatable&src=typed_query&f=live) it is too costly to render everything up front. So Textual renders only the lines that are currently visible on the "screen". The cache ensures that scrolling only needs to render the newly exposed lines, and lines that haven't been displayed in a while are discarded to save memory. ## Color