GEdit / Latex Plugin

[watsonja]

Hello All,

I've been trying to install the latex plugin for GEdit (gedit-latex-plugin-0.2-2.fc15. I believe that I've installed it correctly using yum (it shows up as installed when using 'yum list') but I don't see it listed in the gedit preferences -> plugins list after restarting gedit (I've also tried restarting the machine). Have I missed something out?

I'd be happy to provide further details / testing if it will help.

jim

[DBelton]

I get the same results here, but I do get synctex in preferences. synctex is a part of the latex plugin.

I wonder if the changes to gedit for gnome 3 have broken the latex plugin?

I get highlighting on a latex document, but none of the added features of the plugin.

[watsonja]

I believe that synctex is part of the gedit-plugins.i686 package, as when I installed this package synctex appeared in the plugins menu (along with a number of other plugins). I was looking for the functionality provided by the gedit-latex plugin (I miss the auto complete and the abillty to compile from insde gedit).

I'm returning to Fedora after some time spent away with Ubuntu but the prospect to Gnome 3 has got me back again - I'm a little rusty but will continue to look over the next few days to see if I can figure out why it's not working.

best regards

jim

[ycdmdj]

Hi,
I created a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=699034

This should be fixed.

[watsonja]

Hello All,

Does anyone know if Gedit 3 is backwards compatible with Gedit 2 plugins? Looking at the documentation presented on the following page;

https://live.gnome.org/Gedit/PythonPluginHowTo

The format of the plugins has changed quite a bit when compared to Gedit2. All of the plugins that are working appear to have been converted to the later style. Making a few changes to the latest version of the gedit-latex-plugin available from sourceforge I can get the plugin to be displayed in the list of plugins but selecting it brings up a lot of errors. The fact that modifying the text in the .plugin file causes the plugin to appear suggests that the code requires modification. I hope I'm wrong about this and there is indeed a way of introducing backwards compatibility to the plugins as this was my most used application.

jim