Devel December 2011

devel@lists.geany.org

25 participants
50 discussions

Having trouble with keybindings
by Nathan Broadbent 07 Dec '11

07 Dec '11

Hello, I'm working on the TreeBrowser plugin. I have fixed a few bugs, so I'm looking forward to sending pull requests when geany-plugins is on github :) I'm currently trying to add a keybinding for deleting objects from the treeview. I have added a KB_DELETE_OBJECT keybinding, and I've mapped this to the delete key, which works fine. However, the keybinding for the sidebar is still activated when the editor has focus, and I press the 'delete' key. I would like the keybinding to only activate if the sidebar widget has focus (is active). This is also a problem for the 'rename object' keybinding that was already there. The last parameter to the 'keybindings_set_item' function is: GtkWidget * menu_item - "Optional widget to set an accelerator for, or NULL." I've tried setting this to 'treeview' or 'sidebar_vbox', but that doesn't seem to work. I'd be really grateful if someone would be able to help me understand how to solve this. Thanks very much! Nathan B

2 1

Stop committing to geany-plugins SVN
by Jiří Techet 07 Dec '11

07 Dec '11

Hi, I'm about to start the geany-plugins git conversion so please stop committing to the SVN repository. Cheers, Jiri

1 0

Geany-Plugins: Git-transition
by Frank Lanitz 07 Dec '11

07 Dec '11

Hi developers, Jire and I just finally scheduled git transition of the plugins. This will be done Wednesday evening CET. Please be so kind and stop committing to svn so we can ensure, all changes are going in. Please let me also know you github accounts if available for committing to plugins etc. Cheers, Frank

2 2

Re: [Geany-devel] Indentation using regex (was [PATCH 14/19] Rewrite tab switching queue)
by Jiří Techet 07 Dec '11

07 Dec '11

On Thu, Sep 16, 2010 at 19:27, Thomas Martitz <thomas.martitz(a)student.htw-berlin.de> wrote: > On 16.09.2010 02:23, Lex Trotman wrote: >> >> Hi Jiri, >> >> I couldn't get this to work at all, it printed "calling indent this >> line" all the time but didn't indent :-( >> >> I only had half an hour so I couldn't investigate much. >> > > I have the same experience. Auto-indentation doesn't seem to work anymore > (e.g. when hitting enter after on a line that ends with {, or when typing > }). I have just re-tested it again and it works on my machine (I have forgotten one trace in the code - that's what you see in the console). A quick question: have you read the commit log? This patch makes it possible to specify several regex patterns for every filetype which determine under what condition the indentation is performed. The pattern variables are specified under the [settings] section of the given filetype and their value is the regex to be used. The variables are as follows: * indent_this_line_regex - the match is performed after every keystroke and if the regex matches, the indentation is performed on the current line * indent_next_line_regex - the match is performed only when enter is pressed. The indentation is applied on the next line * unindent_this_line_regex - like indent_this_line_regex but unindents instead * unindent_next_line_regex - like indent_next_line_regex but indents instead Comments and strings are detected from the lexer so these can be ignored inside the patterns. For instance these are very basic rules for GNU indent style: indent_next_line_regex=^.*\\{[[:blank:]]*$ unindent_this_line_regex=^[[:blank:]]*\\}$ indent_this_line_regex=^[[:blank:]]+\\{$ unindent_next_line_regex=^[[:blank:]]*\\}[[:blank:]]*$ By commenting-out the last two lines you get ANSI indentation style. If you replace \\{ and \\} with begin and end, respectively, you get analogous rules for pascal. Notice the double-escaping of { and } - the first escape sequence is for the keyfile ini format (so for the regex itself \\ becomes \). This means that in order to make it work e.g. for C, you have to edit ~/.config/geany/filedefs/filetypes.c (or the corresponding file under /usr/local/share/geany) and add indent_next_line_regex=^.*\\{[[:blank:]]*$ unindent_this_line_regex=^[[:blank:]]*\\}$ indent_this_line_regex=^[[:blank:]]+\\{$ unindent_next_line_regex=^[[:blank:]]*\\}[[:blank:]]*$ under the [settings] section (+ restart geany). Please let me know if it works (but also in the opposite case ;-). Jiri > > Best regards. > _______________________________________________ > Geany-devel mailing list > Geany-devel(a)uvena.de > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel >

6 35

Additions to Addon plugin
by Meyer 06 Dec '11

06 Dec '11

Hi all, I've been working on an addition to the Addons plugin that gives a couple options for wrapping text with characters. It adds two check boxes to the plugin's preferences, one to enable "auto wrapping" and one to enable "keybinded wrapping." Auto wrapping automatically wraps selected text as soon as a certain character is pressed (apostrophe, quote, back tick, left parenthesis, or left square/curly bracket) and keybinded wrapping provides eight keybindings which correspond to eight user-set pairs of characters, which will surround selected text when the keybinding is pressed. The code (two new files and modified addons.c) is here - https://github.com/pzoxiuv/Geany-Plugins/tree/master/geany-plugins-0.21.1/a…. Is there any way this could be eventually added to the Addons plugin? (And thanks Dimitar Zhekov for the advice you gave me in my previous thread, it was very helpful). Cheers, Alex

1 0

Geany Newsletter Issue #4
by Frank Lanitz 04 Dec '11

04 Dec '11

Geany Newsletter #4 ------------------- About Geany =========== Geany is a small and lightweight Integrated Development Environment. It was developed to provide a small and fast IDE, which has only a few dependencies from other packages. Another goal was to be as independent as possible from a special Desktop Environment like KDE or GNOME - Geany only requires the GTK2 runtime libraries. More information about Geany can be found at `geany.org <http://www.geany.org/>`_. Table of contents ================= 1 About Geany 2 Geany 0.21 has been released 3 Geany-Plugins 0.21 has been released 3.1 New Plugins 3.2 Updates and Bugfixes 3.2.1 General 3.2.2 Addons 3.2.3 GeanyLaTeX 3.2.4 GeanySendMail 3.2.5 Spell Check Plugin 3.2.6 Updatechecker 3.2.7 WebHelper 3.2.8 Internationalisation 4 Geany-Plugins 0.21.1 has been released 5 Geany moved to Git 6 Change of project leadership 7 Geany local 7.1 Geany at OpenRheinRuhr 2011 8 Let us introduce you 8.1 Plugin Focus 8.1.1 Split Window 8.2 Feature Focus 8.2.1 Colour Schemes 9 People behind Geany -- Interview 9.1 Enrico Tröger 10 About this newsletter Geany 0.21 has been released ============================ After about 6 months of development, on 2 October 2011 Geany 0.21 was been released. There have been a lot of changes, so only the highlights are listed below: * Add support for real-time symbol parsing. * Fix loading of non-UTF-8 templates. * Update Scintilla to version 2.25. * Add Scala custom filetype (werg). * Add Cython custom filetype (Matthew Brush). * Add support for separate single and multiline comments. * Add support for filetype-specific indentation settings. * Add filetype Cobol (Seth Keiper). * SplitWindow plugin now works on Windows too. * Add translations: fa. * Update translations: ca, cs, de, en_GB, es, fi, fr, gl, it, ja, nl, pt, pt_BR, sl, sv, tr, vi, zh_CN, zh_TW. A more complete list can be found on http://www.geany.org/Documentation/ReleaseNotes Source tarballs as well as Windows binaries can be found as always on http://download.geany.org. Geany-Plugins 0.21 has been released ==================================== On 23 October 2011, about three weeks after Geany 0.21, Geany-Plugins in its final version has been released. As seen in former newsletters it has been a quite active time on plugin development, so we are trying to give you an overview on one hand as well as digging into some of the bigger changes that have happened. New Plugins ^^^^^^^^^^^ Most of the new plugins have been already described in one of the previous editions of this newsletter. However, so only a short overview is provided here. * **Debugger**: A plugin to integrate debuggers like GDB. This is replacing GeanyGDB in many places. * **Devhelp**: Integration for GNOME's Devhelp and google code search. * **GeanyPG**: Encryption, decryption, signing etc. from within Geany via GnuPG. * **GeanyMacro**: A plugin to record and apply macros. * **GeanyNumberedBookmarks**: A plugin to store bookmarks to files and access them easily via a number. * **Tableconvert**: A plugin to convert lists into tables. * **XMLSnippets**: Helps on inserting (common) XML-snippets. Updates and Bugfixes ^^^^^^^^^^^^^^^^^^^^ General ####### Significant rework has been done on the Autotools build system as well as some maintenance work on the Waf-build system. Addons ###### * DocList addon: Add preference to define the order of the documents in the list (#3204573) * Tasks addon: Activate and update the task list when the Tasks addon is enabled GeanyLaTeX ########## * Moved LaTeX menu to a separate menu inside Geany main menu * Added a feature to autocapitalise letters on typing at the beginning of a sentence * Added a way to put an icon for LaTeX wizard into Geany's main toolbar * Added a dialog for inserting BibTeX references based on available \*.bib-files * Upgrade plugin API to version 199 * Ensure not to insert {} after \^ and \_ * Adding a keystroke to toggle inserting {} after ^ and _ * Fixed an issue with wrong inserted formatting using a keybinding * Small update to enable i18n also on Geany >= 0.21 * Various bugfixes and memory leak fixes. GeanySendMail ############# * Some minor cleaning up of code * Fix for an issue with replacing of command string when %r was not used * Don't double free a variable which might end up in a segmentation fault when using plugin function more than once. * Small update to enable i18n also on Geany >= 0.21 Spell Check Plugin ################## * Reduce artifacts on partially checked words * Improve \`Check as you type' feature, making it more reliable Updatechecker ############# * Fix an issue with init threads for older GTK/glib versions by updating to Geany API version 203. * Small update to enable i18n also on Geany >= 0.21 * Fix a typo inside Waf-build system WebHelper ######### * Fix creation of configuration directory in some cases * Fix missing update of navigation buttons on anchor links * Fix thread initialization problem * Fix some issues with keybindings on secondary windows * Add a keybinding to show/hide web view's window (bug #3156262) * Allow for better configuration of secondary windows Internationalisation #################### * Updated translations: de, pt, ru, tr Geany-Plugins 0.21.1 has been released ====================================== Shortly after the major release of Geany-Plugins 0.21, an issue with the build system was found which blocked installation of source tarballs using the Waf-build system. This has been fixed inside a minor source release. The Windows binary release isn't affected by this issue. Geany moved to Git ================== After a long discussion on the mailing list Geany finally moved to Git as the main version control system. The goal is to be more flexible on including patchsets from non-core-developers as well as making use of a number of other features of Git. The new home of the Git repository is http://github.com where you can access Geany's sources at https://github.com/geany/geany During this switch, sources of other Geany-related resources have been moved to GitHub as well and can be found on the overview page at https://github.com/geany Change of project leadership ============================ If you have been using Geany for a while and read the announcement of Geany 0.21's release, you might have noticed something important. The leadership of the Geany project has changed from Enrico Tröger to Colomban Wendling, a current member of the development team. Enrico's priorities changed so he decided it would be best if someone else took on the leadership role. During Enrico's time as leader, Geany has continued to gain in popularity and improve, whilst staying true to its original design goals. Thank you, Enrico, for all that you have done, and thanks for taking over Colomban. Geany local =========== Geany at OpenRheinRuhr 2011 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Together with the guys of Xfce, Geany was presented with another booth at the annual OpenRheinRuhr at November, 11th and 12th in Oberhausen, Germany -- A convention about all topics around Linux, BSD and free software in general. The booth was again well visited and people came not only to ask for help, but also just for having a little chat with Enrico and Frank and discuss about Geany releated topics. Let us introduce you... ======================= This section is intended to introduce particular plugins or features on a regular basis. Plugin Focus ^^^^^^^^^^^^ Split Window ############ The Split Window plugin provides a feature which is so useful you'll never want to be without it. When enabled, choose Tools > Split Window > Side by side | Top and bottom from the main menu and the active window is split into two editing panes. Each pane can be navigated independently of the other, complete with its own scrollbar. In each window you can edit separate parts of the same file, with each pane updated instantly with the changes made in the other. When you want to return to "normal" view, choose Tools > Split Window > Unsplit from the main menu. It's not possible to again split the active window, only unsplit. The plugin was intended to allow you to work on the *same* file but thanks to a "hidden" feature you can work on two different files loaded in the split view. If you open a file while in split window mode, it's loaded in the inactive pane. You can then switch between the split view of the same file or the different files via the file tabs (under the menu bar) as normal. Note that it's not possible to change the file shown in the right-hand pane when Split Window is active. Feature Focus ^^^^^^^^^^^^^ Colour Schemes ################ Introduction ++++++++++++ Geany supports colour schemes which allow you to change the colours applied to various code elements. Two colour schemes are provided with Geany: Default and Alternate but many more are available (see below). To change the colour scheme, select from the menu View > Editor > Colour Schemes > PREFERRED_COLOUR_SCHEME. The colour scheme change is immediate but the list of available schemes is only loaded when Geany starts. Adding Colour Schemes +++++++++++++++++++++ More colour schemes are listed on the Geany Add-ons web page. For the individual schemes, follow the instructions given by their authors. One of the biggest set of schemes was created by codebrainz. The collection is listed on the add-ons page but is hosted at https://github.com/codebrainz/geany-themes Follow the installation instructions given on the page, then restart Geany and all schemes will then be listed in the Colour Schemes menu. How Colour Schemes Work +++++++++++++++++++++++ Geany's colour schemes' format has changed over time, so there's a "legacy" format and the current, preferred format. Schemes in the different formats can be mixed but the current format is easier to maintain and modify. In this issue the focus is on the new format but if readers want it, the legacy format could also be featured in a future newsletter. Current colour scheme format ++++++++++++++++++++++++++++ The current colour scheme format works by first defining the colours to be applied to a file type's elements. This is an extract from a colour scheme named "Oblivion2": default=0xffffff;0x2e3436;false;false tag=0x729fcf;0x2e3436;true;false tag_unknown=0xffffff;0x8C0101;true;false File types and their elements are defined in a file named filetypes.<FILETYPE>: e.g. filetypes.xml, filetypes.html. All filetype files are stored in the 'filedef' directory in Geany's personal data directory. This is an extract from the file type file for HTML: [styling] # Edit these in the colorscheme .conf file instead html_default=default html_tag=tag html_tagunknown=tag_unknown When Geany applies syntax highlighting to a file which matches a filetype, it matches the element (defined in the filetype's file) with the matching colour (defined in the colour scheme's file). The advantage of this scheme over the legacy version is that modifying a colour scheme for all filetypes requires changes to just one file. People behind Geany -- Interview ================================= This is the second in a series of interviews with Geany's contributors: core developers, plugin developers, translators, wiki maintainers and any other job we can think of. The purpose of the interviews is to get to know each of these people a little better: their hopes, dreams, plans and favourite Geany plugin. Enrico Tröger ^^^^^^^^^^^^^ As is mentioned above, Enrico Tröger recently stepped down as leader of the Geany project. In this interview he talks about his history with the project. *What motivates you to develop or contribute to FLOSS projects?* There are different reasons. Most often it is that I want to improve existing software by fixing bugs, adding features I'd like to use and so on. So this is a rather pragmatic reason. Nevertheless, I believe in Free Software and this is another reason why I contribute to Free Software. Free Software allows people to read and modify the source code to their needs, so in theory everyone can make the software or change it to his/her needs. Based on my experience, most people push back their changes and so the developers can include them if appropriate. This is only one of the advantages of Free Software. I doubt this would be possible with paid software projects, at least not as long as they are not free. *How did you become Geany's project leader?* This was much simpler than you might imagine: I created the project :). *What is involved in being Geany's project leader?* Many different things. It all starts with knowing the project, knowing the people involved and ideally knowing the code base :). I think the project leader should coordinate the development and communicate with the community, making the project a project and not just a bunch of lines of code. Also, at least in the Geany case in the past, the project leader makes the releases though this is not necessarily a project leader task. Users, package maintainers and other external people often contact the project leader directly via mail or on IRC to say 'thank you', ask questions about Geany or to discuss project related topics. So this is another task for the project leader. And certainly there are many other aspects which I forgot to list. *What goals did you have when you started as project leader? Did you achieve those goals?* As I didn't explicitly start as project leader but instead just started the project, I didn't have any specific goals to achieve as project leader however I did have goals to achieve with Geany as project. These goals mostly were to create an editor which fits my needs so that I can use it to write code and other text documents without thinking about the editor, how it behaves, why it is so slow or doesn't do what I want. As you see, these were quite personal goals. In the meantime, as those goals basically were achieved with Geany 0.1, the goals changed to be more general: a light and fast editor with basic features of an IDE, without unnecessary dependencies to other libraries yet with useful features. Oh, and we achieved these goals as well though that doesn't mean Geany can't get better anymore. There is always room for improvements and new useful features. *What were some of the highlights of your time as project leader?* Hard to name particular highlights. One great thing which kept from the beginning to now is to receive mails from users who just say 'thank you, Geany is great program'. This is always great to read and always increases motivation to continue working on Geany (in whatever way). I didn't experience anything like this before and would have never expected it. But it's really nice. Maybe another highlight worth mentioning is the many things I learned during time working on Geany. This includes learning how other people use Geany or certain features of Geany, to work with the community and to read other people's code and learn from it. *Are there particular improvements/change/features of which you're proud?* The community. Ok, the community is not an improvement, change or feature :). But this is what Geany makes Geany. Without the many users and contributors, Geany would not be as cool and as stable and as feature-rich as it is now. Thank you all for using and improving Geany, keep up! *How does a FLOSS project balance welcoming contributions with keeping within the project's original goals and scope? In other words, avoid scope creep?* In Geany's case, luckily there were not much conflicts in accepting new features and the overall goal to keep fast and lightweight. However, I think a few times we had to deny a feature request for such reasons or because it the requested feature didn't fit into Geany. This went much better since Nick introduced the plugin interface so that features which don't fit into Geany's core, can be easily implemented as a plugin. Nevertheless, denying a feature request, especially when it was obvious that it would actually help the user who requested it but still doesn't fit into Geany, was hard for me. It's like "I decide that you will not get this functionality". Not a nice job. As said, luckily this didn't happen so often. *Do you have any hopes or dreams for Geany's future?* Of course: Geany should stay on its road it has been all the time. This is, keeping fast and lightweight while offering many useful features to the user. Moreover, I really hope and wish, the current fast and intense development in the community keeps going so that Geany will evolve further and get even better than it is already :). About this newsletter ===================== This newsletter has been created in cooperation by people from Geany's international community. Contributors to this newsletter and the infrastructure behind it, ordered by alphabet: * Colomban Wendling * Enrico Tröger * Frank Lanitz * Lex Trotman * Russell Dickenson

1 0

Geany-Plugins: SVN-URL on git
by Frank Lanitz 04 Dec '11

04 Dec '11

Hi, I didn't found the conclusion on the discussion: What was the outcome on this topic? Which reference to old svn shall be inserted into git repo? Cheers, Frank -- http://frank.uvena.de/en/

3 3

ReST: Image size
by Frank Lanitz 03 Dec '11

03 Dec '11

Hi folks, Its a bit OT, but wondering whether somebody o you could help me: How can I set sizes for images inside ReST? E.g. I want to set it to 50% of page width? Didn't found anything on documentation .... Cheers, Frank

2 10

(no subject)
by Meyer 02 Dec '11

02 Dec '11

Hi, I have two possible situations that I need to differentiate between, and I'm not sure how to do it - The first situation is the user deletes selected text by overwriting it with a new character. The second is the user deletes selected text by pressing backspace/delete, and then enters a new character. I thought this would be fairly easy, but I've been trying to figure it out for awhile and haven't gotten anywhere. Does anyone have any ideas for how I could accomplish this? Thanks, Alex

5 8

Unit tests for Geany (continued from Github)
by Nathan Broadbent 01 Dec '11

01 Dec '11

(continued from github - https://github.com/geany/geany/pull/15) > I don't think any of Geany's developers will argue that having some sort of unit testing would be a good idea, especially for the plugin API, but mainly it boils down to: > > 1) What framework to use (Geany is written in plain C). >From the Stack Overflow question "Is Google Test OK for testing C code?" (http://stackoverflow.com/a/6218365/304706) : It is pretty common to test C code using a C++ testing frameworks, even the leading book on the subject (http://pragprog.com/titles/jgade/test-driven-development-for-embedded-c) follows this approach. I have used googletest extensively in the past to unit test C code and can recommend it. I have written a blog post about it that might be useful: http://meekrosoft.wordpress.com/2009/11/09/unit-testing-c-code-with-the-goo… ... As long as your headers are C++-compatible (not using C++ keywords, export symbols with correct linkage), it should be fine. > 2) How do you run unit tests on a live GUI application with no libraries (surely there's a way). I don't have much experience, so I can't offer any suggestions. But I can do the research. > 3) Who's going to do it :) > > If you want to help with this, I'm sure it would be appreciated. I could help start it off, but it would have to be an on-going thing. I wouldn't have the time to sit down and write tests for the whole application. Each developer could get into the habit of writing a test whenever they change something or add a new feature. > The only real restriction IMO is that it not add any dependencies to the > application or build system under normal conditions. For example, it would be a bummer to make Joe Hacker have to install some exotic > unit testing framework libraries just to do a `make && make install`. I totally agree with not adding dependencies under normal conditions, and I don't think that will be an issue if the code is written well. Test-driven development often enforces particular design patterns, so there will probably need to be some refactoring involved. ------------- To be honest, the real reason that I started talking about unit tests, is because I really need them in order to write a lexer for scintilla. Manual testing for lexers would be a nightmare. <editor_rant> Also to be honest, I'm still a little conflicted with regards to gedit vs. geany vs. others. Gedit uses GTKSourceView, which has definitions for many more languages, but their lexers are XML / Regex based. So they're really slow for larger files, and they don't support code folding, which I'm starting to get used to. But their community seems to be a lot bigger, and a little more active. I also experimented with an editor called 'Redcar' which now appears to be the worst of both worlds... It uses GTKSourceView, plus the main editor is written in Ruby... Ruby might be my favorite language, but it's damn slow. So yeah, I've tried everything from vim to Eclipse, but so far, only Geany seems to have the right balance. So I'd like to put in some effort to make this editor better - after all, I'm going to be using it for 8 hours a day. </editor_rant> Cheers! Nathan P.S. The documentation needs to be updated for the 'waf' build system, in quite a few places, including geany-plugins.

6 16

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel December 2011