Re: [O] org-batch-agenda-csv issue
On Tuesday, 29 Nov 2016 at 19:17, J. Brian Walters wrote:
[...]
> The following command works fine with no errors when executed in a terminal
>
> emacs -batch -l ~/.emacs -eval '(org-batch-agenda-csv "a")'
[...]
> Why would it work fine in the terminal but not when executed via a crontab
> entry?
Maybe cron does not expand ~? Try $HOME/.emacs or ${HOME}/.emacs instead.
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0-3-g4c4e84
signature.asc
Description: PGP signature
[O] Bug: Latex preview overlay scaling not consistent across PPI
The size of the latex preview overlay scaling is inconsistent across screens with different pixel densities. I've set my customization to use dvipng for the latex previews I see when I type C-c C-x C-l. Dvipng is customized as follows: [image: Inline image 1] The "Value" is set to (1.0 . 1.0), which I would think means that the font size in the preview overlay is scaled the same as the font size org buffer's normal text. This is more or less true for a Windows 7 machine connected to a 24", 1920x1080 pixel monitor: [image: Inline image 2] However, on a Windows 10 machine with a 12.3", 2736x1824 pixel monitor, the same customization looks like this: [image: Inline image 3] On the second computer (a Surface Pro 4) the previews are tiny because the screen has a much higher pixel density; the normal text is scaled appropriately but the overlays aren't scaled to match. I'd like keep the same .emacs file across all the machines I have to use, so it would be best if the preview scaling was consistent. Possibly the overlay scaling calculation is done using the function window-text-width without the *pixelwise *argument, which would return a width in characters. To avoid changing the calculation too much, you could use window-max-chars-per-line, which considers font size and some things that would be missed by window-text-width even if *pixelwise* was used. -- my setup -- Emacs : GNU Emacs 25.1.1 (i686-w64-mingw32) of 2016-09-17 Package: Org mode version 9.0.1 (9.0.1-elpaplus @ c:/Users/sotterson/home/.emacs.d/elpa/org-plus-contrib-20161118/)
Re: [O] Capture with org-directory not working?
Alexander Vorobiev writes: > The workaround with lambda worked, thanks a lot! As I mentioned I didn't have > any problems with the > templates in years but they stopped working after a recent update. > The change was made last June (I presume it was committed on the master branch, so it became generally available only when Org 9.0 was released): , | commit 5485170263a46fa17db67b0324c4c4e48bcdfe49 | Author: Nicolas Goaziou | Date: Fri Jun 24 01:11:49 2016 +0200 | | org-capture: Remove forbidden value type from "file" templates | | * lisp/org-capture.el (org-capture-expand-file): Remove plain S-exps | from allowed values. ` -- Nick
[O] latex src block file output
Hello,
When I hit C-c C-c on a latex src block with a :file header, I ultimately get
an error from org-compile-file that the expected output file in a temp
directory was not produced. However, the file is produced in the current
directory.
For instance, evaluating the src block in the following Org document,
* A Little Diagram
#+BEGIN_SRC latex :file diagram.pdf :packages '(("" "tikz")) :border 1em
\usetikzlibrary{shapes,arrows}
\begin{tikzpicture}[->, auto, node distance=3cm]
\node [draw] (A) {A};
\node [ellipse, draw, right of=A] (B) {B};
\path (A) edge node {message} (B);
\end{tikzpicture}
#+END_SRC
Gives me the error,
Debugger entered--Lisp error: (error "File
\"/var/folders/n6/0j2z684n2pq_0d5kphzzvjs8gn/T/babel-7327204x/latex-73272sec.pdf\"
wasn’t produced. See \"*Org PDF LaTeX Output*\" for details")
While the *Org PDF LaTeX Output* buffer says,
...
Output written on latex-73272sec.pdf (1 page, 12285 bytes).
...
and sure enough the file is there in the same directory as the .org file I am
editing.
I understand that the .tex file is in that temp directory, but pdflatex is
dumping its output into the current directory. Is this a known (or even
already-fixed) issue?
Org mode version 9.0.1 (9.0.1-elpaplus @
/Users/acowley/.emacs.d/elpa/org-plus-contrib-20161118/)
Anthony
[O] use custom "cls" style file as export template for LaTeX/PDF
Hi,
I've been struggling for this question for several days and cannot find any
info on the web.
I have a separate cls file that contains the style for LaTeX export.
I'd like to write thesis using this template in org, but the info I found
is all about adding this:
(add-to-list 'org-latex-classes
'("custom-cls"
"\\documentclass{custom-cls}
[NO-DEFAULT-PACKAGES]
[EXTRA]"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
But there is a lot of things in my cls file...
Is there anyway I can link the cls file or define it somewhere so that
org-mode will know its existance?
How can I define it?
Thank you.
--
*PLEASE THINK BEFORE YOU PRINT, PLEASE.*
Re: [O] saving outgoing mail from org-mime
No one has responded to this thread so hopefully the issue is not widespread, but, in case someone needs a solution: I've just written a blog post explaining the fix: http://matt.hackinghistory.ca/2016/11/30/using-mu4e-and-org-mime-together/ Basically, (setq mail-user-agent 'mu4e-user-agent) plus a small change to an internal function in mu4e-compose.el On Fri, Oct 28, 2016 at 9:29 PM, Matt Price wrote: > I've been using org-mime for a while but now that I have mu4e up and > running I would like to save the outgoing mails sent but message-mode to > the default mu4e sent folder (which is in a Maildir). Is there a > straightforward way to do this? > > >
Re: [O] Bug: Latex preview overlay scaling not consistent across PPI
Hello, Scott Otterson writes: > The size of the latex preview overlay scaling is inconsistent across > screens with different pixel densities. > > I've set my customization to use dvipng for the latex previews I see when I > type C-c C-x C-l. Dvipng is customized as follows: > > [image: Inline image 1] > > The "Value" is set to (1.0 . 1.0), which I would think means that the font > size in the preview overlay is scaled the same as the font size org > buffer's normal text. > > This is more or less true for a Windows 7 machine connected to a 24", > 1920x1080 pixel monitor: > > [image: Inline image 2] > > However, on a Windows 10 machine with a 12.3", 2736x1824 pixel monitor, the > same customization looks like this: > > [image: Inline image 3] > > On the second computer (a Surface Pro 4) the previews are tiny because the > screen has a much higher pixel density; the normal text is scaled > appropriately but the overlays aren't scaled to match. I made a change to how dpi is computed in `org-create-formula-image'. Could you test it and report if it fixes your issue ? Regards, -- Nicolas Goaziou
[O] [PATCH] ox-confluence.el: Add support for verbatim & code
A tiny patch to improve text formatting support for exporting to
Confluence wiki-markup.
--
Charles Durst
cwdurst+orgm...@gmail.com
* contrib/lisp/ox-confluence.el (org-confluence-verbatim,
org-confluence-code): New functions.
Convert org-mode =verbatim= and ~code~ into Confluence {{monospace}}.
TINYCHANGE
---
contrib/lisp/ox-confluence.el | 8
1 file changed, 8 insertions(+)
diff --git a/contrib/lisp/ox-confluence.el b/contrib/lisp/ox-confluence.el
index 48bc5ea..bbdc58a 100644
--- a/contrib/lisp/ox-confluence.el
+++ b/contrib/lisp/ox-confluence.el
@@ -41,6 +41,8 @@
:translate-alist '((bold . org-confluence-bold)
(example-block . org-confluence-example-block)
(fixed-width . org-confluence-fixed-width)
+ (verbatim . org-confluence-verbatim)
+ (code . org-confluence-code)
(footnote-definition . org-confluence-empty)
(footnote-reference . org-confluence-empty)
(headline . org-confluence-headline)
@@ -86,6 +88,12 @@
(defun org-confluence-fixed-width (fixed-width contents info)
(format "\{\{%s\}\}" contents))
+(defun org-confluence-verbatim (verbatim contents info)
+ (format "\{\{%s\}\}" (org-element-property :value verbatim)))
+
+(defun org-confluence-code (code contents info)
+ (format "\{\{%s\}\}" (org-element-property :value code)))
+
(defun org-confluence-headline (headline contents info)
(let ((low-level-rank (org-export-low-level-p headline info))
(text (org-export-data (org-element-property :title headline)
--
2.5.4 (Apple Git-61)
Re: [O] Bug: Latex preview overlay scaling not consistent across PPI
Thanks Nicolas, I'd like to test your fix but I'm a github newbie (*). Where did you check it in? I don't know if it's melpa or elpa, or if the fix is in a personal account or something official. Is there a standard way everybody contributes their fixes? Scott (*) For the same reason, I still haven't been able to test the other dvips customization fix you recently made.
