Hi,
At the moment Linux users are essentially left to wait until their respective distribution's repositories are updated and the new release of Geany is added. This process is so tedious, however, that for most non-bleeding edge distributions one has to wait months or years for this to happen (by which time usually an even newer release of Geany is out). So what I propose is that you's provide your own AppImages for Geany. AppImages, for those of you that are unaware, are a type of cross-distribution packaging format that need no special tools (like no special package manager to manage the packages) in order to be run. They merely need to be marked executable (with `chmod +x`) and run (with `./<AppImage>` where `<AppImage>` is the AppImage's filename, including its file extension). They are essentially self-mounting image files with an internal file system that contains all the files required to run the program they provide (which in this case would be Geany, of course).
I have created my own AppImage for Geany (which you can find [here](https://bintray.com/fusion809/AppImages/Geany#files)) but as you might notice it is presently out of date (version 1.28, versus the latest release of 1.29) as the Debian packages (and no this does not mean that this AppImage will only run on Debian systems, it will run on Arch Linux, Fedora, Gentoo, openSUSE, etc. as well) I built it from are presently out-of-date (although no doubt they will be updated soon). Plus my AppImage is built using Debian (Jessie) ingredients so it doesn't work on systems older than Jessie, while it is possible that you's could create a more flexible AppImage. You's could use your Travis CI artefacts instead of the Debian packages I use to build the AppImage, hence providing the very latest (more up-to-date than I could ever hope to provide) build of Geany. The way I uploaded my Geany AppImage to Bintray is using Travis CI, so they both easily integrated with one another. Alternatively you could upload the AppImages to the releases page of this GitHub repository.
If you need help with this I am more than willing to help, although I do believe @probonopd will be far more helpful than I, due to his superior knowledge of AppImages (after all he is the one that created the format).
Thanks for your time,
Brenton
--
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/1303
If a variable name ends with "type", the symbol parser recognizes a symbol which does not exist. As an example, see the following code below:
> procedure plot_labels(iy,iy2: stipint; labtype: stipint);
const
c_marker_type=1;
var
locdbg: boolean;
{actual code}
end;
Which creates two functions: plot_labels (correct) and 1 (this is incorrect). See screenshot below:
--
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/1409
The class / method hierarchy in Ruby files is parsed incorrectly if assigning the result of an `if` / `else` block:
After removing the assignment, all methods are grouped under the enclosing class, as expected:
Tested with the very latest state of the `master` branch (as of 2018-01-18), Arch Linux up to date. Might be related to #587.
--
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/1744
Geany 1.28 Release (Windows and Linux) and Geany 1.29 and I think also Geany 1.27 and before
Lines that start with ';' are syntax highlighted as comment.
Lines that start with '#' are syntax highlighted as comment.
An entry "key=value" in a line starting with ';' is shown in the symbols list.
An entry "key=value" in a line starting with '#' is not shown in the symbols list.
I attached a small test file test.ini, but I had to rename it to test.ini.txt because github refused to upload test.ini
[test.ini.txt](https://github.com/geany/geany/files/464268/test.ini.txt)
--
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/1220
Hi, in older versions of geany you used to be able to use the scroll wheel while hovering the tab bar to cycle through tabs, it seems the recent update to 1.33 vanished that feature into the void.
It was a nice feature, just making a note in case you guys want to implement/re-enable it.
--
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/1848
test:pas is my file:
cat /tmp/test.pas
type {coucou}
L3=string[3];
L2=string[2];
if open with geany it crash.
Remove the space after "type", load it in geany, type a space in geany in the same place, it crash
(I tried before the 1.35 with same bug)
geany -V
geany 1.36 (construit le Oct 14 2019 avec GTK 3.24.1, GLib 2.58.3)
gdb geany
GNU gdb (Gentoo 8.1 p1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from geany...(no debugging symbols found)...done.
(gdb) set args /tmp/test.pas
(gdb) r
Starting program: /usr/bin/geany /tmp/test.pas
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffed6f3700 (LWP 15105)]
[New Thread 0x7fffecef2700 (LWP 15106)]
Thread 1 "geany" received signal SIGSEGV, Segmentation fault.
0x00007ffff7abfcef in ?? () from /usr/lib64/libgeany.so.0
(gdb) bt
#0 0x00007ffff7abfcef in ?? () from /usr/lib64/libgeany.so.0
#1 0x00007ffff7adbe95 in ?? () from /usr/lib64/libgeany.so.0
#2 0x00007ffff7ad822e in ?? () from /usr/lib64/libgeany.so.0
#3 0x00007ffff7adb5a0 in ?? () from /usr/lib64/libgeany.so.0
#4 0x00007ffff7ab3807 in ?? () from /usr/lib64/libgeany.so.0
#5 0x00007ffff7ab4ad6 in ?? () from /usr/lib64/libgeany.so.0
#6 0x00007ffff78e3c73 in ?? () from /usr/lib64/libgeany.so.0
#7 0x00007ffff78e3f9a in document_set_filetype () from /usr/lib64/libgeany.so.0
#8 0x00007ffff78e5a72 in ?? () from /usr/lib64/libgeany.so.0
#9 0x00007ffff7907696 in ?? () from /usr/lib64/libgeany.so.0
#10 0x00007ffff7909b3b in main_lib () from /usr/lib64/libgeany.so.0
#11 0x00007ffff748f6eb in __libc_start_main () from /lib64/libc.so.6
#12 0x000055555555464a in ?? ()
(gdb) quit
--
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/2358
```C++
namespace ns {
class C {
void f( // when typing the ( the calltip says "ns::C::f (junk, rubbish)"
public:
C(junk, rubbish){}
~C(){}
};
};
```
Yep, takes the parameters for the constructor and it uses that as the prototype for the new function that doesn't exist yet.
And ... if there happen to be other functions named `f` the calltips will cycle through the prototypes of those functions and never come back to the erroneous one.
Seems like some extraneous function definition is being made for the calltip. But it never appears in the symbol list. Like as if something is scanning for the ) and using the parameter list immediately before it, ignoring the `public: C(`. But what, its not the parser because the symbol doesn't show in the sidebar?
--
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/1249
geany version - 1.29
Most of the function declarations in glibc header files are marked with __THROW.
Geany cannot identify or incorrectly identifies these functions.
(sample files /usr/include/pthread.h, /usr/include/unistd.h).
--
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/1314
When I typedef int abc; abc is highlighted as a new type, but using abc = int; doesn't.
Moreover, it would be niece to have third kind of color for keywords.
One more thing, is it possible to declare keywords highlighted as numbers (ex. true, false, nullptr in the same color as 42, 0xDEADBEEF and so on) ?
--
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/1944
The multi-line comment within a macro means that `int y` (and all code following it) doesn't get parsed by ctags:
```c
int x;
#define CHANGE_TREE(new_child) \
G_STMT_START { \
/* only change the tag tree if it's actually not the same (to avoid flickering) and if
* it's the one of the current document (to avoid problems when e.g. reloading
* configuration files */ \
if (child != new_child && doc == document_get_current()) \
{ \
if (child) \
gtk_container_remove(GTK_CONTAINER(tag_window), child); \
gtk_container_add(GTK_CONTAINER(tag_window), new_child); \
} \
} G_STMT_END
int y;
```
Removing the comment restores parsing. The macro is actually from Geany's sidebar.c, but #2345 gets rid of it.
--
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/2349