emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com>
Cc: "Liste-emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: org-ref in action
Date: Mon, 30 Jun 2014 05:52:47 -0400	[thread overview]
Message-ID: <87ha32hggg.fsf@gmail.com> (raw)
In-Reply-To: <CAD-VTcGw797ehWSgpeKrekn5ZUX8wWPcBc_MPZ3hDybjdXfZng@mail.gmail.com> (Joseph Vidal-Rosset's message of "Mon, 30 Jun 2014 11:29:19 +0200")

Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:

> 2014-06-29 20:19 GMT+02:00 Eric Schulte <schulte.eric@gmail.com>:
>
>>
>> With ox-bibtex.el [[cite:(page n)one-reference-paper-year]] will export as
>>
>>   \cite[page n]{one-reference-paper-year}
>
>
>
> I am sorry Eric but [[cite:(page n)one-reference-paper-year]]  breaks the
> bibliography reference for me with ox-bibtex.el ... it is too bad because
> it was a convenient solution to get  \cite[page
> n]{one-reference-paper-year} .
>
> I am lost.
>

Could you be more specific?  Does org-mode generate any latex at all,
and how does it differ from what you'd expect?  If no LaTeX is
generated, and Org-mode actually throws an error then please provide a
backtrace.  I should be able to help but I'll need more information.

One thing I noticed is that I got better behavior if I didn't allow line
breaks in the link, which was easily accomplished by replacing
[[cite:(page n)one-reference-paper-year]] with
[[cite:(page~n)one-reference-paper-year]].  In general the later is
actually /preferable/ than the former, as you don't want LaTeX breaking
lines in the middle of a citation either.

Best,

>
> Regards
>
> Jo.

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)

  reply	other threads:[~2014-06-30  9:53 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 18:45 org-ref in action John Kitchin
2014-06-24 19:26 ` Thomas S. Dye
2014-06-24 20:53 ` Ista Zahn
2014-06-25  2:13 ` Matt Lundin
2014-06-25  8:28 ` Bastien
2014-06-25 16:26 ` Vikas Rawal
2014-06-25 20:25 ` Eric Schulte
2014-06-26  1:09   ` Grant Rettke
2014-06-26  1:10   ` Matt Lundin
2014-06-26 12:21     ` Fabrice Popineau
2014-06-26 12:48       ` John Kitchin
2014-06-26 14:08         ` Matt Lundin
2014-06-26 14:09           ` Matt Lundin
2014-06-26 14:11           ` Grant Rettke
2014-06-26 14:13             ` Ken Mankoff
2014-06-26 14:33             ` Jorge A. Alfaro-Murillo
2014-06-26 14:39             ` Matt Lundin
2014-06-26 17:19               ` Alan Schmitt
2014-06-26 18:44                 ` Matt Lundin
2014-06-27  4:27                   ` Xebar Saram
2014-06-27  7:37                     ` Thomas S. Dye
2014-06-27  7:38                     ` Vikas Rawal
2014-06-27  7:52                       ` Melleus
2014-06-27 13:39                     ` Ista Zahn
2014-06-27 23:56                     ` John Kitchin
2014-06-27  6:44                   ` Alan Schmitt
2014-06-27 14:26                     ` Matt Lundin
2014-06-27 17:19                       ` Matt Lundin
2014-06-27 15:49               ` Grant Rettke
2014-06-26 16:14         ` Eric Schulte
2014-06-27  6:55         ` Joseph Vidal-Rosset
2014-06-29 10:18 ` Joseph Vidal-Rosset
2014-06-29 12:09   ` John Kitchin
2014-06-29 18:19   ` Eric Schulte
2014-06-29 18:23     ` Joseph Vidal-Rosset
2014-06-30  9:29     ` Joseph Vidal-Rosset
2014-06-30  9:52       ` Eric Schulte [this message]
2014-06-30 10:06         ` Joseph Vidal-Rosset
2014-06-30 10:22           ` Eric Schulte
2014-06-30 11:27             ` Joseph Vidal-Rosset
2014-08-05 18:28               ` Xebar Saram
2014-08-05 21:08                 ` John Kitchin
2014-08-06 10:54                   ` Xebar Saram
2014-08-06 12:51                     ` John Kitchin
  -- strict thread matches above, loose matches on Subject: below --
2014-06-25  5:57 Leu Zhe
2014-06-26 22:33 Doyley, Marvin M.

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=87ha32hggg.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=joseph.vidal.rosset@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).