Skip to content

Commit 2dee6c6

Browse files
authored
Remove TL-Verilog Editor Modes (#275)
Steve says this project is mostly complete
1 parent 1f56630 commit 2dee6c6

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

content/gsoc/gsoc26-ideas.md

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -49,24 +49,6 @@ or around the cursor would be extra useful.
4949

5050
*Languages/Tools:* Rust. Familiarity with hardware design is helpful to have some context of what the tool is used for is helpful, but the project itself is pure software. Some familiarity with egui is also helpful though certainly not required.
5151

52-
53-
### TL-Verilog Editor Modes
54-
55-
*Details:* TL-Verilog has support in various editors, including VSCode, GitHub, and CodeMirror (used by Makerchip). But all three could use a refresh and improvements. Grammar improvements are needed in TextMate (currently used by VSCode and GitHub), and Tree-sitter support is desired for future use in GitHub and CodeMirror.
56-
57-
175-hr or 350-hr projects are possible. A 175-hr project could focus on improving the existing GitHub TL-Verilog mode (which is rather broken). A 350-hr project might focus on a new grammar. A long project might also add support for the macro-preprocessor used by TL-Verilog (M5) or for JavaScript embedded in TL-Verilog.
58-
59-
*Skill level:* Medium
60-
61-
*Language/Tools:* JavaScript
62-
63-
*Duration:* 175 or 350 hrs
64-
65-
*Repo:* https://github.com/github-linguist/linguist/pull/5331/files
66-
67-
*Mentor:* [Steve Hoover](mailto:steve.hoover@redwoodeda.com)
68-
69-
7052
### cocotb v2 Code Migration Helper
7153

7254
The upcoming cocotb v2.x release will have quite some breaking changes (see https://docs.cocotb.org/en/latest/release_notes.html), so users and extension developers will have to actively migrate existing code.

0 commit comments

Comments
 (0)