Re: An extremely lazy proposal

2024-03-26 Thread Dave Kemper
On Fri, Mar 22, 2024 at 5:24 PM G. Branden Robinson wrote: > My view is expressed in groff(1): ... >An even easier way to do this is to use grog(1) to guess the >preprocessor and macro options and execute the result by using >the command substitution feature of the shell.

Re: An extremely lazy proposal

2024-03-23 Thread Larry McVoy
I've only half paid attention to this thread so if this has been mentioned, sorry. I vaguely remember something like this: .\" $ROFF -s -t $FILES Near the top of the file and then there was a roff script that grepped out that line, set ROFF to groff, FILE to $* and execed that sequence. It's

Re: An extremely lazy proposal

2024-03-23 Thread Oliver Corff via
Dear Branden, Dave, Lennart and Peter (in alphabetical order), thank you for your various replies and suggestions. With regard to hidden caveats in my naive one-for-all attempt, I ignored the potential consequences of the -s option. Thank you for pointing out that. So, next to introducing an

Re: An extremely lazy proposal

2024-03-23 Thread Oliver Corff
Hi Lennart, I constantly ignore this trap due to my less-than-frequent postings. Thank you for pointing out this one. Best, Oliver. On 22/03/2024 22:26, Lennart Jablonka wrote: Quoth Oliver Corff via: Reply-to:  Oliver Corff This might not be the greatest of ideas.  An MUA might just

Re: An extremely lazy proposal

2024-03-23 Thread Ulrich Lauther
I solved this problem for me by having a pseudo comment in the first line of my documents which indicates how this individual document is to be handled. In my bash-script, that eventally calls groff with appropriate options and preprocessors I have FILE="$1" # check for .\" eqn tbl add

Re: An extremely lazy proposal

2024-03-22 Thread G. Branden Robinson
Hi Oliver, At 2024-03-22T21:01:27+0100, Oliver Corff via wrote: > recently I compiled, and re-compiled, and again recompiled a set of > various documents with different tables, equations etc.. For each of > the documents, the precise requirements of preprocessors were > different, and more often

Re: An extremely lazy proposal

2024-03-22 Thread Dave Kemper
I don't have any complaint with your proposal, but it sounds like what you need is a makefile or script to insure groff runs are done the same way every time. More simplistically, you can define a shell alias to invoke all preprocessors: "alias groff='groff -k -e -p -t -R'". (Or name the alias

Re: An extremely lazy proposal

2024-03-22 Thread Peter Schaffter
On Fri, Mar 22, 2024, Oliver Corff via wrote: > Dear All, > > recently I compiled, and re-compiled, and again recompiled a set of > various documents with different tables, equations etc.. For each of the > documents, the precise requirements of preprocessors were different, and > more often than

Re: An extremely lazy proposal

2024-03-22 Thread Lennart Jablonka
Quoth Oliver Corff via: Reply-to: Oliver Corff This might not be the greatest of ideas. An MUA might just decide to reply to you only, instead of to you and the list. Dear All, recently I compiled, and re-compiled, and again recompiled a set of various documents with different tables,

An extremely lazy proposal

2024-03-22 Thread Oliver Corff via
Dear All, recently I compiled, and re-compiled, and again recompiled a set of various documents with different tables, equations etc.. For each of the documents, the precise requirements of preprocessors were different, and more often than not, I forgot to set the appropriate groff option when