gojimmypi

Results 99 issues of gojimmypi

although initially working, somehow this got lost: ![image](https://user-images.githubusercontent.com/13059545/80313168-1f6c5f80-879e-11ea-8d07-8c6e696ac307.png) see [Intellisense/VerilogQuickInfoSource.cs line 203](https://github.com/gojimmypi/VerilogLanguageExtension/blob/057249c9a33ca0b37be6001d51dc68c3d4d27150/Intellisense/VerilogQuickInfoSource.cs#L203)

current logic does not properly distinguish comment chars: `//` and `/*` and `*/` from division and multiplication operators as noted in #10. Workaround: pad with spaces. see [VerilogHelperFunctions.cs : IsDelimiter()](https://github.com/gojimmypi/VerilogLanguageExtension/blob/19b3ee1c7eaa582eaf06b5161d96896339d81854/Globals/VerilogHelperFunctions.cs#L44)

for example, the second line here should have the `ctr_width` declaration as hover text: value `ctr_width = 24`: ``` localparam ctr_width = 24; localparam ctr_max = 2**ctr_width - 1; ```

for example [picorv32.v line 433](https://github.com/gojimmypi/VerilogLanguageExtension/blob/master/TestFiles/picorv32.v.txt#L433) ![image](https://user-images.githubusercontent.com/13059545/71663411-677df700-2d55-11ea-945f-4b802125482b.png)

should not need to press any keys at initial file load time to force redraw for proper highlighting

per review: Need to add support for: ``` wire signed yxz; ``` xyz ends up not being recognized as a wire. It's the "signed" keyword that confuses it.

declarations inside of one module are note properly scoped for hover text definitions where there is more than one module defined in a given file with the same-named variable. For...

# Description This PR polishes https://github.com/wolfSSL/wolfssl/pull/7528 after feedback from @bandi13 and updates: - README files for each of the PlatformIO directories updated. - Publishing Instructions moved to `scripts` - Added...

# Description Corrects the message in `src/ssl_load.c` to indicate the proper name of the file. Fixes zd# n/a # Testing How did you test? Briefly tested in my Espressif wolfTPM...

# Description Applies only to ESP8266 `make` builds. Adds clarification in `wolfssl_client` example for Espressif ESP8266 builds on how the `WOLFSSL_ROOT` value should be used (relative, not absolute), in both...