Change to the way the current directory is managed in version 4.42 onwards

There have been complaints in the past about the way MUSHclient handles the current directory. Specifically, if you browse for files (eg. opening a text file, browsing for a plugin) that changes the current directory. Then, a plugin which opens a file in the current directory subsequently, may not find it.

In an attempt to address all this, version 4.42 has a major change to the way file browsing works. See the release notes for a detailed explanation (point 4 in the link below):

http://www.gammon.com.au/scripts/showrelnote.php?version=4.42&productid=0

Awesome.

So this change effectively means that these plugins will never find their file in the current directory, and the authors should be good coders and use full paths in the first place? :)



GetPluginInfo(GetPluginID(), 6):match("^(.+)\\.-$"))

will return the directory your plugin is installed.

These plugins? Plugins in general I suppose.

If you browse to the plugins directory, at present, that changes the current directory to the plugins directory. However next time MUSHclient starts up, the plugins are not necessarily loaded with the plugins directory being the current one. And even if it was, doing a reload plugin, would not guarantee that.

So yes, plugins should probably use your suggested regexp to find where they are, if they need additional files in the same directory.

I'm not sure the change has made anything much worse than before.

Out of curiosity, what was wrong with:

Those these plugins. :)

The other time I recall this issue flaring up is for someone that didn't know how to modify their Python search path for imports.


And there's nothing wrong with GetPluginInfo(id,20); I just didn't read far enough down the list to know it was there. I recalled needing a regexp to do it in the past.