Comments on: gedit 2.19.1

By: Club Silencio » gedit call to arms

Club Silencio » gedit call to arms — Sat, 30 Jun 2007 20:18:51 +0000

[...] 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 [...]

By: michael

michael — Mon, 25 Jun 2007 12:54:17 +0000

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.

By: pbor

pbor — Mon, 25 Jun 2007 12:12:11 +0000

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.

By: michele

michele — Mon, 25 Jun 2007 11:16:59 +0000

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! :-)

By: On Anon

On Anon — Mon, 25 Jun 2007 11:01:32 +0000

“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’?

By: +1 for dark backgrounds...

+1 for dark backgrounds... — Mon, 25 Jun 2007 10:22:44 +0000

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…