Devel

devel@lists.geany.org

1641 discussions

Re: [Geany-Devel] ntrel - Don't prompt for reload from infobar when there are no unsaved changes
by Thomas Martitz 22 Oct '14

22 Oct '14

Hi, this is about commit ab7a0018b2518793f26af2fe20a06a8a1886e031 and the message reads " Don't prompt for reload from infobar when there are no unsaved changes". What does that mean? I do absolutely want to be asked before reloading even if the file has no changes or saved ones. Best regards

2 2

Nightly builds changes and improvements
by Enrico Tröger 19 Oct '14

19 Oct '14

Hi, I spent some time on the nightly builds and now: - the buildbox was upgraded from Debian Squeeze (oldstable) to Debian Wheezy (stable) - Debian builds work again (they were partly broken for some time for various reasons) - GTK compatibility checks are enabled again, now against GTK 2.24.10 (the GTK2 version in Debian Stable) - Win32 and GTK2 test builds are executed in RAM disk and also use ccache which speeds up the compilation time heavily and reduces disk I/O a lot. The last point won't help much most people but will enable us to enable a future step: building Win32 and GTK2 compatibility check as a commit/push hook to get instant check results. This is not yet implemented but I will do this at some point soon, as time permits. Results can be found on http://nightly.geany.org/. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

1 0

i want to contribute with this project
by robertodmachado . 18 Oct '14

18 Oct '14

Hi, I'm roberto, and would like to participate in this project with my knowledge in C. How should I start ?

5 6

Switched to Win~1
by Dimitar Zhekov 13 Oct '14

13 Oct '14

Hi, Since Debian is leaning more and more towards systemd, especially with gvfs installed, and since systemd-init breaks my system, I finally sat on my back and migrated to Windows. It's not a good system either, but gets the job done. Now, Geany under Win~1 has some deficiencies, due to gtk+, so I'll probably use it as a debugger only, and limit myself to the official releases. But if somebody decides to apply the spawning fix, or parsing the columns in compiler messages, or the small patch that adds virtual column to the status bar, I will be glad to help. Also, if Scope has any problems building with or running under gtk+3, I'll fix them (some Linux programs are not replaceable, so I kept a small Debian system in dual boot). But there will be no gtk+4 support, at least not from me. -- E-gards: Jimmy

8 20

Moving notebook tab keybindings broken
by Nick Treleaven 12 Oct '14

12 Oct '14

keybindings.c:cb_func_move_tab needs to be updated now ScintillaObject is not a child of main_widgets.notebook.

2 3

Windows GTK Runtime 2.24 and config directory
by Enrico Tröger 05 Oct '14

05 Oct '14

Hi, lately, I started building a new Windows installer which includes a recent GTK 2.24 runtime for Windows which need for future releases. While most things went fine I noticed one problem: GTK, in detail Glib, changed the way g_get_user_data_dir() works on Windows: in older releases, something GLib 2.28 or 2.26 and older, g_get_user_data_dir() returned c:\users\<username>\AppData\Roaming, in newer GLib versions it returns c:\users\<username>\AppData\Local. This affects users who already have a config directory located in <...>\Roaming and Geany would look in <...>\Local now. This is the change I'm talking about: https://git.gnome.org/browse/glib/commit/glib/gutils.c?id=9d80c361418f94c60… How do we want to handle this? - continue using the <...>\Roaming directory (and so not using g_get_user_data_dir() anymore) - leave the code as it is, resulting in a new complete config for users - add some code to check if a config in <...>\Roaming exists and if so, move it to <...>\Local I'd implement the last choice if there are no objections. This is not nice because we implement again some magic "config directory move" code but at least the user won't notice that GLib change. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

5 27

Glade progress
by Thomas Martitz 03 Oct '14

03 Oct '14

Hello, I want to let you knows know that glade upstream just merged my backports for the "topological sorting algorithm" into glade-3-8 branch. This means that we can now use upstream glade for our geany.glade as the major outstanding deficiency is fixed: it now sorts the generated xml in a predictable and stable manner, suitable for diff-review and probably git merges too. The backports should appear in 3.8.5 if you'd like to wait for a realease. Best regards

3 2

Patch: Enable per project line wrapping
by Tim Tassonis 25 Sep '14

25 Sep '14

Hi all As threatened two weeks ago, I now created a patch to geany to enable line_wrapping on a per-project basis. Seems to be working fine, I put the checkbox to enable it on the Editor tab of the project properties. I hope I did everything right: - git clone git://github.com/geany/geany.git geany - Made my changes - Did a fresh git pull - git commit -a - git format-patch HEAD^ I attach the resulting patch to the email, please tell when you need it in another way. Kind regards Tim -- decentral.ch - IT Stuff Tim Tassonis Dennlerstasse 36 8047 Zürich stuff(a)decentral.ch +41 79 229 36 17

2 2

per-project line wrap
by Tim Tassonis 12 Sep '14

12 Sep '14

Hi all Thanks first everybody involved for geany, have been using it now for several years for all my programming work and never, ever even thought about looking back. Since I want to start to do some text writing with geany as well, I'd like to toggle line wrapping on a project basis, which currently does not seem to be possible. My question is: Would you take a patch to enable this or is there a good reason not to implement it? Kind regards Tim

2 1

[ANN] document_find_by_id() added to plugin API
by Nick Treleaven 04 Sep '14

04 Sep '14

See: http://www.geany.org/manual/reference/document_8h.html#aa14a04c6596cd3261b3… Real-world example when clicking a Messages item: https://github.com/geany/geany/commit/18181c2e9043add8b13c1fc94c66db2ca5b88… Code that uses doc->is_valid or DOC_VALID() outside of iterating documents_array probably should be using document_find_by_id() instead, because closed document pointers only stay invalid until another document needs to be opened. Regards, Nick

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel