Ekopalypse

I second what @Kered13 shared.

> I found it hard to understand, probably many others will find it the same. Who understands the topic, please comment. After clarifying these, I plan to make a PR...

@victorel-petrovich > You mentioned threads: what I get is that, for asynchronous queue, in order to process new events while the handler works, N++ uses other threads, to work concurently....

> I'm not sure if it is relevant, but is every created queue specific to the a particular handler ... From my understanding, there is a queue for synchronous and...

> I assume "beNotified" is the mechanism via which PS is registered to be notified, thus called, by N++ when events of interest to PS happen in N++. (That's enough...

> By the way, do you have an idea why my PR here to update the doc has been ignored so far (5 days ) ? How long it's normal...

Yes, we have the same/similar saying in Germany: "You have to strike while the iron is hot" :-)

To avoid corrupting existing code, a third parameter such as `curLineIfEmptySel=False` should be used instead.

@victorel-petrovich I think we all agree that no existing code should be broken when a change is introduced. So the current behavior should remain as it is. This means that...

Since this is marked as invalid, can it be closed? Providing additional icons doesn't make sense to me, since one usually chooses a particular icon to remind what a particular...