Scripts
From UA Libraries Digital Services Planning and Documentation
(Difference between revisions)
| Line 36: | Line 36: | ||
**Check the "Always Open With" box. | **Check the "Always Open With" box. | ||
**Select Utilities>Terminal | **Select Utilities>Terminal | ||
| - | ** | + | **Then click "Open" and you should be good to go. |
''Running Scripts'' | ''Running Scripts'' | ||
| - | *Since the MACs come with | + | *Since the MACs come with many scripting languages pre-installed the scripts are essentially run by double clicking on the file name, although manually launching them from the terminal should work as well. |
**For example: | **For example: | ||
$ python foo.py | $ python foo.py | ||
$ ./foo.py | $ ./foo.py | ||
| - | *In the second case the script AND in the case of double-clicking the | + | *In the second case the script AND in the case of double-clicking the filename, the script would have to include the appropriate shebang line, for example '''#!/usr/bin/python''' for Python scripts and '''#!/usr/bin/perl''' for Perl scripts. |
**This will allow the MACs to know where to locate Python and Perl, respectively. | **This will allow the MACs to know where to locate Python and Perl, respectively. | ||
| - | **If for some reason this doesn't work, make sure the script is saved with a UNIX style byte order so that the shebang will be read properly by the MAC. | + | **If for some reason this doesn't work, make sure the script is saved with a UNIX style byte order so that the shebang will be read properly by the MAC. UTF-8 encoding is also recommended. |
**A good text editor like Notepad ++ (Windows) easily allows one to make these changes to text files. Alternately, saving the file on a Linux or MAC OS station should do the trick. | **A good text editor like Notepad ++ (Windows) easily allows one to make these changes to text files. Alternately, saving the file on a Linux or MAC OS station should do the trick. | ||
Revision as of 21:40, 10 November 2010
All software available from this site uses the Creative Commons BSD License; the license template is available here.
Cabaniss_Software (For the Cabaniss NHPRC project)
Mass_Content_Software (for mass digitization of collection materials to be linked to from finding aid, without manually-created item level metadata)
For Getting batch information about your files
On Making Scripts Work on Mac OSX:
Associating Scripts on the MAC
- To associate files with particular software , CTRL-click on the file.
- Choose "open with". If that isn’t available, choose "open".
- In the Enable box, set the value to "All Applications".
- Check the "Always Open With" box.
- Select Utilities>Terminal
- Then click "Open" and you should be good to go.
Running Scripts
- Since the MACs come with many scripting languages pre-installed the scripts are essentially run by double clicking on the file name, although manually launching them from the terminal should work as well.
- For example:
$ python foo.py $ ./foo.py
- In the second case the script AND in the case of double-clicking the filename, the script would have to include the appropriate shebang line, for example #!/usr/bin/python for Python scripts and #!/usr/bin/perl for Perl scripts.
- This will allow the MACs to know where to locate Python and Perl, respectively.
- If for some reason this doesn't work, make sure the script is saved with a UNIX style byte order so that the shebang will be read properly by the MAC. UTF-8 encoding is also recommended.
- A good text editor like Notepad ++ (Windows) easily allows one to make these changes to text files. Alternately, saving the file on a Linux or MAC OS station should do the trick.
