<?xml version="1.0" encoding="utf-8" ?> <!-- for emacs: -*- coding: utf-8 -*- -->
<!-- Apache may like this line in the file .htaccess: AddCharset utf-8 .html -->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN" "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg-flat.dtd" >
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head><title>setup</title>
<link rel="stylesheet" type="text/css" href="../../../../Macaulay2/Style/doc.css"/>
</head>
<body>
<table class="buttons">
<tr>
<td><div><a href="_setup__Emacs.html">next</a> | <a href="_set__Random__Seed_lp__Z__Z_rp.html">previous</a> | <a href="_setup__Emacs.html">forward</a> | <a href="_set__Random__Seed_lp__Z__Z_rp.html">backward</a> | up | <a href="index.html">top</a> | <a href="master.html">index</a> | <a href="toc.html">toc</a> | <a href="http://www.math.uiuc.edu/Macaulay2/">Macaulay2 web site</a></div>
</td>
</tr>
</table>
<hr/>
<div><h1>setup</h1>
<div class="single"><h2>Synopsis</h2>
<ul><li><div class="list"><dl class="element"><dt class="heading">Usage: </dt><dd class="value"><div><tt>setup()</tt></div>
</dd></dl>
</div>
</li>
<li><div class="single">Consequences:<ul><li>Initialization files for emacs and the standard command shells will have lines added to them to allow the Macaulay2 files to be found. A missing initialization file will be created only if doing so will not prevent the command shell from reading further initialization files. The user is prompted before each file is modified and offered the opportunity to review or reject the changes.</li>
</ul>
</div>
</li>
</ul>
</div>
<div class="single"><h2>Description</h2>
<div><p>Backup files are made carefully, and if a mangled initialization file is detected, it will not be modified. The lines added are bracketed by comment lines containing the phrases <tt>Macaulay 2 start</tt> and <tt>Macaulay 2 end</tt>.</p>
<p>The initialization files will contain added commands that add the appropriate directory to the front of the environment variable <tt>PATH</tt> so the program <tt>M2</tt> can be found, unless that directory already occurs in the path, in which case it does not check whether that directory is the first one on the path containing a program whose name is <tt>M2</tt>, for fear of escalating a competition with another init file. (The expert user may prefer to remove those commands and instead, to create a symbolic link from a directory already on their path to the program <tt>M2</tt>.)</p>
<p>The other environment variables affected are <tt>MANPATH</tt>, <tt>INFOPATH</tt>, and <tt>LD_LIBRARY_PATH</tt>.</p>
<p>This function is intended to be run only by users, not by system administrators, nor on behalf of users by system administrators, because system administrators can easily install Macaulay2 in such a way that the files can all be found.</p>
</div>
</div>
<div class="single"><h2>Caveat</h2>
<div>Warning: there is at least one important situation where you will not want to run the Macaulay2 <tt>setup()</tt> command. For example, suppose you have installed M2, not in its own private location as described above, but in a directory with many other executable files. Suppose also that your account is adapted so it will run programs correctly on hardware of more than one architecture, or on differing operating systems, or even on various releases of the same operating system. Then <tt>setup()</tt> will modify your command shell init files so the directory containing M2 will the first one searched when looking for a program. If you then try to use your account on different hardware, incorrect programs may be found, namely, those in the same directory as M2. Similarly, incorrect sharable libraries may also be found.</div>
</div>
<div class="single"><h2>See also</h2>
<ul><li><span><a href="_setup__Emacs.html" title="">setupEmacs</a></span></li>
</ul>
</div>
<div class="waystouse"><h2>Ways to use <tt>setup</tt> :</h2>
<ul><li>setup()</li>
</ul>
</div>
</div>
</body>
</html>
