emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Minor problems with dvipng latex image preview
Date: Thu, 23 May 2013 18:53:19 +0200	[thread overview]
Message-ID: <87wqqptz7k.fsf@gmail.com> (raw)
In-Reply-To: <87y5b5znnu.fsf@pierrot.dokosmarshall.org> (Nick Dokos's message of "Thu, 23 May 2013 12:06:13 -0400")

Nick Dokos <ndokos@gmail.com> writes:

> I learnt quite a bit from this discussion (thank you!), but I'm still a
> bit puzzled about your reluctance that custom options be added to the
> latex call. Why is that? Too many customizations? dvipng should be
> deprecated?  Too many twisty passages to explain?

Huh? I'm not reluctant to anything with regards to this discussion. I'm
just suggesting solutions to your problem.

Anyway, in a nutshell, your proposal is to:

  - add a custom variable, e.g., `org-latex-dvi-process-options' (which
    library should it belong to?)
  - modify `org-latex-listings' docstring (in particular, add third
    elements and new custom variable)
  - add a custom variable, e.g., `org-latex-dvi-process-debug', which,
    when non-nil asks to leave produced "tex" file.

Is that right?


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-05-23 16:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 22:27 Minor problems with dvipng latex image preview Nick Dokos
2013-05-22 19:03 ` Nicolas Goaziou
2013-05-23  6:21   ` Nick Dokos
2013-05-23 13:21     ` Nicolas Goaziou
2013-05-23 16:06       ` Nick Dokos
2013-05-23 16:53         ` Nicolas Goaziou [this message]
2013-05-23 21:37           ` Nick Dokos
2013-05-25 20:20             ` Nicolas Goaziou
2013-05-26  6:38               ` Nick Dokos
2013-05-30 15:12                 ` Nicolas Goaziou
2013-05-30 15:25                   ` Nick Dokos

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=87wqqptz7k.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@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).