Rick Frankel writes:
> On 01.05.2013 13:28, Daimrod wrote:
>> Thanks for the report, I've attached a patch that fixes this problem
>> (in
>> both `org-display-inline-images' and `org-preview-latex-fragment').
>> However I don't know if it is the right approach or if I should try
>> to
>> narrow t
On 01.05.2013 13:28, Daimrod wrote:
Thanks for the report, I've attached a patch that fixes this problem
(in
both `org-display-inline-images' and `org-preview-latex-fragment').
However I don't know if it is the right approach or if I should try
to
narrow this to lower-level functions.
I know
Rick Frankel writes:
Hello Rick,
> `org-startup-with-inline-images' is a customizable variable. The
> problem is that if an org file is visited in a non-graphics buffer (or
> batch), `org-display-inline-images' is called an throws an error
> ("Non-X frame used").
>
> This problem also occurs when
`org-startup-with-inline-images' is a customizable variable. The
problem is that if an org file is visited in a non-graphics buffer (or
batch), `org-display-inline-images' is called an throws an error
("Non-X frame used").
This problem also occurs when e.g., `org-babel-after-execute-hook' is
set
