Dmytro Maluka

> Is it worth documenting this there, just for faster realization? At the moment I'm inclined to think it's better to leave this without documenting, this is of too little...

> Why exactly was it named `SpawnMultiCursorUpN()` Just because we also have `UpN()`. > > I tried it with `MouseMultiCursor` too, but this does respect the visual lines only and...

> I understand, just because of the consistency. Well, then we go again with this ugly name. I don't find it particularly ugly. It is "move N lines up", where...

`MouseMultiCursor` just spawns a cursor wherever you click with the mouse, without any relation of to the previous cursor's position, right? So what does `MouseMultiCursor` have to do with anything...

Now I'm inclined to think that adding such options would be a good improvement (although I still think it would good to implement what I suggested in https://github.com/zyedidia/micro/pull/3385#issuecomment-2229630375; but that...

And another thought: maybe we should go ahead and make it the _default_ behavior? Or maybe not just yet, but at least eventually? So it seems that instead of `locksettings`...

> I think only a minority of the users would care about the settings and bindings to be formatted/commented, and I reckon the user would normally expect the `set` and...

> `SetGlobalOption()` / `SetGlobalOptionNative()` on the other hand is a bit tricky since there are plugins that do use it unfortunately. I personally think we should just treat it as...

> Hi @dmaluka @Neko-Box-Coder ! any chance this would be merged? I guess not. If we merge it, we are stuck with these `lock*` options forever, whereas as we discussed...

Ok, I see @Neko-Box-Coder just pushed an updated version. But it doesn't make a lot of sense to me.