emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jacob Gerlach <jacobgerlach@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Internal Links with Spaces
Date: Wed, 11 Mar 2015 15:17:06 +0100	[thread overview]
Message-ID: <874mprzkil.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAA6UvuHJwpC_S5h7XM=dWF1bSNkJouV2SEbsUDJjWqRz_KYRCw@mail.gmail.com> (Jacob Gerlach's message of "Wed, 11 Mar 2015 09:58:19 -0400")

Jacob Gerlach <jacobgerlach@gmail.com> writes:

> (Did I break the thread by adding "[PATCH]" to the subject? Apologies
> if so, original thread was [1])

I read the thread before asking the question.

> In more detail (repeating/summarizing the prior messages on original thread):
> Internal Links stored with org-store-link and inserted with
> org-insert-link fail on export for headlines with spaces because of %
> encoding the spaces. (This is orthogonal to the patch, just the
> original motivation that led to it).
> One solution is to use org-id. I also came up with a hack to unhex the
> link after it is inserted.
> In either case, the links inserted have descriptions.

This is where I don't follow you. You can insert links without
description, using `org-insert-link'. What makes you think you cannot?

> Links with descriptions always export as hyperref's using the headline
> text (instead of regular \ref's using the label).

That's intended, indeed. If you added a description to a link, Org
should use it.


  reply	other threads:[~2015-03-11 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 13:58 [PATCH] Internal Links with Spaces Jacob Gerlach
2015-03-11 14:17 ` Nicolas Goaziou [this message]
2015-03-11 14:36   ` Jacob Gerlach
2015-03-11 14:52     ` Nicolas Goaziou
  -- strict thread matches above, loose matches on Subject: below --
2015-03-11 13:34 Jacob Gerlach
2015-03-11 13:41 ` Nicolas Goaziou

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:

  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=874mprzkil.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=jacobgerlach@gmail.com \


* 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


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