Ctrl-Enter not working properly into the code editor of Lazarus ("uses" clause)
Original Reporter info from Mantis: ChrisF
-
Reporter name:
Original Reporter info from Mantis: ChrisF
- Reporter name:
Description:
Inside the code editor of Lazarus, the Ctrl-Enter feature (i.e. open/switch to the corresponding unit at the cursor position into the "uses" clause) doesn't work when a &LtPos;tab> character (i.e. ASCII character = 009) is immediately preceding the name of concerned unit.
Steps to reproduce:
-Start a new project with Lazarus/FPC.
-Add this line into the "implementation" section of the form unit code (i.e. unit1.pas), replacing the following "&LtPos;tab>" string with a real tab character:
uses&LtPos;tab>SysUtils;
-click on "SysUtils" to position the cursor on this unit and press Ctrl-Enter (i.e. Control + Enter keys) to open this unit into the code editor,
-nothing appears (i.e. the "SysUtils" unit is not displayed).
Additional information:
1/ When any other valid characters (e.g. &LtPos;space> or comma character) is immediately preceding the name of the unit, it's OK.
Working samples (replace the &LtPos;space> and &LtPos;tab> strings with "real" space and "real" tab characters);
uses&LtPos;space>SysUtils;
uses&LtPos;tab>&LtPos;space>SysUtils;
uses&LtPos;space>MyUnit,SysUtils;
uses&LtPos;space>MyUnit,&LtPos;space>SysUtils;
Non working samples:
uses&LtPos;tab>SysUtils;
uses&LtPos;space>&LtPos;tab>SysUtils;
uses&LtPos;space>MyUnit,&LtPos;tab>SysUtils;
2/ This is of course exactly the same problem for a user's unit (i.e. not only for system units coming with Lazarus/FPC). For instance, another non working sample:
uses&LtPos;tab>MyUnit;