Fix mingw-gcc 'ordered comparison of pointer with integer zero' warning
Update of Slovenian translation by Jože Klepec
Update notes for adding a custom filetype
Improve custom filetype formatting/links
Fix missing warning section
Updated Hebrew translation
Set group for Clojure filetype
Add flag to tm_tags_find() to indicate the tags array may not be sorted

tm_tags_find() relies on a sorted tags array to be passed in but in
tm_source_file_set_tag_arglist() we don't have a sorted array yet and
sorting it on demand seems more heavy than the alternative:
make tm_tags_find() search the array linear if the new flag is set.

This fixes a bug in the Python parser when assigning the argument list
of __init__() methods to their class' argument list which annoyed me
for years already.

Also add a test case for this.
Adjust test case tags file for fixed Python parser (class arglist assignment)
Read filetype's mime type from the configuration files

This allows custom filetypes to define a mime type, hence the icon
displayed for this filetype;  as well as moving ones for built-in
filetypes out of the code to the configuration files.
Use GIcon for the filetype icon rather than rendered pixbuf

This allows to re-use the icon more easily since it's not rendered at
a particular size but simply an icon description.  It also allows for
implicit icon updating when the theme changes if the display code
implements it (and GTK widgets does).
Do not ignore keys inside inherited groups

When inheriting a group in a filetypes file, do not ignore local keys.
This allows for partial overrides of the parent group, like:

	[settings=Parent]
	key=value

All keys from Parent's group "settings" would be imported, but now the
"key" key wouldn't be ignored anymore and would override a "key" key
from the group copied from Parent if it exists.
Update Scintilla to version 3.3.6
Merge branch 'scintilla-update-336'
Update HACKING a bit for C99 standard
If we write C99, we better make sure we compile as such
Add info on how g_spawn is broken on Windows
Plug a possible memory leak

There is no need to check doc->real_path since the usage is NULL-safe,
and if it actually is empty or NULL it isn't a bug in the caller itself
anyway, and this could leak.
Simplify utils_get_hex_from_color() and plug a possible memory leak in it
Plug a possible memory leak