Ken wrote:
That is basically the same thing as doing a rebase, except that way is
more work. It would invalidate every checked-out copy of the revision
control tree. It _might_ be useful, but would it be worth it?
I think not, if there's not a reasonable way to deal with
checked-out copies.
Bill wrote:
David Levine levin...@acm.org writes:
Ken wrote:
I've seen a number of nmh man pages which say things like this:
Consult the Advanced Features section of the nmh User's Manual for more
information on making digests.
Which leads to to ask ... which manual are they
Yes, it would be awesome to prepend git's history with the original
RCS files. That could probably be done by exporting the git
repository, started anew, importing the RCS files, and then importing
the exported git repository.
Thanks for the approach, it sounds doable but not by me at this
David Levine levin...@acm.org writes:
Ken wrote:
I've seen a number of nmh man pages which say things like this:
Consult the Advanced Features section of the nmh User's Manual for more
information on making digests.
Which leads to to ask ... which manual are they talking about, exactly?
David Levine levin...@acm.org writes:
I found a goldmine: the MH 6.8.5 tar ball contains RCS files
for all of the source code. And it contains the sources
for all of the documentation.
I currently have it staged for addition at docs/historical/mh-6.8.5/
Before committing, is there a way
Hi Paul,
and i'd also propose that we feel free to use groff extensions;
nobody's going to build this on a DWB system again.
Might be nice to stick within the large set of groff that's also
Heirloom troff. Can't think of any obvious reason to step outside of
that for simple documentation.
I've got nothing against bringing in the original troff input; it's
just that what's in the MH 6.8 sources isn't exactly pure troff.
It's got to be run through the build system to get rid of all the
@BEGIN@/@END@ pairs (and I'm not even sure what definitions we
should use to do
David Levine writes:
The old docs, ps converted to pdf, are now in docs/historical/
I notice we've also got plain text and PDF versions of Rose/Romine's
How to process 200 messages a day and still get some real work done
paper in there too. It might be worth grabbing the TeX source while
it's
On Wed, 29 Feb 2012 09:49:08 GMT, Tethys said:
PS. That was the paper that introduced me to the world of MH, some
time in the late '80s. At the time, 200 messages a day was an
inconceivably huge number. At the peak of the spam problem a few
years ago, I was getting over
as Paul implied, troff input is perfectly usable, very much more so than
MSWurd or the Prodigal Data Format
I've got nothing against bringing in the original troff input; it's
just that what's in the MH 6.8 sources isn't exactly pure troff.
It's got to be run through the build system to get rid
On 2012-02-29, at 11:26 AM, Ken Hornstein wrote:
I've got nothing against bringing in the original troff input; it's
just that what's in the MH 6.8 sources isn't exactly pure troff.
It's got to be run through the build system to get rid of all the
@BEGIN@/@END@ pairs (and I'm not even sure
as Paul implied, troff input is perfectly usable,
very much more so than MSWurd or the Prodigal Data Format
-mo
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
On 2/29/2012 7:26 PM, Ken Hornstein wrote:
It's got to be run through the build system to get rid of all the
@BEGIN@/@END@ pairs (and I'm not even sure what definitions we should
use to do that). Someone has to do that grunt work ... and I haven't
heard anyone volunteer for that just yet.
all
I found a goldmine: the MH 6.8.5 tar ball contains RCS files
for all of the source code. And it contains the sources
for all of the documentation.
I currently have it staged for addition at docs/historical/mh-6.8.5/
Before committing, is there a way to not include the contents of
each file in
I found a goldmine: the MH 6.8.5 tar ball contains RCS files for
all of the source code. And it contains the sources for all of the
documentation.
I currently have it staged for addition at docs/historical/mh-6.8.5/
Before committing, is there a way to not include the contents of each
file in
Lyndon wrote:
On 2012-02-29, at 11:26 AM, Ken Hornstein wrote:
I've got nothing against bringing in the original troff input; it's
just that what's in the MH 6.8 sources isn't exactly pure troff.
It's got to be run through the build system to get rid of all the
@BEGIN@/@END@ pairs (and
On Tue, Feb 28, 2012 at 08:53:47PM -0500, Ken Hornstein wrote:
Looks like the MH User's Manual. I found a copy here:
ftp://ftp.vim.org/pub/mail/mh/doc/MH.ps.gz
Hm. Can people actually view this? I tried printing it out and it
died with a PostScript error. I tried opening it on my Mac
On Wed, Feb 29, 2012 at 06:50:13PM -0500, Ken Hornstein wrote:
I found a goldmine: the MH 6.8.5 tar ball contains RCS files for
all of the source code. And it contains the sources for all of the
documentation.
I currently have it staged for addition at docs/historical/mh-6.8.5/
Before
Ken wrote:
I've seen a number of nmh man pages which say things like this:
Consult the Advanced Features section of the nmh User's Manual for more
information on making digests.
Which leads to to ask ... which manual are they talking about, exactly?
Looks like the MH User's Manual. I
Is there a place to store them on Savannah? Or
should I just throw them into the git repo? About 3.5 MB.
Get them into docs/ subdir in the repo before they get lost. We can find a
better home later if that makes sense.
--lyndon
___
Nmh-workers
Looks like the MH User's Manual. I found a copy here:
ftp://ftp.vim.org/pub/mail/mh/doc/MH.ps.gz
Hm. Can people actually view this? I tried printing it out and it
died with a PostScript error. I tried opening it on my Mac and it
could only view the first page; the subsequent pages were all
Thus spake Ken Hornstein:
Looks like the MH User's Manual. I found a copy here:
ftp://ftp.vim.org/pub/mail/mh/doc/MH.ps.gz
Hm. Can people actually view this? I tried printing it out and it
died with a PostScript error. I tried opening it on my Mac and it
could only view the first
I don't suppose anyone is around who still has the original source to
this thing, do they?
Following up myself ...
I found it! It's in the original mh-6.8.4 source, under conf/doc! Yeah,
we should totally get that in our git tree. It's going to take some love to
extract it from the original
It's also probably
going to take a troff guru to figure out how to make it usable.
If you can get the source extracted I can take a run at cleaning up the
troff.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
The old docs, ps converted to pdf, are now in docs/historical/
David
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
I've seen a number of nmh man pages which say things like this:
Consult the Advanced Features section of the nmh User's Manual for more
information on making digests.
Which leads to to ask ... which manual are they talking about, exactly?
--Ken
___
26 matches
Mail list logo
