From: Rasmus <rasmus@gmx.us>
To: alan.schmitt@polytechnique.org
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] make options available for custom source environment in ox-latex
Date: Mon, 18 Jan 2016 15:21:55 +0100 [thread overview]
Message-ID: <87vb6r6k8s.fsf@gmx.us> (raw)
In-Reply-To: <m2io2r55yz.fsf@polytechnique.org> (Alan Schmitt's message of "Mon, 18 Jan 2016 15:15:32 +0100")
Hi,
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> On 2016-01-18 12:28, Rasmus <rasmus@gmx.us> writes:
>
>>>> I almost forgot: would you mind preparing an entry about it for
>>>> ORG-NEWS?
>>>
>>> Is this too detailed?
>>
>> IMO Yes. As I recall the examples are also in the docstring, so just
>> refer to that.
>>
>> IMO a NEWS item should be a headline and one or two lines of explanation,
>> with a reference to the manual or, probably better, a docstring.
>>
>> Exceptions exists of course, e.g. when commands to repair files are
>> suggested.
>
> Excellent point, how about:
>
> *** Attributes support in custom language environments for LaTeX export
> Custom language environments for LaTeX export
> (~org-latex-custom-lang-environment~) can now define the string to be
> inserted during export, using attributes to indicate the position of the
> elements.
Thanks Alan!
It's good. The reference tend to be towards the end, but this is really
your decision. Maybe add a "see" in front of the variable name.
Feel free to push at your discretion.
Cheers,
Rasmus
--
Nothing's wrong with an email that ends in a minor key
next prev parent reply other threads:[~2016-01-18 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 10:31 [PATCH] make options available for custom source environment in ox-latex Alan Schmitt
2016-01-14 10:47 ` Nicolas Goaziou
2016-01-14 13:40 ` Alan Schmitt
2016-01-16 14:11 ` Nicolas Goaziou
2016-01-18 8:59 ` Alan Schmitt
2016-01-18 11:28 ` Rasmus
2016-01-18 14:15 ` Alan Schmitt
2016-01-18 14:21 ` Rasmus [this message]
2016-01-18 14:30 ` Alan Schmitt
2016-01-18 14:31 ` Rasmus
2016-01-18 14:41 ` 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=87vb6r6k8s.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
/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).