I've been happily using Geany for a little while now, coding mostly in
Python. I have a couple questions:
1. For a dark color scheme, eg Vibrant Ink, how do i get the active
line to not be highlighted. White text + white highlighting =
invisible text on the line I'm trying to edit. Arrgh!
2. Any debugger advice for python? I am finding winpdb is pretty slow
and actually crashes on my machine a fair amount.
I'm on a windows 7 64 bit installation.
A musician must make music, an artist must paint, a poet must write,
if he is to be ultimately at peace with himself.
- Abraham Maslow
The default syntax highlighting orange color for strings IMO looks bad.
I wish you would change that default for many languages.
Couldn't you just throw people who like windows editors a bone and have
a GUI for syntax highlighting instead of editing a file?
http://www.fastmail.fm - The way an email service should be
> This said, why did you want to edit filetypes.html/python? If you want
> to change the colors, with 1.22 you can now easily write a colorsheme
> file, look e.g. at the alt.conf scheme distributed with Geany (most
> probably /usr/share/geany/colorschemes/alt.conf on Linux). This way you
> won't have to bother what's in filetypes.* for the colors, and they will
> apply to all filtypes.
I am afraid I have to bother with all this filetypes.* files because if I define
background color for string in colorscheme file, then all the white space in
config files will be filled with that color. See my previous post. The only way -
do not touch filetypes.common (only basic changes) and setup highlighting in
numerous filetypes.* files.
And the question I would like to ask.
What file is responsible for highlighting of bash scripts? I do not see
filetypes.bash. I have filetypes.sh, but changes there do not reflect on bash
I've made a tarball and zip release for Geany-Themes 1.22 file at:
* Improved Solarized light and dark schemes (thanks Joshua Hoff)
* Improved Gedit theme (thanks Jean-Philippe Fleury)
* Improved Dark theme (thanks Harold Aling)
* Remove Alternate (alt.conf) theme since it's shipped with Geany now
* Updated credits and licensing information
I'm hoping to make the releases/tarballs somewhat predictable to make it
easier for distro package maintainers who want to create Geany-Themes
packages. The main version number will follow Geany's and releases in
between Geany releases will have a micro number like 1.22.1, 1.22.2,
etc. Let me know if this format is going to work out or if there's any
other files or something I need to add or re-format to simplify building
If anyone has any original or ported themes they want to include in
Geany-Themes, make a pull request or Github or just email it to me or
While we're close to the subject of the filetypes files, does anyone know why
they are named for example, "filetypes.xml"? Geany seems to know it isn't an
xml file but it does confuse other editors and the file manager.
I would suggest a format such as "xml.conf" and "python.conf" would be more
logical. What do you all think?
Hi translators and friends of Geany,
After 1.22 release of Geany we are on final road to release also
The list of changes done for this release is long and so a lot of
string have changed or were added. I like to ask all translators to
check the translations.
I'd be very happy if you could send a patch, a pull request or single
file with translation to either the geany-i18n mailing list or direct
to me within the next two weeks so we can include it to the next
release. Deadline will be 2012-07-07.
To make it more easy for you I've already uploaded updated versions of
the po files (and now this is new) to git master as well as
1.22_release-branch at github. You can either download the direct via
web or by cloning the repository from
This can be done e.g. with
git clone https://github.com/geany/geany-plugins.git
Also at http://i18n.geany.org/plugins are statistics and daily updated
As mentioned before, we are trying to have all translations complete by
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to
translate same things two or three times. Also please feel to ping me
for every question or if you like to start a new translation for an
Thanks and happy translating
This is my first post in the list and, as usual, i come with a problem ;)
I'm trying to configure the syntax highlighting for asm language with Geany but have experienced some strange issues.
- The more important is that i'm not able to configure the highlighting for comments. I'm trying to use the standard C comments (// for a line and /* */ for a block) using the keywords:
and then configuring a color in [styling] section but Geany always seems to ignore me and only accept the standard asm comment ';' symbol (that in my case i need a different one) although this symbol is not present at all in the file filetypes.asm.
The file i'm modifying is filetypes.asm and my version of geany is Geany Portable 0.20 i'm also using Windows XP SP3. Any idea?
Thanks in advance.
I'm now running Geany 1.22 on Ubuntu 11.10. For some reason, the
interface is now using nn_NO. This locale is not complete, so the
interface is rather confusing. Is there any way to select nb_NO (my
default) or en_US instead?
PHP definitions are ruled in filetypes.html, because inside filetypes.php is
almost nothing but record to see filetypes.html.
OK. I went to filetypes.html. There are groups of definitions which start from
html_, sgml_, php_, jscript_, python_
I changed the settings which start from php_ and indeed my php scripts now look
Then I changed the settings which start from python_ but nothing changed in my
python scripts. And then I realized that maybe there is another file for python,
and indeed the definitions for python are in filetypes.python. And changes there
reflect my highlighting of python script. I also must say that there is no record
in filetypes.python to go to filetypes.html. So, it is like independent file for
1) Why there is a group of settings python_ in filetypes.html, if they do
2) Why there are groups of settings for different languages in one file? It
confuses a lot.
> This is the expected behaviour. You are editing the 'string' named style
> which is used for all filetypes. Instead you should just override a
> style in filetypes.php.
But this is a string, not white space! Why all the white space becomes highligted
Besides, there is a separate definition of white space
but it is not working.
I thought it would be convenient to change the setting one time in
And if I change the setting for string in filetypes.php, why not highlight all
the white space inside php script in pink, according to Geany logic?