On 3 May 2012 16:21, John BORIS wrote:
[snip]
> I was wondering if there is anyone on the list that had dealt with
> troff documents and came across a profiler or some other script or code
> highlighter that you could run the document through that would tell you
> certain things are missing or ou
Mark,
>Ah, fond memories.
memories you might like to forget
>As suggested, a revision control system would be a huge help. You
don't need
>anything as fancy as a distributed client/server system--I'm a big fan
of
>using RCS (possibly in addition to svn) for local revision control.
yes something I
In the message dated: Thu, 03 May 2012 11:21:26 EDT,
The pithy ruminations from "John BORIS" on
<[lopsa-discuss] Looking for help with troff documents> were:
=> Here at $WORK I maintain a legacy system that does its reports with
=> essentially troff. We use an enhanced ve
Howard,
A Version control system sounds a good way to go but I would have to
make it automated. These files are on 17 remote systems and it wouldn't
be a major event to do this. I get these calls usually four separate
times a year (when they run these reports). Usually they made a backup
copy of th
On Thu, May 3, 2012 at 11:21 AM, John BORIS wrote:
> The documents were created years ago and each year they have just been
> edited. My issues normally are with someone deleting a .\} or a \{\ or
> add an errant one of these. Things work fine until the perfect storm and
> bingo pages print on to
Here at $WORK I maintain a legacy system that does its reports with
essentially troff. We use an enhanced version called Eroff but the
commands are the same except for the ones that Eroff adds but the normal
ifs, else and brackets are the same. This is not a macro issue it is an
issue with section
