From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Bastien <bzg@altern.org>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Macro question with new texinfo exporter
Date: Mon, 04 Feb 2013 05:43:36 -1000 [thread overview]
Message-ID: <m14nhskrtj.fsf@tsdye.com> (raw)
In-Reply-To: <87ehh12gjp.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 31 Jan 2013 22:23:06 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Bastien <bzg@altern.org> writes:
>
>> Now back to the issue at hand, what about simply allowing to escape
>> the , and " characters? This was Thomas first try, and a natural one
>> I'd say.
>
> I have pushed a fix in maint for that. It should now be possible to use
> {{{kbd(C-\,)}}} to get "C-," as argument.
I need a bit more help with this. I created a tracking branch for
maint:
git branch --track maint origin/maint
Then, I checkout maint:
git checkout maint
Reloading Org yields these messages:
The following features were found in load-path, please check if that's correct:
(org-e-texinfo org-export)
Some error occured while reloading Org features
(ob-core ob-tcl)
Please check *Messages*!
Org-mode version 7.9.3e (7.9.3e @ /Users/dk/.emacs.d/src/org-mode/lisp/)
cond: Symbol's function definition is void: org-e-latex-export-to-latex
I'm stymied here. I'd like to be able to use the new macro code with
the new exporter. How is that possible?
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
next prev parent reply other threads:[~2013-02-04 15:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 20:19 Macro question with new texinfo exporter Thomas S. Dye
2013-01-29 18:21 ` Nicolas Goaziou
2013-01-29 18:49 ` Thomas S. Dye
2013-01-30 9:22 ` Bastien
2013-01-30 12:44 ` Nicolas Goaziou
2013-01-30 16:14 ` Bastien
2013-01-30 22:24 ` Nicolas Goaziou
2013-01-31 2:21 ` Thomas S. Dye
2013-01-31 13:51 ` Bastien
2013-01-31 13:58 ` Nicolas Goaziou
2013-01-31 21:23 ` Nicolas Goaziou
2013-02-04 15:43 ` Thomas S. Dye [this message]
2013-02-04 17:26 ` Bastien
2013-02-04 18:57 ` Achim Gratz
2013-02-16 9:21 ` Bastien
2013-02-16 10:19 ` Achim Gratz
2013-02-16 10:34 ` Bastien
2013-02-16 10:39 ` Achim Gratz
2013-02-16 13:18 ` Eric Abrahamsen
2013-02-16 13:23 ` Reloading uncompiled and testing from several git branches (was: Macro question with new texinfo exporter) Bastien
2013-02-16 14:10 ` Reloading uncompiled and testing from several git branches Achim Gratz
2013-02-16 14:21 ` Bastien
2013-02-16 14:59 ` Eric Abrahamsen
2013-02-17 0:08 ` François Pinard
2013-02-18 12:57 ` Nicolas Richard
2013-02-18 19:17 ` Achim Gratz
2013-02-19 1:17 ` François Pinard
2013-02-16 16:40 ` Macro question with new texinfo exporter Nick Dokos
2013-02-16 16:47 ` Nick Dokos
2013-02-16 16:19 ` Nick Dokos
2013-02-16 17:37 ` Thomas S. Dye
2013-02-04 18:10 ` Nicolas Goaziou
2013-02-04 18:48 ` Thomas S. Dye
2013-02-04 18:38 ` Achim Gratz
2013-02-04 20:21 ` Thomas S. Dye
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=m14nhskrtj.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.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).