View Single Post
Old 02-05-2025, 03:36 AM   #7
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,445
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by chaley View Post
If it is a SYSTEM environment variable then you must use setx to change it. See https://learn.microsoft.com/en-us/wi...-commands/setx. The change is permanent, written to the registry. You will need another setx to reset it

I solve this problems with batch files: one to set both the from-source env var and config directory env var then start calibre-debug, another to set only the config directory env var then start calibre-debug. I don't have a system env var set.
I just use the built-in system environment variable editor from the System Properties tool. I did play with batch files but don't switch enough to make it worthwhile.
Attached Thumbnails
Click image for larger version

Name:	Screenshot 2025-02-05 003137.png
Views:	100
Size:	22.9 KB
ID:	213435  
DNSB is offline   Reply With Quote