>> If it follows org-latex-preview-cache, then there is no way to specify >> :image-dir specifically for HTML exports separately from the LaTeX >> preview storage directory. IIRC this was a problem with the old system. > > True, but now we decoupled `org-preview-latex-image-directory' and > `org-latex-preview-cache', so that's no longer a problem.
But the old behavior is undesirable, why continue it? Suppose we have (setq org-latex-preview-cache "~/org/ltximg/") ;absolute path Then the value of org-preview-latex-image-directory is also this, since it's an alias. Now 1. :image-dir in org-html-latex-image-options is not respected. 2. The user might want to specify a different image store for HTML exports, but can't without changing org-latex-preview-cache. 3. HTML exports with LaTeX images can no longer be portable. 4. If they set the :inline option in org-html-latex-image-options, the value of org-preview-latex-image-directory is no longer respected, which is also confusing. When using org-html-latex-image-options, both :inline and :image-dir are part of the same plist and it's more clear what will happen if you pick :inline. This just seems like a bad idea. I think it might be better to break org-preview-latex-image-directory and mention org-html-latex-image-options, but it's your call. Karthik
