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 125449 - Scripts menu not available if no scripts in scripts folder
Scripts menu not available if no scripts in scripts folder
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: Scripts facilities
3.19.x
Other All
: Low normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 314967 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-10-24 21:56 UTC by Raul Acevedo
Modified: 2021-06-18 15:33 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Raul Acevedo 2003-10-24 21:56:50 UTC
If the scripts folder is empty, the File -> Scripts menu does not appear.

This is a problem for the following reasons:

1.  Unless I happen to see the very last item in the Nautilus docs, I'll
never find out scripts exist or are possible.

2.  The documentation is wrong/unclear.  It doesn't say anything about that
menu item not showing up if there are no scripts.  This led me to waste
time poking around all nautilus menus and property dialogs, trying to find
the Scripts menu, to no avail.

3.  Given that there is no way to access the scripts folder from Nautilus
if you are just starting out, and given that the documentation doesn't tell
you what the magical scripts folder is, I have no way of knowing how to add
scripts to Nautilus unless I've done it already.

Nautilus should either always have the scripts menu available (preferable),
or the documentation should explicitly mention two things:

1.  The scripts menu won't show up unless you already have scripts.

2.  The actual location of the scripts folder, so you know where to put
your first script without having to spend 20 minutes scanning Google to
find out that it's ~/.nautilus/scripts.  Oh wait a minute, that didn't
work, this other search result says it's ~/.gnome/nautilus-scripts.  Oh
wait a minute, that didn't work either, maybe it's this search result,
~/.gnome2/nautilus-scripts.  Oh ok, that worked.

Thank you!

Raul
Comment 1 Daniel Brown 2004-04-05 02:31:11 UTC
*bump*
Comment 2 Matthew Gatto 2004-05-18 21:14:49 UTC
a) I have a ~/.gnome2/nautilus-scripts directory created for me when running
nautilus for the first time with a clean profile (tested on 2.6)
b) "scripts" doesn't show up in the context-menu if you don't have any scripts
in the directory _by design_ since it's an advanced user feature. it would
clutter up the menu for people who don't need or want to use scripts.

As far as the documentation problems for scripts, constructive comments and/or
patches can be added to bug 136779.

*** This bug has been marked as a duplicate of 136779 ***
Comment 3 Joachim Noreiko 2006-01-19 08:32:22 UTC
Reopening. Documentation is updated in Bug 324966, but I also agree that the Open Scripts item should be visible even when no scripts are installed.
Comment 4 Christian Neumair 2006-02-26 08:12:35 UTC
Updating version. Lowering priority, since I think the future of our builtin scripting is not clear based on the success of nautilus-actions.
Comment 5 Cosimo Cecchi 2008-08-30 10:40:36 UTC
*** Bug 314967 has been marked as a duplicate of this bug. ***
Comment 6 Alexandre Franke 2016-01-25 09:23:08 UTC
Do scripts even exist anymore?
Comment 7 Carlos Soriano 2016-01-25 10:59:35 UTC
(In reply to Alexandre Franke from comment #6)
> Do scripts even exist anymore?

Yes.

The only fix to this imho is in docs. Functionality or discoverability of this is not going to be changed.
Comment 8 David Cavallini 2016-05-07 02:19:22 UTC
As a user with both Nautilus and Nemo installed in Ubuntu, I really like the way Nemo fixed this bug: a clear and simple management screen for scripts, actions and extensions.
Comment 9 André Klapper 2021-06-18 15:33:43 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.