From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>,
Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: BUG ??? Cannot export custom link type to ASCII :-(
Date: Wed, 29 Sep 2010 07:55:05 +0200 [thread overview]
Message-ID: <3227634B-2C33-47F9-A61B-A48F8254ED77@gmail.com> (raw)
In-Reply-To: <8762yjvwv1.fsf@gmx.de>
Hi Sebastian,
is this still an open issue? If you, can you please summarize
again and show the code you are using for your link definition?
I am not sure if I have up to date information.
- Carsten
On Sep 6, 2010, at 3:13 PM, Sebastian Rose wrote:
> Bastien <bastien.guerry@wikimedia.fr> writes:
>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>
>>> C-c C-e A
>>>
>>> gives me:
>>>
>>> Debugger entered--Lisp error: (void-variable type)
>>
>> This should now be fixed in git - please pull and try.
>
> Yes, it is fixed.
>
>
> I still can return what ever I want with no effect (ASCII only):
>
>
> <mime-attachment>
>
> Org file:
>
> * Test links
>
> [[track:((9.707032442092896 52.37033874553582))test.svg][test-track]]
>
>
> ASCII-export:
>
> 1 Test links
> ~~~~~~~~~~~~~
>
> [test-track]
>
>
> [test-track]: track:((9.707032442092896 52.37033874553582))test.svg
>
>
> Sebastian
next prev parent reply other threads:[~2010-09-29 6:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 1:37 BUG ??? Cannot export custom link type to ASCII :-( Sebastian Rose
2010-09-05 5:59 ` Carsten Dominik
2010-09-05 11:03 ` Sebastian Rose
2010-09-05 18:05 ` Bastien
2010-09-05 23:01 ` Sebastian Rose
2010-09-06 6:19 ` Carsten Dominik
2010-09-06 7:33 ` Sebastian Rose
2010-09-06 11:16 ` Bastien
2010-09-06 13:13 ` Sebastian Rose
2010-09-29 5:55 ` Carsten Dominik [this message]
2010-09-29 22:35 ` Sebastian Rose
2010-09-30 19:57 ` Carsten Dominik
2010-09-30 22:15 ` Sebastian Rose
2010-09-06 6:50 ` Bastien
2010-09-06 7:29 ` Sebastian Rose
2010-09-06 7:52 ` Bastien
2010-09-06 7:54 ` Carsten Dominik
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=3227634B-2C33-47F9-A61B-A48F8254ED77@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian_rose@gmx.de \
/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).