Thanks, David, for your response.  I suspected it might not be that easy to
fix.

I hadn't thought of making a custom command which only used mandatory
arguments.  I'll try it out and see if I like it.

Thanks,

Scot


On Sun, Jun 13, 2010 at 3:16 PM, David Maus <dmaus@ictsoc.de> wrote:

>
> Scot Becker wrote:
>
> >If I put a LaTeX citation command inside one of org's inline
> >footnotes, no problem, thus:
>
> >Lorem ipsum dolor sit amet,\footnote{\cite{rowe_acts_2007} }
> >consectetur adipisicing elit,
>
> >But if I need an optional argument, no dice.  This:
>
> > ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute
> irure dolor
>
> >exports to LaTeX like this:
>
> >ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute
> irure dolor
>
> >(i.e. there is no \footnote{} macro created)
>
> >For consistency in my markup, I would rather use org's inline
> >footnotes for citations like this (which sometimes number several
> >inside a footnote).   If I can't, I'd just go ahead and use LaTeX
> >\footnote{} macros right in my org files.
>
> >Is the present behaviour likely to be fixable?  Or should I just
> >write my footnotes as LaTeX \footnotes{}?
>
> This does not look like easy to fix: It are the square brackets of the
> \cite command that prevent Org mode from recognizing the inline
> footnote.
>
> You could try to work with a LaTeX hack, something along:
>
> ,----
> | \newcommand{\mycite}[2]{\cite[#1]{#2}}
> `----
>
> This would provide the macro \mycite with two arguments given in
> curly brackets that is expanded to the \cite sequence.
>
> HTH
>   -- David
>
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de
>