emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jacob Gerlach <jacobgerlach@gmail.com>
To: Jacob Gerlach <jacobgerlach@gmail.com>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Internal Links with Spaces
Date: Wed, 11 Mar 2015 10:36:43 -0400	[thread overview]
Message-ID: <CAA6UvuHCKxY=bvT_rETQ28VcC91N+e+D4J90YxusY0TY=JKbcg@mail.gmail.com> (raw)
In-Reply-To: <874mprzkil.fsf@nicolasgoaziou.fr>

On Wed, Mar 11, 2015 at 10:17 AM, Nicolas Goaziou
<mail@nicolasgoaziou.fr> wrote:
> This is where I don't follow you. You can insert links without
> description, using `org-insert-link'. What makes you think you cannot?

I thought that I had tested `(org-insert-link nil nil "")' and found
that a description (repeating the headline text) was still inserted,
but I just tried again and it does in fact insert a link with no
description. (In the meantime I switched from ELPA to git, so perhaps
this behavior has changed?). This solves my problem, so sorry if this
was all noise.

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

At least in the case of org-id, I can imagine that the description
might only be used to control appearance in the org buffer, not to
express desired export behavior.
A link that uses org-id really begs for a description for readability,
but then you can't get \ref{label} on export. Perhaps this is a corner
case that doesn't justify another customization.


[1] https://lists.gnu.org/archive/html/emacs-orgmode/2015-03/msg00350.html

  reply	other threads:[~2015-03-11 14:36 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
2015-03-11 14:36   ` Jacob Gerlach [this message]
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='CAA6UvuHCKxY=bvT_rETQ28VcC91N+e+D4J90YxusY0TY=JKbcg@mail.gmail.com' \
    --to=jacobgerlach@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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