| Next revision | Previous revisionLast revisionBoth sides next revision |
| tutorial:shell_custom [2019/01/22 17:13] – external edit 127.0.0.1 | user_guide:howto:shell_custom [2019/01/25 16:02] – ↷ Links adapted because of a move operation oroehrig |
|---|
| ===== Customizing the polymake shell ===== | ===== Customizing the polymake shell ===== |
| |
| Here we won't speak about really mighty features like defining own rules or object types; they are described [[reference:rulefiles|elsewhere]]. Instead we'll start with tiny, easy to use tools of fine-tuning. | Here we won't speak about really mighty features like defining own rules or object types; they are described [[user_guide:extend:rulefiles|elsewhere]]. Instead we'll start with tiny, easy to use tools of fine-tuning. |
| |
| ==== Custom variables ==== | ==== Custom variables ==== |
| |
| -- All definitions are repeated in a text file residing in your home directory: ''~/.polymake/customize.pl'' . You are invited to load it in your favorite text editor and study its contents. The variables are sorted there first by applications, then by package names. Most of them will appear as deactivated (that is, the lines start with ''#'' which is the perl fashion of making comments to programs). This means, the default values assigned to them somewhere in the polymake source code are in effect. If you want to change them, simply remove the ''#'' sign and fill in your desired value. By the way, the color values don't need to be entered in numerical RGB notation; any color name listed in the system color list addressed in ''$Visual::Color::RGBtxt_path'' can be used instead. | -- All definitions are repeated in a text file residing in your home directory: ''~/.polymake/customize.pl'' . You are invited to load it in your favorite text editor and study its contents. The variables are sorted there first by applications, then by package names. Most of them will appear as deactivated (that is, the lines start with ''#'' which is the perl fashion of making comments to programs). This means, the default values assigned to them somewhere in the polymake source code are in effect. If you want to change them, simply remove the ''#'' sign and fill in your desired value. By the way, the color values don't need to be entered in numerical RGB notation; any color name listed in the system color list addressed in ''$Visual::Color::RGBtxt_path'' can be used instead. |
| .. Some variable definitions appear accompanied by a preceding line of the form ''ARCH('//xyz//')'' . These are special in that they are dynamically set by auto-configuration routines lurking in some rule files, and therefore potentially dependent on the computer architecture. (Recall that you may use polymake on alternating computer platforms having different paths to programs etc.) The preferred way of changing these variables is to use the ''[[general#Configuration|reconfigure]]'' command as described below, because with some of them additional consistency checks may be associated. But in many cases they can be easily edited as well. | .. Some variable definitions appear accompanied by a preceding line of the form ''ARCH('//xyz//')'' . These are special in that they are dynamically set by auto-configuration routines lurking in some rule files, and therefore potentially dependent on the computer architecture. (Recall that you may use polymake on alternating computer platforms having different paths to programs etc.) The preferred way of changing these variables is to use the ''[[..:general#Configuration|reconfigure]]'' command as described below, because with some of them additional consistency checks may be associated. But in many cases they can be easily edited as well. |
| .. A few variables are stored in a different file: ''~/.polymake/prefer.pl'' . They are separated from the rest because they don't belong to any application but rather control the universal facilities like history editing in the interactive shell or locating extensions. When specifying various search paths, you may use ''~'' as an abbreviation for your home directory; other environment variables can be referred as ''$ENV{//name//}'' | .. A few variables are stored in a different file: ''~/.polymake/prefer.pl'' . They are separated from the rest because they don't belong to any application but rather control the universal facilities like history editing in the interactive shell or locating extensions. When specifying various search paths, you may use ''~'' as an abbreviation for your home directory; other environment variables can be referred as ''$ENV{//name//}'' |
| .. Please remember that you shouldn't edit any of these files as long as a polymake process is running anywhere under your account. Sometimes polymake needs to store some changes there on its own behalf, but this happens immediately before the exit; so either your or polymake's changes will definitely be lost. | .. Please remember that you shouldn't edit any of these files as long as a polymake process is running anywhere under your account. Sometimes polymake needs to store some changes there on its own behalf, but this happens immediately before the exit; so either your or polymake's changes will definitely be lost. |
| :: restore the default value | :: restore the default value |
| .. Both commands come into effect immediately, but also mark the variable as changed, so that the new value will also appear in your personal customization file after the session end. You can also change the custom variables for the rest of current session only, without updating the file -- by a plain assignment. If you want to change some value temporarily, just to influence the evaluation of the next expression, write the ''local'' keyword instead of ''set_custom''. (It's not polymake's black magic, just normal perl operator.) | .. Both commands come into effect immediately, but also mark the variable as changed, so that the new value will also appear in your personal customization file after the session end. You can also change the custom variables for the rest of current session only, without updating the file -- by a plain assignment. If you want to change some value temporarily, just to influence the evaluation of the next expression, write the ''local'' keyword instead of ''set_custom''. (It's not polymake's black magic, just normal perl operator.) |
| | |
| | === Configuring applications === |
| | There are two custom variables related to applications. The list ''@start_applications'' contains names of all applications to be loaded at the very beginning of the interactive session (although the process of loading applications is totally transparent to you, having loaded your favorites in advance avoids annoying delays during the session). The variable ''$default_application'' names the application to be made current at the beginning of the session. Until you change this, it will be ''polytope'' for its undisputed merits as the oldest and most prominent application in polymake. |
| |
| ==== Preferences ==== | ==== Preferences ==== |