On Mon, Jan 27, 2025 at 06:26:22AM -0600, G. Branden Robinson wrote: > At 2025-01-24T07:47:00+0100, Ingo Schwarze wrote: > > G. Branden Robinson wrote on Wed, Jan 22, 2025 at 08:47:20PM -0600: > > > At 2025-01-22T07:10:54+0100, Ingo Schwarze wrote:
> > [...] So a line of text is hardly longer than what a human reader > > instantly recognizes anyway (except when using insane line lengths > > like 100-200 characters; i never understood how people who use such > > wide terminals manage to keep track of which line they are currently > > reading in the first place). > > Me neither! Years ago I used to tolerate this and found myself much > happier when I forced an 80-column limit on man pages I viewed. Since > joining groff development I've embraced a 72-column limit in much of my > work. I am one who often uses these allegedly "insane" line lengths, and I find my personal ideal very dependent on monitor size, resolution, current distance from monitor, eyesight, caffeination level, the language of the text I'm currently reading, and a number of other factors. Fortunately, I have flexibility. > I don't know of anyone who's in love with Git's submodule approach. Not > that finding an alternative would completely address your grievance--but > it would help. You're in luck! I got a patch into Gnulib some years ago that allows using it without submodules, and since git submodules have a hateful UI, I recommend that you switch to it: https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=c083cd5af2655e6cd0240d02dccb28556bad8dbf https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=90f289f249a266b1afb9c63e182f5d979d17df5f It should be a matter of removing .gitmodules and instead setting GNULIB_REVISION in bootstrap.conf to refer to the desired Gnulib commit ID. You can then change that with ordinary commits as needed, rather than trying to remember the submodule commands. -- Colin Watson (he/him) [cjwat...@debian.org]
