argothiel wrote: > fact is that it is still default behaviour in for example vscode
@timon-ul I think that's the backward compatibility lock-in. Given the `replace` mode is new and usually implemented after the `insert` mode, the editor developers don't want to surprise users with a change of behavior. I have the same issue with Neovim now. I want to implement the `replace` mode in Neovim and I would gladly change the default to `replace` when implemented, but I don't think that's warranted. Changing the mode could be a breaking change for some users, so probably `insert` will remain the default there too, just like it is in VS Code. https://github.com/llvm/llvm-project/pull/197249 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
