Lazarus Ctrl Space jumping to uses section

[marcioarp]

In Lazarus, Ctrl + Space should show the code complement, but in my case, sometimes it jumps to use sections. How can I stop this jump and force always show these complements?

[Martin_fr]

The jump happens if codetool cannot parse the source. It jumps to where the source is unparsable. The message window should give more info.

You can go back with Alt-H.

You can switch off the jump: Tools > Options > Codetools > Identifier Completion: "Jump to error"

But even if it does not jump, it may not be able to show you the completion list. You still need to look at what it says in the messages window.

[gii]

The jump happens if codetool cannot parse the source. It jumps to where the source is unparsable. The message window should give more info.

You can go back with Alt-H.

You can switch off the jump: Tools > Options > Codetools > Identifier Completion: "Jump to error"

But even if it does not jump, it may not be able to show you the completion list. You still need to look at what it says in the messages window.

I also suffer from this problem.

This problem did not occur in version 1.8

The code is compiled and executed normally, but Ctrl + Space does not work.

Every time this happens, I have to restart the IDE.

In the console the following message is displayed (message in PT/BR).

"Error: Final do fonte não encontrado."

@edit

When I try to access an event through the Object inspector, the following error is displayed:

"Incapaz de exibir método. Favor corrigir o erro mostrado na janela de mensagens, que se localiza normalmente abaixo do editor de código."

@edit2

Another problem I see is a "duplication of methods".

When I press Ctrl + Shift + C (sometimes automatically) the editor creates the methods again.

I can not simulate this problem intentionally. But it occurs several times a day. It's very annoying.

[macfly]

Hi,

This error often occurs to me.

In addition to this other: "end of source not found"

They occur when there is no uses in implementation section.

Should be something related to code parsing.

One workaround is to create a empty class just to place a uses in implementation.

Code: [Select]

unit myunit;

interface

uses
 blabla;

implementation

uses  <--- Without this uses then editor get lost
 my_dummy_unit;