Describe the bug
Path highlighting is not configured right, causing paths to appere as sections in directives such ad incdir

  incdir ../modules ;Relative path
  incdir ./modules ;Same folder path
  incdir modules ;Legal syntax for compiler 

Self-test report
Path has following properties

1. entity.name.section
2. source.asm

dots and slashes has:

1. source.asm

Does this behaviour appear in a specific case or in the whole script? Everywhere though not applicable in many places

Screenshots or minimal (broken)working example

Hello,

I'm running VSCode 1.65.2 under Zorin Core Linux 16.0. I've installed the extension and restarted VSCode. When I open an existing .asm file that I wrote to compile with vasm oldstyle, nothing is highlighted.

Here's a stupidly simple .asm file that compiles fine under vasm oldstyle:

    org $8000

start:
    lda #$FF
    sta $6003
    sta $6001

loop:
    jmp loop:

    org $FFFE
    word start

When I open that file, nothing is highlighted.

Is there something I should be doing to get the highlighting?

Thank you,
Rick

Many themes do not support highlighting the scopes introduced, although #5 improved upon this, most themes highlight <50% of the code.

Describe the solution you'd like
Create a list of scopes covered by themes on a general basis, and apply them accordingly.

Describe alternatives you've considered
Currently, the included theme solves this issue, but it is annoying to manually change the theme when changing between projects/files - this will also be improved upon with the above-mentioned solution.

Get feedback and autocomplete when coding

Describe the solution you'd like
Implement VSCodes semantic api