From: Daniel Russel (drussel_at_gmail.com)
Date: Tue Feb 04 2014 - 10:13:28 CST

It was just one plugin, and you are right that works, sort of. I had been
testing things by trying to open a file from the command line using the
plugin and hadn't noticed that the plugin loads, just after the file fails
to open. Is there some way to get that to work? Thanks very much.
         --Daniel

On Mon, Feb 3, 2014 at 2:52 PM, John Stone <johns_at_ks.uiuc.edu> wrote:

> Hi,
> From your email it's not clear if you're asking about loading
> just one extra plugin, or an entire collection? If you're just
> loading one or a handful, it is quite easy, and you can do something
> very simple like this in your .vmdrc:
>
> if { [vmdinfo arch] == "LINUXAMD64" } {
> puts "Loading Lattice Microbe plugin..."
> vmd_plugin_scandirectory
> /Projects/vmd/testfiles/lm/lm-2.0/Build-thor/lib *.so
> }
>
> Cheers,
> John Stone
> vmd_at_ks.uiuc.edu
>
> On Mon, Feb 03, 2014 at 02:04:55PM -0800, Daniel Russel wrote:
> > Is loading molefile plugins from some place other than the VMD plugins
> > directory something that is currently supported? If so, what is the
> best
> > procedure? A couple of us have tried various permutations on `set
> > auto_path` and `vmd_plugin_scandirectory`-based approaches without any
> > success so far (with a plugin that loads fine if dropped in the vmd
> > plugins dir of an install). If those are supported, do things like the
> > directory structure under the provided path matter? That is, does
> there
> > need to be an analogue to the vmd plugins directory or can I just
> point
> > the directory containing the .so.
> > On linux. VMD 1.9.1.A
> > Thanks.
>
> --
> NIH Center for Macromolecular Modeling and Bioinformatics
> Beckman Institute for Advanced Science and Technology
> University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
> http://www.ks.uiuc.edu/~johns/ Phone: 217-244-3349
> http://www.ks.uiuc.edu/Research/vmd/
>