nautilus-script-* scripts not enabled upon installation

Bug #31776 reported by Matt Galvin
30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus-script-manager (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

The various nautilus-script-* scripts should be enabled upon installation. Since these are scripts to bring command line functionality up to the GUI, a user should not be expected to have to go to the command line to figure out how to get these tools to work. Esspecialy b/c in this case the user may not know to look for nautilus-script-manager.

IIRC these scrips use zenity... since a nautilus restart is require for the enabled scripts to be used, maybe a simple zenity --notification would be a nice way to tell the user to log out and back in again to enable the functionality.

Revision history for this message
Lukas Fittl (lfittl) wrote :

The reason why I wrote nautilus-script-manager, is that we don't have a global nautilus scripts directory and installation to a user's home directory is not possible. This could be fixed by simple patching some stuff into nautilus before feature freeze, but my gnome and gtk2 knowledge is very limited..

Revision history for this message
Denis Moyogo Jacquerye (moyogo) wrote :

nautilus-script-* should not always be enabled upon installation. Some users on a machine might not want those scripts.

For me it would be better if there was a tab in the nautilus preferences where users could enabled or disable nautilus-scripts. This would probably need some gconf magic for admins to be able to set defaults.

Revision history for this message
Lukas Fittl (lfittl) wrote :

Thats exactly what I wanted to do, and hopefully I will find time to get this feature into edgy.

Revision history for this message
Thomas Schwinge (tschwinge) wrote :

I'd also like to state the need for such a functionality that either the scripts are enabled by default or at least that there is a way to get them enabled without using the command line.

Revision history for this message
Áron Sisak (asisak) wrote :

I wrote a small script to handle this bug.
Please make comments about is.

You can find it at Bug #81435

Changed in nautilus-script-manager:
status: Unconfirmed → Confirmed
Revision history for this message
Lukas Fittl (lfittl) wrote :

The solution I would prefer is patching nautilus to have a configuration area for scripts as mentioned above, your solution can't be integrated into a package unfortunately, because packages can't contain data for user home directories.

Revision history for this message
Scott Wegner (swegner) wrote :

I also find it unintuitive to need to enable a script even after it is installed. I just installed nautilus-script-collection-svn, and couldn't figure out for the longest time why I couldn't access the script.

Enabling by default would be tricky because it is a user-level setting. Perhaps a better idea would be to give the user some notification message after install, explaining how to enable the script (and similarly, some GUI front-end to nautilus-script-manager would be useful). I imagine the notification happening similar to the dialog presented when Firefox is upgraded ("Please restart Firefox for updates to take effect...").

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.