From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: new exporter drops :parameters ?
Date: Fri, 06 Jul 2012 20:22:44 -0700 [thread overview]
Message-ID: <87vci06yrf.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: 87wr2iq68z.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> cberry@tajo.ucsd.edu writes:
>
>> BTW, "#+name: aname" and "#+NAME: aname" are handled differently in e-latex. The
>> former gets placed in the latex output as "\#+name: aname". Bug?
>
> There is a known bug about affiliated keywords not being removed during
> export, but I don't know if you're describing the same problem.
>
> Do you have an ECM illustrating it ?
Yes and No.
I tried to put an ECM together earlier today, but couldn't trigger the
bug.
Then a few minutes ago it bit.
And this simple subtree triggered it:
,----
| * here is a subtree to export
| #+COMMENT: (org-export-to-buffer 'e-latex "*rnw out*" t)
|
| ** src block
|
| #+name: ablock
| #+begin_src R
| rnorm(10)
| #+end_src
`----
But I restarted emacs, loaded contrib/lisp/org-export.el and
contrib/lisp/org-e-latex.el, and ran the command in the COMMENT line
again and the *rnw out* buffer looked justed fine (no \#+name... stuff).
And I repeated as many of my earlier steps as I could and still no bug bite.
So whatever the problem is, it is not something I can reliably reproduce.
If I come up with anything, I'll get back to you.
Chuck
>
>
> Regards,
--
Charles C. Berry Dept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
prev parent reply other threads:[~2012-07-07 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 3:51 new exporter drops :parameters ? Charles Berry
2012-07-03 9:16 ` Nicolas Goaziou
2012-07-04 18:19 ` cberry
2012-07-05 20:53 ` Nicolas Goaziou
2012-07-07 3:22 ` cberry [this message]
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=87vci06yrf.fsf@tajo.ucsd.edu \
--to=cberry@tajo.ucsd.edu \
--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).