From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gerlach Subject: Re: Internal Links with Spaces Date: Tue, 10 Mar 2015 10:39:54 -0400 Message-ID: References: <1825534239.18268273.1425911896744.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54068) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVLK8-0007wN-G4 for emacs-orgmode@gnu.org; Tue, 10 Mar 2015 10:40:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YVLK7-00058p-BX for emacs-orgmode@gnu.org; Tue, 10 Mar 2015 10:39:56 -0400 Received: from mail-qg0-x22b.google.com ([2607:f8b0:400d:c04::22b]:44860) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVLK7-00058f-7V for emacs-orgmode@gnu.org; Tue, 10 Mar 2015 10:39:55 -0400 Received: by qgfl89 with SMTP id l89so2241865qgf.11 for ; Tue, 10 Mar 2015 07:39:54 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Kitchin Cc: Leo Ufimtsev , Org-mode On Mon, Mar 9, 2015 at 7:28 PM, John Kitchin wrote: > I think you need to set > > (setq org-id-link-to-org-use-id 'create-if-interactive) Indeed, this is a variation of what Leo suggested and customizing org-id-link-to-org-use-id is almost working for me... Unfortunately, I want the links to export to latex using latex \ref{}'s and section labels. A link stored with a custom id has to have a description to have a reasonably readable org buffer, but links with descriptions are exported using the headline text instead of the section number. Is there a workaround for this? On Mon, Mar 9, 2015 at 4:50 PM, Jacob Gerlach wrote: > When exploring this, I found the function org-id-store-link. This > seemed like what I wanted - it creates a custom ID if one doesn't > exist, but it doesn't actually store a link (or at least, it wasn't > available when I then ran org-insert-link). The docstring is pretty > light, but it seems like this might be a bug. Is this the expected > behavior? After perusing the source code further, I think that my confusion about org-id-store-link arose because this function isn't intended to be called on it's own (it's called by org-store-link when appropriate based on the value of org-id-link-to-org-use-id). I've seen a double hyphen in function names to sometimes indicate internal functions. Would this function be more appropriately named org-id--store-link or am I misunderstanding the convention? Regards, Jake