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
I upgraded from Geany 1.26 to 1.27 and I get an error saying that "libgcc_s_dw2-1.dll" cannot be found.
I'm using the "nogtk" installer on Windows 10 (via chocolatey, actually). Chocolatey also installed GTK for me (from http://downloads.sourceforge.net/gtk-win/gtk2-runtime-2.24.10-2012-10-10-as…).
I reverted back to 1.26 and everything works just fine.
---
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/976
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
This looks wierd:
```
#: ../src/keybindings.c:474
msgid "Send to Custom Command 1"
msgstr "Передать пользовательской команде 1"
#: ../src/keybindings.c:476
msgid "Send to Custom Command 2"
msgstr "Передать пользовательской команде 2"
#: ../src/keybindings.c:478
msgid "Send to Custom Command 3"
msgstr "Передать пользовательской команде 3"
#: ../src/keybindings.c:480
msgid "Send to Custom Command 4"
msgstr "Передать пользовательской команде 4"
#: ../src/keybindings.c:482
msgid "Send to Custom Command 5"
msgstr "Передать пользовательской команде 5"
#: ../src/keybindings.c:484
msgid "Send to Custom Command 6"
msgstr "Передать пользовательской команде 6"
#: ../src/keybindings.c:486
msgid "Send to Custom Command 7"
msgstr "Передать пользовательской команде 7"
#: ../src/keybindings.c:488
msgid "Send to Custom Command 8"
msgstr "Передать пользовательской команде 8"
#: ../src/keybindings.c:490
msgid "Send to Custom Command 9"
msgstr "Передать пользовательской команде 9"
```
Could you collapse this into "Send to Custom Command %d"?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/953
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
I've updated geany and it's plugins from official PPA, and again debugger fails to open files if they are located in nonASCII paths. (this bug was fixed twice and now has appeared again)
---
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/416
This are the changes to geany that allow plugin signals to be used by GI-based plugins (e.g. through peasy).
- signal params must be boxed or gobject (I used gboxed)
- the GType must be passed to g_signal_new()
- since glib 2.30 there is a generic marshaller which can be used. otherwise we'd need a lot of duplicated, new marshaller code. I chosed to use the generic marshaller (by passing NULL to g_signal_new's marshall func)
- geanyobject must be exposed to connect to. I chosed to implement a get_instance() function (singleton pattern)
Please review and comment
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1038
-- Commit Summary --
* plugin api: convert GeanyDocument to GBoxed internally
* plugin api: convert GeanyFiletype to GBoxed internally
* plugin api: convert GeanyEditor to GBoxed internally
* plugin api: rename document_new_file to _create_file
* plugin api: export geanyobject
-- File Changes --
M plugins/geanyplugin.h (1)
M src/Makefile.am (1)
M src/document.c (32)
M src/document.h (4)
M src/editor.c (11)
M src/editor.h (4)
M src/filetypes.c (11)
M src/filetypes.h (3)
M src/geanyobject.c (231)
M src/geanyobject.h (3)
-- Patch Links --
https://github.com/geany/geany/pull/1038.patchhttps://github.com/geany/geany/pull/1038.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/1038