Are you by any chance reading in a saved state file (e.g.
0-coot.state.scm)? The command set_default_bond_thickness is written in
the state file too, so this 'trumps' the preference file (maybe it
shouldnt?! up for debate).
B
[ coot 0.6.2-pre-1 2983 miramar via sbgrid ]
[ lucid lynx ]
i
Hi
I have noticed this too - I think it's because when you start coot with the
command line argument '--pdb filename.pdb' the pdb is read *before* coot.py,
coot-preferences.scm or ~/.coot so the bond preferences are only applied to the
next pdb opened from within coot.
Huw
--
Dr Huw
On 15/07/10 09:32, Huw Jenkins wrote:
I have noticed this too - I think it's because when you start coot with the
command line argument '--pdb filename.pdb' the pdb is read*before* coot.py,
coot-preferences.scm or ~/.coot so the bond preferences are only applied to the
next pdb opened from
[ 2nd of two emails in thread - see penultimate ]
aha - using the command line argument '--pdb filename.pdb' is correlated with
my aforementioned confusion.
i.e. launching coot without CLA's indeed respects the user preferences and i
see the expected bond with numbers and graphics.
so is
