While all current callers pass valid data to ascii_hspan() only,

it's safer to assume incoming enum data might be invalid
and catch it instead of happily returning an unitialized int.
No functional change right now.

1 files changed, 1 insertions, 1 deletions

diff --git a/term_ascii.c b/term_ascii.c
index 248a6ca4..753cc832 100644
--- a/term_ascii.c
+++ b/term_ascii.c
@@ -253,7 +253,7 @@ ascii_hspan(const struct termp *p, const struct roffsu *su)
 	case SCALE_EM:
 		r = su->scale;
 		break;
-	case SCALE_MAX:
+	default:
 		abort();
 		/* NOTREACHED */
 	}