On Sun, 18 Feb 2007 05:00:54 -0600, "Jeff Pohlmeyer" <yetanothergeek(a)gmail.com> wrote: Yes, looks quite good. I think I'll add this tomorrow. Seems to be a nice feature and isn't hard to implement. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.key

On Thu, 22 Feb 2007 20:46:11 +0100, Enrico Tröger <enrico.troeger(a)uvena.de> wrote: It took some more days than expected and it wasn't that trivial ;-). But now it's in SVN and should work, at least a little bit. You can define several custom commands and execute them via the edit and/or popup menu in Geany with SVN r1334. This only works if there is a selection. Then the selected text will be written to the standard input of the chosen command and its output on its standard output will be used to replace the selection. If the executed command prints any error messages on its standard error, these messages will be printed on Geany's standard output. My tests worked but I'm sure there might be some bugs in the code, so please test it. The code needs further improvements in the future because there is somewhere a bug when writing and reading the commands pipes. I have workaround'ed it but it needs a fix not only a workaround ;-). Currently, it doesn't work on Windows. Without any investigation, I guess it doesn't work because of the usage of pipes. Maybe anyone knows how to do it on Windows otherwise I would disable it for Windows. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.key

Nice work, Enrico - it looks like a great start! But I'm running into a some problems, along with a few other comments... My system is set to plain old-fashioned ASCII, and the g_get_charset() call in utils_set_up_io_channel() returns "ANSI_X3.4-1968" but apparently g_io_channel_read_line() doesn't like this, it still tries to read UTF-8, which causes it to fail, and cc_iofunc() never finishes reading, which causes something like an endless loop. That smells like a bug in the glib documentation, but at any rate changing the encoding to NULL for g_io_channel_set_encoding() seems to solve the problem. ( That's really weird, because the build commands have always worked fine, I'm not sure why this is any different. ) I also don't think the g_io_channel_read_line() loop is quite right, it seems like it should keep looping as long as it returns G_IO_STATUS_NORMAL or G_IO_STATUS_AGAIN, and the cc_iofunc() should *always* return false, because unless you save the contents of the GString somewhere, it will always get clobbered if the function gets called more than once. Finally, this one doesn't appear to cause any problems, but regarding the write() call in tools_execute_custom_command() the libc documentation says: "Your program should always call write in a loop, iterating until all the data is written." so I think it might be better to make sure all the data gets written, just in case. Here is a patch with the above-mentioned changes, any opinions/feedback are welcome. Regards, - Jeff

On 3/1/07, Enrico Tröger <enrico.troeger(a)uvena.de> wrote: I think the problem is because the channel really should block when no data is available - can you try commenting out line 1218 in utils.c? // g_io_channel_set_flags(ioc, G_IO_FLAG_NONBLOCK, NULL); As far as I can tell, that solves the problem without any side effects. - Jeff

On 2/25/07, Enrico Tröger <enrico.troeger(a)uvena.de> wrote: Enrico, why limit key combos to only the first three? As it happens, I've already got four: 1. rewrap paragraph (fmt) 2. rewrap #-commented paragraph (fmt --prefix=# --width=70) (Note, possible bug: this one only works if I *don't* put single or double quotes around the # symbol.) 3. my own script to create a nice comment box for various heading-type comments. 4. my own script to comment lines by just putting a '# ' at the beginning of each line. Geany's default ``comment lines'' puts the comment symbol right in front of the first non-whitespace character, and I think it's less readable than a nice uniform vertical line of comment symbols right at column 0. So, can we have all 10 (Ctrl-1, Ctrl-2, Ctrl-3, ... Ctrl-0)? Or are they unavailable, or maybe earmarked for some other purpose? If you're a haggling man, how `bout 5? ;) Thanks, ---John

On 3/2/07, Enrico Tröger <enrico.troeger(a)uvena.de> wrote: Thanks Enrico. So, you've pared me back down to 3 for the time being. :) ---John

On 3/2/07, John Gabriele <jmg3000(a)gmail.com> wrote: I didn't read the docs, but perhaps it's talking about single line, as opposed to block, comments. Like // ... versus /* ... */

On 3/2/07, Enrico Tröger <enrico.troeger(a)uvena.de> wrote: Doh. Of course. Though, as long as you make a point to mention it in the docs, for clarity, you might change the note from: ``This setting only works for single line comments.'' to ``Of course, this setting only applies to single-line style comments (as opposed to multi-line).'' Thanks, ---John

On Fri, 2 Mar 2007 13:52:20 -0500, "John Gabriele" <jmg3000(a)gmail.com> wrote: Oops, thank you. Fixed in SVN r1361 and the online documentation is updated, too. Well yes. But the other way doesn't work. If you have "comment_use_indent" set to "true", it makes no difference because multi line comments start always at the beginning of the line. Therefore using of indention makes only sense when using single line comments. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.key

On 3/2/07, Jeff Pohlmeyer &lt;yetanothergeek(a)gmail.com&gt; wrote: Hehehe. :) That's a delightful idea, Jeff. Thanks. That actually would give me fewer key combos to remember. When my little gui dialog pops up, it'll get focus and I can at that point have key combos to choose the little util I want -- while I'm looking right at a list of the names (shown in the dialog). Cool idea. I'm going to try and use this method I think. Another good thing about it is that it doesn't hog up all the Ctrl-<number> Geany key combos. ---John

I have been down loading the SVN tarballs and seeing that the Project additions are beginning to be added. As indicated in a previous email I have an interest in using Geany as a IDE for our undergraduates, hopefully giving a single editor with a simple gui that can be used, at least for the first year or so, for a number of different languages, typically C/C++/Assembler/Octave/Matlab/Basic and possibly Latex. One thing I am interested in doing is running c/c++ both locally and cross compiled and wondered if anything like this planned for your project management, i.e. the understanding of different target directories for different architectures. Also I noticed that the documentation seems to be a 1-2 of verssions behind and wondered one what timescales it might be upgraded. Also if anyone is using or planning to use Geany for teaching and if anyone had written any suitable documentation before we 're-invent the wheel'. Thanks again for all the work being put in on the package, Regards Peter

On 02/19/2007 02:47:29 PM, P.J.G. Long wrote: We're not planning on extending the build system, but we will add support for a project root directory and a project executable. For a build procedure any more complicated than a compile and link, I would suggest using a Makefile. In your case perhaps you could write a default target for the Makefile that builds the code for Linux and a special target, say 'make arm' that builds for the ARM based microcontroller. Then you could use the 'Make Custom' command with the 'arm' argument to cross-compile. We welcome any documentation sent to us for the manual or any tutorials we can link to on the website. I'm not aware of any tutorials yet. There was a short message that mentioned using 'Geany to write small programs with my students', but I don't know what happened after that. http://lists.uvena.de/pipermail/geany/2006-January/000037.html I'd be interested to know how you get on with Geany, and which things could be improved. We are unlikely to implement big feature changes however (although in the medium-term a plugin system is planned). Regards, Nick