Follow-up Comment #6, bug#60930 (group groff): [comment #0 original submission:] > * Make the script portable by removing dependencies on > bash-specific features
I'm now wondering if there's some wisdom to doing a first cut that simply checks whether bash is available and bails gracefully if not. This would leave some users out in the cold, but it would serve a lot of them, and that's got to be an improvement over serving none. And it wouldn't require a bash install dependency for groff, just a run-time one for one groff utility that provides functionality groff didn't provide before anyway. > * Write a man page Four years ago, James K. Lowden volunteered to do this (http://lists.gnu.org/r/groff/2020-04/msg00071.html). I'm adding him to the cc to see if he's still up for this. Divide and conquer! > * Write some test cases to ensure it works as expected It's possible Peter Schaffter, the script's developer, has some he's used privately and would be willing to share. Putting him on cc as well. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60930> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
