![](https://www.dresan.com/blog/wp-content/uploads/2023/07/Screenshot-2023-07-27-at-12.51.42-PM-600x450.png)
So, in case you don’t own this cat, the little brow-furrowed face Loki is currently making is his “I really want your food but you’re not letting me eat it, so I’m going to sit just at arms length and fume” face. He thinks if he waits long enough, he’ll be able to sneak in and try some. My long arm thinks otherwise.
Anyhoo, while I said I wanted to put blogging at the first of the day to make sure it got done, it turns out that I was way more interested in making sure that I didn’t fall grievously behind on my Camp Nano project, Dakota Frost #7, SPIRAL NEEDLE, nor miss any of my other responsibilities.
I’m mostly caught up now, so I’m trying to put blogging back on the queue. Interestingly enough, after my rant about blocks, the WordPress folks have reached out to talk to me about blocks. Talk about customer service! So I’m also blogging trying to replicate the bugs I observed the other day that set me off.
So far, I cannot replicate the cut-and-paste error, where trying to select all the text only copied part of it – it is entirely possible that the system had just gotten into a cruftly state, which can happen to any program of sufficient complexity.
I can, however, replicate the cut-and-paste problem I had, where trying to re-order sentences introduced new paragraph breaks in a way that’s not standard for Word, Google Docs, or TextEdit. This is probably most directly attributable to the text being in blocks, but it might be fixable.
I also reproduced the “Where’s Waldo” interface issue where I could not easily inject new blocks – though now I see that can be fixed with a carriage return followed by a slash, which is documented in the interface, it is also possible that at the time something was just wrong with my editor.
I also debugged the problem I had with the interface. In TextEdit, Word and Google Docs, the first line of your document is the first line of your document. In WordPress, it is invisibly a title, as opposed to the Classic Editor which distinguishes this with a different text entry box. This is also probably fixable.
But there are other strange errors. Like, the sidebar that let you change the properties of the post are normally present when I blog, but had disappeared when I started this post. Weirdly, not even the button to show them was present – I had to toggle several other buttons and then it appeared, just where I remembered it. Not sure what’s going on there. Since I restarted my computer recently and re-logged into WordPress, perhaps this is a “sticky” setting that went away when I cycled my browser. Still investigating.
-the Centaur
Pictured: Loki, trying to help me study generative AI.