"Upgraded" from Geany 1.33, now Geany isn't able to access or use mapped network drives in the slightest..
The drives don't appear in Geany's open guide, even though everything else can access it.
If you can give me some troubleshooting things to do, I can get you data to help solve it.
Thanks!
--
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/2794
Currently there are 30+ "programming languages", 20+ "scripting languages", 9 "markup languages" and some "Misc" languages.
The first two categories are so big the menu (Document->Set Filetype->) won't fit on screen (at least with a laptop).
Especially the first should be broken up. This is a call for suggestions of how that should be done.
Otherwise I will make a pull request breaking them up in a reasonable but somewhat arbitary way, rough popularity measure and degree of support. :grin:
--
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/2087
Hi !
on the attached (sorry, I cannot attach PHP file) PHP file, at line 1583,
I have the following code (started before by /*, and finishing after by */) :
` * V...|.......................Jour courant..................................>|<...................................Lendemain.................................................>|`
When I write the "<" character, on this line 1583, Geany closes.
In /var/log/syslog there is :
Mar 30 12:58:29 PRINCIPAL kernel: [ 2151.269486] geany[12005]: segfault at 0 ip 00007f1b1a5cf9de sp 00007ffe7d451aa8 error 4 in libc-2.23.so[7f1b1a531000+1bf000]
Mar 30 13:05:45 PRINCIPAL kernel: [ 2586.680237] geany[13373]: segfault at 0 ip 00007fd0b0b929de sp 00007fffe225d0b8 error 4 in libc-2.23.so[7fd0b0af4000+1bf000]
Mar 30 13:08:16 PRINCIPAL kernel: [ 2737.718143] geany[13586]: segfault at 0 ip 00007fd4ff5ae9de sp 00007ffcc369f738 error 4 in libc-2.23.so[7fd4ff510000+1bf000]
and more ...
On this line 1583, " * V...|.......................Jour courant.....".
I removed the first "<", before the words "Jour courant", just after the first "|" character, and I cannot write it back, because Geany closes each time I trie.
Original was : "V...|**<**.......................Jour courant....."."
If I clic before the second "<" (do not look for the first one, it does not exist anymore), before the word "Lendemain", nothing happen.
If I clic after the second "<" (do not look for the first one, it does not exist anymore), Geany closes.
If I clic after the last ">" Geany does not close.
Let me know if you want my PHP file.
Thank you for looking about it ...
Nils
--
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/1455
Would it be possible to have an option either in the preferences or in the build menu to execute the lint command periodically ?
---
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/1032
```
template <typename T> using Uptr = std::unique_ptr<T>;
```
Does not recognise Uptr as a typename;
---
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/975
I'm a keyboard user with carpal tunnel. When I search for a string, half the time it's going to be above the cursor in the file. Unfortunately, the default option in the Question dialog is "Cancel":
I think a more useful default would be to Find again. If I want to Cancel, I'll press Esc. If I want to find again, I have to press two keystrokes (Alt+F, or Right Arrow then Enter). I know one extra keystroke is not much, but they add up.
Any thoughts on making `Find` the default?
--
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/1192
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
![src="https://user-images.githubusercontent.com/2157285/140661024-3df31…](http://src="https://user-images.githubusercontent.com/2157285/140661024-3df31d57-b8c0-486f-aa9c-d87ff8c0532f.png%22%3E){kind=link}
![src="https://user-images.githubusercontent.com/2157285/140660989-7f779…](http://src="https://user-images.githubusercontent.com/2157285/140660989-7f77901c-3f45-4ca1-a475-2c73d453a084.png%22%3E){kind=link}
![src="https://user-images.githubusercontent.com/2157285/140661000-748a0…](http://src="https://user-images.githubusercontent.com/2157285/140661000-748a08c8-246f-4fe7-a6be-b5efae10ba47.png%22%3E){kind=link}
![src="https://user-images.githubusercontent.com/2157285/140661031-4904f…](http://src="https://user-images.githubusercontent.com/2157285/140661031-4904f174-a6b5-42dc-8447-be71d03edfc7.png%22%3E){kind=link}