[Users] usage of absolute paths in clawsrc

Andrej Kacian andrej at kacian.sk
Mon Mar 13 13:16:37 CET 2017

On Mon, 13 Mar 2017 12:14:34 +0100
Olaf Hering <olaf at aepfle.de> wrote:

> On Mon, Mar 13, Paul wrote:
> > If there is no full path ${pluginsdir} is used.
> Thanks.  I will try just the basename now.
> Somehow the full path was stored in clawsrc. I think that happend
> during initial setup with 3.14.1. Maybe the fileselector dialog
> returns full paths, and claws does not strip ${pluginsdir} from these
> paths?

By default, loaded plugins are saved with full path, due to a design
decision long time ago (with which I disagree, by the way).

User can strip the full path from clawsrc manually, which will cause
Claws Mail to look in its default plugin dir, making it possible to
have a shared .claws-mail. This is a feature which was added later.

To make things more interesting, I noticed that some of the mechanisms
which cause plugin loading, do not add the full path. I suspect it's
when you load a plugin that has other plugins as dependencies (e.g.
dependency of pgpmime plugin is pgpcore plugin), these dependencies are
added without a full path. I could be wrong on this, though.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20170313/d67c733a/attachment.sig>

More information about the Users mailing list