directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete --json API. Every conda command should fully support --json time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". 4.6. Developer This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro

time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". site_data_dir(appname This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro settings go in the CSIDL_LOCAL_APPDATA directory. (Note: I'm interested in examples of what some windows apps use for a logs dir.) OPINION: This function appends "Logs" to the CSIDL_LOCAL_APPDATA value for Windows

directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete --json API. Every conda command should fully support --json time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". 4.6. Developer This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro

directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete --json API. Every conda command should fully support --json time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". site_data_dir(appname This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro

directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete --json API. Every conda command should fully support --json time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". site_data_dir(appname This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro

directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete --json API. Every conda command should fully support --json time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". site_data_dir(appname This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro

directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete --json API. Every conda command should fully support --json time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". site_data_dir(appname This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro

directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete --json API. Every conda command should fully support --json time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". 398 Chapter This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro

time of installation, instead of the application adding data during runtime. Also, in practice, Linux apps tend to store their data in "~/.config/" instead of "~/.local/share/". site_data_dir(appname This is identical to the non-roaming app data dir (the default returned by user_data_dir above). Apps typically put cache data somewhere under the given dir here. Some examples: ...MozillaFirefoxPro settings go in the CSIDL_LOCAL_APPDATA directory. (Note: I'm interested in examples of what some windows apps use for a logs dir.) OPINION: This function appends "Logs" to the CSIDL_LOCAL_APPDATA value for Windows

directly recog- nized by verlib’s NormalizedVersion are supported better • conda run command, to run apps and commands from packages • more complete –json API. Every conda command should fully support –json