Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.groff.bug > #1869

[bug #55278] src/devices/grotty/grotty.1.man, doc/groff.texi updates

From "G. Branden Robinson" <INVALID.NOREPLY@gnu.org>
Newsgroups gnu.groff.bug
Subject [bug #55278] src/devices/grotty/grotty.1.man, doc/groff.texi updates
Date 2020-06-12 04:41 -0400
Message-ID <mailman.1751.1591951319.2541.bug-groff@gnu.org> (permalink)
References <20181224-182600.sv93119.20700@savannah.gnu.org> <20190101-211121.sv93119.25514@savannah.gnu.org> <20191219-044626.sv93119.64617@savannah.gnu.org> <20200604-015900.sv93119.29954@savannah.gnu.org> <20200612-084157.sv108747.42386@savannah.gnu.org>

Show all headers | View raw


Update of bug #55278 (project groff):

                  Status:                    None => Fixed                  
             Assigned to:                    None => gbranden               
             Open/Closed:                    Open => Closed                 
         Planned Release:                    None => 1.22.5                 

    _______________________________________________________

Follow-up Comment #4:

Fixed in 69c400e082f2b11c8b79a4a6224f174ee8a28d53.

A separate bug could/should be filed for describing how the troff -a output
should actually be read.  Now that I've seen inside src/roff/troff/*.cpp I
have a notion, but the subject sure could use some explanation for a general
audience.

    _______________________________________________________

Reply to this item at:

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

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

Back to gnu.groff.bug | Previous | Next | Find similar


Thread

[bug #55278] src/devices/grotty/grotty.1.man, doc/groff.texi updates "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> - 2020-06-12 04:41 -0400

csiph-web