cutelisp

> I can't see why. Adding/removing a tab is triggered by a mouse click (even if it's a double click), not by a mouse move, so it doesn't depend on...

It's not clear to me what is the best behavior for deleting on middle click perhaps someone can give their opinion. If a tab contains only unmodified buffers, the behavior...

>the last option (a single prompt, all or nothing) seems the most attractive Right, I was leaned towards that option too

As discussed above added new tab bar features: **add**, **delete** & **drag**. Made separated commits for review process.

Seems a great addition but looks odd on a non read-only buffers, I wonder if we could make it a `common option` strictly for read-only buffers. So the user have...

> Being able to change the setting individually for each buffer means you can still have the cursor visible in some read-only buffers (so you can eg. select some text...

Nice POV, perhaps the call is to make possible for plugins to hide buffer's cursor as you suggested. > > [...] could be better provide a more direct programmatic way...

From what I can see: no. `fastdirty` seems to be hardcoded to be enabled when the file size exceeds a constant (50KB). Maybe we could turn this into an option...

> i.e. doesn't check if the undo stack isn't empty when checking if the buffer is modified or not. Is that enough? Since I can add a char and delete...

I was just pointing out that, with this approach, Micro can flag a buffer as modified even if its content hasn’t changed. In fact, you already wondered about this :https://github.com/zyedidia/micro/pull/3430#issuecomment-2295343252