FE Nautilus Scripts

DOWNLOAD page

( FE = Freedom Environment )

FE Home page > FE Downloads page > This 'FE Nautilus Scripts' Download page

! Note ! A few notes here may be touched up or revised occasionally
--- especially after a new release.
In addition, some screenshots (or videos of an install) may be updated.

< Go to 'FE Nautilus Scripts' Download Link and Instructions, below. >
(Skip the Introduction)

INTRODUCTION :

In 2009, I finally 'took the plunge' and migrated my mail, bookmarks, etc. from a (main) Microsoft Windows machine to a (main) Linux machine. I have documented reasons why I went to Linux, along with install notes, on an Ubuntu Install notes page

I do a lot of web page development in which a lot of photos and other image files are processed (renamed, cropped if need be, down-sized, gamma-corrected if need be, thumbnailed, etc.).

Since I could not find a program on Linux that would do all the things I needed to do with directories of image files (such as batch thumbnail making, which I could do with the free 'Irfanview' program on MS Windows), I looked into writing scripts using a couple of ImageMagick commands --- to accomplish those tasks, and even more.

After developing a set of about 20 ImageProcessing scripts, I found that there were at least 10 other categories of scripts that I wanted to develop --- and I found that I could put them in separate directories of my Nautilus scripts directory --- which is the '.gnome2/nautilus-scripts' directory of one's home directory.

I soon had a set of Nautilus utility scripts organized into the categories (and directories) :

  • AUDIOtools
  • EXAMINEfiles
  • FILESlists
  • FINDfiles
  • IMAGEtools
  • LinuxHELPS
  • PROCESSlists
  • SPACElists
  • TERMINALtools
  • VIDEOtools

To see the details of that script-development story (along with images of the code of many of the Nautilus scripts), see the FE Nautilus Scripts Description page.

If it looks like many of those scripts might be useful to you, then, rather than downloading the code images one by one, you can install the several directories of those Nautilus scripts as described in the next section. (The self-extracting install file will almost always be more up-to-date than the code images on the web pages.)

More 'FE Nautilus Scripts', in more categories (sub-directories), may be added in the future .


2011 Feb 04 Update :

I have added a couple of new items to the menu list (directories) above :

  • CHANGEfiles
  • zMORE

as seen in this image of the Nautilus 'right-click-on-file(s)' popup menu.

The 'zMORE' menu item provides a popout to about 17 additional FE Nautilus Script groups (sub-directories), as seen in this zMORE menu image.

Additionally, I have put a 'TEST' sub-directory (sub-menu) in some of the 'FE Nautilus Script groups' --- to hold scripts that I need to test (more).

Since the code is 95% to 100% in place for those scripts to work in a useful fashion, I go ahead and provide those scripts (mainly for me to try them out, on some of my other computers, such as netbooks, when I am on the road).

If the 'TEST' scripts don't work quite right for you, you can simply edit them --- like you can with ANY of the 'FE Nautilus Scripts'.


Using Multi-file scripts:

As I have mentioned in the 'FE Nautilus Scripts' description pages, if I am going to apply a 'multi-file-input' script to a large number of files, say 40, I first apply it to a few, say 3 --- to see if the script is functioning and doing what I want.

If the script goes OK on the first 3 files, then I apply the script to the other 37 files.

I suggest that you use that cautious procedure when performing 'batch' file script applications.

May the shell script force be with you.


    Special note on filenames containing spaces :

    In the 'CHANGEfiles' group of scripts is a script ---

        '00_multiFiles_RENAME_SPACE2underscore_tr-mv.sh'

    --- that I use to put underscores in place of spaces, in filenames that contain spaces.

    That script originally used a

        while test ! -z "$1"
        do
           ...
           shift
        done
        

    technique, instead of a

        FILENAMES="$@"
        ...
        for FILENAME in $FILENAMES
        do
           ....
        done
        

    technique that I used in most other 'multiple-filenameS-input' scripts. The latter technique fails on files whose names have embedded spaces.

      A nice way that we can deal with the embedded-spaces-in-filenames problem is to replace any occurrence of the statements

        FILENAMES="$@"
        ...
        for FILENAME in $FILENAMES
        do
           ....
        done
        

      with the minimalist loop

        ...
        for FILENAME
        do
           ....
        done
        

      This is based on the following section of 'man bash':

               for name [ in word ] ; do list ; done
        
                 The list of words following 'in' is expanded, generating a list of
                 items.  ...  If the 'in word'  is  omitted,  the  'for'  command
                 executes 'list' once for each positional parameter that is set.
        

    The 'SPACE2underscore' 'CHANGEfiles' script has handled any problems that I have had with filenames containing spaces. Hence, until mid-2011 (when I discovered the 'minimalist-for-loop' technique), I did not update the 'FE Nautilus Scripts' (the scripts that have multiple-filenames-input) to eliminate the 'for FILENAME in $FILENAMES' technique --- which fails when encountering a filename containing spaces.

    However, in July 2011, I swept through the FE Nautilus Scripts to replace the 'for FILENAME in $FILENAMES' technique with the 'for-loop-without-in' technique in the various 'multi-filenames-input' scripts. That should fix the spaces-in-filenames 'handling deficiency' in the pre-July2011 'FE Nautilus Scripts' code.

    Starting with the '2011jul15' release, the FE Nautilus Scripts should handle filenames with spaces embedded in the filenames. You can notify me via contact info on the 'Contact' page if you find a script that does not handle spaces in filenames. (You can, of course, edit and fix the code in your copy of the scripts.)


Coming attractions :       (in the months after 2 May 2011)

The 'FE Nautilus Scripts' system is by no means finished. I keep finding utilities that I need, that can be nicely implemented in a Nautilus script. For example, there are still more 'IMAGEtools' that I will add, using the ImageMagick 'convert' command. In particular, I will probably add more utilities that transform or add colors to image files --- with or without embossing, or other decorative (image-enhancing) touches.

In addition, I will be testing some of the file-conversion and video-capture 'VIDEOtools' and moving some scripts out of the 'TEST' sub-directories and removing the string '_PRELIM' from some script names--- if I can verify that they work on a variety of input video files --- of various formats, image dimensions, frame rates, bit rates, etc. (Video tools are a notoriously 'tricky' area on Linux.)

In the 'FINDfiles' category, I find that when I apply some of those 'recursive' utilities on a huge directory structure, it may be almost a half-minute or more before the results list pops up. I would like to be assured, throughout the run, that the script is running. I will probably change those scripts to run the 'find' command in an 'xterm' that pops up at the start of the search. The 'xterm' window will provide a kind of progress bar, showing the names of files being searched.

This 'progress window' will be better than a 'progress bar' that shows filenames being searched, because this 'progress window' will show about 40 filenames at a time, rather than just one at a time. And, by grabbing the terminal scroll bar with your mouse, you may be able to freeze the listing of files and scroll back a few hundred filenames to review some of the files being processed.

In the 'EXAMINEfiles' category, I may promote a few scripts out of the 'TEST' sub-directory. In particular, I want to test a script that compares two directories --- '02_show_DIFF_of2dirs.sh' and/or '02_show_SDIFF_of2dirs.sh' --- because, for example, it will be handy when I want to compare the files in two releases of one of my sub-systems ('FE xpg' or 'FE AppMenus'), by selecting the two release directories, in Nautilus, and then right-clicking and going to the 'EXAMINEfiles' group to initiate the comparison.

In the 'zMORE' categories, I will be adding 3D file conversion utilities to the '3Dtools' group --- and I will be adding 'gnuplot' utilities to the 'PLOTtools' group. And I will be adding various DVD, CD, and USB tools.

Furthermore, in any FE Nautilus Scripts added in the future, I plan to use the 'for-without-in' technique (and other techniques) --- to handle filenames that contain spaces --- even though I usually avoid such filenames myself, by using underscores rather than spaces.

So you see that there are plenty more additions and enhancements coming in the 'FE Nautilus Scripts' system. In fact, it will probably be the case that I will be adding utilities to that system until I die. This FE system may never reach a 'plateau'. So check back here every few months.


2012 Mar 01 Update :   (Naming Convention for the scripts)

After about 2 years of using these scripts and going through 'gyrations' in naming them, I have settled on a naming convention that eliminates most of those gyrations.

The new naming convention is described in detail on a separate NAMING CONVENTION web page.

Basically, the naming boils down to the format

    [part1]_[part2]_[part3]_[part4].sh
where
  • part1 is a sorting and grouping numeric (or alphanumeric) indicator

  • part2 tells what file(s) need to be selected in Nautilus, and, in most cases, is an indicator of whether there are input file(s) --- and, if so, how many and what kind

  • part3 is a function indicator, such as 'RENAME' or 'ROTATE' or 'list' or 'show' (This indicator often has imbedded hyphens or underscores.)

  • part4 is a utilities indicator, to indicate the main utilities and parameters that are used to perform the function (This indicator often has imbedded hyphens or underscores.)

In the past, I was ending up with script names in which there was a 'mash-up' of parts 2 and 3. And part4 was often missing, and I found that I was quite often perplexed without part4.

This naming convention has taken most of the 'gyrations' out of the script naming.

Here are some examples:

  • 00_anyfile_list-manCMDS-TOPICS_man-k.sh
  • 01_anyfile_show-manHELP4topic_man-w-zcat-groff-col.sh
  • 00_anyfile4Dir_start-Gterminal-here_gnome-terminal.sh
  • 00_1imgfile_ROTATE_convert-rotate.sh
  • 01_multi-img-files_CONVERT-TOjpg_convert-quality-100.sh
  • 01_multi-JPG-files_RENAME-JPG2jpg_cut-sed-mv.sh
  • 02a_2files_shoDIFFS-sideByside_sdiff.sh
  • 00_multiFiles_SHOW-with-XPG.sh

One of my main conundrums now is which characters to make upper-case and which to make lower-case. Conundrums like this are relatively minor.

Here is a 'snapshot' listing of the 450-plus (!) 'feNautilusScripts' script names that existed in early 2012.

The 450-plus scripts are in 35-plus sub-directories. The following image shows 3 menu panels (left-to-right): the usual Nautilus right-click-on-file(s) menu, the FE Nautilus scripts menu pop-out with the first 11 categories, and the 'zMORE' menu pop-out with its 24 added categories. (image as of mid-2012)

See many examples of the 4-part script names on the 'feNautilusScripts' NAMING CONVENTION web page, where the script-naming --- especially 'part2' --- is described in more detail.

Note that you have the FREEDOM to rename any of the scripts as you see fit.

'FE Nautilus Scripts' DOWNLOAD LINK and Install Instructions :

The install file is a self-extracting shell script. It would be nice if we could simply name it with a '.sh' suffix. But it appears that most web browsers (or, actually, web servers) will assume that it is an all-text file, when, in fact, it has a gzipped tar file appended to the script portion.

When the web browser asks for the file from the web server, if the file has the '.sh' suffix, the file will be downloaded in 'ascii' mode instead of 'binary' mode. The binary data in the file (the gzipped tar stuff) gets corrupted.

As a workaround, the '.sh' file is provided with a suffix of '.sh.exe' --- in hopes that the web-server/web-browser combo will think the file is a 'binary' file and download it in a 'binary' mode that does not corrupt the file.

    This seems to work. The '.sh.exe' file downloads fine for me, using the Seamonkey2 web browser on Ubuntu 9.10 Linux (the last good Ubuntu release, in my opinion) --- on a little Acer netbook.


* feNautilusScripts *

Right click here, on the link to the '.sh.exe' file, and, in the popup menu of your web browser, choose to save this self-extracting shell script in a download directory on your machine. (Your web browser will offer an option such as 'Save Link Target As ...'.)

 

For good measure (that is, as an alternative), the install file is also provided with the suffix '.sh.tar'. So if the '.sh.exe' file does not work for you (say, the web-server/web-browser 'dance' tries to do something 'funny' with files with a '.exe' suffix), right click here, on the '.sh.tar' file, and, in the popup menu of your web browser, choose to save this self-extracting shell script in a download directory on your machine.


To see the quick version of installing the 'FE Nautilus Scripts', go to the brief SUMMARY section at the bottom of this web page.

To see a movie on how to install 'FE Nautilus Scripts', click here (or right-click and save the movie file to local storage). OR, go to the FE Videos page to see the install videos for the several FE subsystems. The install procedure for each subsystem is similar --- prepare and run a self-extracting script, in 3 quick steps.


    NOTE: The '2015nov14' release of the 'FE Nautilus Scripts' is a fairly mature release --- corresponding to a '0.9', say, release of systems using that kind of release numbering system. In fact, many of the scripts are suitable for 1.0 release.

      The '2015nov14' release might be considered to be a '0.7' or '0.8' release in light of the comments in the 'Introduction' above, where it is pointed out that there are still more additions and enhancements coming. (In particular, I know that I would like to add more scripts to the 'NETQUERYtools' and 'SECUREtools' groups, in the 'zMORE' subgroup of FE Nautilus Scripts.)

      But, in the sense that probably the utilities that I use, and will be using, the MOST have already been implemented, it is correct to say the '2015nov14' release corresponds to a '0.9' release --- or even 1.0.

      In fact, I find myself using scripts in the 'IMAGEtools', 'TERMtools', 'EXAMINEfiles', 'FINDfiles', 'LinuxHELPS', or 'FILESlists' groups on an almost daily basis.

    The 'FE Nautilus Scripts' have not had the benefit of feedback from lots of users. Hence, it would not be appropriate to call the '2015nov14' release a '1.0' release.


    Aiming for a 'mature' release :    (by providing flexible viewing capabilities)

    Many of the 'FE Nautilus Scripts' need a text viewer program to view a text output file. The 'FE Nautilus Scripts' installation includes a common 'include script' to set a TXTVIEWER variable, that is used in any of the FE Nautilus Scripts that need that variable --- that is, in any of the scripts that need the text file viewing function.

    After the install, you should see a file named 'zEdit_VIEWERvars.sh' near the bottom of the 'Scripts       >' menu of Nautilus.

    At any time in the future, you can click on that edit script to edit a common 'include script' file --- named '.set_VIEWERvars.shi'.

      NOTE: The dot prefix makes the '.shi' file a 'hidden' file --- assuring that it will not show in the Nautilus 'Scripts' menu. It is a partial script that does not provide any useful function if you attempt to run it by itself. The suffix '.shi' stands for 'shell include'.

      The 'zEdit' script uses 'zenity' to prompt you for a GUI editor to use --- to edit the '.shi' file. If 'zenity' (a simple GUI prompting utility) is not on your computer, the 'zEdit' script will look for one after another of about 5 popular GUI editors on your computer and use one of those if it finds one. [In any case, you can simply edit the 'zEdit' script and set the editor that you want to use whenever you want to edit the '.set_VIEWERvars.shi' file.]

    The user can choose the text viewer he/she wants to use by editing that one '.shi' 'include' file that contains some simple lines of shell script code --- rather than editing about 100-plus scripts in the 25-plus 'FE Nautilus Scripts' sub-directories.

    There are several example 'TXTVIEWER=' assignment statements. For example, you can use a GUI text editor --- like 'gedit', 'scite', 'kwrite', or 'leafpad'. And there is an example 'TXTVIEWER=' assignment statement for the FE 'xpg' text-file browse/search/extract-all-matches utility. [That is the text viewer that I use.]

    De-comment the 'TXTVIEWER=' statement that you want to use, and comment the others.

    Of course, the user can edit any of the 'FE Nautilus Scripts' and tailor the text viewing utility to be different from TXTVIEWER, for that particular script. In other words, you can over-ride TXTVIEWER in any script.

    You will see several other viewer/editor variables that you can set in that '.shi' 'shell script include file'. Examples: TXTEDITOR, HTMLVIEWER, IMGVIEWER, IMGEDITOR, ANIGIFVIEWER. These variables are used in various FE Nautilus Scripts --- sometimes along with the TXTVIEWER variable or with some other viewer/editor variable. For example, some HTML-generating scripts use both HTMLVIEWER and TXTEDITOR.

    Scan the 'viewer/editor' variables to see which ones you want to change.

      Of course, you could navigate to the '$HOME/.gnome2/nautilus-scripts' directory at any time and edit the '.set_VIEWERvars.shi' file. The 'zEdit' script is not really necessary. But having the 'zEdit' option show in the Nautilus 'Scripts       >' list is a reminder and a convenience --- to make it quite fast and easy to make a different viewer/editor program the default.


The install steps, in detail :

Your home directory or the 'Desktop' directory of your home directory will do, as a download directory. BUT ...

    To keep an organized directory structure, you may find it better to make a directory named 'DOWNLOADS', for example, in your Home directory. Then save ALL your 'third party' application install files there, from then on.

    By 'third party', I mean applications that are not distributed via a monolithic package management system of your Linux/Unix system --- like the FE apps are not.

    Seamonkey2 (a Mozilla.org web browser, son of Netscape) is another example of such an app. In mid-2010, it was not available in the 'Ubuntu Software Center' nor in the 'Synaptic Package Manager'.

    I downloaded the Seamonkey2 Linux install file from the Seamonkey website into my $HOME/DOWNLOADS directory --- and I installed it into a $HOME/apps directory that I created for apps that I want to preserve during Linux upgrades. I preserve the apps simply by not overlaying my home directory (and by backing up my home directory as a precaution).

    Similarly, the FE subsystem self-extracting install scripts can be put in $HOME/DOWNLOADS and installed in $HOME/apps. So the install scripts can be kept in $HOME/DOWNLOADS and the install files are in $HOME/apps --- with a few FE 'config' files in $HOME/.freedomenv, as indicated below.

    So all files of the FE subsystems are in your home directory. The files get backed up if you backup your home directory. Furthermore, the files are preserved (not wiped out) if you preserve your home directory when you update your operating system.

Again, to see the quick version of installing the 'FE Nautilus Scripts', go to the brief SUMMARY section at the bottom of this web page. A longer, more detailed version of the installation instructions is in the following paragraphs.


Preparing the downloaded '.sh' install file for execution :

First, rename the install file --- remove the '.exe' or '.tar' suffix.

    If you are positioned at your download directory with the Nautilus file manager, simply right click on the install file, choose 'Rename' in the popup menu, and use the Backspace or Delete key to remove the last 4 characters from the filename.

    Alternatively, if you are in a terminal window, positioned at your download directory, you can use the 'mv' (move/rename) Linux/Unix command in a form like this :

                  mv  whatever.sh.exe  whatever.sh
    

NOTE:
When you download the self-extracting script file to your file system, it may lose its execute permissions. [This is a nice security feature, making it harder for people to run rogue programs on your computer.] You can make sure the '.sh' file is executable as follows.

  • Navigate to the downloaded install file in the Nautilus file-manager --- if you're not there already.

  • Right-click on it and choose 'Properties' at the bottom of the Nautilus options window that pops up.

  • Go to the 'Permissions' panel on that 'Properties' window and make sure the checkbox labelled 'Allow executing file as program' is turned on.

Altnernatively, in a terminal window, when you are positioned in the directory in which you put the '.sh' install file, issue the 'chmod 755' command on the filename of the self-extracting script. The format :

             chmod 755  whatever.sh


Content of the '.sh' file :

While you are in a terminal window, positioned at the directory which contains the self-extracting install script, you can examine the script lines of the file by issuing the 'head -250' command against the file. You will see about 230 lines of script text (lots of comment lines) --- and then some gobbledy-gook characters in the terminal window. That gobbledy-gook is the starting contents of the gzipped tar file that contains the 'FE Nautilus Scripts' installation sub-directories and files.

The self-extracting script is a combination of text lines and binary data. If you try to view the install script with a text editor, like 'gedit', it will not view the file, because the editor detects the binary data and thinks it is dealing with a binary file. The authors of 'gedit' do not allow you to try to display the file --- partly because 'lines' in (some) binary data files are thousands of bytes long.

However, if you want to examine the '.sh' install file in a GUI file viewer, you could use the 'bless' (a contraction of 'binary less') hex-editor that is available on most Linux systems. Just be sure not to change the file. [I use the 'FE xpg' utility to look at such file contents safely, as described on the FE 'xpg' sub-system download page. Look for the string 'finicky' on that web page.]


How to execute the '.sh' install script :

If you are still in a terminal after doing the 'head' command on the '.sh' file, you could execute the '.sh' file right there via the command line. (See a mouse-click method, below.)

Enter a command of the form

           ./whatever.sh
    

That is, type a dot and slash, then type (or paste) the filename and press Enter.

You will see some output from the execution of the script, including

  • the 'tail' command that is used to extract the gzipped tar file from the entire file --- putting the '.tgz' file in the '/tmp' directory

  • output of the 'file' command applied to the extracted file --- confirming (hopefully) that the extracted file is indeed a 'gzip compressed data' file

  • the output of 'ls -l' on that extracted file --- to show the number of bytes in that gzipped tar file --- should be 4,786,039 bytes in the 2015nov14 file (NOTE: This is about 6 times bigger than pre-2013feb26 versions because we are including several 3D viewer/editor executables in the '3Dtools' group of FE Nautilus Scripts. To conserve storage space, you can remove those executables.)

  • the output of 'tar ztvf' on that extracted file --- to show the 'table of contents' of the extracted file

      (The table of contents will simply be the directory names and filenames that make up the installation --- along with some file permissions information.)

  • a 'cd' command that sets up the 'working directory' of the following un-tar command of the install script --- the 'tar zxvf' command --- at the '$HOME/.gnome2/nautilus-scripts' install directory

  • the output of 'tar zxvf' on the extracted file, which gunzips the file into a tar file and then extracts the contents of that tar file into the install directory

      (The output of 'tar zxvf' will look a lot like the 'table of contents' output, the output of 'tar ztvf' --- but without the file permissions info.)

      (The 't' in the tar command stands for table of contents, the 'x' for extract.)

  • the 'mkdir' commands that make a '.freedomenv' directory in your home directory --- and a subdirectory named 'feNautilusScripts' under that directory --- if they did not exist already.

  • a 'cp' command that copies a 'set_DIR_NautilusScripts.shi' shell 'include' file to the '$HOME/.freedomenv/feNautilusScripts/' directory --- from a 'hidden' '.set_DIR_NautilusScripts.shi' file in the installation 'nautilus-scripts' directory.

      (The 'set_DIR_NautilusScripts.shi' shell 'include' file is code that supplies the Nautilus scripts install directory whenever a Nautilus script needs the directory name to find another utility script.)

Note that the above description amounts to 'full-disclosure' of the install process for the 'feNautilusScripts' subsystem. (More than you wanted to know, eh?)


An alternative to running the install script by typing its name
in a terminal-shell window (namely, a GUI mouse-click method) :

If you are positioned at the '.sh' script (that is, in your download directory) with Nautilus, you could double-click on the '.sh' file --- after making sure that it has execute permission, as described above --- and choose the option to 'Run in a terminal'. You will see the messages described above appearing in the terminal that pops up.

    If the terminal window just flashes and does not stay open (or the installation goes so fast that the terminal window does not even flash), navigate to the '$HOME/.gnome2/nautilus-scripts' directory, and see if the 'AUDIOtools' directory and about ten other 'FE Nautilus Scripts' directories were created.

    Check if the 'AUDIOtools' directory contains some '.sh' script files. If those exist, then the installation probably went OK.


    A NOTE ON SEEMINGLY EMPTY INSTALL DIRECTORIES:

    I did a test install in which the FE Nautilus Scripts directories were created but the scripts did not seem to be put in the directories, even though the messages from the 'tar zxvf' command indicated that the files, as well as the directories, were being extracted from the tar file.

    It turned out that the FE Nautilus Scripts *WERE* in the script sub-directories --- such as 'AUDIOtools' and 'FINDlists' --- but they could not be seen with the Nautilus file manager. On the other hand, I could see the scripts were installed by opening a terminal window and issuing a command like 'cd $HOME/.gnome2/nautilus-scripts' and then issuing a command like 'ls -R'.

    It turned out that I could see the scripts of each sub-directory (in Nautilus) if I clicked on the 'Reload' button (the curled arrow) when in each sub-directory. However, instead of doing that for each sub-directory, it is easier to simply shutdown and then start up your computer and login again. Then you should be able to see the scripts, with Nautilus, in any of the 35-plus FE Nautilus Scripts sub-directories.

    It seems this failure to show the scripts may occur if you remove (or move) a previous version of the FE Nautilus Scripts from the 'nautilus-scripts' directory (using file operations in Nautilus) and then install the new version. The Nautilus file manager seems to keep a 'cache' of pointers to the previously existing script names, and when you install new scripts in their place, the pointers to the new scripts are not updated. Hence Nautilus does not show the new script filenames in its GUI.

    There are ways to avoid re-starting the computer to refresh Nautilus, but probably the least confusing and least tedious way to refresh the Nautilus pointers to the 'nautilus-scripts' files is to simply do the computer re-start and login again.

    Again, before doing the re-start, you could confirm that the scripts were indeed installed by opening a terminal window and issuing a command like 'cd $HOME/.gnome2/nautilus-scripts' and then issuing a command like 'ls -R'.


Where the application files 'land' : (via a safer-than-most install strategy)

When the self-extracting shell script file executes, it automatically puts a set of sub-directories in the 'hidden' directory '$HOME/.gnome2/nautilus-scripts' in your home directory.

Note that you do not have to change to 'root' to do the install. In fact, I never like having to switch to 'root' to do an install.

    When I have to give the root password to do an install, I am being put in the position of having to trust the people who put the install package together that they are NOT going to use that all powerful permission to do serious damage to the root-owned directories and files on my machine.

    And I am trusting that they will NOT install key-loggers or Linux/Unix viruses/trojan-horses on my machine, hidden in that massive directory structure. Or 'they' could install a program, hidden among all those directories, that sends an organization (or person) a notice over the Internet, or do some other useless-to-me thing, whenever I unknowingly run their program (and when I have my connection to the Internet turned on). [I, and my wife, have been a victim of these several things on MS Windows. Now I set up separate 'admin' and 'user' accounts on MS Windows --- like 'root' and 'user' on Linux.]

    Do you hear that? --- HP, Microsoft, Google, and a large number of other software distributors? Cut the nonsense out! At least prompt us, before taking liberties with our computers. For example, let us decide whether we want your programs to start up as part of our computer's boot up process. Maybe we don't want your 'stuff' shoved in our faces every time we log on --- or every time we start up an app in which your (never-going-to-be-used-by-me) stuff has been included as an intrusive plugin. (Are you listening, Mozilla Firefox and Google and Yahoo?? Let ME decide if I want those plugins, up front.)

So rest easy. This install does not require you to open yourself to damage like mangling of your root-owned directories --- nor commandeering of root-owned processes. And nothing is added to your computer's startup processes. YOU are the one who decides when the 'FE Nautilus Scripts' installed components are run.

This install does not ask for an install directory. It uses the '.gnome2/nautilus-scripts' sub-directory that you probably have already, in your home directory.

    NOTE:
    If you are using the new-in-2012 'Caja' spin-off of Nautilus, in the MATE project's spin-off of several Gnome 2.x utilities, then you will need to copy or move the directories and files installed under '$HOME/.gnome2/nautilus-scripts' to '$HOME/.config/caja/scripts'.

    And change the name

      $HOME/.gnome2/nautilus-scripts
      

    in the 'set_DIR_NautilusScripts.shi' script in directory '$HOME/.freedomenv/feNautilusScripts' to

      $HOME/.config/caja/scripts
      


    Having apps like this in your home directory can be a real boon at Linux OS upgrade time. If you follow the procedure of preserving your home directory (in a separate disk partition) during a Linux OS upgrade, then you do not have to re-install the FE Nautilus Scripts, after your Linux upgrade.

    Since these installation files are not in a system directory like '/usr', they will not be wiped out in a Linux system upgrade.

    And even if you allow the Linux OS upgrade to wipe out your home directory, if you simply drag your 'nautilus-scripts' directory onto a USB stick (or some other storage device) before the Linux upgrade, you can simply drag it back to your home directory after the Linux upgrade is complete.


Size of the installation :

After installation, the 'FE Nautilus scripts' files occupy on the order of 6 Megabytes of space. The self-extracting install script is about 4.5 Megabytes in size.

    (Before 2013feb26, the self-extracting install script was only about 0.76 Megabytes in size. It is now much larger because of some 3D viewer/editor executables included in the '3Dtools' group of FE Nautilus Scripts.)

The self-extracting install script extracts the appended, gzipped tar file into install directories that occupy about 6 Megabytes of disk space. This is small compared to applications like GIMP or Firefox.

I contend that you can get a lot of bang, for zero bucks, from this set of about 400-plus small shell scripts.


The sub-directories of the 'FE Nautilus Scripts' install :

The install directories go under the '$HOME/.gnome2/nautilus-scripts' directory --- in a simple, 'flat' directory structure --- only one level of directories.

    [Well, that was the original intention. But now, there is one more level of subdirectories under 'zMORE' --- a category that I added about a year into 'feNautilusScripts' releases --- to keep the list of categories from being too long.

    After a year of adding scripts to the first eleven, top-level categories, I found that I needed to add some sub-categories (sub-directories) to those eleven top-level categories --- to keep the list of scripts in each of those top-level sub-directories to no more than about 20.]

The top-level directory names are

  • AUDIOtools
  • CHANGEfiles
  • EXAMINEfiles
  • FILESlists
  • FINDlists
  • IMAGEtools     (with many sub-categories)
  • LinuxHELPS
  • PROC-MEMlists
  • SPACElists
  • TERMtools
  • VIDEOtools     (with many sub-categories)
  • zMORE     (with about 25 more categories)

There are about 5 to 20 script files in each subdirectory.


Running the FE Nautilus Scripts :

You run these Nautilus Scripts in the usual way: You navigate to an appropriate directory and right-click on a file --- or select multiple files, then right-click. In the popup menu that appears, hold your mouse cursor over the line 'Scripts       >'.

Then you will see the list of 12 'FE Nautilus Script' directory names that are listed above. Slide your cursor over one of those directories. A submenu will open, with the script names showing. Click on the script that you want to run.

    I have tried to give the scripts meaningful names, that indicate their function and/or their input and/or their output. But you can rename them, if the names don't work for you.

    In fact, there are numeric prefixes --- like '00_' and '01a_' --- on the script filenames, so that you/I can make the script names appear in the order you/I like, simply by changing the number/prefix --- that is, by simply renaming the script files in the '~/.gnome2/nautilus-scripts' subdirectories.

The 'LinuxHELPS' scripts and the 'PROC-MEMlists' scripts are rather unique, because those scripts do not pay any attention to the directory and file that you have clicked on.

You can right-click on ANY file in ANY directory (including a directory in a directory) to get to (and execute) the 'LinuxHELPS' scripts, at any time.

The scripts in the 'LinuxHELPS' category give you a way of exploring your computer, quickly, to see what utility programs are on your computer --- along with showing 'man' helps for many of the programs, quickly. The 'LinuxHELPS' file-lists and man-helps are shown in a GUI text browser of your choice.

SUMMARY of the install steps :

The detailed install description above may sound like a lot, but the install takes only a few steps after downloading the self-extracting install script to your computer :

  • rename the file to remove the '.exe' or '.tar' suffix, leaving the '.sh' suffix intact
  • make sure the '.sh' file has execute permission
  • double-click on the '.sh' file to execute it     (or right-click and Open)

and all three of these steps can be done in Nautilus or some other capable file manager. That is, the install can be done with mostly mouse clicks --- rather than using the command line. (The only keyboard use would be the Backspace or Delete key to remove the suffix.)

When you double-click on the '.sh' file, there is no need for a progress bar. The install occurs in about one second.

After the install, remember to use the 'zEdit_VIEWERvars.sh' script, near the bottom of the 'Scripts     >' menu of Nautilus, to set the default VIEWERs and EDITORs that you want to use --- as described above.


To see a movie on how to install 'FE Nautilus Scripts', click here (or right-click and save the movie file to local storage). OR, go to the FE Videos page to see the install videos for the several FE subsystems. The install procedure for each subsystem is similar --- prepare and run a self-extracting script, in 3 short steps.


    If I install a new release of the 'FE Nautilus Scripts' on one of my non-development computers, here is what I do. You may want to use this technique if you download a new release.

    It involves moving the old 'FE Nautilus Scripts' directories (rather than deleting them), to make room for the new ones. This provides a backup --- and the old scripts are available for comparison/reference. I may keep the old ones for a few weeks, or more. (A few Megabytes of disk space being used is not enough to worry about.)

    In the '~/.gnome2/nautilus-scripts' directory, with Nautilus, I make a new subdirectory named something like '.NautilusScriptsFE_OLDyyyymmmdd', where 'yyyymmmdd' (or 'yyyymmm') is a date like the approximate release date of the old release.

    Then I drag the old 'FE Nautilus Scripts' directories --- AUDIOtools through VIDEOtools, and zMORE and a couple of 'VIEWERvars' files --- into the 'OLD' directory.

    Note that I used a 'dot' ( . ) on the front of the directory name '.NautilusScriptsFE_OLDyyyymmmdd'. This is so that that directory name does not show up whenever I open the Nautilus 'Scripts      >' menu.

    Then I simply do the installation as described above --- namely, download the '.sh.exe' self-extracting script into a download directory and perform the three simple steps to extract it.


For more info on the nature of the 'FE Nautilus Scripts' and how they are organized and used, please see the 'FE Nautilus scripts' Description page.

Sample images of the code in many of the scripts are available via that page. (Some of those code images may be out-of-date compared to the scripts in the install file of this page.)

You can browse the comments in any of the scripts to see their purpose and to see any unique considerations on how they can be run. And examine the 'guts' (code) of the scripts. Pick up script writing tips. (Or think about the way you would write the scripts, to improve on them.)

Just in case the latest release of the FE Nautilus Scripts is deficient in some way, here are some of the past releases of the self-extracting-script files. They can be installed using the simple 3-steps described above.

Simply right-click and use 'Save Link Target As...' (or the equivalent) to save the self-extracting-script to your downloads directory.

"FE . . . . Software that Scratches Where It Itches."

Bottom of the FE Nautilus Scripts Download page.

To return to a previously visited web page, click on the
Back button of your web browser a sufficient number of times.
OR, use the History-list option of your web browser.
OR ...

< Go to Top of Page, above. >

OR ...

< Go to the FE Home page >

Page created 2010 Aug 22. Changed 2015 Nov 14.