> Date: Thu, 6 Apr 2023 21:18:22 -0500 > From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx> > Cc: Eli Zaretskii <eliz@xxxxxxx>, dirk@xxxxxxxxxxx, > linux-man@xxxxxxxxxxxxxxx, help-texinfo@xxxxxxx > > > Hmm, now that I think, it's probably an issue of coordinating man(1) > > and less(1). I sometimes wish that when I resize a window where I'm > > reading a man page, it would reformat the page from source. > > Seems like it shouldn't be impossible to me, but what I imagine would > require a little reëngineering of man(1), perhaps to spawn a little > custom program to manage zcat/nroff pipeline it constructs. This little > program's sole job could be to be aware of this pipeline and listen for > SIGWINCH; if it happens, kill the rest of the pipeline and reëxecute it. This should be possible, but it flies in the face of the feature whereby formatted man pages are kept for future perusal, which is therefore faster: if the formatted pages reflect the particular size of the pager's window, it is meaningless to cache them. > ... Run the command 'sudo make uninstall'. (If you successfully used > 'make install', simply run 'make uninstall'.) At a minimum, some > directories not particular to groff, like 'bin' and (depending on > configuration) an X11 'app-defaults' directory will remain, as will > one plain file called 'dir', created by GNU Texinfo's 'install-info' > command. (As of this writing, 'install-info' offers no provision for > removing an effectively empty 'dir' file, and groff does not attempt > to parse this file to determine whether it can be safely removed.) > All other groff artifacts will be deleted from the installation > hierarchy. > > Any chance 'install-info' could get savvy as noted above? (Maybe it > already has--I'm running 6.7.0.) Why does it make sense to do that? An "empty" DIR file is not really empty: it has instructions at its beginning, which are important for newbies. Also, on well-maintained system, DIR will rarely become empty, and if it does, it will soon enough become non-empty again, since all the Info manuals installed on the system should be mentioned there, and why would we want to imagine a system which has no Info manuals at all, not even an Info manual that describes how to use Info (which comes with the Texinfo distribution)? So I think Groff should remove that paragraph from its instructions, because (IMO) it is misleading and unnecessary. Of course, mine is not the authoritative opinion about how the Texinfo project should develop its programs, it is just one opinion. So wait for Gavin to chime in.
