<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Thanks for this suggestion. The + and - were added to make it easier to generate a nicely formatted list, though its possible to look for transitions from non-list to list and back to non-list. Think of + as similar to \begin{description}\item … and - as
\item … \end{description}.
<div class=""><br class="">
</div>
<div class="">I’ve updated doctext to allow both - and a isolated . for an argument description. In the process of doing this, I added checks for errors in the use of the doctext formatting, and found many minor errors, as well as updating the old arg lists
that didn’t use the + .. - . I have a branch for petsc that fixes all of those (it was the easiest way for me to be sure my doctext fixes worked) that will need to be merged. Let me know how you’d like me to submit that. There are also many malformed entries
where there is no description. I’ve turned those warnings off by default, but -Wargdesc will warn for each argument that is missing a description; some of these should use different formatting instead of the argument lists.</div>
<div class=""><br class="">
</div>
<div class="">The new version, in sowing-1.1.26, also has updates to bfort (which requires the patch that I sent earlier to bin/maint/generatefortranstubs.py ) and other miscellaneous fixes. I’ve uploaded this version to my web page and it is the default when
you download sowing.tar.gz . I am unable to update the confdb macros to fix errors in them - the permissions have changed on the repository (for my own files!). Because of that and other problems, I plan to move sowing to a git repository that I fully control
soon; this weekend if I can.</div>
<div class=""><br class="">
</div>
<div class="">Let me know if you have any problems.</div>
<div class=""><br class="">
</div>
<div class="">Bill</div>
<div class=""><br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
William Gropp<br class="">
Director and Chief Scientist, NCSA<br class="">
Thomas M. Siebel Chair in Computer Science<br class="">
University of Illinois Urbana-Champaign</div>
<br class="Apple-interchange-newline">
</div>
</div>
<br class="Apple-interchange-newline">
</div>
<br class="Apple-interchange-newline">
</div>
<br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Jun 15, 2019, at 12:06 PM, Smith, Barry F. <<a href="mailto:bsmith@mcs.anl.gov" class="">bsmith@mcs.anl.gov</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class=""><br class="">
<br class="">
<blockquote type="cite" class="">On Jun 15, 2019, at 11:57 AM, Patrick Sanan <<a href="mailto:patrick.sanan@gmail.com" class="">patrick.sanan@gmail.com</a>> wrote:<br class="">
<br class="">
Great! I'll leave that commit there for reference, but as you say it would be even nicer (but more coding) to avoid needing to explicitly mark the starts and ends of lists.<br class="">
</blockquote>
<br class="">
Yeah, I only remember vaguely that initially we didn't use the + and - on the lists and there was some issue so they were introduced.
<br class="">
<br class="">
Barry<br class="">
<br class="">
<blockquote type="cite" class=""><br class="">
Am Sa., 15. Juni 2019 um 17:54 Uhr schrieb Smith, Barry F. <<a href="mailto:bsmith@mcs.anl.gov" class="">bsmith@mcs.anl.gov</a>>:<br class="">
<br class="">
Patrick (and Bill)<br class="">
<br class="">
Good timing. Bill is actually updating Sowing now and could perhaps fix this glitch. Currently we use a . for a single entry in the list and I'd hate to have to change them all the -. Likely it is possible to fix the formatting for the . case to have the
same indent as the + . - cases.<br class="">
<br class="">
Barry<br class="">
<br class="">
<blockquote type="cite" class="">On Jun 15, 2019, at 10:15 AM, Patrick Sanan via petsc-dev <<a href="mailto:petsc-dev@mcs.anl.gov" class="">petsc-dev@mcs.anl.gov</a>> wrote:<br class="">
<br class="">
Lists on the man pages don't seem to be able to have a single entry, because sowing requires you to start lists with "+" and end them with "-", requiring at least two entries.<br class="">
<br class="">
This leads to ugly-looking indentation for man pages for functions with a single input or output parameter, e.g.
<a href="https://www.mcs.anl.gov/petsc/petsc-dev/docs/manualpages/DMSTAG/DMStagVecGetArrayDOF.html" class="">
https://www.mcs.anl.gov/petsc/petsc-dev/docs/manualpages/DMSTAG/DMStagVecGetArrayDOF.html</a><br class="">
<br class="">
I think that this can be remedied with a small change to sowing (doctext), to interpret a lone '-' as opening a list (and then closing it after one entry):
<a href="https://bitbucket.org/psanan/sowing/commits/780ea53824388e8c6089ae2d6210332c63935edb" class="">
https://bitbucket.org/psanan/sowing/commits/780ea53824388e8c6089ae2d6210332c63935edb</a><br class="">
<br class="">
(Posting this here since I'm not sure how closely the <a href="http://bitbucket.org/petsc/pkg-sowing" class="">
bitbucket.org/petsc/pkg-sowing</a> repository is monitored)<br class="">
</blockquote>
<br class="">
</blockquote>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>