Re: usenet to email gateway

[Karl Berry]

not sure who to report that to

I've asked the FSF sysadmins.  I can see from the mailing list
configuration that the gateway is intended to be operational, but don't
know how to debug what it happening from there.

Best,
Karl

bashref.texi niglets

[Karl Berry]

Hi Chet,

Perusing bashref.texi ...

1) Technically, version.texi should be before the %**end of header.

2) @setchapternewpage odd creates blank pages.  There's no need to
inflict them on everyone by default.  If the FSF or anyone wants that
for printing, they can always use -t @setchapternewpage odd or whatever.

3) The "Permission is granted ..." paragraph is part of the old
permissions statement and shouldn't be used with the GFDL.  (The FDL
grants the same permission.)  And no need for blank line before
@end quotation.

4) The Temple Place FSF address is stale and has been for years
(http://www.fsf.org/about/contact/ has their present address).  I
suggest removing it from here and let the FSF put in wherever they
happen to be when and if they print the manual.  (BTW, they aren't
distributing it now, as far as I can see from
http://shop.fsf.org/category/books/.)

5) Mention the bash home page.  What the heck?

6) Better to send bug reports to the list than you personally?

Happy documenting,
Karl


--- ORIG/bashref.texi   2011-01-16 12:31:57.0 -0800
+++ bashref.texi2012-08-22 08:57:35.0 -0700
@@ -4,7 +4,4 @@
 @settitle Bash Reference Manual
-@c %**end of header
-
-@setchapternewpage odd
-
 @include version.texi
+@c %**end of header
 
@@ -20,6 +17,2 @@
 
-Permission is granted to make and distribute verbatim copies of
-this manual provided the copyright notice and this permission notice
-are preserved on all copies.
-
 @quotation
@@ -35,3 +28,2 @@
 developing GNU and promoting software freedom.''
-
 @end quotation
@@ -61,9 +53,2 @@
 @insertcopying
-
-@sp 1
-Published by the Free Software Foundation @*
-59 Temple Place, Suite 330, @*
-Boston, MA 02111-1307 @*
-USA @*
-
 @end titlepage
@@ -77,3 +62,4 @@
 This text is a brief description of the features that are present in
-the Bash shell (version @value{VERSION}, @value{UPDATED}).
+the Bash shell (version @value{VERSION}, @value{UPDATED}).  The Bash
+home page is @url{http://www.gnu.org/software/bash/}.
 
@@ -7663,3 +7649,3 @@
 Please send all reports concerning this manual to
-@email{chet.ramey@@case.edu}.
+@email{bug-bash@@gnu.org}.
 

Diff finished at Wed Aug 22 08:59:34

Re: [Bash-announce] source of tar, gzip, gunzip, bzip, bunzip2 and compress ???

[Karl Berry]

am not quite sure, if this is the right site for this question.

[EMAIL PROTECTED] or bug-bash@gnu.org would have been better, but
your mistake is understandable.  Cc-ing bug-bash here, since this is
certainly not an announcement.

Where e.g. I can obtain the source code of the commands like following:
tar, gunzip, compress, and gzip ???

You can download the sources for most GNU packages (including those)
from http://ftp.gnu.org/gnu.

In the bash-source code, the commands (about 3300 bash commands) are
not included with their own source code ???

They are not bash commands.  They are their own packages.

Hope this helps,
[EMAIL PROTECTED]

Re: Patch to bashref.texi

[Karl Berry]

On this mail from last month ...

Date: Tue, 20 Apr 2010 14:03:25 -0400
vincent> > The thing is that when you get the manual from this page
> > [[http://www.gnu.org/software/bash/manual/bashref.info.tar.gz]]

chet> I don't distribute that.  Try the bashref manual from the source
> distribution.

I updated http://www.gnu.org/software/bash/manual/ from the 4.1 sources,
using the name bash.texi this time.  I admit I don't understand the
purpose bash/bashref name switch in bash's doc/Makefile, but hopefully
this works ok.

BTW, Chet, if you'd be willing to update the manual in the future, I'd
be happy to give you the incantation of the gendocs.sh utility
(described in maintain.texi) that does all the work.

Happy documenting,
karl

Re: Patch to bashref.texi

[Karl Berry]

> hmm as a side effect you broke all the links to bashref.html out there...

Oh yeah :).  I'll put in a redirect, or something.

Thanks,
k