re. maybe unconsider... sorry to tell, this last change is in fact entirely moot or of no consequence in practice... I'm even considering to revert it shortly... the stance is: what seems to work for you, having general relative paths based on ../... and so on, is not acceptable for plugins, sorry again. the rule is: plugins must always be found under one of the configured plugins search paths, not anywhere else. that's the rule to follow if you want no absolute paths in session files. taking back my 2c. :) hyu. ps. reverted, [xpluginpath 498cf555f] is the new tip; you'll need to git reset --hard origin/xpluginpath after this. Reply
sorry to tell, this last change is in fact entirely moot or of no consequence in practice... I'm even considering to revert it shortly...
the stance is: what seems to work for you, having general relative paths based on ../... and so on, is not acceptable for plugins, sorry again.
the rule is: plugins must always be found under one of the configured plugins search paths, not anywhere else.
that's the rule to follow if you want no absolute paths in session files.
taking back my 2c. :)
hyu.
ps. reverted, [xpluginpath 498cf555f] is the new tip; you'll need to
git reset --hard origin/xpluginpathafter this.