language-systemverilog package - add a word to the language

[stefaniecg]

I use the following package https://web.pulsar-edit.dev/packages/language-systemverilog
but it is missing one word: coverpoint
How can i add it so that it is shown colored in the syntax?

Thank you for the help you can provide.

[savetheclocktower]

It looks like coverpoint ought to be colored like a keyword — but for you it's just showing up as plain text? Can you give some sample code that produces a situation in which coverpoint is not being highlighted?

[savetheclocktower]

OK, just pushed a new package: https://web.pulsar-edit.dev/packages/pulsar-language-systemverilog

Disable your existing language-verilog package, then install this one and let me know how it goes.

[stefaniecg]

Thank you 🙂, I"ll give it a try.

[savetheclocktower]

@stefaniecg, how'd this work out for you?

[stefaniecg]

@savetheclocktower, hi thank you for reaching out.

Couple feedback:

1. The package works in the Pulsar of my MacOS machine, but does not work in the Pulsar of my Linux machine.
2. the basic keyword "var" ist not recognized as a language reserved word, i.e. not colored. eg. var int mylar; It should be colored in the same way or level as parameter int myparam; which is the opposite of var
3. parameters passed with hash # to a module instantiation in the form of module_type #(.const_var(3)) my module(); are not highlighted, but only shown in black.

Cuz i disabled the package in my Linux machine, where i mostly work, this is the only feedback that i have so far. :)
Perhaps i'll have more feedback once i use it in my Linux machine.

Thank you so much for taking a look at this and for taking this feedback into consideration. :)

[savetheclocktower]

Oof, that's interesting. I don't have an immediate theory for why it would be working on macOS but not Linux.

A few thoughts:

1. Double-check that your existing language-verilog package is disabled (or not installed) on Linux. Then re-enable pulsar-system-verilog and do a basic sanity check by opening a SystemVerilog file.

2. In what way does it fail to work? Does a SystemVerilog file render as plain text? Does the grammar itself not appear in the grammar selector? When you've got a SystemVerilog file open, do you see the text “SystemVerilog” anywhere in the status bar along the bottom of your window?

3. With pulsar-system-verilog installed and enabled on your Linux machine, open a SystemVerilog file, place the cursor anywhere in the document, then execute the Editor: Log Cursor Scope command via the command palette. A notification will appear in the corner; screenshot it and show me what it looks like. It should be something like this:

   

   The rest of the list may vary, but the top line should say source.systemverilog.

4. Let's make sure it offers you the right grammar. Go to Settings -> Packages -> search for grammar-selector -> click on Settings. Make sure “Hide Duplicate Grammars” is unchecked. Then open a SystemVerilog file. Look for the place in your status bar at the bottom of the window where it says “SystemVerilog,” then click on it (or run Grammar Selector: Show from the command palette). Type system in the palette and make sure you have at least one grammar listed:

   

   If it doesn't look anything like that, take a screenshot of it and add it to this issue so I can figure out what's happening.

   If you do see a SystemVerilog option in the palette and it isn't already selected, go ahead and click on it and see if that makes any difference.

The var issue is easy to fix, so I'll push that update.

As for the parameter assignment example, here's how it looks on my machine with the One Dark syntax theme. The old language-systemverilog is on the left, and the new pulsar-language-systemverilog is on the right:

You said it looks black, so it sounds like you're using a light syntax theme. So here's how it looks in One Light:

Yeah, more of the text is black than it should be, so it sounds like this is the theme you're using. If you're expecting the const_var token to be red like other variables, that's actually a quirk of One Light. It colors most variables red, but it colors parameters black, for some reason. In most other themes, const_var would show up like a variable.

You can override that weird behavior by putting this in your user stylesheet:

@import "syntax-variables";

.syntax--variable.syntax--parameter {
  color: @syntax-color-variable;
}

Save the file after you make that change and parameters should instantly turn red.

Thanks for the feedback in the first place; the new systems we've added to Pulsar since the Atom days make it easier to bootstrap small language packages like these, so I'm eager to ship as many of these as possible and increase the number of languages that are supported well. Hopefully we can get it working just as well for you on Linux as it does on macOS.