t***@onepost.net
2014-02-09 03:33:37 UTC
While waiting for the last translations to be updated, I've acted upon some recent comments from Liviu. Specifically:
* added a commandline option -a|--share-config= DIR
This will trigger loading of data from file config[whatever] in DIR, after any other config data are loaded. This means you can, for example, create a shared version of some or all config data (say, plugins or filetypes) and advise users when first running the application to run with emelfm2 -a DIR, to initialise suitable config data for your context. Data are loaded from DIR, but not saved there. Saving at session-end still occurs in the user's local config dir as normal.
* added support for <system default> as a command in filetypes config data
Probably you'd add to filetypes config data something like _Default <system default> %p.
If present and activated, that will trigger an interrogation of any relevant .desktop files and mimetype information, to try to invoke the command which the desktop environment considers to be the default for the filetype in question.
Eventually the string "<system default>" should be translated (like similar tokens e.g. "<none>"), but that will have to wait until next release, because most translators have already finished their work for this coming release.
Regards
Tom
* added a commandline option -a|--share-config= DIR
This will trigger loading of data from file config[whatever] in DIR, after any other config data are loaded. This means you can, for example, create a shared version of some or all config data (say, plugins or filetypes) and advise users when first running the application to run with emelfm2 -a DIR, to initialise suitable config data for your context. Data are loaded from DIR, but not saved there. Saving at session-end still occurs in the user's local config dir as normal.
* added support for <system default> as a command in filetypes config data
Probably you'd add to filetypes config data something like _Default <system default> %p.
If present and activated, that will trigger an interrogation of any relevant .desktop files and mimetype information, to try to invoke the command which the desktop environment considers to be the default for the filetype in question.
Eventually the string "<system default>" should be translated (like similar tokens e.g. "<none>"), but that will have to wait until next release, because most translators have already finished their work for this coming release.
Regards
Tom