7

I have installed Nemo (initially a Nautilus fork) in Ubuntu 14.04.1 LTS.

I used to use Nautilus actions with Nautilus. Now that I have installed Nemo, I can't use them anymore.

I was wondering if there is any way to use Nautilus actions and the Configuration tool with Nemo - as it is a fork of Nautilus.

  • Can Nautilus actions be used in Nemo? How?

  • Is the Nautilus actions tool (editor) usable for Nemo?

brunces
  • 659
  • 1
  • 10
  • 17

3 Answers3

2

Found this on the Arch wiki -

enter image description here

.nemo_action files can be used to create menu entries in the pop-up dialog that comes up since these files are read by nemo whenever you right click. You can invoke a script from these .nemo_action files that does your job, similar to what nautilus-actions does.

You can have a look at /usr/share/nemo/actions/sample.nemo_action and /usr/share/nemo/actions/myaction.py to get an idea of how it works. These files have detailed information on what each field in the action files indicates.

You can visit this website for an example.

Edit :

Nemo actions are similar to nautilus actions in content but vary with respect to the extension name.

In nautilus, newly created actions and menus will be stored on the disk as .desktop files.

The nautilus-actions tool, a graphical editor for nautilus actions, will therefore not work with nemo because it looks for .desktop files, not .nemo_action files.

Summary -

Nautilus scripts can be used if invoked by .nemo_action files, just like nautilus action .desktop files did, and these in turn can be adapted for that purpose. nautilus-actions tool is NOT usable for Nemo due to the difference in paths and extension names.

Rohith Madhavan
  • 8,377
1

I use Nemo without Cinnamon on Ubuntu 14.04 using a PPA.

Nemo is much more configurable then Nautilus. Whether or not that is "better" then Nautilus is a matter of taste IMHO. I prefer complex things over simple ones… :-)

That being said, defining your personal Nemo actions or nemo scripts is very straightforward: scripts can be copied verbatim in 90+% of cases and actions can be defined yourself easily (I made my own "Add to VLC" and "Open with BackInTime" in 5 minutes flat by using the provided example) You can also find tons of user-designed actions around the web.

There are tons of extensions readily available, so the need to define your own actions is hardly needed…

A.B.
  • 92,125
Fabby
  • 35,017
1

Summing up what I have learned from the main answer:

  1. Nemo or Nautilus actions are similar in content and purpose (namely, adding menu items) but vary with respect to the extension name. (In nautilus, newly created actions and menus will be stored on the disk as .desktop files, In nemo as nemo_action files.) They invoke certain commands including scripts (which are in this sense called nautilus or nemo scripts). Therefore, nautilus scripts can be used if invoked by nemo_action files, just like nautilus actions did, and these can be adapted for that purpose
  2. The nautilus-actions tool, a graphical editor for nautilus actions, will therefore not work with nemo because it looks for .desktop files, not .nemo_action files.
Community
  • 1