From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: feng shu <tumashu@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'=.
Date: Tue, 02 Jul 2013 19:21:43 +0200 [thread overview]
Message-ID: <87vc4sop20.fsf@gmail.com> (raw)
In-Reply-To: <87fvvwnank.fsf@gmail.com> (Jambunathan K.'s message of "Tue, 02 Jul 2013 22:48:07 +0530")
Hello,
Jambunathan K <kjambunathan@gmail.com> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> Hello,
>>
>> feng shu <tumashu@gmail.com> writes:
>>
>>> From 63eba2e491a0c410b3841cbad2dd1a9f80416bca Mon Sep 17 00:00:00 2001
>>> From: Feng Shu <tumashu@gmail.com>
>>> Date: Tue, 2 Jul 2013 11:52:10 +0800
>>> Subject: [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'=.
>>>
>>> * ox-latex.el (org-latex-pdf-process): let =`make'= be a
>>> preconfigured choice and change the wording of the docstring.
>>
>> I don't mind applying it, but shouldn't it as simple to provide
>> a function that will call "make" instead?
>>
>> It's impossible to provide every solution in the wild for that. Is this
>> one really necessary: it doesn't have complicated arguments.
>
> Can (other ...) be used here? See (info "(elisp) Composite Types")
AFAIU, `other' means "whatever your answer is, always do the same",
which is not what we want.
If you want "give whatever you want and we'll use it", it should be
a `string' type. But can't `function', which is already implemented, do
the same anyway?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-07-02 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 4:07 [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'= feng shu
2013-07-02 16:54 ` Nicolas Goaziou
2013-07-02 17:18 ` Jambunathan K
2013-07-02 17:21 ` Nicolas Goaziou [this message]
2013-07-02 17:48 ` Jambunathan K
2013-07-02 23:09 ` feng shu
2013-07-02 23:51 ` Suvayu Ali
2013-07-03 6:22 ` Feng Shu
2013-07-03 8:31 ` Suvayu Ali
2013-07-03 14:01 ` Feng Shu
2013-07-03 8:12 ` Bastien
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=87vc4sop20.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=tumashu@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).