[KevinH]

The plugin runner actually builds a sigil.cfg file that the plugin launcher code parses to get appdir, dictionary and other paths for the wrapper code that are then added to the plugin interface. The correct way to handle this is to change MainWindow.cpp to add a routine to access m_CurrentFilePath, and use that new interface in PluginRunner to add this new path to the sigil.cfg and then add associated interface routines to the launcher/wrapper and then plugin type specific codes.

This involves quite a bit of work. So please explain why it is needed? Is this just to seed a possible name for output plugins? Why would an edit plugin need to know the name of the epub file as it can not be changed without messing up Sigil. Ditto for a validation plugin?
And input plugins are to load other files anyway so the current filename does not make much sense to me there either.

Kevin