emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Jacob Gerlach <jacobgerlach@gmail.com>
To: Leo Ufimtsev <lufimtse@redhat.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Internal Links with Spaces
Date: Mon, 9 Mar 2015 16:50:51 -0400	[thread overview]
Message-ID: <CAA6UvuEumP2-VsSTFvzW557sT=D2+QHhKZY1_eVQKXdh=6ZB_Q@mail.gmail.com> (raw)
In-Reply-To: <1825534239.18268273.1425911896744.JavaMail.zimbra@redhat.com>

On Mon, Mar 9, 2015 at 10:38 AM, Leo Ufimtsev <lufimtse@redhat.com> wrote:
> On the side, if of any help:
>
> I generally use ID's for linking to headings.
> The benefit is that headings can be re-named safley and links still work.

A great suggestion. I wasn't aware of the feature, and renaming safety
is a great benefit while also solving my space problem.

I don't suppose there's a trick to automatically update descriptions
for links whose target has been renamed?

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?

Thanks for the pointer in any case.

Regards,
Jake

next prev parent reply	other threads:[~2015-03-09 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 13:05 Internal Links with Spaces Jacob Gerlach
2015-03-09 14:38 ` Leo Ufimtsev
2015-03-09 20:50   ` Jacob Gerlach [this message]
2015-03-09 23:28     ` John Kitchin
     [not found]       ` <CAA6UvuEG_9b0+b=boXMSsi+8yZWZORBkMAfgKj+9rhPpuevsgQ@mail.gmail.com>
2015-03-10 14:30         ` John Kitchin
2015-03-10 14:39       ` Jacob Gerlach
     [not found]         ` <m2egowj0h7.fsf@andrew.cmu.edu>
2015-03-10 19:47           ` Jacob Gerlach

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='CAA6UvuEumP2-VsSTFvzW557sT=D2+QHhKZY1_eVQKXdh=6ZB_Q@mail.gmail.com' \
    --to=jacobgerlach@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lufimtse@redhat.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

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).