Quote:

4. Changed the way the current directory is handled.

In previous versions the current directory (that is, the default directory used in a file open if no full pathname is specified) would vary if you used the file browser dialog. For example, if you loaded a plugin (by browsing to find it), then the file browser would leave the current directory as the one the plugin was in.

I didn't want to change the file browser to not remember where you last browsed to, because that would be annoying if you wanted to load lots of plugins (say) from a non-standard location, and had to keep browsing to the same spot.

On the other hand, having the current directory change randomly can make plugins stop working.

The solution is now as follows:

a) When MUSHclient starts up, it remembers the startup directory (the current directory). This is stored internally (See GetInfo (68)).

b) The "file browsing" directory is initially set to be the startup directory.

c) When you use the file browser (there are about 36 places this happens), the current directory is set to be the file browsing directory - before the dialog appears. This way, file browsing remembers where you last browsed to.

d) After you have browsed for a file, MUSHclient remembers the now-current directory as the file browsing directory, for next time you browse a file.

e) After that, the current directory is reset back to the startup directory.

Note that the script function ChangeDir *does* change the current directory, as advertised.

Oriol said:

The problem was that I was running mush from a shortcut and it'd pick up desktop as the working directory.
Is tehre any way to fix this or do I need to run it directly from the folder?

Oriol said:

Any way to let mush know where the default plugins dir should be?