From: "Thomas S. Dye" <tsd@tsdye.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>, mail@christianmoe.com
Subject: Re: org-add-link-type
Date: Sat, 12 Feb 2011 13:16:52 -1000 [thread overview]
Message-ID: <254C5983-D49B-4363-943A-9AC029AF3CEF@tsdye.com> (raw)
In-Reply-To: <878vxkvpwf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 16 bytes --]
Aloha Bastien,
[-- Attachment #2: 0001-lisp-org.el-Documentation-change-for-org-add-link-ty.patch --]
[-- Type: application/octet-stream, Size: 1022 bytes --]
From 7f8d2f1ccab79b9e0978ebfe730fb3f5bb82b6ca Mon Sep 17 00:00:00 2001
From: Tom Dye <tsd@tsdye.com>
Date: Sat, 12 Feb 2011 13:14:55 -1000
Subject: [PATCH] * lisp/org.el: Documentation change for org-add-link-type
---
lisp/org.el | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index e56ce4f..8168a28 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8268,7 +8268,8 @@ EXPORT should format the link path for export to one of the export formats.
It should be a function accepting three arguments:
path the path of the link, the text after the prefix (like \"http:\")
- desc the description of the link, if any, nil if there was no description
+ desc the description of the link, if any, or a description added by
+ org-export-normalize-links if there is none
format the export format, a symbol like `html' or `latex' or `ascii'..
The function may use the FORMAT information to return different values
--
1.7.1
[-- Attachment #3: Type: text/plain, Size: 673 bytes --]
All the best,
Tom
On Feb 12, 2011, at 12:39 PM, Bastien wrote:
> Hi Thomas,
>
> "Thomas S. Dye" <tsd@tsdye.com> writes:
>
>> Thanks for looking at this. The problem isn't that the description
>> is
>> being protected from conversion, it is that it is there at all. The
>> link in the example lacks a description and the documentation says
>> that in this case desc will be nil, so it was a surprise to find a
>> value being passed instead.
>
> Yes -- that's because org-export-normalize-links add a description
> when
> there is none.
>
> Can you tell me where the documentation is wrong about this? I cannot
> find it right now.
>
> Thanks!
>
> --
> Bastien
[-- Attachment #4: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-02-12 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 0:29 org-add-link-type Thomas S. Dye
2010-12-27 6:10 ` org-add-link-type Christian Moe
2010-12-27 7:06 ` org-add-link-type Thomas S. Dye
2010-12-27 10:58 ` org-add-link-type Christian Moe
2011-01-17 18:35 ` org-add-link-type Bastien
2011-01-18 17:45 ` org-add-link-type Thomas S. Dye
2011-02-12 22:39 ` org-add-link-type Bastien
2011-02-12 23:16 ` Thomas S. Dye [this message]
2011-02-12 23:32 ` org-add-link-type Bastien
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=254C5983-D49B-4363-943A-9AC029AF3CEF@tsdye.com \
--to=tsd@tsdye.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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
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).