Re: Org-mode ASCII Export to support numbered references for links

[Husain Alshehhi]

On Sun 12 Dec 2021 at 19:30, "Samuel Wales"  wrote:

> you can also use inline footnotes.google[fn::https://google.com] which
> will be exported like you like as a kludge if there is noe.

Surprisingly, this does the job. However, this fundamentally changes
the semantics of what I am writing. The link is not a footnote, it is
just a link. So, when I export the document in HTML, it is rendered as
footnotes rather than links.

Re: Org-mode ASCII Export to support numbered references for links

[Husain Alshehhi]

On Sun 12 Dec 2021 at 19:27, "Samuel Wales"  wrote:

> idk but you can put them in place using org-ascii-links-to-notes for a
> dry effect.

This is fine if the link is short. But if I want to include a very long
link, such as
https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=search+for+something&submit=Search&idxname=emacs-orgmode
it becomes less practical.

Re: Org-mode ASCII Export to support numbered references for links

[Samuel Wales]

you can also use inline footnotes.google[fn::https://google.com] which
will be exported like you like as a kludge if there is noe.

On 12/12/21, Samuel Wales  wrote:
> idk but you can put them in place using org-ascii-links-to-notes for a
> dry effect.
>
> On 12/12/21, Husain Alshehhi  wrote:
>> Org-mode's ascii export uses the link's description to create a reference
>> to
>> it at the end of the document. For example, a link to google will look
>> like
>> this:
>>
>> ,
>> | This is a [link to google].
>> |
>> | [link to google] 
>> `
>>
>> Is there a way to modify this behavior to using a number reference rather
>> than link description? Such as:
>>
>> ,
>> |
>> | This is a link to google[1].
>> |
>> | [1] 
>> `
>>
>> The reasoning behind this is that using numbers is more intuitive (as it
>> is
>> the common practice it plain text posts, emails etc.) Also, when there
>> are
>> two different links with the same description, the export is going to be
>> confusing to the reader. This happens when I use the description "link".
>>
>>
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

Re: Org-mode ASCII Export to support numbered references for links

[Samuel Wales]

idk but you can put them in place using org-ascii-links-to-notes for a
dry effect.

On 12/12/21, Husain Alshehhi  wrote:
> Org-mode's ascii export uses the link's description to create a reference to
> it at the end of the document. For example, a link to google will look like
> this:
>
> ,
> | This is a [link to google].
> |
> | [link to google] 
> `
>
> Is there a way to modify this behavior to using a number reference rather
> than link description? Such as:
>
> ,
> |
> | This is a link to google[1].
> |
> | [1] 
> `
>
> The reasoning behind this is that using numbers is more intuitive (as it is
> the common practice it plain text posts, emails etc.) Also, when there are
> two different links with the same description, the export is going to be
> confusing to the reader. This happens when I use the description "link".
>
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

Org-mode ASCII Export to support numbered references for links

[Husain Alshehhi]

Org-mode's ascii export uses the link's description to create a reference to it 
at the end of the document. For example, a link to google will look like this:

,
| This is a [link to google].
|
| [link to google] 
`

Is there a way to modify this behavior to using a number reference rather than 
link description? Such as:

,
|
| This is a link to google[1].
|
| [1] 
`

The reasoning behind this is that using numbers is more intuitive (as it is the 
common practice it plain text posts, emails etc.) Also, when there are two 
different links with the same description, the export is going to be confusing 
to the reader. This happens when I use the description "link".