From: email@example.com (Thomas S. Dye)
To: Bastien <firstname.lastname@example.org>
Cc: Org Mode Mailing List <email@example.com>,
Nicolas Goaziou <firstname.lastname@example.org>,
Eric Schulte <email@example.com>
Subject: Re: [patch] ox-latex.el to allow customization of verbatim environments (e.g., to use fancyvrb)
Date: Sun, 14 Apr 2013 14:07:19 -1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Bastien's message of "Mon, 15 Apr 2013 01:25:32 +0200")
Bastien <firstname.lastname@example.org> writes:
> Nicolas Goaziou <email@example.com> writes:
>> I'm not sure a new variable is needed here. After all, that's what
>> filters are for.
> Filters are for advanced Emacs users, not normal Emacs users.
> A "normal" Emacs users is someone who knows how to set an option
> but who doesn't know how to write a function.
> This is always a trade-off: if something is badly needed by users,
> let's have an option. If something is needed only for a few users,
> let's encourage someone to share her/his filter(s)*.
> I don't really have an opinion here: my impression is that the
> filter is correct in this case.
> * Btw, maybe we should consider gathering filters in some unique
> place, so that users can search and find them easily? Either a
> new directory in Worg or a new repository on the server? This
> is powerful enough to deserve a separate place IMO.
Perhaps the Library of Babel would be a good place?
All the best,
Thomas S. Dye
next prev parent reply other threads:[~2013-04-15 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 17:48 [patch] ox-latex.el to allow customization of verbatim environments (e.g., to use fancyvrb) Eric Schulte
2013-04-14 19:26 ` Nicolas Goaziou
2013-04-14 23:25 ` Bastien
2013-04-15 0:07 ` Thomas S. Dye [this message]
2013-04-15 0:25 ` Eric Schulte
2013-04-15 5:40 ` Nicolas Goaziou
2013-04-14 20:02 ` Daimrod
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).