Devel August 2011

devel@lists.geany.org

16 participants
37 discussions

Minor problems with plugin API docs
by Matthew Brush 28 Aug '11

28 Aug '11

Hi, There's some stuff in the plugin API docs that are documented but provide no functionality. There's also some stuff that's used by plugins, which is not documented. One example is support.h. This shows up in the plugin API, yet there is nothing available in it. Another example is GeanyFilePrefs, where the struct is documented in the API, but no members are documented. There are some plugins using members of this, despite them not being documented (ex. ao_blanklines.c:67), so maybe we should put them into the documented API. IMO, if a file has no "public" functions or a struct has no "public" members, these should not show up in the API docs *at all*, otherwise it's a little confusing what's available and what's just not documented properly. Any thoughts? Cheers, Matthew Brush

2 3

Geanyembrace: Anybody who like to maintain it?
by Frank Lanitz 27 Aug '11

27 Aug '11

Hi folks, I had a short email conversation with Prim András the original author of geanyembrace.He did not touch this plugin for quiet a long time and doesn't plan to do so in future. Does anybody of you use the plugin and might like to become maintainer? If not, what we going to do with it? Cheers, Frank -- http://frank.uvena.de/en/

4 12

Default snippets
by Alexander Eberspächer 27 Aug '11

27 Aug '11

Dear list, the default snippets that are installed to prefix/share/geany/snippets.conf have C/C++ code in the [default] section. This can lead to C/C++ code in a Fortran file. In the patch attached to this mail, I reorganized the snippets. Default behaviour should not change with this patch [1]. Thanks for taking care. Sincerely, Alex [1]: One exception: people could insert a C++ try{} block into a C. This is not possible anymore.

5 11

Per-filetype indentation settings
by Colomban Wendling 26 Aug '11

26 Aug '11

Hi, Recent bug report #3390435 [1] remembered me about per-filetype indentation settings. This would remove hard-coded settings we have for Makefile and Fortran 77, moving the setting to the filetype definitions, as well as allowing further per-filetype tweaking -- e.g. we could imagine that somebody would like to have Python set to "4 spaces" to follow PEP8. I have come with an initial implementation and would like your wise criticism and design opinions. A few trivial questions: * should the settings be "indent_type" and "indent_width" under [settings] rather than adding a new section? * do you think it's sensible to reset the indentation settings when switch from a filetype that had specific settings? * do you think the filetype-specific settings should override the auto-detection? (the second patch makes auto-detection prevail) So, what do you think of the feature, the implementation, the missing parts, the universe and everything? Cheers, Colomban [1] https://sourceforge.net/tracker/?func=detail&atid=787791&aid=3390435&group_…

2 11

Re: [Geany-devel] [Geany] Expose yellow wavy line in GeanyIndicators
by Dimitar Zhekov 25 Aug '11

25 Aug '11

On Fri, Aug 5, 2011 at 1:32 PM Filip Gruszczyński <gruszczy(a)gmail.com> wrote: > Right now there are only two values in GeanyIndicators. There is a > cool red underline for errors, but it would be even cooler to have a > yellow wavy underline for warnings. Would that be possible for you to > expose such value there? ALL: while on that, woudn't it be a good thing to have underlining for FIF / Find Usage? There is an arrow indicator, but it's only for the clicked line, and the markers margin may be invisible. I'd prefer all matching lines marked, and there is a similar feature request [1]. Of course, it's easier to make it as Liviu suggested (a SCI_SETFOCUS is enough), but I find that confusing - looks like the editor is actually focused - and it's also for the clicked line only. Filip: that yellow looks too bright to me as well. Of course, due to the different color schemes, nothing will look good for everyone. The right thing will be to make it configurable, see GEANY_INDICATOR_SEARCH in highlighting.c for an example. ALL: unlike all other settings, our error underlining is a constant 0xFF0000, though I think the Japanese developers would prefer 0x00FF00. How about making it configurable?.. [1] http://sourceforge.net/tracker/?func=detail&aid=3386140&group_id=153444&ati… -- E-gards: Jimmy

4 20

Re: [Geany-devel] SF.net SVN: geany-plugins:[2161] trunk/geany-plugins/debugger
by Alexander Petukhov 25 Aug '11

25 Aug '11

fixed. Regards, Alex

2 1

Geany-Plugins 0.21: Release plan
by Frank Lanitz 25 Aug '11

25 Aug '11

Hi plugin developers, As we discussed a release for Geany 0.21 around October, 1st I'm thinking also that it would make sense to do a geany-plugins release around this time. Unfortunately I'm not sure, beside the string freeze and translation stuff, which goals need to be matched until release. What do you think? If there are no show stopper I suggest a cycle 2 weeks after Geany core, so release date would be October, 15th. Any opinions? Cheers, Frank -- http://frank.uvena.de/en/

3 5

Geany Newsletter Vol. 3
by Frank Lanitz 23 Aug '11

23 Aug '11

Geany Newsletter #3 ------------------- Contents ======== About Geany Geany Development Bumping dependencies for GTK2 and GLib Plugins Bumping dependencies for Geany-Plugins project at Geany 0.21 and GTK2 2.12 Geany Universe New Geany Wiki Let us introduce you... Plugin Focus Spell Check Feature Focus Line Breaking vs Line Wrapping Line Breaking Line Wrapping People behind Geany -- Interview Columban Wendling About this newsletter 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 http://www.geany.org/ Geany Development ================= Bumping dependencies for GTK2 and GLib ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Starting with SVN r5839 Geany depends on GTK2 >= 2.12 and GLib >= 2.16 to make use of some new features introduced with these releases and to avoid maintaining duplicate code and complicated #ifdef structures. Plugins ======= Bumping dependencies for Geany-Plugins project at Geany 0.21 and GTK2 2.12 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Starting with SVN 2095 the general section of the combined Geany-Plugins project depends on Geany 0.21 and similarly Geany depends on GTK2 >= 2.12. Geany Universe ============== New Geany Wiki ^^^^^^^^^^^^^^ Several weeks ago the Geany wiki was created, in which interesting facts around Geany can be collected. Some pages are still empty and some topics might be missing, but a good start has been made. Check out the pages at http://wiki.geany.org/. Please contribute whatever you can, including your favorite snippets, color schemes etc. Let us introduce you... ======================= This section is intended to introduce particular plugins or features on a regular basis. Plugin Focus ^^^^^^^^^^^^ Spell Check *********** Although Geany is primarily an editor aimed at programming tasks, it's often used to write plain text. All of us would like to think that we can spell correctly but, especially for foreign words, a little help is always welcome: Geany's Spell Check plugin can help, either checking on demand or as you type. To check the spelling of the current document on demand, select Tools > Spell Check > [language] from the main menu. If you often use this feature consider creating a keyboard shortcut to make activating it easier. In case you would prefer to have your spelling checked immediately, enable the "Check spelling while typing" option in the plugin's preferences: Edit > Plugin Preferences > Spell Check. The default language used by Spell Check is configured in Spell Check's preferences. The Spell Check plugin can offer suggestions for misspelled words in the Message window, in the context menu or both. Choose whichever option suits you best by checking the options in the plugin's preferences. Any suspect words are marked with a red squiggly underline. To correct these, right-click on them and highlight the "Spelling Suggestions" item in the context menu. From there you can either select from a list of suggested words, add the word to your personal dictionary or ignore it. You can install extra dictionaries in Myspell format which is especially useful if you're often using words which are not in a standard dictionary. Feature Focus ^^^^^^^^^^^^^ Line Breaking vs Line Wrapping ****************************** In the Document menu are check boxes Line Breaking and Line Wrapping. Although their names are similar, they behave differently. Line Breaking ############# When the Line Breaking option is enabled and you type a word past the "Line breaking column" (set in Preferences), Geany will input a carriage return at the end of the line and put the cursor on the line below. This option is best used with plain text files when you you want to keep every line to a maximum length. It's not recommended for code since you might not notice the line break occur and later have to debug the result. Line Breaking is activated only when you move the cursor past the "Line breaking column" while editing. This means that an already long line will simply get longer if you add text before the "Line breaking column". When this happens you can use the "Reflow Lines/Block" function (in the Edit > Format menu) to adjust all lines so that they're within the line breaking column. Line Breaking must be enabled per document via the menu option Document > Line Breaking. Line Wrapping ############# The Line Wrapping option is similar to Line Breaking but the lines are only wrapped visually; no carriage returns or line feeds are added. This option is best used when you want to be able to see the entire file within the current window. So that it's obvious which lines have been wrapped, a visual indicator is added to the end of each wrapped line. Line Wrapping is very CPU-intensive and can slow down Geany if it's enabled while editing a very large file. If you prefer to have Line Wrapping enabled by default, there is an option for this in the Preferences dialog box Editor > Features. With this option enabled, you can disable Line Wrapping via the menu option Document > Line Wrapping. People behind Geany -- Interview ================================= This is the first 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. Columban Wendling ^^^^^^^^^^^^^^^^^ Thank you to Colomban Wendling for agreeing to an interview and congratulations for being the very first. Now on to the questions... *What motivates you to develop Geany?* I use Geany on a daily basis, so I'm concerned about its development and improvement. I'm also happy to give back a little bit of all the good Geany given me through the years I used it :) And don't be silly: the FAME! :D *Why do you develop for free instead of devoting this time to paid projects?* Philosophy, naivety... Actually I don't "develop for free" if it only means "without being paid", I develop for free "as in freedom" software because I like the ideology behind it. Not being paid is only a concern in the way I need to do some other stuff beside to get money in. What I probably prefer in free software is the fact one can learn from reading the code. It was a great source of help and knowledge when I started learning programming, and it still is. A related thing is the ability to modify the software to better fit my needs, or simply to fix a bug that concerns me. It serves me from time to time (once I discover an annoying bug ^^) and allows me to send back the fix to upstream developers, hopefully helping other users. I won't give all the philosophy behind free software, I think you've got my point :) *Do you do development on other projects that are of interest to you?* Not really beside my personal projects. As said above, I send patches from time to time to developers of software I use, but I'm not really involved in any other project than Geany. *Do you have a favourite Geany feature and if so, what is it?* Most probably the tag completion; but also that almost everything is configurable to fit ones needs. *Do you have a favourite Geany plugin and if so, what is it?* If I'd not fear to sound selfish, I'd say GeanyGenDoc :D Otherwise, SpellCheck without a doubt. *What do you do when you're not developing Geany?* I continue studying programming, or work on personal projects though it's almost the same thing. *What do you use Geany for?* Every one of my programming tasks, and some other text editing. *Do you use any editors other than Geany? (Of course the answer here should be "Absolutely not!" but I'm asking it anyway. :)* I use Nano for commit messages and administration tasks I need to do as root, but for all serious text editing I use Geany. *In which environments do you use Geany?* GNU/Linux (with GNOME), and occasionally Windows (but only when I'm forced to use Windows). 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, Russell Dickenson

1 0

git on the wiki
by Josh 23 Aug '11

23 Aug '11

I just wanted to let everyone know I've started a page on the geany wiki here: https://wiki.geany.org/version_control_options to host some info about vcs' and some web-based tools for viewing/administering/using them. I've outlined what we have (hopefully with accuracy, but I suppose that's why it's a wiki; so we can edit it). I've also just started, so there's only a little info on git and github.com. I'll add more info on other vcs'/websites once I research them. Cheers, Josh

1 0

Use of Scintilla word boundaries for word searches
by Colomban Wendling 23 Aug '11

23 Aug '11

Hi, I'm trying to address bug 3386129 [1], and I'd like comments & reviews about my fix, because the whole thing don't look obvious at all... We already have 2 ways of determining what a "word" is: a manual one using GEANY_WORDCHARS or a caller-given list of wordchars, and one that uses Scintilla's word boundaries. The former seems to make more sense when the caller code knows the kind of characters it wants (e.g. tags lookups), but the latter is better when getting the word to search for. Currently the latter is only used to select the current word, and the second everywhere else we want to get the current word. Actually if we do a whole word search we *need* to get what Scintilla sees as a "word" since we leave the search to it (see bug report for a example of what's going wrong otherwise). So in the attached patch, I added a alternative way to get the the current word (that uses the same algorithm as the word selection) and tries to use it whenever the word was fetched for a search. I'd appreciate reviews & comments :) Cheers, Colomban [1] https://sourceforge.net/tracker/?func=detail&atid=787791&aid=3386129&group_…

4 25

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel August 2011