I want to be able to change the behaviour of double click to select a single word when underscores are used as word separators. Currently if I double click `this_is_a_test` in geany the whole entire sentence is selected. I want to be able to double click and select only the words in it. This isn't a problem for dashes `this-is-a-test` double clicking any word in this test selects only the word. I read through #492 but that seemed to be for keyboard interactions not mouse interactions.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3068
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3068(a)github.com>
According to the Scintilla Documentation:
> Any markers not associated with a visible margin will be displayed as changes in background colour in the text. A width in pixels can be set for each margin. Margins with a zero width are ignored completely.
All lines with markers, either builtin or used by plugins (`git-changebar`), appear on the white background, which is ugly, especially in dark themes.
This MR disables rendering of markers by making them fully transparent on the overview.
Additionally, it fixes `SETMARGINWIDTHN` for the last (missing) margin:
> 5 margins are allocated initially numbered from 0 to SC_MAX_MARGIN (4).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1147
-- Commit Summary --
* Overview: hide markers
-- File Changes --
M overview/overview/overviewscintilla.c (5)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1147.patchhttps://github.com/geany/geany-plugins/pull/1147.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1147
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1147(a)github.com>
Geany 1.36
(built on or after Mar 22 2020)
Using GTK+ v3.24.20 and GLib v2.64.6 runtime libraries
When 'Find' dialog is opened,
Go back to text editor tab and double click some word you'd like to find other occurences if any.
'Find' dialog regain focus but search zone is still filled with old value
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3057
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3057(a)github.com>
@eht16 Did the new cxx parser fix this issue on Windows?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/349#issuecomment-999914319
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/349/999914319(a)github.com>
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
){kind=link}