1,330
edits
Coot: Difference between revisions
Jump to navigation
Jump to search
→Assorted questions and answers (from the mailinglist)
| Line 332: | Line 332: | ||
A: Add (set-show-symmetry-master 1) to the appropriate file. | A: Add (set-show-symmetry-master 1) to the appropriate file. | ||
---- | |||
Q: I still have a ".coot" file in my home folder for a few coot preferences that I couldn't find in the new ".coot-preferences/coot-preferences.scm". There is a warning that I should not add commands to this file. So is a "~/.coot" still the proper place to add default commands for coot? | |||
A: Coot does not create a ~/.coot file for you, but will read it if it exists. Likewise, ~/.coot.py in which you can write python commands.~/.coot-preferences is a directory in which all .scm files and .py files are executed. coot-preferences.scm and coot_preferences.py there are generated by using the Edit -> Preferences dialog (and thus it overwrites older versions - hence the warning). | |||
If you want to create a script that will be read by everyone then put those files into a directory defined by environment variable $COOT_SCHEME_EXTRAS_DIR (for *.scm) or $COOT_PYTHON_EXTRAS_DIR (*.py). All *.scm in $COOT_SCHEME_EXTRAS_DIR and *.py files in $COOT_PYTHON_EXTRAS_DIR will be executed at start up. | |||
So you have a variety of places. Personally I mostly use ~/.coot. | |||
---- | ---- | ||
It should be noted that the answers ("A") are from Paul Emsley himself (and were maybe slightly edited). | It should be noted that the answers ("A") are from Paul Emsley himself (and were maybe slightly edited). | ||