ascii section references for id links can be inline?

ascii section references for id links can be inline?

[Samuel Wales]

can ascii output for id links be inline?

=== org source
Some recent test results are [[id:aa8795c5-7ee7-48e2-84f7-49d26f371632][here]].
===

=== current output
Some recent test results are [here].

[here] See section 6.2.2.2
===

=== possible new output
Some recent test results are in section 6.2.2.2
===

i'm not sure what syntax or feature would be appropriate.

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

The NIH, FDA, and CDC are not there for you.  Not without activism.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: ascii section references for id links can be inline?

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> can ascii output for id links be inline?
>
> === org source
> Some recent test results are [[id:aa8795c5-7ee7-48e2-84f7-49d26f371632][here]].
> ===
>
> === current output
> Some recent test results are [here].
>
> [here] See section 6.2.2.2
> ===
>
> === possible new output
> Some recent test results are in section 6.2.2.2
> ===
>
> i'm not sure what syntax or feature would be appropriate.

You can remove the description. Otherwise, Org will do its best to use
it.

Regards,

-- 
Nicolas Goaziou

Re: ascii section references for id links can be inline?

[Samuel Wales]

On 3/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> === possible new output
>> Some recent test results are in section 6.2.2.2
>> ===

> You can remove the description. Otherwise, Org will do its best to use
> it.

in maint, [[id:...]] results in the filename, rather than the section number.

Re: ascii section references for id links can be inline?

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> On 3/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>>> === possible new output
>>> Some recent test results are in section 6.2.2.2
>>> ===
>
>> You can remove the description. Otherwise, Org will do its best to use
>> it.
>
> in maint, [[id:...]] results in the filename, rather than the section
> number.

Odd. In maint, the following document

  * Headline
  :PROPERTIES:
  :id:       whatever
  :END:


  See [[id:whatever]] !

results in

  1 Headline
  ══════════

    See 1 !


Regards,

-- 
Nicolas Goaziou

Re: ascii section references for id links can be inline?

[Samuel Wales]

On 3/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Odd. In maint, the following document
>
>   * Headline
>   :PROPERTIES:
>   :id:       whatever
>   :END:
>
>
>   See [[id:whatever]] !
>
> results in
>
>   1 Headline
>   ══════════
>
>     See 1 !

the behavior i found occurs when you use a link that refers outside
the exported subtree, which i'd classify as user error.  can that be
made to raise an error signal?

"you are linking to outside the subtree being exported.  the result
will be meaningless for the typical recipient of the export."

thanks.

-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

The NIH, FDA, and CDC are not there for you.  Not without activism.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

Re: ascii section references for id links can be inline?

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> On 3/7/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> Odd. In maint, the following document
>>
>>   * Headline
>>   :PROPERTIES:
>>   :id:       whatever
>>   :END:
>>
>>
>>   See [[id:whatever]] !
>>
>> results in
>>
>>   1 Headline
>>   ══════════
>>
>>     See 1 !
>
> the behavior i found occurs when you use a link that refers outside
> the exported subtree, which i'd classify as user error.  can that be
> made to raise an error signal?
>
> "you are linking to outside the subtree being exported.  the result
> will be meaningless for the typical recipient of the export."

This is a user error then. Besides, both files could belong to the same
publishing project.

If you are sure you don't want to export these, just filter them out of
the output using a hook or a filter.

Regards,

-- 
Nicolas Goaziou

Re: ascii section references for id links can be inline?

[Samuel Wales]

On 3/10/17, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> the behavior i found occurs when you use a link that refers outside
>> the exported subtree, which i'd classify as user error.  can that be
>> made to raise an error signal?
>>
>> "you are linking to outside the subtree being exported.  the result
>> will be meaningless for the typical recipient of the export."
>
> This is a user error then. Besides, both files could belong to the same
> publishing project.

just to clarify, that was a proposed error message and a hypothesized
cause.  while i personally think an error in this case could be
useful, at least for people like myself who always export subtrees,
it's not huge.

> If you are sure you don't want to export these, just filter them out of
> the output using a hook or a filter.

just to clarify, i would always want to export them, but to be told by
org that i am referring to outside what i am exporting.