From: Daimrod <daimrod@gmail.com>
To: Evan Misshula <evanmisshula@gmail.com>
Cc: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org
Subject: Re: LaTeX preview
Date: Thu, 14 Feb 2013 17:56:52 +0100 [thread overview]
Message-ID: <87sj4y7s17.fsf@tanger.home> (raw)
In-Reply-To: <CAPV3ZjxSkp5M+YEnPj8CvpM5wZdWGSafs=rbdS6sFSwQuNv7Wg@mail.gmail.com> (Evan Misshula's message of "Thu, 14 Feb 2013 08:03:48 -0500")
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
Evan Misshula <evanmisshula@gmail.com> writes:
> +1 This is great, I wanted to do something but did not know how. I
> am going to look at the patch.
I'm glad to know other people like it too :)
> If you have an interest in explaining to an interested Noob what you
> did. I would be grateful.
Sure,
I knew I wanted something like the inlineimages STARTUP keywords. So,
I've searched in the source all references to inlineimages.
M-x moccur-grep RET inlineimages RET
I've found:
a custom variable: `org-startup-with-line-images'
an entry in `org-startup-options'
Then I've searched for `org-startup-with-inline-images' and found:
> (when org-startup-with-inline-images
> (org-display-inline-images))
Then, I've searched the name of the function which toggled the latex
preview. C-h a latex RET then C-s preview in the *Apropos* buffer.
At this point I had everything and I just needed to copy what was done
for inlineimages and adapt it for latexpreview.
> Best,
> Evan
--
Daimrod/Greg
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2013-02-14 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 10:35 LaTeX preview Daimrod
2013-01-11 12:20 ` Bastien
2013-01-11 13:46 ` Daimrod
2013-01-11 16:23 ` Bastien
2013-01-11 16:47 ` Daimrod
2013-01-11 16:53 ` Bastien
2013-01-24 13:07 ` Daimrod
2013-02-14 8:17 ` Bastien
2013-02-14 13:03 ` Evan Misshula
2013-02-14 16:56 ` Daimrod [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj4y7s17.fsf@tanger.home \
--to=daimrod@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=evanmisshula@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).