[bug #64612] consider an environment variable for general resources/inclusions

Follow-up Comment #4, bug #64612 (project groff): I was not aware that a change proposed to forbid paths in .fp third parameter and the "name" written by afmtodit, had also (unintentionally) prevented paths in the grops download file, with no diagnostic message. The proposed "fix" seems to be add

[bug #64612] consider an environment variable for general resources/inclusions

Update of bug #64612 (project groff): Status:None => Need Info ___ Follow-up Comment #5: Hi Deri, [comment #4 comment #4:] > I was not aware that a change proposed to forbid paths in .fp

[bug #64612] consider an environment variable for general resources/inclusions

Follow-up Comment #6, bug #64612 (project groff): Hi Phil, [comment #3 comment #3:] > I think what you are saying is that the groff-specific font metric files (e.g. "desc/TR") should remain where they have always been. Agreed -- they are specific to groff, and there is no need to change the curr

[bug #64594] [troff] "warning: cannot select font 'C'"

Follow-up Comment #4, bug #64594 (project groff): _pandoc_ has fixed this upstream. https://github.com/jgm/pandoc/issues/9020 No word about go-md2man yet. ___ Reply to this item at:

[bug #64602] [troff] `fl` request behavior difficult to rationalize

Follow-up Comment #2, bug #64602 (project groff): [comment #1 comment #1:] > The only output I see in the ps-file is "foobar". > > How is the code supposed to alter the output? > > Comments to explain the code are missing. Comment #0 was written mainly as a note to myself because I have

[bug #64612] consider an environment variable for general resources/inclusions

Follow-up Comment #7, bug #64612 (project groff): [comment #5 comment #5:] > > If the download file containing the path to the postscript > > font is only writeable by root I think we can trust the path. > > That seems unnecessarily restrictive to me. A user might have > a "local" font directory