tahnk you. that makes sense for validity. still not sure about
uniqueness. it's not needed for me to understand, though.
of course with across-export link stability then uniqueness would be meaningful.
On 5/21/21, Nicolas Goaziou wrote:
> Hello,
>
> Samuel Wales writes:
>
>> so i am curious
Hello,
Samuel Wales writes:
> so i am curious what the purpose of the default is?
I think the purpose of the default value is to offer a solution that
works for everyone. It is certainly not the best one in all situations.
For example, I heard that even in 2021, using full Unicode in a URL is
thanks for the example. yes, that is the example i was thinkng of.
i was asking, why does adding uniqueness do any good currently. if
the user has your example as follows, it does create duplicates in the
output, but i don't get why that all by itself needs fixing by
default.
===vvv
I may try t
* Samuel Wales [2021-05-21 01:19]:
> thanks for pointing us to this variable.
>
> docstring says "This process ensures that these values are unique and
> valid...", so it sounds like you could create non-unique or invalid
> identifiers without it.
>
> does this mean, for example, if the user exp
thanks for pointing us to this variable.
docstring says "This process ensures that these values are unique and
valid...", so it sounds like you could create non-unique or invalid
identifiers without it.
does this mean, for example, if the user exports a subtree with two
link targets with the same
* Nicolas Goaziou [2021-05-20 23:00]:
> > Is there a possibility to tell Org, that <> really remains
> > "target" as in id="target" instead of a random ID?
>
> See `org-html-prefer-user-labels'.
Thanks.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Hello,
Jean Louis writes:
> Is it possible to create a custom <>:
>
> From: (info "(org) Internal Links")
>
> 1. one item
> 2. <>another item
> Here we refer to item [[target]].
>
> That is fine, however, in the HTML output the <> will become
> something like: another item
>
> As
Is it possible to create a custom <>:
From: (info "(org) Internal Links")
1. one item
2. <>another item
Here we refer to item [[target]].
That is fine, however, in the HTML output the <> will become
something like: another item
As I am developing finely grained referenced Org out
