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:
![image](https://cloud.githubusercontent.com/assets/14856598/10121213/521dc426-64af-11e5-8c40-bc47d504da8d.png)
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:
![image](https://cloud.githubusercontent.com/assets/14856598/10121233/11c50b7c-64b0-11e5-9680-b3421e7c5bea.png)
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
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
This is running under Sway, testing with Wayland native apps only (no xwayland).
When I first open a file in Geany, I can copy out of Geany and paste into another program by selecting and then middle clicking in the usual way. I can do that multiple times with different selections. If I then select something ("foo" for example) in the other program, I can middle click paste it into Geany. I can do this with multiple selections as well. All OK so far.
At this point if I select something in Geany ("bar" for example), I can no longer middle click paste it outside of Geany. I just get "foo" instead, even if I make sure to unselect "foo" in the other app before selecting "bar" in Geany. Middle click copy/paste within Geany works fine still. It also works fine within and between non-Geany applications. It is as if Geany is now using a different primary buffer than everything else.
Opening a new file in Geany (or closing and reopening an existing one) gets things working again temporarily.
I've tested this with Geany 1.36 and also the latest Master branch. I also tried applying the patch from here, but saw no difference: https://sourceforge.net/p/scintilla/bugs/2127/
I have mainly been using kitty (0.18.3) and firefox (78.3.0 esr) as the other applications. Sway is version 1.5-3. This is on Debian Bullseye. I also briefly tried to check if SciTe exhibits the same behavior, but middle click copy paste did not work at all there (at least to other programs, not sure if it worked within SciTe).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2629
Created a project. Added a header and source file. Closed project. Always have to re add source files after closing project.
Was wondering if this is normal or a problem with my computer.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3212
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3212(a)github.com>
Github actions can do Linux (Ubuntu 16.04, 18.04 and 20.04) and windows and OSX Catalina and Big Sur so testing could check all platforms.
This is a placeholder issue, not sure what is _actually_ involved, but somebody who knows might replace this with a checklist.
PS IIUC github actions can run docker so the @eht16 one could be used maybe?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2671