Cronos87

I did my best to enhance it and to be more flexible. Feedback is very welcome 🙏

> Perhaps this makes sense not only for doc comments, but for regular ones too. Kate has interesting behavior: > > 1. Enter copies the indentation of the previous line....

> Regarding the Kate-like behavior, I agree that it's too much and requires a separate proposal. But I think it would be reasonable to discuss extending the feature to regular...

It seems like opinions are divided regarding expanding this behavior to regular comments. Originally, my idea was to reproduce the VSCode behavior that I used for years, and I always...

Many thanks for the clarification @RedMser, that's really helped me understand the workflow better! 🙏 The clues you gave me are really useful for enhancing my understanding. Signal seems to...

I'm quite happy with the new implementation; it seems much better and more flexible. However, I still need to implement the case with a delimiter like `/** */`, where the...

> It looks like you edited the documentation XML by hand Yeah, haha, you got me! I didn't know about it! It will help me because every time I break...

~TODO: Using complex operations without adding comments generates an error. Need to be sure a doc comment will be added.~ EDIT: Fixed in the last commit. ``` tx->begin_complex_operation(); tx->begin_multicaret_edit(); ```

Every features I wanted to implement are now pushed, and it works with C# delimiters. I still need clarification about the file `core/object/script_language_extension.h`. I don't know if I did it...

I give it a try using callbacks instead of a signal. Please be aware that this is my first step in the C++ world; it might not be perfect, and...