mike-lischke/vscode-antlr4 issues and pull requests

#312 - [BUGFIX] Debugger variable indexing of "Input Tokens" is wrong

Pull Request - State: closed - Opened by HerrMotz 8 days ago - 2 comments

#311 - How do I find out the embedded Antlr version?

Issue - State: open - Opened by serefarikan 19 days ago - 1 comment
Labels: question

#100 - VS Code crashes when debugging nested rules

Issue - State: closed - Opened by Husan almost 5 years ago - 1 comment
Labels: duplicate

#100 - VS Code crashes when debugging nested rules

Issue - State: closed - Opened by Husan almost 5 years ago - 1 comment
Labels: duplicate

#99 - VS Code crashes when debugging nested rules

Issue - State: closed - Opened by dspickes almost 5 years ago - 2 comments
Labels: possible bug

#99 - VS Code crashes when debugging nested rules

Issue - State: closed - Opened by dspickes almost 5 years ago - 2 comments
Labels: possible bug

#98 - Support for multiple importdirs

Issue - State: closed - Opened by rgiacomin almost 5 years ago - 1 comment
Labels: feature request

#98 - Support for multiple importdirs

Issue - State: closed - Opened by rgiacomin almost 5 years ago - 1 comment
Labels: feature request

#97 - Split grammar changes not detected during debug

Issue - State: closed - Opened by obiwanjacobi about 5 years ago - 26 comments
Labels: help wanted

#97 - Split grammar changes not detected during debug

Issue - State: closed - Opened by obiwanjacobi about 5 years ago - 26 comments
Labels: help wanted

#96 - Fix bug on issue #87

Pull Request - State: closed - Opened by mrd1996 about 5 years ago - 1 comment

#96 - Fix bug on issue #87

Pull Request - State: closed - Opened by mrd1996 about 5 years ago - 1 comment

#95 - Lexer/Parser change iterations not detected by antlr-debug parseTree configuration option

Issue - State: closed - Opened by iiian about 5 years ago - 2 comments
Labels: help wanted

#95 - Lexer/Parser change iterations not detected by antlr-debug parseTree configuration option

Issue - State: closed - Opened by iiian about 5 years ago - 2 comments
Labels: help wanted

#94 - Update grammar-debugging.md

Pull Request - State: closed - Opened by solartes about 5 years ago

#94 - Update grammar-debugging.md

Pull Request - State: closed - Opened by solartes about 5 years ago

#93 - Error while launching debug session: start rule "tune" not found

Issue - State: closed - Opened by Andis59 about 5 years ago - 1 comment

#92 - Debugging not pause at breakpoint

Issue - State: closed - Opened by thanhson208s about 5 years ago - 1 comment
Labels: duplicate

#92 - Debugging not pause at breakpoint

Issue - State: closed - Opened by thanhson208s about 5 years ago - 1 comment
Labels: duplicate

#91 - Getting call stack exceeded when running visualiser across my grammar

Issue - State: closed - Opened by michaeljquinn about 5 years ago - 6 comments
Labels: help wanted

#91 - Getting call stack exceeded when running visualiser across my grammar

Issue - State: closed - Opened by michaeljquinn about 5 years ago - 6 comments
Labels: help wanted

#90 - How can I disable or format the "Generated from" comment in antlr

Issue - State: closed - Opened by Thaina about 5 years ago - 8 comments

#90 - How can I disable or format the "Generated from" comment in antlr

Issue - State: closed - Opened by Thaina about 5 years ago - 8 comments

#89 - The file generation call should not use parameters for values that have not been given in the settings

Issue - State: closed - Opened by Thaina about 5 years ago - 7 comments
Labels: feature request

#89 - The file generation call should not use parameters for values that have not been given in the settings

Issue - State: closed - Opened by Thaina about 5 years ago - 7 comments
Labels: feature request

#88 - Debugger won't start with VSCode 1.37.0 update

Issue - State: closed - Opened by obiwanjacobi about 5 years ago - 1 comment

#88 - Debugger won't start with VSCode 1.37.0 update

Issue - State: closed - Opened by obiwanjacobi about 5 years ago - 1 comment

#87 - Omitting startrule doesn't fallback to first parser rule (when debugging)

Issue - State: closed - Opened by ronnieoverby about 5 years ago - 1 comment
Labels: possible bug

#87 - Omitting startrule doesn't fallback to first parser rule (when debugging)

Issue - State: closed - Opened by ronnieoverby about 5 years ago - 1 comment
Labels: possible bug

#86 - Is it possible to add highlighting,diagnose,completion for file using .g4 grammer?

Issue - State: closed - Opened by yafacex over 5 years ago - 5 comments
Labels: question

#86 - Is it possible to add highlighting,diagnose,completion for file using .g4 grammer?

Issue - State: closed - Opened by yafacex over 5 years ago - 5 comments
Labels: question

#85 - debugger ignores superClass option of grammars

Issue - State: closed - Opened by itgenie98 over 5 years ago - 1 comment

#85 - debugger ignores superClass option of grammars

Issue - State: closed - Opened by itgenie98 over 5 years ago - 1 comment

#84 - Debugger Visualisation dosnt work when no internet

Issue - State: closed - Opened by itgenie98 over 5 years ago - 3 comments
Labels: possible bug

#84 - Debugger Visualisation dosnt work when no internet

Issue - State: closed - Opened by itgenie98 over 5 years ago - 3 comments
Labels: possible bug

#83 - C# as output language

Issue - State: closed - Opened by zinov over 5 years ago - 5 comments
Labels: question

#83 - C# as output language

Issue - State: closed - Opened by zinov over 5 years ago - 5 comments
Labels: question

#82 - ActionFile.js example Not working

Issue - State: closed - Opened by mellester over 5 years ago - 7 comments

#82 - ActionFile.js example Not working

Issue - State: closed - Opened by mellester over 5 years ago - 7 comments

#81 - Typescript - Generation

Issue - State: closed - Opened by wagmannj over 5 years ago - 1 comment

#81 - Typescript - Generation

Issue - State: closed - Opened by wagmannj over 5 years ago - 1 comment

#80 - Debugger fails to load

Issue - State: closed - Opened by jhyry-gcpud over 5 years ago - 1 comment

#80 - Debugger fails to load

Issue - State: closed - Opened by jhyry-gcpud over 5 years ago - 1 comment

#79 - Test

Issue - State: closed - Opened by mike-lischke over 5 years ago

#79 - Test

Issue - State: closed - Opened by mike-lischke over 5 years ago

#78 - Use "CharStreams" instead of "ANTLRInputStream"

Pull Request - State: closed - Opened by WopsS over 5 years ago - 2 comments

#78 - Use "CharStreams" instead of "ANTLRInputStream"

Pull Request - State: closed - Opened by WopsS over 5 years ago - 2 comments

#77 - Extension causes high cpu load

Issue - State: closed - Opened by Naghme98 over 5 years ago - 1 comment
Labels: duplicate

#77 - Extension causes high cpu load

Issue - State: closed - Opened by Naghme98 over 5 years ago - 1 comment
Labels: duplicate

#76 - Update extension-settings.md

Pull Request - State: closed - Opened by AdhirRamjiawan over 5 years ago

#76 - Update extension-settings.md

Pull Request - State: closed - Opened by AdhirRamjiawan over 5 years ago

#75 - Extension causes high cpu load

Issue - State: closed - Opened by YangPatrick over 5 years ago - 1 comment

#74 - Debugging breakpoints are ignored

Issue - State: closed - Opened by brikken over 5 years ago - 7 comments
Labels: possible bug

#73 - Suggestion: Give a choice to choose either auto generate codes nor manually generate.

Issue - State: closed - Opened by HsunGong over 5 years ago - 2 comments

#72 - not all features available

Issue - State: closed - Opened by amryounis over 5 years ago - 2 comments

#71 - Extension architecture design questions

Issue - State: closed - Opened by cdietschrun over 5 years ago - 4 comments
Labels: help wanted

#70 - help

Issue - State: closed - Opened by maodou38 almost 6 years ago - 3 comments

#69 - How can I pass command line arguments to antlr?

Issue - State: closed - Opened by BrentRector almost 6 years ago - 2 comments
Labels: feature request

#68 - How do I find all occurences of a symbol?

Issue - State: closed - Opened by kaby76 almost 6 years ago - 2 comments
Labels: feature request

#67 - about parse tree

Issue - State: closed - Opened by maodou38 almost 6 years ago - 1 comment
Labels: help wanted

#66 - debug is random use，please help

Issue - State: closed - Opened by maodou38 almost 6 years ago - 2 comments
Labels: help wanted

#65 - Can't get debugger to work

Issue - State: closed - Opened by MishaBeek almost 6 years ago - 4 comments
Labels: help wanted

#64 - GraphViz dot

Issue - State: closed - Opened by flip111 almost 6 years ago - 6 comments
Labels: help wanted

#63 - Debug token decomposition

Issue - State: closed - Opened by Thomasb81 almost 6 years ago - 3 comments
Labels: help wanted

#62 - Add a way to collapse/expand all parse tree nodes with one click

Issue - State: open - Opened by chakpongchung almost 6 years ago - 9 comments
Labels: feature request

#61 - Error while launching debug session: start rule "Hello" not found

Issue - State: closed - Opened by kevinfay almost 6 years ago - 3 comments
Labels: help wanted

#60 - Debug adapter process has terminated unexpectedly in vscode 1.30.1

Issue - State: closed - Opened by L-Zephyr almost 6 years ago - 2 comments

#59 - Fix CodeLens positions being off by one while editing and reference count being wrong

Pull Request - State: closed - Opened by uwx almost 6 years ago - 4 comments

#58 - Formatting

Issue - State: closed - Opened by xied75 almost 6 years ago - 1 comment
Labels: feature request

#57 - Allow specifying a Java binary to run the ANTLR4 jar with

Issue - State: closed - Opened by xied75 about 6 years ago - 8 comments
Labels: feature request

#56 - Cannot read test input file ${workspaceFolder}\${command:AskForTestInput}

Issue - State: closed - Opened by RobertBaruch about 6 years ago - 1 comment
Labels: duplicate

#55 - golang: lexer generated, parser and listener missing?

Issue - State: closed - Opened by Lercher about 6 years ago - 1 comment
Labels: question

#54 - Kalyan

Issue - State: closed - Opened by kalyank23 about 6 years ago - 1 comment
Labels: help wanted

#53 - Add ability to generate tmLanguage and similar syntax highlighting files from a grammar

Issue - State: open - Opened by mike-lischke about 6 years ago - 3 comments
Labels: feature request

#52 - Parse tree rendering fails in the presence of rules matching an empty string

Issue - State: closed - Opened by MDoerner about 6 years ago - 4 comments
Labels: possible bug

#51 - Language Server Implementation fro ANTLR4

Issue - State: closed - Opened by SharkJ about 6 years ago - 1 comment

#50 - Debug broken in September VSCode Release (version 1.28)

Issue - State: closed - Opened by johnholliday about 6 years ago - 3 comments

#49 - Semantic predicates are not behaving correctly

Issue - State: closed - Opened by cprieto about 6 years ago - 1 comment

#48 - Not possible to use ${} macros in launch.json

Issue - State: closed - Opened by cprieto about 6 years ago - 6 comments
Labels: possible bug

#47 - Graphs not rendering

Issue - State: closed - Opened by brikken about 6 years ago - 8 comments
Labels: possible bug

#46 - Lexer grammar ignored + debug not working

Issue - State: closed - Opened by GabrieleFrau about 6 years ago - 4 comments
Labels: feature request

#45 - Change in Lexer Rules is not applied when debuging

Issue - State: closed - Opened by sirgru about 6 years ago - 8 comments

#44 - Extension host terminated unexpectedly.

Issue - State: closed - Opened by ishuuwag about 6 years ago - 6 comments
Labels: possible bug

#43 - Parse tree in same window as input file

Issue - State: open - Opened by johnholliday about 6 years ago - 1 comment
Labels: feature request

#42 - Add parse tree settings

Issue - State: open - Opened by johnholliday about 6 years ago
Labels: feature request

#41 - Plugin Internal Error on EOF

Issue - State: closed - Opened by blkt over 6 years ago
Labels: possible bug

#40 - Export Call Tree also with "interactive highlights" not only as static SVG

Issue - State: closed - Opened by TheGenezis over 6 years ago - 1 comment

#39 - We need a "for dummies" Quickstart Guide

Issue - State: closed - Opened by srw over 6 years ago - 2 comments
Labels: help wanted

#38 - Parse Tree Visualization not showing

Issue - State: closed - Opened by TheGenezis over 6 years ago - 6 comments
Labels: possible bug, duplicate

#37 - Debugging gets stuck with visualParseTree set to true

Issue - State: closed - Opened by Shodan79 over 6 years ago - 6 comments

#36 - "$antlr-format off" removes remaining lines in file

Issue - State: closed - Opened by StephenWeatherford over 6 years ago - 1 comment
Labels: possible bug

#35 - Debug adapter process has terminated unexpectedly

Issue - State: closed - Opened by tekord over 6 years ago - 5 comments

#34 - Issue using C#

Issue - State: closed - Opened by bnjepsen over 6 years ago - 5 comments
Labels: help wanted

#33 - How to configure language generation settings

Issue - State: closed - Opened by ChaseLewis over 6 years ago - 1 comment
Labels: help wanted

#32 - Interactive Debugger view

Issue - State: open - Opened by robertical over 6 years ago - 2 comments
Labels: feature request

#31 - Debug visualization improvements

Issue - State: open - Opened by robertical over 6 years ago - 1 comment
Labels: feature request

#30 - Debugger won't work when using 'external' mode

Issue - State: closed - Opened by littleEndianOne over 6 years ago - 2 comments
Labels: possible bug

#29 - Error while launching debug session: start rule "undefined" not found

Issue - State: closed - Opened by goldie83 over 6 years ago - 4 comments
Labels: possible bug

#28 - ATN graph cannot be drawn even after code generation.

Issue - State: closed - Opened by smwikipedia over 6 years ago - 21 comments
Labels: possible bug

#27 - How to configure the output folder of generated parser code?

Issue - State: closed - Opened by smwikipedia over 6 years ago - 1 comment
Labels: help wanted

GitHub / mike-lischke/vscode-antlr4 issues and pull requests