[bug #64360] [PATCH] [gropdf] does not correctly handle white space after 'w' command

[Dave]

Follow-up Comment #26, bug #64360 (project groff):

[comment #25 comment #25:]
> * My comment #22 was addressed to Dave, not you; please don't
> feel under any expectation to present a detailed response to it.

I'll also not respond in detail.  I agree with large portions of it, but more
importantly, as I said at the end of comment #21, I consider the debate
largely academic.  (Not entirely, as Branden points out, because there's a
higher hurdle for enacting an API change, but I don't foresee any real
opposition to that in practice, either, since it's CSTR #54 conforming.)

> [comment #24 comment #24:]
> > Try:-
> > 
> >   vlc http://chuzzlewit.co.uk/screen.mp4
> 
> That's a lot of work.  :-|

Indeed, and writing code must be even more of a chore using that input method
(slick as it is for what it does).  Consider me more impressed that the nearly
4000-line gropdf exists and is well written.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64360>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/