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
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
In the Build Commands dialog there are additional commands under `Conf commands`, `Independent commands` and `Execute commands` that are not available to setup in Preferences|Keybindings. It would be very useful to be able to set keybindings for these. Further to this the command names in Build commands can be modified but this is not reflected in Keybindings preferences.
Just a quick thought too; a button linking to the keybindings prefecences would be a helpful addition to the Build commands dialog.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/705
I was using [`git-new-workdir`](http://nuclearsquid.com/writings/git-new-workdir/) and recently switched to using the newer form [`git worktree`](https://github.com/blog/2042-git-2-5-including-multiple-worktree… however found this stops the plugin working.
The reason appears to be that instead of a `.git` directory in the 'worktee directory' there is a `.git` file that contains a reference to the original directory. e.g. `gitdir: /home/ubuntu/origdir.git/.git/worktrees/newdir.git`.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/285
Geany is an excellent tool but gdb support unfortunately does not support cross-debugging, which is a rapidly growing need. I certainly don't want to be forced to use some ugly mastodent like eclipse just for that.
This patch is very short, so it seems that there is little functionality missing to achieve this. Would it be possible to integrate something like this into geany-plugins?
http://faumarz.blogspot.fr/2014/03/gdb-and-geany-ide-remote-cross-debugging…
Thanks.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/303
Bash allows more characters besides `[[:alnum:]_]` when declaring
function names using the `function` keyword. It also does not require
having a pair of parentheses after the name. Some shells may actually
implement it differently but we don't have to be that strict since the
user explicitly specifies the `function` keyword anyway.
This update implements the ones described above, and also invalidates
function names that are completely made up of digits.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/662
-- Commit Summary --
* Enhance detection of sh functions
-- File Changes --
M tagmanager/ctags/sh.c (125)
-- Patch Links --
https://github.com/geany/geany/pull/662.patchhttps://github.com/geany/geany/pull/662.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/662
Hello, I have a very simple request for Geany which I use heavily.
On my system I frequently view the output of commands the following way:
$ ls -l | nano -
here, nano reads standard input as a new unsaved file, making it easy to quickly access ls command output.
I would love to be able to do the same with geany:
$ ls -l | geany -
In other words, instead of a file, having standard input read as a new unsaved file (which would open either as new window or new tab depending on user's settings, but this is of no concern to me).
Thank you
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/780
I am really enjoying using Geany and congratulate you on its richness of functions but there is one thing that makes me curse:
I have to close the "find" pop-up dialog each time that I select a new area of text to find and then re-open it by clicking "find" or ctrl-f.
I have been used to using TexPad which re-writes the new find text each time without having to close the pop-up.
Thank you for your great efforts.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/758
For example `10.5`. Some other editors accept that value.
Thanks :-)
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/703
){kind=link}