Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.groff.bug > #1747 > unrolled thread
| Started by | "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> |
|---|---|
| First post | 2020-02-13 05:40 -0500 |
| Last post | 2020-02-13 05:40 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.groff.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
[bug #55941] [PATCH] test-nroff: Create this file to accompany "test-groff" "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> - 2020-02-13 05:40 -0500
| From | "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> |
|---|---|
| Date | 2020-02-13 05:40 -0500 |
| Subject | [bug #55941] [PATCH] test-nroff: Create this file to accompany "test-groff" |
| Message-ID | <mailman.778.1581590423.2412.bug-groff@gnu.org> |
Follow-up Comment #4, bug #55941 (project groff):
I have a new appreciation for Bjarni's request now that I've had to actually
write a test for nroff. :P
Because of the variable runtime environment, influenced by the configuration
parameters, we can't just ship canned tests for it: we have to generate them,
then run them.
I solved this problem in dd725dce808dcff643d33f180ed7ac73e32b0760 but it took
a little bit of effort and thought, mainly due to my lack of familiarity with
automake.
Just a comment. Future nroff tests can ape my example and we still won't need
a 'test-nroff', but if generating the tests comes to be viewed as ugly or
excessively weighty, it might be wise to reconsider this report.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55941>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Back to top | Article view | gnu.groff.bug
csiph-web