emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-ref code
Date: Mon, 12 May 2014 14:36:02 +0100	[thread overview]
Message-ID: <871tvzm859.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <CAJ51EToS2H8qMEKhfkr4oxbcU2AdRVxWeMQbbcKo-cDa+SeEQA@mail.gmail.com> (John Kitchin's message of "Sun, 11 May 2014 14:48:40 -0400")

On Sunday, 11 May 2014 at 14:48, John Kitchin wrote:

[...]

> C-c ] should be bound by default to org-ref-insert-cite-link. It is defined
> in a hook function in line 104 of org-ref.org.

Yes.  It is.  

I don't use this binding.  I use evil mode and don't like chorded
commands.  I have org-ref-insert-cite-link bound to ", r" but that's
beside the point, in any case.

>> 1. C-u on it does not give me a choice of citation method
>
> If you type C-u M-x  org-ref-insert-cite-link
> do you get a choice?

No.  I get prompted for the expression to search for and then I get
prompted for an optional argument and the final text inserted in my org
buffer is \cite{....}, not cite:....

> I just tried this on a fresh pull and it does work for me. I am not sure
> why this wouldn't work for you.  Do you tangle the .el file from the .org
> file? I have this code somewhere else to build it when needed:

I do tangle and then eval-buffer just to make sure I have the right code
loaded.

>> 2. the link inserted "looks" like a link (it's blue) but there are
>>      actually no [[...]] characters surrounding it.
>>
> There are no [[...]]. The links work fine without them for me. Are they
> necessary for some reason? I can add them, but since they do not do
> anything but disappear in this case, I leave them out.  

Well, I obviously have something not quite configured properly in my
environment.  The cite: text is highlighted as a link in the org buffer
(as it should with org-highlight-links set) but is treated as simple
text when exported so that I simply get "cite:..." in the latex
output.  If I "C-c C-l" it and don't add a description, the org buffer
*looks* the same but the export works because org and/or the exporter
know that it's a link.

Is there some org variable I have not set that tells org to treat cite:
plain text as a link on export?  Obviously org already recognises it as
a link but the export doesn't...  org-link-protocols and org-link-types
look fine.

I am most puzzled... :(

By the way, in my use case, even if the above would work properly, it
would still definitely help if the [[...]] were inserted as I sometimes
use superscript indices and in those cases I do not want any whitespace
between the text and the citation that follows.  Anyway, this is
secondary.

thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.6-949-g751506

  parent reply	other threads:[~2014-05-12 13:36 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 20:59 org-ref code John Kitchin
2014-05-01  6:23 ` Eric S Fraga
2014-05-01 10:01 ` Eric S Fraga
2014-05-01 12:21   ` Seb Frank
2014-05-01 14:08     ` Eric S Fraga
2014-05-01 12:36   ` John Kitchin
2014-05-01 12:47     ` John Kitchin
2014-05-01 13:30       ` Eric S Fraga
2014-05-01 17:07         ` John Kitchin
2014-05-10 14:44           ` Eric S Fraga
2014-05-11 18:48             ` John Kitchin
2014-05-12  8:12               ` Andreas Reuleaux
2014-05-13  2:37                 ` John Kitchin
2014-05-12 13:36               ` Eric S Fraga [this message]
2014-05-12 17:20                 ` Andreas Reuleaux
2014-05-12 17:26                   ` John Kitchin
2014-05-13  0:03                     ` Andreas Reuleaux
2014-05-13 11:00                     ` Eric S Fraga
2014-05-13 18:51                       ` John Kitchin
2014-05-13 20:01                         ` Eric S Fraga
2014-05-13 20:11                         ` Eric S Fraga
2014-05-14  0:28                           ` John Kitchin
2014-05-14 18:17                             ` Eric S Fraga
2014-05-14 19:03                               ` Andreas Reuleaux
2014-05-14 19:48                                 ` Sharon Kimble
2014-05-14 20:08                                   ` Andreas Reuleaux
2014-05-14 22:14                                 ` Eric S Fraga
2014-05-14 20:35                               ` John Kitchin
2014-05-15  6:58                                 ` Eric S Fraga
2014-05-15  8:17                                   ` Eric S Fraga
2014-05-15 13:05                                     ` John Kitchin
2014-05-15 13:14                                       ` Eric S Fraga
2014-05-15 13:30                                       ` Eric S Fraga
2014-05-15 14:19                                         ` John Kitchin
2014-05-15 14:31                                           ` Eric S Fraga
2014-05-15 15:03                                             ` Eric S Fraga
2014-05-15 13:15                                   ` John Kitchin
2014-05-14  3:58                           ` Andreas Reuleaux
2014-05-14 13:17                             ` John Kitchin
2014-05-13 23:33                         ` Andreas Reuleaux
2014-05-14  0:38                           ` John Kitchin
2014-05-14  3:39                             ` Andreas Reuleaux
2014-05-14 13:14                               ` John Kitchin
2014-05-14 17:39                                 ` Andreas Reuleaux
2014-05-18 17:16                             ` org-ref for biblatex Andreas Reuleaux
2014-05-18 21:40                               ` John Kitchin
2014-05-18 22:38                                 ` Andreas Reuleaux
2014-05-19 11:38                                   ` John Kitchin
2014-05-19 12:15                                     ` Andreas Reuleaux
2014-05-19 17:34                                 ` Andreas Reuleaux
2014-05-08  8:31 ` org-ref code Vikas Rawal
2014-05-08 13:53   ` John Kitchin
2014-05-15 10:09     ` Bastien

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=871tvzm859.fsf@pinto.chemeng.ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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).