As discussed in various discussions in the past, e.g. #679 and #524, we finally remove Waf build system support from Geany, mainly to reduce the build system maintenance overhead.
Steps to do:
- [ ] Remove code references in GIT master, including manual
- [ ] Remove website references
- [ ] Remove wiki references
More?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/768
At the moment tags with identical names are stored into a linked list in
tags_table and parents_table. This however leads to quadratic complexity
when looking up the nearest parent or tag in tree because the whole list
has to be traversed.
Use binary trees indexed by line number instead of lists so the lookup can
be performed in log(N) time and the overall complexity is N*log(N) instead
of N^2.
The GTree API is a little stupid because during the search it doesn't give
access to the value and it doesn't tell when a leaf node was reached. For
this reason the lookup has to be made in two steps - first, the best line
number is found (returned in user_data) and then a normal search for the
found line number is made to get the value stored in the tree.
This patch fixes the problem described in #577 when e.g. a big json export
file contains many identically named tags.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/797
-- Commit Summary --
* Store "equal" tags into binary trees instead of lists in Symbol tree
-- File Changes --
M src/symbols.c (249)
-- Patch Links --
https://github.com/geany/geany/pull/797.patchhttps://github.com/geany/geany/pull/797.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/797
The <b>justify</b> command is very useful Please consider having it co-operate with <b>vertical selection</b> so that justifying the comment on line 1 produces line 6 as opposed to line 8
Such a feature would useful in formatting code, for example producing line 5 instead of line 7:
<b>Thanks!</b>
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/821
Since things like the HTML and configure have been removed from VCS the difference between building from GIT and the extra dependencies that needs and building from tarball is getting bigger. Needs to be made clear.
Or maybe README says how to build from git (since its visible on the github front page) and HACKING or INSTALL says how to build from tarball. Thoughts?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/756
The extension is used by both C and C++ and lexing/parsing C headers with
the C++ parser causes less problems (identifiers named like C++ keywords
get highlighted and tags aren't generated for them) than parsing C++
headers with the C parser (parsing and lexing completely broken).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/857
-- Commit Summary --
* Treat the "h" extension as a C++ file
-- File Changes --
M data/filetype_extensions.conf (2)
-- Patch Links --
https://github.com/geany/geany/pull/857.patchhttps://github.com/geany/geany/pull/857.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/857