emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Unintended behavior? Links without description
Date: Sun, 13 Feb 2011 13:49:35 +0100	[thread overview]
Message-ID: <4D57D35F.7050403@christianmoe.com> (raw)
In-Reply-To: <87hbc8vr7k.fsf@gnu.org>

Hi,

I've sent a patch separately. Please take a hard look at it, since 
org-bbdb.el is a suggested model for people to look at when devising 
custom link types.

Yours,
Christian


On 2/12/11 11:11 PM, Bastien wrote:
> Hi Christian,
>
> Christian Moe<mail@christianmoe.com>  writes:
>
>> I think I've tracked down the problem, but I don't necessarily understand
>> what org-export-normalize-links is supposed to do or what other behaviors
>> depend on this, so I'm not going to submit a patch. If this is now the
>> intended behavior, it will be no problem to rewrite the custom link export
>> definitions to take account of it.
>
> Here again*, I think org-export-normalize-links: various backends will
> decide what to do about having identical [path] and [desc].
>
> I'd welcome a patch making org-bbdb.el a bit more clever about this.
>
> Thanks!
>
> * see my recent email about org-footnote-normalize
>

  parent reply	other threads:[~2011-02-13 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 10:29 Unintended behavior? Links without description Christian Moe
2010-12-31 20:09 ` Thomas S. Dye
2011-02-12 22:11 ` Bastien
2011-02-13 12:45   ` [PATCH] " Christian Moe
2011-02-15  4:38     ` Bastien
2011-02-13 12:49   ` Christian Moe [this message]
2011-02-15  4:39     ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2010-12-28 10:11 Christian Moe

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=4D57D35F.7050403@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=bastien.guerry@wikimedia.fr \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).