```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
I prefer that the terminal doesn't use bold fonts when printing characters with bold or highlight attribute since it's easier to my eyes.
This patch allows VTE to be configured that way through `vte_terminal_set_allow_bold()`.
Preview: http://i.imgur.com/KPZwPyi.png?1
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1132
-- Commit Summary --
* Allow VTE to be configured to not use bold fonts
-- File Changes --
M data/geany.glade (15)
M doc/geany.txt (3)
M src/keyfile.c (2)
M src/prefs.c (6)
M src/vte.c (3)
M src/vte.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/1132.patchhttps://github.com/geany/geany/pull/1132.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/1132
When open a .nim file or creating an project with a .nim file
The Build pull down menu doesn't offer the 'Compile' button.
--
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/2669
The menu options
View -> Show Markers Margin
View -> Show Line Numbers
don't control the respective items on the right side split.
You can "unsplit," set the options, and then split again and the new window has the proper appearance.
--
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-plugins/issues/600
The regex engine used by Geany does not match the one used by upstream ctags, so incorporating the regex parsers would need two regex engines.
Either this should be accepted (IMHO preferred as it allows to keep in sync with upstream) or an alternative implementation for those languages should be provided.
--
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/2119
