{"id":48,"date":"2008-04-26T22:28:17","date_gmt":"2008-04-26T22:28:17","guid":{"rendered":"http:\/\/www.piglets.org\/?p=48"},"modified":"2008-04-26T22:28:17","modified_gmt":"2008-04-26T22:28:17","slug":"geany-and-other-development-tools","status":"publish","type":"post","link":"https:\/\/www.piglets.org\/blog\/2008\/04\/26\/geany-and-other-development-tools\/","title":{"rendered":"Geany and other Development Tools"},"content":{"rendered":"

I've tried lots of programming editors and ides over the years, obviously in Unix and Linux this is a Holy War<\/a>, particularly between the advocates of vi<\/a> and emacs<\/a>. It is common for both groups to suggest that the other editor is hopelessly over-complex or clumsy. I think there's some truth in that, because essentially, they both stink.<\/p>\n

I tend to be an emacsen user myself, but I just think emacs is slightly less awful than vi. My first action on a new install is usually to use vi to edit my sources.list in Debian, to help me install emacs. Perhaps thats strange, because I really like sed<\/a>. So what's the problem with them? They both share this kind of puritanically awkward interface that works well on a console, but sucks in a GUI. They both use ridiculously arcane sequences of key presses to do anything, and I mean even basic stuff like saving and quitting. Yes, yes, you don't have to lecture me about old terminals and their limitations, been there done that, got the t-shirt. I tend to do all my systems maintenance in emacs, but when I'm programming, I've started to love the softness of a decent editor that actually makes it plain and simple to edit multiple buffers of source code, even though its a pain to use different editors for console and gui work.I can't bring myself to love gedit<\/a>, it's just a bit clunky, and I've generally used Kate<\/a> for lots of PHP. It's quite nice, but it's a KDE graft in my otherwise Gnome world, and that causes a few minor annoyances, plus, at least on Debian Kate still doesn't seem to support a PHP symbol browser.<\/p>\n

So, I just tried Geany<\/a> for a few days. I really like it, it's simple, fast, lean, has some nice features like showing a feint line at an indentation level, working PHP symbol browsing (the compile function even runs php -l) on the file to check for syntax errors, simple but neat. I nice VC plugin allows easy diffs, but the VC integration could be nicer. All in all, I think I'll play with it for some more time, but one thing it does annoys me. When I save a PHP file with no new line after the closing characters, it adds one automatically. Bah, I don't like that, I'd do it if I wanted it. Oh, by the way, I also use PySVN Workbench<\/a> for casual subversion<\/a> jobs, it's nice, clear and makes it easy to avoid silly mistakes. I still tend to use the command line for more complex stuff though.<\/p>\n","protected":false},"excerpt":{"rendered":"

I've tried lots of programming editors and ides over the years, obviously in Unix and Linux this is a Holy War, particularly between the advocates of vi and emacs. It is common for both groups to suggest that the other editor is hopelessly over-complex or clumsy. I think there's some truth in that, because essentially, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"vkexunit_cta_each_option":"","footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"enabled":false},"version":2}},"categories":[6,3],"tags":[118,115],"class_list":["post-48","post","type-post","status-publish","format-standard","hentry","category-7-programming","category-3-review","tag-7-programming","tag-3-review"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[],"jetpack_shortlink":"https:\/\/wp.me\/p52I4w-M","_links":{"self":[{"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/comments?post=48"}],"version-history":[{"count":0,"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/media?parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/categories?post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.piglets.org\/blog\/wp-json\/wp\/v2\/tags?post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}