View Single Post
Old 03-09-2019, 09:10 AM   #145
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
Originally Posted by BetterRed View Post
It was not a "random' decision, it was a "much considered decision" to enable me to have alternative calibre configurations - you should be using the environment variable - they reason they exist is to prevent situations like this.

Irrespective of environment variables, the location of the configuration folder shouldn't be effectively 'hard coded' at a moment in time. If someone moves their calibre installation (with the calibre Export/Import tools) to a different computer (maybe a different OS) under a different user name the location of their configuration folder will change. The raison detre for the Export/Import tools is to facilitate doing that in as frictionless manner as possible - including no plugin reinstalls.

BR

The .../calibre/plugins... directory is not "configuration", excluding the .json files that reside there by Calibre design. It has "resources" defined both by a plugin and by the users themselves to be used with the plugin. It also contains the plugin .zip files themselves.

Example: The user-defined and user-created icons to use for the Entities Manager column icon creation rules. EM also places all automatically backed-up column icon rules into a special directory under .../calibre/plugins... so the user can un-do what they just did.

Example: The user-defined and user-created Tag Browser icons specified by the user via the Job Spy "Customize User Category Tag Browser Icons" tool.

Example: The example .csv files, and .xlsx/.ods instructions and example files, that are used with the Job Spy "Scrub Tags" tool.

Example: The Calibre Spy example .bat files and icons for running CS for multiple Calibre Libraries simultaneously when the Calibre GUI is not running at all.

Example: The special backup files for the Job Spy "back up and restore Last Modified Date Metadata" tool.

Example: The many user-created English Noun Frequency word-lists for adding overrides and exceptions to the standard ENF lists.

Example: The documentation for at least four (4) other plugins that is comprised of huge .pdf files with many images that can be opened instantly via simple menu selection only because they have already been extracted from the .zip file into their resources folder.

I you want to change the Calibre environment variable, it is easy to manually copy-and-past the entire .../calibre/plugins/... directory from where it was to where it should be moved to. Given that you would lose all of your .json files, that would be a very good idea in any event. It would also copy all of the plugin .zip files that are located in .../calibre/plugins/... too.

One would think that the Calibre export/import configuration tool would do copy the entire .../calibre/plugins/... directory too. There is no reason not to, and every reason to do so.




DaltonST

Last edited by DaltonST; 03-09-2019 at 10:09 AM.
DaltonST is offline   Reply With Quote