From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [new exporter][texinfo] Macro definition section
Date: Mon, 12 Nov 2012 13:39:36 -0500 [thread overview]
Message-ID: <CAEWDx5fPu9VHw+q5MjZvRdyRUx8NCqTUdksO5YSU6rj9p2u7zg@mail.gmail.com> (raw)
In-Reply-To: <m1zk2mpukf.fsf@tsdye.com>
[-- Attachment #1: Type: text/plain, Size: 4321 bytes --]
Hello Tom
On 12 November 2012 13:03, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha Jon,
>
> I'm working on an Org version of the Org manual that (hopefully) can be
> used to generate the required texinfo version.
>
> My goal at this point is to export a document that matches org.texi.
>
Do you want it to match org.texi exactly? Or that the generated info
document end up matching?
> My problem is not with the macro definitions, which can be wrapped as
> you point out. It is with their placement in org.texi between @finalout
> and @copying. IIUC, this should happen around line 670 of
> org-e-texinfo.el, but the code seems to expect that there are two blank
> lines between these commands and no macro definitions or other material.
>
I didn't mean wrapping the macro definitions themselves. I meant
replacing the macro definitions with equivalent Org macros.
For example the =orgcmd{key,command}= macro could be replaced with
something like (ommiting the ifset and iftex logic):
#+MACRO: tkbd @@info:@kbd{@@$1@@info:}@@
#+MACRO: tcode @@info:@code{@@$1@@info:}@@
#+MACRO: tkindex @@info:@kindex $1@@
#+MACRO: tfindex @@info:@findex $1@@
# - instead of @item since items are list elements
#+MACRO: orgcmd {{{tkindex($1)}}}\\{{{tfindex($2)}}}\\- {{{tkbd($1)}}}
{{{tcode($2)}}}
And you could them use {{{orgcmd(C-c C-r,org-reveal)}}} (org.texi line
1316). It would also then be backend agnostic, since non-texinfo
exporters would be read the line as:
- $1 $2
Would that work for your needs? Or would you rather still be able to
generate the macros themselves for use on export?
> In view of my goal, it would be nice to have something like
> #+TEXINFO_POST_HEADER that would pass the macro definitions through to
> this location in the texinfo document.
>
> All the best,
> Tom
>
>
Regards,
--
Jon
>
> Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
>
> > Hello, (helps if I hit paste before hitting send)
> >
> > On 11 November 2012 15:22, Thomas S. Dye <tsd@tsdye.com> wrote:
> >
> >> Aloha all,
> >>
> >> The texinfo source for the Org manual has a number of macro definitions
> >> for commands and keys between the end of the header (@finalout) and the
> >> beginning of the Copying section.
> >>
> >> The texinfo back-end for the new exporter doesn't have a slot here and
> >> I'm wondering if it needs one?
> >>
> >>
> > I believe I accounted for most of the special strings that are
> > directly transcoded in texinfo. There may be some that are missing,
> > however they can be added directly in the document using the
> > =@@info:<texinfo command>@@= syntax (inline export snippets).
> >
> > Are there any particular pieces of synxtax that you believe would be
> > useful to have added to org-entities that would also be useful in
> > other backends?
> >
> >
> >> All the best,
> >> Tom
> >> --
> >> T.S. Dye & Colleagues, Archaeologists
> >> 735 Bishop St, Suite 315, Honolulu, HI 96813
> >> Tel: 808-529-0866, Fax: 808-529-0884
> >> http://www.tsdye.com
> >>
> >>
> > Regards,
> >
> > --
> > Jon
> > Hello, (helps if I hit paste before hitting send)
> >
> > On 11 November 2012 15:22, Thomas S. Dye <tsd@tsdye.com> wrote:
> >
> > Aloha all,
> >
> > The texinfo source for the Org manual has a number of macro
> > definitions
> > for commands and keys between the end of the header (@finalout)
> > and the
> > beginning of the Copying section.
> >
> > The texinfo back-end for the new exporter doesn't have a slot here
> > and
> > I'm wondering if it needs one?
> >
> >
> >
> > I believe I accounted for most of the special strings that are
> > directly transcoded in texinfo. There may be some that are missing,
> > however they can be added directly in the document using the
> > =@@info:<texinfo command>@@= syntax (inline export snippets).
> >
> > Are there any particular pieces of synxtax that you believe would be
> > useful to have added to org-entities that would also be useful in
> > other backends?
> >
> >
> > All the best,
> > Tom
> > --
> > T.S. Dye & Colleagues, Archaeologists
> > 735 Bishop St, Suite 315, Honolulu, HI 96813
> > Tel: 808-529-0866, Fax: 808-529-0884
> > http://www.tsdye.com
> >
> >
> >
> > Regards,
> >
> > --
> > Jon
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
[-- Attachment #2: Type: text/html, Size: 6401 bytes --]
next prev parent reply other threads:[~2012-11-12 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 20:22 [new exporter][texinfo] Macro definition section Thomas S. Dye
2012-11-12 14:57 ` Jonathan Leech-Pepin
2012-11-12 14:58 ` Jonathan Leech-Pepin
2012-11-12 18:03 ` Thomas S. Dye
2012-11-12 18:39 ` Jonathan Leech-Pepin [this message]
2012-11-12 22:52 ` François Pinard
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=CAEWDx5fPu9VHw+q5MjZvRdyRUx8NCqTUdksO5YSU6rj9p2u7zg@mail.gmail.com \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).