Bug: Org LaTeX preview scaling bug under Windows [9.1.9 (release_9.1.9-65-g5e4542 @ c:/bin/emacs-26.3-x86_64/share/emacs/26.3/lisp/org/)]
Dear Everyone,
Using official emacs 26.3 binaries for Windows, TexLive, and imagemagick
LaTeX preview messes up if
scale in org-format-latex-options is set to 1.5 or higher. To reproduce try
saving the following (also attached) as an org file and running it with a
completely clean emacs setup. Call the source code blocks and
org-toggle-latex-fragment on the fragments in order. If the scale is set to
1.49 or lower everything works fine. If it is set to 1.5 or higher the
pagination is messed up. I tried playing with the latex template but I do
not know enough about it. Sorry
Attaching a screenshot of the result. I do not have a Linux box to test this
bug.
After the org file I included the relevant version strings for the programs
in use.
Best,
Gennady.
#+BEGIN_SRC emacs-lisp
(setq
temporary-file-directory "c:/Users/guraltsev/AppData/Local/Temp/"
org-latex-pdf-process
'("%latex -interaction nonstopmode -output-directory %o %f" "%latex
-interaction nonstopmode -output-directory %o %f" "%latex -interaction
nonstopmode -output-directory %o %f")
org-preview-latex-default-process 'imagemagick)
)
#+END_SRC
#+RESULTS:
: imagemagick
#+BEGIN_SRC emacs-lisp
(setq
org-format-latex-options
'(:foreground default :background default :scale 1.49 :html-foreground
"Black" :html-background "Transparent" :html-scale 1.0 :matchers
("begin" "$1" "$" "$$" "\\(" "\\["))
)
#+END_SRC
#+RESULTS:
| :foreground | default | :background | default | :scale | 1.49 |
:html-foreground | Black | :html-background | Transparent | :html-scale |
1.0 | :matchers | (begin $1 $ $$ \( \[) |
\begin{equation}
\mathbb{R} \subset \mathbb{C}
\end{equation}
#+BEGIN_SRC emacs-lisp
(setq
org-format-latex-options
'(:foreground default :background default :scale 1.5 :html-foreground
"Black" :html-background "Transparent" :html-scale 1.0 :matchers
("begin" "$1" "$" "$$" "\\(" "\\["))
)
#+END_SRC
#+RESULTS:
| :foreground | default | :background | default | :scale | 1.5 |
:html-foreground | Black | :html-background | Transparent | :html-scale |
1.0 | :matchers | (begin $1 $ $$ \( \[) |
\begin{equation}
\mathbb{Q} \subset \mathbb{R}
\end{equation}
pdfTeX 3.14159265-2.6-1.40.21 (TeX Live 2020/W32TeX)
kpathsea version 6.3.2
Copyright 2020 Han The Thanh (pdfTeX) et al.
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Han The Thanh (pdfTeX) et al.
Compiled with libpng 1.6.37; using libpng 1.6.37
Compiled with zlib 1.2.11; using zlib 1.2.11
Compiled with xpdf version 4.02
Version: ImageMagick 7.0.10-13 Q16 x64 2020-05-17 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2018 ImageMagick Studio LLC
License: http://www.imagemagick.org/script/license.php
Visual C++: 180040629
Features: Cipher DPC Modules OpenCL OpenMP(2.0)
Delegates (built-in): bzlib cairo flif freetype gslib heic jng jp2 jpeg lcms
lqr lzma openexr pangocairo png ps raw rsvg tiff webp xml zlib
Emacs : GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
of 2019-08-29
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
c:/bin/emacs-26.3-x86_64/share/emacs/26.3/lisp/org/)
current state:
==
(setq
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-html-format-inlinetask-function
'org-html-format-inlinetask-default-function
org-odt-format-headline-function 'org-odt-format-headline-default-function
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-mode-hook '(#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook
org-show-block-all append local] 5]
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook
org-babel-show-result-all append local]
5]
org-babel-result-hide-spec
org-babel-hide-all-hashes)
org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-archive-hook '(org-attach-archive-delete-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-preview-latex-default-process 'imagemagick
org-metaup-hook '(org-babel-load-in-session-maybe)
org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3
"\n\n(fn ENTRY)"]
org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
org-babel-pre-tangle-hook '(save-buffer)
org-tab-first-hook
RE: issue tracker?
Hello everyone, I have been following the org-mode ML and I have seen the discussion about having a bug tracker. I wanted to offer my 2 cents as a non-developer; barely a power user. Org-mode works incredibly well and I use it on a daily basis. It is true that development is very active. However I might say that saying that no bugs fall through the cracks in the ML is a bit of a confirmation bias. My personal experience was different. I actually submitted some bug reports through emacs about some slightly less used parts of org-mode e.g. ob-eshell. The mailing list is moderated (or has anti-spam) so the result was that my mail did not appear AT ALL. I had that issue before, too, but here in IRC I was suggested to wait for several days. The previous time I think the e-mail eventually got through. When I submitted the bug report for ob-eshell it never did. I found a workaround by using shell instead of ob-shell so I never pursued the issue. Probably the bug is still there. I am glad that the ML works for the most active developers, and I suppose it works well for the linux kernel since it needs to be centralized and somewhat focused. However org-mode could benefit from more community involvement even of newbies, especially around the parts that are "part of" org-mode but are not that often used and don't receive enough love and attention from the main developers. A good bug tracker could also help identify parts that are not used or buggy and that should, maybe, be slated for removal or at least separated in a independent package. You see, for a beginner a bug is quite daunting because you never know if it is actually a bug or if it is your own fault for misunderstanding or misconfiguring something. And, honestly, in emacs, it is quite easy for a beginner to misconfigure something. All this to say that the ML works great and I picked up great ideas while reading through it in my mailbox (I am subscribed), however it still has a significant "gatekeeper" effect. Please, at least address the issue that some bug reports don't even make it to the list AT ALL. I do not want this email to be offensive in any way to anyone. I also realize that what I described may not be representative. I excuse myself in advance if my tone was inappropriate. More than anything I still wish to thank everyone for a piece of fantastic software that has helped me out crucially on multiple occasions! Sincerely, Gennady P.S. I wrote essentially the same e-mail on the IRC channel to be sure that it gets delivered somewhere. -Original Message- From: Emacs-orgmode On Behalf Of Jud Taylor Sent: Wednesday, 20 May, 2020 12:42 To: Stefan Nobis Cc: emacs-orgmode@gnu.org Subject: Re: issue tracker? I second that. Nicolas, thank you! Great product, better vision, high energy! ‐‐‐ Original Message ‐‐‐ On Wednesday, May 20, 2020 7:12 AM, Stefan Nobis wrote: > Detlef Steuer ste...@hsu-hh.de writes: > > > I would go as far as saying this list is one of the fastest reacting > > amd friendliest communities I have been part of. The job Nicolas > > does is just awesome. > > +1! > > -- > > Until the next mail..., > Stefan.
