[VSCodeCounter] There was no target file.

[uctakeoff]

[VSCodeCounter] There was no target file.

[APerricone]

looks the problem is that in my extension did define the extension without the dot.

I added the dot in the last commit APerricone/harbourCodeExtension@d306520

[uctakeoff]

VSCodeCounter itself has no language parsing function.

https://marketplace.visualstudio.com/items?itemName=ekon.harbour

I confirmed that it works by installing the above extension.

[JoseluisSanchez]

I'm using this extension for Harbour
https://github.com/APerricone/harbourCodeExtension
I'll try doing a clean installation of VSCode to see if it works.
Regards,

[JoseluisSanchez]

I have make the extension work in one of my computers at work, but at home in my laptop it doesn't work. When I run the extension, the file generates this content:

Date : 2019-11-18 17:08:41
Directory : c:\alanit\develop\fester\prg
Total : 0 files, 0 codes, 0 comments, 0 blanks, all 0 lines

Languages
+----------+------------+------------+------------+------------+------------+
| language | files | code | comment | blank | total |
+----------+------------+------------+------------+------------+------------+
+----------+------------+------------+------------+------------+------------+

Directories
+--------------------------------------------------------------+------------+------------+------------+------------+------------+
| path | files | code | comment | blank | total |
+--------------------------------------------------------------+------------+------------+------------+------------+------------+
+--------------------------------------------------------------+------------+------------+------------+------------+------------+

Files
+--------------------------------------------------------------+----------+------------+------------+------------+------------+
| filename | language | code | comment | blank | total |
+--------------------------------------------------------------+----------+------------+------------+------------+------------+
| c:\alanit\develop\fester\prg\Alanit\TRecordBiel.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\TRecordBiel2.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\main.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\tInforme.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\tfsdi.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\trecord.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\ut_brw.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\ut_calend.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\ut_common.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\ut_dbf.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\ut_index.prg | (Unsupported) | -1 | 0 | 0 | -1 |
| c:\alanit\develop\fester\prg\Alanit\ut_index.prg.bak | (Unsupported) | -1 | 0 | 0 | -1 |
...
How can I do for support Harbour files in your extension ?

Regards,
José Luis

[uctakeoff]

The difference is whether the Ignore Unsupported File option is ON or OFF.

VSCodeCounter refers to the language extension table inside VSCode.
Have you tried the Harbor extension?

[JoseluisSanchez]

I've tried your extensión in 3 computers, in one of them it works but in the others doesn't. All they have installed harbourCodeExtension.
Where can I find the language extension table inside VSCode ?
Regards,

[uctakeoff]

It seems that the setting may not be reflected unless it is restarted.
If not try it.

According to the debug log of the program, the grammar configuration file of the harbor file referenced the following file:

{home dir}\.vscode\extensions\aperricone.harbour-0.9.5\syntaxes\language-configuration.json
(Windows10)

please make sure.

[uctakeoff]

I did was find the cause just now too.
I hope this solves the problem.

[JoseluisSanchez]

Thanks to both for your kind support, I'll try later but I'm sure that now the extensión will work fine.

Regards,

[APerricone]

Anyway the result can be incorrect, harbour is a strange language:
The comment starts with // or with && (rarely used i think)
If the line starts with asterisk or the word "note" this line is a comment, unless the line before ends with a semicolon, in this case is the continuous of previous line.
As plus, you can include C source code inside the pragma dump...
So, it is a mess.

Theoretically my or your extension can export an method to manage this extreme case, see https://code.visualstudio.com/api/references/vscode-api#extensions

If the other extension is not installed it returns undefined.

[legenddcr]

I also encountered this issue. It is better if the dependency issue could be resolved by extension.