For a verilog file, the variables list parses the old (1995) style verilog module declarations. Verilog 2001 enhanced the syntax and seems to confuse Geany....
1995 syntax:
module (foo, bar, buz);
input foo; // foo port
output bar; // bar port
output buz; // buz port
reg buz; // buz variable
2001 syntax:
module (
input wire foo, // foo port is a wire
output wire bar, // bar port is a wire
output reg buz // buz port is a variable
);
// note: the "wire" is optional and the ports could have been declared with or without
Geany variables list seems to get confused by the 2001 style. It seems to parse the wire keyword as the variable name if I keep the optional "wire" keyword:
If I omit the "wire" keyword, Geany still gets confused, but in a different way. It seems to parse every other variable and then parse the "input" or "output" keywords as variables in some cases:
If someone who knows the code base can even point me to the module(s) doing the parsing for the variables, I may be able to help create the fix/enhancement for this. I'd be happy to try anyway. I am not familiar with the Geany code base so just getting started seems like an insurmountable task.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/670
SystemVerilog is almost identical syntax to Verilog. It could be quite easy to support SystemVerilog filetype (.sv) using same rules as Verilog which is already implemented.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3511
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3511(a)github.com>
I am looking for some kind of "Console View" like it is available for example in Eclipse.
Currently a terminal / shell opens when executing a script in Geany. In this shell one can see the process streams stdout and stderr and can write to stdin of the new process.
However, I would rather eliminate this new terminal window popping up and changing focus each time I launch a script in Geany.
I think it is better to have the process communication (stdout, stdin, stderr) embedded in a view within Geany like it is done in many IDEs. The different streams could be colored e.g. stderr in red and stdin (input from the user) in green.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/675
Hello!
Can Dart be supported in geany
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3313
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3313(a)github.com>
this PR is adding the ctags for FORTH. It's very simple, it only detects the ":" for the beginning of a word:
Possible improvements:
- it could write "words" instead of "section" in the symbol list
- it could only parse the first word after the ":", and not the eventual code after it
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3377
-- Commit Summary --
* adding forth ctags
* adding forth.c for ctags
-- File Changes --
M ctags/Makefile.am (1)
M ctags/main/parsers_p.h (1)
A ctags/parsers/forth.c (78)
M src/filetypes.c (2)
M src/tagmanager/tm_parser.c (6)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/3377.patchhttps://github.com/geany/geany/pull/3377.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3377
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3377(a)github.com>