From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [question/patch] How detailed may org.texi be?
Date: Wed, 29 Oct 2014 21:44:07 +0100 [thread overview]
Message-ID: <871tpqfvxk.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <8738a7f1qd.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 29 Oct 2014 14:24:10 +0100")
Hello,
Rasmus <rasmus@gmx.us> writes:
> I would like to push the following patch to org.texi on export
> behavior of sub/superscripts and LaTeX delimiters. To me it seems
> relevant, but it's somewhat technical. Is it relevant to include such
> "implementation" details/choices in org.texi?
FWIW, I think it's too technical.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-10-29 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 13:24 [question/patch] How detailed may org.texi be? Rasmus
2014-10-29 20:44 ` Nicolas Goaziou [this message]
2014-10-30 16:13 ` Skip Collins
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=871tpqfvxk.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).