[Lazarus] How to enable Kylix 3 language help inside Lazarus IDE

[Graeme Geldenhuys]

Jürgen Hestermann wrote:
>>> And even much better than in Delphi (at least in Version 7, where 
>>> persistent blocks are used as search default - when existing - which 
>>> is realy annoying).
>> Are you sore? I think Lazarus does too. But persistent or not, 
>> Lazarus only uses "one line" blocks as default. So any multi-line 
>> block is always ignored
>
> Yes, I see it now. I only tested it with multiline blocks. But I find 
> that behaviour a bit illogical. Why should the search dialog suddenly 
> use the block as default (instead of the text at cursor) only because 
> it consists of one line only? That makes no sense. I would want to use 
> the text at cursor in *all* cases (independent from persistent blocks) 
> because I may not even be aware that a block is still active. This way 
> I have to think about this side effect whenever I use the search 
> function.
I don't disagree.
I just pointed out, that nothing changed. For non persistent blocks, it 
was ok to use the block, and since you usually not search for multi line 
strings it was ok to limit it to one line blocks.

For persistent, I would actually think the past was to limit it to 
one-line blocks, but only if the cursor is IN or AT the block

>> The other thing you may find about the 2 block points is that  some 
>> IDE/Editor actions may change them (even is the block is shown => it 
>> would hide it). The reason is that a lot of IDE stuff (like 
>> codetools) used the selection to modify the text (this would work, 
>> that a new selection would be set, replaced, and cleared). All this 
>> had to be changed. I did so, for the stuff I found. If I missed 
>> anything, I only need to know what.
>
> There seems to be 2 other code tools functions that change the 
> persistent block: Jump to BEGIN or END. Afterwards the persistent 
> block no longer exists and cannot be recovered with Ctrl+K,H nor can I 
> jump to its former location with Ctrl+Q,B or Ctrl+Q,K.
>
Will look at later.