bugGNU roff - Bugs: bug #59545, MORE.STUFF: Add material

 
 

bug #59545: MORE.STUFF: Add material

Submitter:  Bjarni Ingi Gislason <bjarniig>
Submitted:  Wed 25 Nov 2020 06:45:45 PM UTC
   
 
Category:  General Severity:  3 - Normal
Item Group:  Documentation Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 26 Sep 2023 05:23:39 PM UTC, comment #13: 

comment #12:

> If it someday acquires content, the "collection of user macrosets"
> at http://github.com/Allfifthstuning/awesome-groff-user-macrosets


It's acquired a fair amount since I wrote that!

Another resource was referenced on the email list since then as well: http://www.port.de/cgi-bin/groff/GroffTips (one of its tips was linked in http://lists.gnu.org/r/groff/2023-08/msg00059.html).

Dave <barx>
Group Member
Sat 23 Jul 2022 10:57:55 PM UTC, comment #12: 

Steering back to the intended topic of this bug, another thing that could be added to MORE.STUFF is the groff examples repository: http://www.froude.eu/groff/ (announced in http://lists.gnu.org/r/groff/2021-08/msg00092.html) or gopher://froude.eu/1/groff (announced in http://lists.gnu.org/r/groff/2021-09/msg00004.html).

If it someday acquires content, the "collection of user macrosets" at http://github.com/Allfifthstuning/awesome-groff-user-macrosets (announced in http://lists.gnu.org/r/groff/2022-06/msg00066.html) could be added as well.

Dave <barx>
Group Member
Sun 17 Jul 2022 03:16:38 PM UTC, comment #11: 

Discussion about incorporating busgrap into groff has had a change of venue: see bug #62778.

Dave <barx>
Group Member
Thu 14 Jul 2022 09:23:00 AM UTC, comment #10: 


comment #9:

> As I understand it, that is not the purpose of contrib.
>
> I recently captured that understanding (which is subject to correction by those longer in the tooth than I) in the "LICENSE" file.
>


> Files in the contrib/ subdirectory of the source distribution are not
> strictly part of groff.  That is, they are distributed with it and are
> Free Software <https://www.gnu.org/philosophy/free-sw.en.html>, but they
> are not considered essential parts of the distribution.  Further, they
> may bear licenses other than the GPL or the FSF does not administer
> their copyrights.  To determine their copyright status and licensing,
> see the "COPYRIGHT" file in the appropriate subdirectory of contrib/.


>
> I don't consider lack of testing a gate to inclusion.  We can write a smoke test for basic sane operation and go from there.
>
> Similarly, if it makes sense to move sboxes out of contrib, we can do that.


I want to follow up to make sure I'm not misunderstood here.  I mean that by not having busgrap or sboxes in contrib, I don't mean not having them in the groff distribution at all, but rather placing them alongside the "main", regular content, i.e., where Deri's gropdf and other contributions already are.

G. Branden Robinson <gbranden>
Group administrator
Wed 13 Jul 2022 04:51:12 AM UTC, comment #9: 

comment #7:

> I do have a question about what we should do with busgrap, don't answer that, and don't change a single letter in the name!


Wuh-oh.  You're really wedded to the name?

'Cause, darn, I sure did have some punning ideas... ;-P

> Probably better to put it into contrib first given the lack of testing it has received.


As I understand it, that is not the purpose of contrib.

I recently captured that understanding (which is subject to correction by those longer in the tooth than I) in the "LICENSE" file.


Files in the contrib/ subdirectory of the source distribution are not
strictly part of groff.  That is, they are distributed with it and are
Free Software <https://www.gnu.org/philosophy/free-sw.en.html>, but they
are not considered essential parts of the distribution.  Further, they
may bear licenses other than the GPL or the FSF does not administer
their copyrights.  To determine their copyright status and licensing,
see the "COPYRIGHT" file in the appropriate subdirectory of contrib/.


I don't consider lack of testing a gate to inclusion.  We can write a smoke test for basic sane operation and go from there.

Similarly, if it makes sense to move sboxes out of contrib, we can do that.

> Either way I would appreciate some help with the makefile required.
>
> The latest version with various fixes and minor documentation changes is at:-
>
> http://chuzzlewit.co.uk/busgrap-20220712.tgz
>
> And the previous link published in emails is now a link to this version.


I'd like to have a look at this because the visual results sure are nice.

It's in my mental queue, somewhere behind the internally-linking-MR-in-PDF-man-pages stuff you sent me, and making afmtodit and BuildFoundries more paranoid (and, ultimately, robust, or at least more helpful to the user when something goes wrong).

G. Branden Robinson <gbranden>
Group administrator
Wed 13 Jul 2022 12:49:16 AM UTC, comment #8: 

comment #7:

> One way is to incorporate it into groff, -B seems to be available.


That's probably a discussion best raised on the main email list, where it'll have more visibility than in this bug report, where this whole discussion is becoming increasingly off topic. :-)

Dave <barx>
Group Member
Tue 12 Jul 2022 10:20:06 PM UTC, comment #7: 

I had forgotten about this! I can confirm all the items found by Peter have been fixed and I will be refreshing the download file soon. I do have a question about what we should do with busgrap, don't answer that, and don't change a single letter in the name!

Where should it be hosted, currently on a Cubox-I4Pro in my office (shed) in the back garden?

Best way to get testers.

One way is to incorporate it into groff, -B seems to be available.

Probably better to put it into contrib first given the lack of testing it has received.

Either way I would appreciate some help with the makefile required.

The latest version with various fixes and minor documentation changes is at:-

http://chuzzlewit.co.uk/busgrap-20220712.tgz

And the previous link published in emails is now a link to this version.

Deri James <deri>
Group Member
Mon 11 Jul 2022 05:17:12 PM UTC, comment #6: 

comment #5:

> What I need is response from testers,


The only one I'm aware of is when Peter did a detailed writeup about it (http://lists.gnu.org/r/groff/2015-06/msg00006.html).  I don't see a response to this (though you may have sent one off-list) so wasn't sure what there had been addressed, other than his first item that echoed Ralph's observation.

But as it stands today, busgrap surely warrants a mention in MORE.STUFF, which may give it more visibility and thus garner more feedback.

Dave <barx>
Group Member
Mon 11 Jul 2022 03:26:43 PM UTC, comment #5: 

If I remember correctly, I included Ralph's patch. I also added .pdfbackground as part of testing the new gropdf feature. What I need is response from testers, I am pretty sure there are probably lots of bugs in the code, also, I was hoping someone (who is incredibly good at technical writing :-)) would rip up all I have written and do it properly.

Deri James <deri>
Group Member
Mon 11 Jul 2022 11:13:06 AM UTC, comment #4: 

The mailing-list link in comment #1 is not clickable.  http://lists.gnu.org/r/groff/2022-04/msg00015.html is a clickable version of it.

The initial "busgrap" announcement was http://lists.gnu.org/r/groff/2015-05/msg00020.html in 2015.  This gives an overview of the package and what it's intended, and not intended, to do.  At the time, it was described like an alpha release; the 2022 posting doesn't make clear what of the 2015 feedback has been incorporated and what, if anything, remains to be done.

Dave <barx>
Group Member
Sun 10 Jul 2022 02:31:41 PM UTC, comment #3: 

Changed Summary as requested by Submitter in comment #1

Dave <barx>
Group Member
Thu 28 Apr 2022 01:48:31 AM UTC, comment #2: 

Corrected web address:

http://chuzzlewit.co.uk/busgrap-20181129.tgz

  That is https -> http and tg.z -> tgz

Bjarni Ingi Gislason <bjarniig>
Thu 28 Apr 2022 01:39:22 AM UTC, comment #1: 

  Add "busgrap" for pie charts, see

"lists.gnu.org/archive/html/groff/2022-04/msg00015.html" and following messages number 16-18.

https://chuzzlewit.co.uk/busgrap-20181129.tg.z

N.B.
  Change subject to "MORE.STUFF: add material".

Bjarni Ingi Gislason <bjarniig>
Wed 25 Nov 2020 06:45:45 PM UTC, original submission:  

MORE.STUFF: Add material about "mandoc" and "demandoc"

For example

mandoc

  Useful for checking for bad usage of conventions, style, macros, and
more with "mandoc -T lint"

demandoc

  The demandoc utility emits only the text portions of well-formed
mdoc(7) and man(7) UNIX manual files.  [demandoc(1)]

Bjarni Ingi Gislason <bjarniig>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by deri (Posted a comment)
  • -email is unavailable- added by barx (Posted a comment)
  • -email is unavailable- added by gbranden (Updated the item)
  • -email is unavailable- added by bjarniig (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-07-10 barx SummaryMORE.STUFF: Add material about &quot;mandoc&quot; and &quot;demandoc&quot; MORE.STUFF: Add material
    2022-06-15 gbranden CategoryCore General

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code