Re: BUG ??? Cannot export custom link type to ASCII :-(

[Carsten Dominik <carsten.dominik@gmail.com>]

Hi Sebastian,

I believe I have fixed the bug.  But please note that there is a
typo in your function osm-org-link-export, in the last line it
must be target, not taget.

HTH

- Carsten

On Sep 30, 2010, at 12:35 AM, Sebastian Rose wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>> 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
>
>
> Hi Carsten,
>
>
> it's still an issue when exporting to ASCII.  The reason is, that my
> "track" links have looooong paths (all the coordinates of the track  
> plus
> the desired filename, see the comments in the code for an example  
> link).
> That causes the "footnote" for a track to span pages (worsed case).
>
> See the example ASCII export on the bottom of this mail.
>
> Anyway, I'll rarely export the files to ASCII, so it's not urgent at
> all.
>
>
>
> The code is here:
>
>   http://github.com/SebastianRose/org-osm/blob/master/org-osm-link.el
>
>
> The function to export those links is:
>
> <mime-attachment>
>
>
>
>
>> On Sep 6, 2010, at 3:13 PM, Sebastian Rose wrote:
>>> 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