Jordan McConnon

> try putting both of those sections in a single `lua > ```lua > lua local nvimlspconfig = require('lspconfig') > local configs = require('lspconfig/configs') > local util = require('lspconfig/util') >...

@wsnyder I'm currently working on this, just as a heads-up. I've made some progress (the test design here, and all 3 example designs given in #4879 are now giving the...

I have every one of the force variables being recognized as unpacked variables now (turns out only the m_enVarp was being treated as a non array). However I am having...

So far I have this working for flat (i.e. non-nested) unpacked arrays for force & release. TODO: Work for arbitrarily structured unpacked arrays Tidy-up code (it is very ugly atm)...

if you check ./docs/guide/exe_verilator.exe, there is a command option `--no-unlimited-stack` which stops verilator from trying to run `ulimit -s unlimited` as it appears that your error is caused by this...

The error isn't too descriptive but my guess is that the `ulimit -s unlimited` command verilator is trying to run is required for you to run verilator for this particular...

To workaround this issue, generate a `.svg` via the wavedrom editor and open said `.svg` of your schematic inside of the `inkscape` program. You will notice that the full long...