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
Hi, I already read about this bug but not on GitHub and never with a solution, so I hope this is not a duplicate. I tried to write a program in pascal, using the command "type". After typing the word "type", pressing any button caused Geany to crash. After that, Geany can be opened as usual, just that since then I cannot even compile simple hello world programs. I get the error message "ld: library not found for -lc" and "/usr/local/bin/ppcx64 returned an error exitcode" as well as exitcode 127. In addition, shell files and files of type .res are created in the working directory. I tried deleting them, uninstalling fcp and Geany but nothing worked. Attached you can find a screenshot of the error message.
<img width="562" alt="Screenshot 2021-11-05 at 11 25 50" src="https://user-images.githubusercontent.com/71439619/140496459-d514a52d-fc50-…">
--
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/2982
Maybe this already exists in the settings somewhere, but I couldn't find it: I'd like it if geany could remember the width of the side panel (where symbols, documents tabs are) across instances.
Every time geany opens, the side panel is very small and I always have to resize it. It'd be nice if this could be remembered.
--
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/2562
This pull request switches us to the new cxx parser for C and C++.
There is nothing really special worth noting here apart from the
change how anonymous tags are called in the new parser. In the
old parser we had e.g.
```
anon_struct_1
anon_union_2
anon_typedef_3
```
which are now called just
```
__anon1
__anon2
__anon3
```
The question is whether we should do something about that or just keep it this way (it should be possible to rename the tags in our code, the only problem is that we have to go through all the tags and apart from tag names also update scope names).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3032
-- Commit Summary --
* Add "l" prefix to functions in lcpp.c/h
* Rename C/C++ parsers to "Old"
* Add the new cxx parser
* Enable the new cxx parser
* Update C/C++ unit tests
-- File Changes --
M ctags/Makefile.am (32)
A ctags/parsers/cpreprocessor.c (2297)
A ctags/parsers/cpreprocessor.h (137)
A ctags/parsers/cxx/cxx.c (163)
A ctags/parsers/cxx/cxx_debug.c (182)
A ctags/parsers/cxx/cxx_debug.h (63)
A ctags/parsers/cxx/cxx_debug_type.c (54)
A ctags/parsers/cxx/cxx_keyword.c (639)
A ctags/parsers/cxx/cxx_keyword.h (178)
A ctags/parsers/cxx/cxx_parser.c (2023)
A ctags/parsers/cxx/cxx_parser.h (27)
A ctags/parsers/cxx/cxx_parser_block.c (804)
A ctags/parsers/cxx/cxx_parser_function.c (2281)
A ctags/parsers/cxx/cxx_parser_internal.h (388)
A ctags/parsers/cxx/cxx_parser_lambda.c (332)
A ctags/parsers/cxx/cxx_parser_namespace.c (345)
A ctags/parsers/cxx/cxx_parser_template.c (858)
A ctags/parsers/cxx/cxx_parser_tokenizer.c (1689)
A ctags/parsers/cxx/cxx_parser_typedef.c (491)
A ctags/parsers/cxx/cxx_parser_using.c (170)
A ctags/parsers/cxx/cxx_parser_variable.c (917)
A ctags/parsers/cxx/cxx_qtmoc.c (342)
A ctags/parsers/cxx/cxx_scope.c (276)
A ctags/parsers/cxx/cxx_scope.h (86)
A ctags/parsers/cxx/cxx_subparser.c (125)
A ctags/parsers/cxx/cxx_subparser.h (45)
A ctags/parsers/cxx/cxx_subparser_internal.h (27)
A ctags/parsers/cxx/cxx_tag.c (700)
A ctags/parsers/cxx/cxx_tag.h (202)
A ctags/parsers/cxx/cxx_token.c (185)
A ctags/parsers/cxx/cxx_token.h (124)
A ctags/parsers/cxx/cxx_token_chain.c (1220)
A ctags/parsers/cxx/cxx_token_chain.h (288)
M ctags/parsers/geany_c.c (130)
M ctags/parsers/geany_lcpp.c (48)
M ctags/parsers/geany_lcpp.h (32)
M ctags/parsers/geany_verilog.c (2)
M src/tagmanager/tm_parser.c (62)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (5)
M src/tagmanager/tm_tag.c (2)
M tests/ctags/backslashes.c.tags (10)
M tests/ctags/bit_field.c.tags (46)
M tests/ctags/bug1201689.c.tags (2)
M tests/ctags/bug1466117.c.tags (8)
M tests/ctags/bug1491666.c.tags (8)
M tests/ctags/bug1563476.cpp.tags (1)
M tests/ctags/bug1575055.cpp.tags (2)
M tests/ctags/bug1585745.cpp.tags (8)
M tests/ctags/bug1764143.h.tags (4)
M tests/ctags/bug1770479.cpp.tags (2)
M tests/ctags/bug1773926.cpp.tags (2)
M tests/ctags/bug1799340.cpp.tags (6)
M tests/ctags/bug1907083.cpp.tags (8)
M tests/ctags/bug1924919.cpp.tags (4)
M tests/ctags/bug507864.c.tags (6)
M tests/ctags/bug556645.c.tags (3)
M tests/ctags/bug556646.c.tags (42)
M tests/ctags/bug639639.h.tags (6)
M tests/ctags/bug639644.hpp.tags (4)
M tests/ctags/c-digraphs.c.tags (6)
M tests/ctags/c-trigraphs.c.tags (6)
M tests/ctags/cpp_destructor.cpp.tags (6)
M tests/ctags/cxx11-final.cpp.tags (6)
M tests/ctags/cxx11-noexcept.cpp.tags (4)
M tests/ctags/cxx11-override.cpp.tags (6)
M tests/ctags/cxx11enum.cpp.tags (10)
M tests/ctags/cxx14-combined.cpp.tags (6)
M tests/ctags/extern_variable.h.tags (2)
M tests/ctags/func_typedef.h.tags (2)
M tests/ctags/local.c.tags (2)
M tests/ctags/macros.c.tags (4)
M tests/ctags/namespace.cpp.tags (4)
M tests/ctags/prototype.h.tags (2)
M tests/ctags/signature.cpp.tags (9)
M tests/ctags/static_array.c.tags (2)
M tests/ctags/var-and-return-type.cpp.tags (6)
-- Patch Links --
https://github.com/geany/geany/pull/3032.patchhttps://github.com/geany/geany/pull/3032.diff
--
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/pull/3032
```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
Only a few of the symbols for the file `sidebar.c` show up in the symbols pane. This is due to the lines [here](https://github.com/geany/geany/blob/5b307bc05dbb055a06dc83c1d749ffab4… within a comment inside a macro not being backslashed confusing ctags.
Because cpp removes comments before preprocessing its not a problem for the compiler, cpp never sees the comment and the macro is whole, but ctags gets confused and gives up.
Should we just add the backslashes as a workaround. And is it worth reporting since we don't use the ctags "new C/C++" parser?
--
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/2916
