From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: interaction between org-latex-custom-lang-environments and name when exporting to latex
Date: Tue, 24 Nov 2015 09:07:12 +0100 [thread overview]
Message-ID: <m2poyz3jnz.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <8737vw1u13.fsf@gmx.us> (rasmus@gmx.us's message of "Mon, 23 Nov 2015 18:54:00 +0100")
[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]
Hi Rasmus,
On 2015-11-23 18:54, Rasmus <rasmus@gmx.us> writes:
> Hi Alan,
>
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> What I propose is to have either a string or a function in
>> `org-latex-custom-lang-environments'. A string would be used as it is
>> currently, whereas a function would be applied. Here is what it could
>> look like:
>
> I think a format-string is fine, though I don’t oppose allowing a function
> as well. I don’t foresee a great necessity of the latter, though.
>
> I'd use format-spec. E.g. here’s how hyperref is filled
>
> (let ((template (plist-get info :latex-hyperref-template)))
> (and (stringp template)
> (format-spec template (org-latex--format-spec info))))
I did not know about `format-spec', it's really nice!
> Then the cdr of an element in org-latex-custom-lang-environments can be
> something like:
>
> \begin{%e}[label=%l, myfunkyoption=val]
> %c
> \end{%e}
What would "%e" be bound to? Since this is a customization for a given
source block, it should be fixed, so I think we only need "%l" and "%c".
> The only downside is that you’d have to somehow discriminate between the
> "old" case where the cdr is a single word denoting an environment.
> Something like this might work:
>
> (string-match-p "\\`\\w+\\'" "hest1")
This was the main reason why I did not want to go that route. This said,
after understanding this regexp, I see how I can explain how the two
cases are distinguished in the docstring.
>> My main design question is what the arguments to the function should be.
>> I thought the formatted source code and label would work, but I'm
>> wondering if it may be better to simply give the `src-block' and `info'
>> arguments directly.
>
> Well, functions would be user written. In general I’d favor info and
> src-block, but I don’t think it’s very user-friendly, as it requires quite
> some knowledge about how ox works. Also, when using such functions, the
> user would have to write a lot of boilerplate to get e.g . the label.
Yes. I'll give the template string a try and will report back.
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated November 22, 2015, Mauna Loa Obs.): 400.35 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-11-24 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 12:59 interaction between org-latex-custom-lang-environments and name when exporting to latex Alan Schmitt
2015-11-20 7:55 ` Alan Schmitt
2015-11-20 10:41 ` Rasmus
2015-11-20 11:06 ` Alan Schmitt
2015-11-23 11:13 ` Alan Schmitt
2015-11-23 17:54 ` Rasmus
2015-11-24 8:07 ` Alan Schmitt [this message]
2015-11-24 13:14 ` Rasmus
2015-11-25 7:59 ` Alan Schmitt
2015-11-25 9:57 ` Rasmus
2015-11-27 16:27 ` Alan Schmitt
2015-11-27 21:05 ` Rasmus
2015-11-30 12:12 ` Alan Schmitt
2015-11-30 13:11 ` Rasmus
2015-12-01 8:14 ` Alan Schmitt
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=m2poyz3jnz.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).