My understanding was that Tim uses pythonic extensions - I guess that
this is one of those (rare, I think) functions where the python
preference is not accounted for. I'll take a look - it should be a
I intend to update to guile-gnome at some stage - it was the major
feature/update slated for 0.8.
On 02/03/13 02:39, Tim Fenn wrote:
> This is because coot uses guile-gui, which along with guile-gtk is
> deprecated, no longer has a home and cannot be included/supported with
> fedora releases. So extensions which depend on it (like add strand)
> will fail, while those that don't (like add helix) run OK.
> I'm hoping that eventually these extensions will be updated to use
> guile-gnome (Paul?).
> If these functions are important to you, you'll have to use one of
> Paul's binaries or build it yourself.
> On Fri, Mar 1, 2013 at 2:27 PM, Yogesh Gupta <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
> Hello coot users,
> Recently updated fedora (fedora core 17) and installed coot-0.7
> using binary (coot-0.7-1.20120929svn4458.fc17.x86_64). Coot is
> working normally except in one case when attempted adding a
> strand, i encountered with following error:
> ((safe_scheme_command) Error in proc: key: unbound-variable
> args: (#f Unbound variable: ~S (place-strand-here-gui) #f))
> I ran the script (place-strand-here-gui) manually and that too
> failed with these errors:
> 1) Error in python scripting panel:
> coot >> place-strand-here-gui
> BL WARNING:: Python error!
> (Or you attempted to use an invalid guile command...)
> Python error:
> name 'place' is not defined
> <type 'exceptions.NameError'>
> coot >>
> 2) Error shown in coot terminal window:
> Read OK: /usr/share/coot/reference-structures/1h97.pdb
> INFO:: SSE status was OK
> has 0 sheets
> Strand addition failure: message: Not Done
> Also, there was another error at the beginning in coot terminal:
> load "coot-utils.scm"
> (Error in proc: misc-error args: (#f ~A ~S (no code for module
> (os process)) #f))
> I updated guile package but that did not help. Any suggestions on
> how to fix this?
> I thank you in advance.