After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 313834 - new shell script plugin
new shell script plugin
Status: RESOLVED WONTFIX
Product: gedit-plugins
Classification: Other
Component: General
2.11.x
Other All
: Normal enhancement
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2005-08-18 13:21 UTC by Rafael Jannone
Modified: 2019-03-23 20:54 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
plugin code (18.31 KB, text/x-csrc)
2005-08-18 13:23 UTC, Rafael Jannone
Details

Description Rafael Jannone 2005-08-18 13:21:41 UTC
This plugin allows for gedit to have a dedicated scripts folder, just like
Nautilus. The contents of this folder is then monitored via GnomeVFS and updated
in real time onto the "Tools" menu in gedit.

When any of these scripts is activated, the current gedit selection is
redirected to their stdin, while their stdout is directed to the document
itself, making for a good way of filtering/generating text.

Also, stderr is presented using the gedit output panel (which is only visible
when at least one line is sent to stderr).

There are some things to be fixed and reviewed yet. Look for "fixme"s in the code.
Comment 1 Rafael Jannone 2005-08-18 13:23:15 UTC
Created attachment 50913 [details]
plugin code
Comment 2 Paolo Borelli 2005-09-25 14:31:02 UTC
Hi Rafael, sorry for not having responded sooner at this bug report, but we have
been really busy in  the last period.

Unfortunately I haven't really had time to look at your plugin, but I wanted at
least apolgize for that and underline that this kind of work is appreciated. I
urge you to publish your plugin if you feel is mature enough to be useful for
other people: we'd love to have a more active plugin community outside of the
set of plugins shipped with gedit itself.

I also wanted to notice that all our current work is happening on the
http://live.gnome.org/Gedit_2fNewMdi branch which includes a substantial rework
of the plugin system, thus making the old plugin obsolete: this is a bit
unfortunate for the people that have already developed a plugin for the old
interface, but it was long overdue and we are confident that it will be better
in the long run
Comment 3 Rafael Jannone 2005-09-26 20:27:24 UTC
Hi Paolo,

I understand, and I'll be looking into porting the plugin to the new branch (if
it fits).

Hmm, what does "publish" mean in the plugin context?  I mean, the code is
attached... Do you want me to make sure it works, so that it'll enter CVS?

Thanks for your appreciation.
Comment 4 Paolo Borelli 2005-09-26 21:21:06 UTC
I mean that with the new plugin system in place we commit ourself to a well
established public interface and we very much welcome external plugins to be
published outside of the gedit tarball: just tell us the web page and I'll link
it on gedit.org.

We could also decide to recreate a gedit-plugins external cvs  module that
collects the more useful/common plugins.

The problem with including all the plugins in gedit itself is that we don't have
enough time to maintain a huge collection of plugins
Comment 5 Paolo Borelli 2005-09-26 21:25:42 UTC
By the way, as of today plugins can be developed in python :)

[maybe you don't care about it, but it's so cool I had to say that!] 
Comment 6 John Pye 2005-10-07 07:52:12 UTC
I tried following your steps for installing the plugin above, following the
instructions at http://live.gnome.org/Gedit_2fNewMDIPluginHowTo on the Wiki. I
wanted to help out by packaging this plugin. 

I found I couldn't compile either the old 2.8.1 (latest FC3 src rpm) or the
latest (2.12.1) versions. For reasons like that, I'd advocate that as far as
possible you integrate new plugins like this one into your CVS. You might want
to mark them as experimental, that's fine. But make sure they get included into
the main distros so that we don't all have to fiddle about to get them working.

Maybe it's time I moved up to a newer distro...
Comment 7 Rafael Jannone 2005-10-07 14:52:21 UTC
Hi John, thank you for your interest. The plugin was developed on Gedit 2.11. I
believe you'll just need the gedit-dev package to compile it (along with some
GNOME dependencies, like the GnomeVFS dev package).

Notice it has not yet been ported to the new plugin API on CVS (the
Gedit_2fNewMDIPlugin stuff), since it's radically different.
Comment 8 Rafael Jannone 2005-10-08 19:16:58 UTC
Check this out, I have just made a tarball for the plugin:

http://jannone.org/shellscript/

Hope it helps...
Comment 9 Paolo Maggi 2006-03-04 18:02:18 UTC
We are moving all the request for plugins that we don't plan to add to gedit
itself on live.gnome.org/Gedit.

Closing as WONTFIX.