Patrick Sanan writes:
>> Am 26.05.2021 um 18:39 schrieb Jed Brown :
>>
>> Patrick Sanan mailto:patrick.sa...@gmail.com>>
>> writes:
>>
Am 25.05.2021 um 22:58 schrieb Barry Smith :
Now that the users manual is html and we can properly link into it, it
would be
> Am 26.05.2021 um 18:39 schrieb Jed Brown :
>
> Patrick Sanan mailto:patrick.sa...@gmail.com>>
> writes:
>
>>> Am 25.05.2021 um 22:58 schrieb Barry Smith :
>>>
>>>
>>> Now that the users manual is html and we can properly link into it, it
>>> would be great to have links from the manual
> Am 27.05.2021 um 00:24 schrieb Barry Smith :
>
>
>
> Jed pointed out previously that ideally we would not just generate a million
> pages of .rst or markdown but we would have the structure of a manual page as
> an abstract object on which one could write code to validate, to add new
>
Jed pointed out previously that ideally we would not just generate a million
pages of .rst or markdown but we would have the structure of a manual page as
an abstract object on which one could write code to validate, to add new
information and to output in a particular .rst or markdown.
Patrick Sanan writes:
>> Am 25.05.2021 um 22:58 schrieb Barry Smith :
>>
>>
>> Now that the users manual is html and we can properly link into it, it
>> would be great to have links from the manual pages to appropriate locations
>> in the users manual. For example SNESSetFunction.html
> Am 25.05.2021 um 22:58 schrieb Barry Smith :
>
>
> Now that the users manual is html and we can properly link into it, it
> would be great to have links from the manual pages to appropriate locations
> in the users manual. For example SNESSetFunction.html would have a link to
> the
Now that the users manual is html and we can properly link into it, it would
be great to have links from the manual pages to appropriate locations in the
users manual. For example SNESSetFunction.html would have a link to the
generated Spinx location where SNESSetFunction is discussed.
