Devel May 2011

devel@lists.geany.org

17 participants
39 discussions

Re: [Geany-devel] Build System User Guide
by Randy Kramer 24 May '11

24 May '11

All, Lex and I have had a little bit of off-line conversation about his document, the Build System User Guide. He suggested that I put it on the wiki. I made a feeble attempt, and now recommend instead that, at least on a temporary basis, it be put on the geany.org website with one or more links from the wiki to the document. This is because: * the document is a fully formed, standalone HTML document * and, in that form, is not directly "pastable" into the wiki Instead, unless I'm missing something, it would have to be copied and pasted in as plain text, and then marked up with DokuWiki markup. Lex, On Tuesday 17 May 2011 08:04:56 pm you wrote: > Well as Enrico says, the document should be located on the Wiki, and > this is the stuff that should go on the page where it is to tell > people what it is. > No grabs, but then it matters less if its on the Wiki and introduced > as above. > > Since you are the Wiki-spurt (well you are writing a lexer for them) > maybe you can create a page with the first cut of the intro and I can > add the document later. Ok, I made a simple minded attempt at putting your document on the wiki. Before I give you the link, let me tell you it is not really worth looking at or what you'd expect. Apparently DokuWiki (if that is the wiki being used) cannot handle html markup. (Foswiki (nee TWiki), can, although it would probably choke on some of the things in your document (like the scripts and CSS).) Thus, to really put your document "in" the wiki, it would have to be copied and pasted as plain text, then marked up with DokuWiki markup. More work than I'm willing to do immediately. Further, I don't know the DokuWiki markup (as opposed to the Foswiki markup, much of which I use every day. So, I recommend that at first, your document not be put in the wiki, but instead be put on the geany.org website, separate from the wiki, as an HTML document, with one or more links from the wiki to the document. Overtime, as people have an interest, they can move all or parts of the document to the wiki and (modify and) mark it up as desired. The wiki page I started is here: http://wiki.geany.org/documentation/programmingfeatures The page designation (/documentation/programmingfeatures) may not fit with a more thought out scheme for the overall organization of the wiki which may be developed (by others), thus that page may get deleted or moved (and, certainly, as you will see, needs modification). I'm sending a copy of this to the mail list to propose that your document be put on the geany.org website separate from the wiki (at least on a temporary basis). Randy Kramer > > Any comments on the documents content would be good too, thats the > main reason for releasing it ATM. Even if its only lousy grammar and > spelling (since Geany's spell checker isn't fixed yet, hi Enrico :-).

4 17

Geany Newsletter Vol. 2
by Frank Lanitz 22 May '11

22 May '11

Geany Newsletter #2 ------------------- Contents ======== About Geany Geany Development Update to Scintilla 2.25 Real-time tag parsing Automatic indentation width detection Fixes to template encoding Plugins New plugins geanycfp GeanyNumberedBookmarks GeanyMacro Other features Significant updates on Split Window Plugin A view onto GeanyVC usage Let us introduce you... Plugin Focus Save Actions Auto Save Instant Save Backup Copy Feature Focus Append Toolbar to the Menu Other screen-space-saving tips Geany local Geany at Chemnitzer LinuxTage (March, 19th-20th) 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 geany.org <http://www.geany.org/>. Geany Development ================= Update to Scintilla 2.25 ^^^^^^^^^^^^^^^^^^^^^^^^ With Subversion revision 5682 another update to Scintilla has been done so Geany's development version is now powered by Scintilla 2.25 in favor of the version previously used: 2.22. As with every update of Scintilla there have been a lot of improvements. This includes changes to Scintilla itself, for example: fixing an issue with marking of a word when double clicking or fixing some memory leaks and unneeded redraws of editor window as well on used lexer e.g. for SQL. A detailed list of changes done with Scintilla can be found at Scintilla ChangeLog <http://www.scintilla.org/ScintillaHistory.html>. Real-time tag parsing ^^^^^^^^^^^^^^^^^^^^^ Parsing of symbols (also known as tags) in the file currently being edited can now be done directly in memory. This change means that tag parsing for the current document happens in real time when the content changes; so the symbol list reflects the actual content of the document rather than the state when it was last saved. This can be configured (and disabled) in the preferences by the `Symbol list update frequency` option under `Editor -> Completions`. Automatic indentation width detection ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Geany now has the ability to detect the indentation width used by a file when opening it, making it easier to work with files which use different indentation widths. The auto-detection, however, doesn't yet work if the file uses a tabs-only indentation type. To enable automatic detection of indentation width, open the Preferences dialog and check `Detect width from file` in the `Editor->Indentation` section. Fixes to template encoding ^^^^^^^^^^^^^^^^^^^^^^^^^^ The encoding of template files is now properly auto-detected, fixing loading of any template using an encoding incompatible with UTF-8. Plugins ======= New plugins ^^^^^^^^^^^ geanycfp ******** Back in January, William Fraser add the geanycfp plugin which adds a couple of interesting new functions to Geany's plugin pool. After some time this plugin has been split up into GeanyNumberedBookmarks and GeanyMacro, but this process is not yet finished. GeanyNumberedBookmarks ###################### The plugin adds an option to store bookmarks in files and directly access them via a keybinding. To set a numbered bookmark press Ctrl+Shift+(a number from 0 to 9). You will see a marker appear next to the line number. If you press Ctrl+Shift+(a number) on a line that already has that bookmark number then it removes the bookmark, otherwise it will move the bookmark there if it was set on a different line, or create it if it had not already been set. GeanyMacro ########## Macros are well known from other tools. Users of Photoshop are always saying how amazing the batch processing is for manipulating images. However, this plugin adds something similar to Geany with its macro feature: the plugin can record small actions and rerun them after pressing e.g. a keybinding. This could be very helpful for example if you need to remove the last two letters of a line and search & replace or rectangle selection are not able to solve the request. Other features ############## Remembering fold states: By default, Geany does not remember the status of folding when reloading a file e.g. on startup. This can be annoying when you have a huge number of nested structures e.g. inside an XML-document. This feature helps you to remember those states so you don't have to fold again after loading. Significant updates on Split Window Plugin ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ There have been quite a few improvements and bug fixes done in the Split Window plugin that ships with Geany which allows viewing two documents at the same time. Code folding is now supported in the split editor as of revision 5626. Since revision 5633, the terminology used in the Split Window menu under the Tools menu has been improved to avoid ambiguity regarding the direction in which the split will take place. Rather than using the word Horizontal for when the editors are laid out horizontally (the splitter is vertical), the words "Side by Side" are now used. Likewise, when the editors are laid out vertically (the splitter is horizontal), the words "Top and Bottom" are now used. Previously, when the Split Window was active and the document currently being viewed in it was closed in the main documents notebook, the Split Window plugin would unsplit, even if there were other documents which could be viewed instead. As of revision 5634, when this happens, the Split Window plugin will switch to view the current document in the main documents notebook instead. If there are no more documents open, the Split Window plugin will unsplit. Probably the most significant improvement to the Split Window plugin is that it will now work on Microsoft Windows. Previously, the plugin was using a trick to work around a bug in the Scintilla widget Geany uses as editing component. A side effect of this workaround was that it caused serious issues on Windows and so the plugin was disabled for the Windows build. Matthew Brush fixed the bug in Scintilla and sent the fix to the Scintilla project where it was merged upstream. Geany is no longer required to use the previously mentioned trick, and so the plugin was re-enabled for the Windows build, with equivalent functionality as it has on other platforms. A view onto GeanyVC usage ^^^^^^^^^^^^^^^^^^^^^^^^^ GeanyVC is one of the oldest plugins of Geany and adds bindings for some popular version control systems to Geany such as Subversion and GIT. To get a feeling which bindings are being used we started a little Doodle poll a couple of weeks ago. The output was interesting and a little surprising: Until the end of April 2011, 33 people took part in the poll and the first surprise was that none of these are using GeanyVC for working with either CVS or SVK. In terms of CVS this has been a real surprise as it was one of the most popular version control systems during the last decades. SVK always took place a role inside 2nd row as its trying to add some offline functionality to Subversion but keeping Subversion inside core. With the introduction of GIT and a number of new features being added to Subversion with version 1.6, the biggest advantages were also went away. However, most users do use the plugin for working with GIT (~90%) followed by Subversion as you can see from the tiny chart at <newsletter.geany.org> Bazaar and Mercurial are also getting used, but only seem to have a minor role in GeanyVC's universe. Let us introduce you... ======================= This section is intended to introduce particular plugins or features on a regular basis. Plugin Focus ^^^^^^^^^^^^ Save Actions ************ The Save Actions plugin adds options available to you when saving files, including: Auto Save, Instant Save and Backup Copy. Each of the options can be enabled independently but they can be even more powerful when used in combination. Read on, discover their functions, and judge for yourself if this plugin might make your use of Geany easier and more productive. Auto Save ######### Auto Save provides an option to automatically save either the current file or all open files at a defined interval. It can be very useful if you tend to forget to save because it works in the background. The default interval is 300 seconds, which is 5 minutes, but you might prefer to set a longer or shorter interval. Instant Save ############ Instant Save aims to make it easier to make use of Geany's file-specific features with newly-created files. With this plugin activated you can specify what file type new files are to be treated as. If you often work with Python for example, and are testing code snippets, you can activate the plugin, configure new files to be treated as Python and Geany's full Python support is available when the file's created. Backup Copy ########### Backup Copy will keep backup copies of files as you save them. Instead of cluttering the file's own directory, the backups are stored in a specific directory. So that you can identify when each backup was created, the backup files have the current date and time added to the end of their names, with the date and time format being configurable. To make finding your backups even easier there is even an option to recreate the directory structure in which the current file is stored. When combined with the Auto Save option, the Backup Copy option can provide a basic form of versioning with a backup copy of your file(s) every time they were saved. A version control system such as GIT, Subversion or Mercurial is definitely recommended instead when possible. Feature Focus ^^^^^^^^^^^^^ Append Toolbar to the Menu ************************** The popularity of the netbook means that many people are looking at screens which are less than the desktop PC sizes of 15 inch and above. A netbook's screen format is usually widescreen, so vertical space is more limited than horizontal space. If you navigate to Edit -> Preferences you'll find an option titled "Append Toolbar to the Menu". Checking this option will result in the toolbar being moved from below the menu bar to beside it, resulting in more vertical space being available. Other screen-space-saving tips ****************************** Geany has several other options which increase the amount of room available for the editing pane. In the View menu you'll find an option titled "Toggle all Additional Widgets" which hides all elements of the user interface except for the menu bar and scrollbars. Also in the View menu is an option titled "Fullscreen" which maximizes the Geany window to take up the entire screen, also turning off the window's titlebar and borders. This view can be especially useful if you want to minimize distractions from other applications. Geany local =========== Geany at Chemnitzer LinuxTage (March, 19th-20th) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Together with the guys of Xfce, Geany was presented with a booth at the annual Chemnitzer LinuxTage event in March, a convention about all topics around Linux, BSD and free software in general. The booth was well visited and people came not only to ask questions or report a bug but also to tell us what they are using Geany for. So Dominic, Enrico and Frank had a lot of questions to answer and a lot of feedback to respond to. 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, Dominic Hopf, Enrico Tröger, Frank Lanitz, Matthew Brush, Nicholas Manea, Russell Dickenson

1 0

allow always save all fix
by Dimitar Zhekov 22 May '11

22 May '11

Hi, With allow_always_save=true, both Save and Save All are always enabled (unless there are no files, of course). Obviously, that makes sense for Save. But what you invoke Save All and there are no modified files? It doesn't save all files regardless of modification, as you may think, nor does it save the current file - in fact, it does nothing, and allow_always_save has no effect on it. So IMHO, en/disabling of Save All should not be affected by the value of allow_always_save. The attached patch does that, and makes the preference changeable, provided that you call ui_save_buttons_toggle() after change (we'll need this when/if the various preferences editor is included in Geany). I also edited the documentation accordingly. But that's enough description for a one-liner... -- E-gards: Jimmy

2 3

[PATCH] Fix some unused variables
by Eugene Arshinov 22 May '11

22 May '11

Hi. I think, this patch is pretty obvious. There is also `dummy' variable in stash_group_add_radio_buttons() which is set but never used, but I'm not sure about it. -- Best regards, Eugene.

2 1

Can't compile Geany with -ansi (va_copy is undefined)
by Eugene Arshinov 21 May '11

21 May '11

Hi, and sorry for spamming this list. I recently tried to compile Geany with -ansi flag as the HACKING file suggests. When compiling mio-memory.c GCC reports a warning that va_copy is undefined, and linker fails with the same message. Should something be done about it? -- Best regards, Eugene.

2 2

[CODE REVIEW] Changes to encodings
by Matthew Brush 19 May '11

19 May '11

Hi all, I was wondering if anyone had time to review some changes I've been working on? There's two commits involved (attached patches and linked below): 1) Allow embedded NUL chars in files (without truncating). 2) Add more regex patterns for guessing encoding. The first one is kind of large and affects several files/functions. One thing I did which should change is in a few places I added a 'gsize tmp_size' var to pass to the encodings_convert_to_utf8* functions, where a simple NULL size parameter would've sufficed, in these cases, the string is known to be NUL-terminated so this parameter isn't required. Unfortunately I made a commit after this so fixing this will come afterwards (though it's not such a big deal). Also, I'm not completely satisfied with the name of the sci_add_text2() function added to the sciwrappers files, but there was already a function named sci_add_text() which truncates the text at the first NUL, and the new function is a more direct wrapper of the SCI_ADDTEXT message. These changes break the plugin API, and would require two small changes to the geany-plugins GeanyVC: geanyvc.c:480 and geanyvc.c:498 as well as GeanyGenDoc: ggd-plugin.c:343. It should be obvious why this breakage was required I hope. The following bug reports are related to the first set of changes: [1][2][3][4]. A few of the comments seem to suggest that it's not desired to support text files containing NUL control bytes, but IMO, it's nice to be able to show these anyway, especially since Scintilla has a nice way of dealing with these. IMO, as long as the file gets marked read-only, displaying as much as possible is better than truncating at the first NUL byte. The second one is a simple refactoring of the code around the regex-based encoding detection and adding a few more patterns to detect a few more types of files. Especially needing review are the actual pattern strings I used since, quite frankly, I suck at regexps. One thing I noticed looking at the bug report here[5], after creating these patches/commits, is that it seems the <?xml ... encoding="" ?> is already supported by the CODING regex, so you can ignore the new XML one I added if that truly is the case (I'll remove it from the proper patch I send in the future). Like I said, my regex skills aren't great :) If you want to use the GitHub UI to review the commits [6][7] otherwise, patches are attached. If you have a GitHub account, you can leave comments on the commits and/or specific lines of the commits. Any feedback would be much appreciated as I plan to submit these changes as proper patches once I've ensured they are good enough. In the meanwhile, I will continue testing... Cheers, Matthew Brush [1] https://sourceforge.net/tracker/index.php?func=detail&aid=3232135&group_id=… [2] https://sourceforge.net/tracker/index.php?func=detail&aid=2893180&group_id=… [3] https://sourceforge.net/tracker/index.php?func=detail&aid=3232135&group_id=… [4] https://sourceforge.net/tracker/index.php?func=detail&aid=2695290&group_id=… [5] https://sourceforge.net/tracker/index.php?func=detail&aid=3183506&group_id=… [6] https://github.com/codebrainz/geany/commit/81c89cce736c88f235761ce5765f2361… [7] https://github.com/codebrainz/geany/commit/5dec6db43b498378be3496d4e8949683…

3 16

Collecting patches inside wiki
by Frank Lanitz 19 May '11

19 May '11

Hi, Not sure whether this is the best idea, but I've jsut created a page inside the wiki at http://wiki.geany.org/patches/review_list where we could collect patches/patchsets to just keep an overview as it appears on this mailing list some patches might get lost due lot of traffic/discussion. Tell me what you think about and maybe make some usage of it ;) Cheers, Frank

5 7

Build System User Guide
by Lex Trotman 19 May '11

19 May '11

Hi All, The confusion shown by Eugenio and others recently has spurred me to finish the attached User Guide to the build system that I started some time ago. This is version 0.1 for review. It is too big to go in the manual but I suggest that it can be put on the website and linked from the manual. Note the attached HTML doesn't include the screenshots yet, but then that helps to keep it small :-) The source is in asciidoc since thats what I started it in, but it can be converted to rest if it is really necessary. Happy reading and all comments welcome. Cheers Lex

4 5

Printing fixes
by Алексей Антипов 17 May '11

17 May '11

Hi everybody, I've recently tried printing come documents with Geany, and the result disappointed me. The right edges of lines would behave their own way, independent on printer settings and my own "field margins" patch. It seemed that the problem was deeper than just printer margins adjustment. After all, I've created a patch containing a major code rewrite for printing.c. The main idea was to make use of Pango functionality for word wrapping and page calculations. That should fix the following issues: - When printing a non-ASCII UTF-8 text, long words go past right edge of the line - Add word wrapping abilities (use pango's WRAP_WORD_CHAR) - Use Pango capabilities to calculate page borders and other things more correctly The only disadvantage of this code is that it takes more time to calculate page borders (i.e. where in text should a new page start). That's so because it would fill Pango layout with text and get its line count, repeating until lines_per_page is reached; all these actions give a more precise result, but are time consuming. I tried printing a 300-page Harry Potter book to PDF file, and the delay between sending a job and print start was several seconds. When printing typical amount of text (25-page formatted C code), the delay is neglectible. Please consider the patch attached and some examples. These are PDF files with "lorem ipsum" printed from Geany in several variations both in English and Russian (2-byte UTF-8 chars). "Old" refer to current version of Geany, while "new" are for version with my patch. The patch should be considered experimental, but, if you are interested in it, I can continue work and fix issues with it, if any Regards, Alexey

1 0

Re: [Geany-devel] Fix crash and memory leak in treebrowser.c.
by Enzo Matrix 13 May '11

13 May '11

Hello, sorry for my laggy response, i have no possibilities to apply and commit the patch in short time, (i am replacing linux with windows last month :( for a while, for doing msaccess and msexcel diploma work). If anybody have spare time to do that, will be great, if no, i think after week i will be ready to get back :) Best regards Adrian Le 12/05/2011 20:33, Thomas Martitz a écrit : > Am 12.05.2011 20:32, schrieb Colomban Wendling: >> The patch looks OK to me, but I wouldn't commit to a plugin without the >> author's agreement. > > Which is why I posted it here in the first place :) I'll wait a bit > longer and deactivate the plugin in the meantime. You can still patch your local copy ^^ And maybe just send a mail directly to Adrian, maybe he doesn't read this ML in a daily basis. Cheers, Colomban _______________________________________________ Geany-devel mailing list Geany-devel(a)uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Devel May 2011