This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revisionBoth sides next revision |
| howto:configure [2014/01/03 15:45] – external edit 127.0.0.1 | howto:configure [2019/01/25 15:03] – ↷ Links adapted because of a move operation oroehrig |
|---|
| The configuration path may consist of several global files if needed, separated by semicolon. The trailing element ''user'' allows the user to store his individual settings permanently in the directory ''~/.polymake''; alternative location may be specified in the environment variable ''POLYMAKE_USER_DIR'' or by putting ''user=~/other/path'' as the trailing element of the configuration path. | The configuration path may consist of several global files if needed, separated by semicolon. The trailing element ''user'' allows the user to store his individual settings permanently in the directory ''~/.polymake''; alternative location may be specified in the environment variable ''POLYMAKE_USER_DIR'' or by putting ''user=~/other/path'' as the trailing element of the configuration path. |
| |
| If the private directory is omitted in the configuration path, the user won't be able to save his private settings between the sessions (the interactive shell input history won't be stored either). This setup might be appropriate for a teaching lab where several students share the same login account. Another sensible use case for this mode is when polymake is called from a program linked with its [[reference:callable|callable library]]. Since the users of such a program doesn't see polymake directly, there might be a good reason for hindering polymake to leave any traces in the user's home directory. | If the private directory is omitted in the configuration path, the user won't be able to save his private settings between the sessions (the interactive shell input history won't be stored either). This setup might be appropriate for a teaching lab where several students share the same login account. Another sensible use case for this mode is when polymake is called from a program linked with its [[:callable|callable library]]. Since the users of such a program doesn't see polymake directly, there might be a good reason for hindering polymake to leave any traces in the user's home directory. |
| |
| The elements of the configuration path may start with ''~/'', designating the user's home directory, or refer to other environment variables using usual syntax ''$NAME''. | The elements of the configuration path may start with ''~/'', designating the user's home directory, or refer to other environment variables using usual syntax ''$NAME''. |