gedit 2.19.1

First of all, congratulations to Paolo Maggi, who just became father for the second time… I guess that this will leave him little time to work on gedit, but that is surely a more important “release” :-)

I am distchecking gedit 2.19.1 as I write, this will be the first developement release that features the port to the new version of gtksourceview, so to install it you will need gtksourceview 1.90.1 and pygtksourceview 1.90.1

gedit, new highlighting features

Casual gedit users will not probably note any substantial changes, but if you use gedit to code or to write latex or for any other syntax highlighted language you will take advantage of the new features. Chances are that you will also spot some regressions in the highlighting of your favourite language, so please help us improve the .lang files since we do not know the details of all the syntaxes we can currently highlight: lang files are shipped in gtksourceview and are located in $PREFIX/share/gtksourceview-2.0/language-specs.

The .lang file format is documented on the wiki: http://live.gnome.org/GtkSourceView/NewLangFormat

Obviously even if you don’t spot any regression, there are also plenty of improvements that could be made: since most of the lang files have just been converted from the old format, they do not take advantage yet of the new features of gtksourceview. New lang files are also more than welcome.

The gtksourceview upgrade also affects plugins: if you had any plugins using (py)gtksourceview directly, they need to be updated to the new gtksourceview api.

From the UI point of view, the gtksourceview upgrade affects syntax highlighting color configuration: if you ever tried to customize the syntax highlighting colors from the current gedit preference dialog you know how painful that is. You need to set the style seprately for every tag of every language you use… gtksourceview 2 instead supports style scheme files.

At the moment I totally removed the Syntax Highlighting colors configuration page from gedit preference dialog, but we need to put back a way to at least switch style schemes. A style scheme editor would be nice too, but it requires to design a sensible UI… suggestions are welcome. For now you can set the sytle scheme used changing the /apps/gedit-2/preferences/editor/source_style/scheme gconf key and you can add your own style scheme files in $PREFIX/share/gtksourceview-2.0/styles or in ~/.local/share/gtksourceview-2.0/styles.

At the moment just two styles schemes are included in gtksourceview one called ‘gvim‘ (similar to gedit default colors) and one called ‘kate’, similar to kate default colors… I would really love to have at least a dark-background style scheme, a style scheme using the tango palette and an emacs-like style scheme. Please create and share with us your style scheme!

6 Responses to “gedit 2.19.1”

  1. +1 for dark backgrounds... Says:

    Lots of people, like me, use gvim or emacs just for its good dark background color scheme, that’s very important when you stay too many hours programming or editing files…

  2. On Anon Says:

    “At the moment just two styles schemes are included in gtksourceview one called ‘gvim‘ (similar to gedit default colors) ”

    Does the gvim scheme have a similar colour scheme to gedit defaults? Or should that be ‘similar to gvim default colors’?

  3. michele Says:

    Here you find the best (IHMO) dark color scheme for (g)vim:

    http://www.vim.org/scripts/script.php?script_id=1464

    Would be cool to have this inside gedit! :-)

  4. pbor Says:

    Does the gvim scheme have a similar colour scheme to gedit defaults? Or should that be ’similar to gvim default colors’?

    gedit defaults colors have always been similar to gvim default colors.

  5. michael Says:

    First off, I have been unable to use GEdit for latex until now, just gave the latest trunk version a try and it works really nice now, thanks!

    I also began work on a tango color scheme… so far I converted the gvim scheme to tango. The only problem I see here becomes very visible in a XML document, because tango’s purple colors are not easily distinguishable on small fonts…

    Also, I filed bug #450868, which would help the maintainablility of color schemes.

  6. Club Silencio » gedit call to arms Says:

    [...] was in the list that Lucas posted, but that was in part due to the fact that we were working on the gtksourceview 2 port and release was blocking on that. That said, lack of time and manpower is a real issue for gedit [...]