diff options
| -rw-r--r-- | ChangeLog | 1 | ||||
| -rw-r--r-- | ChangeLog.1 | 1 | ||||
| -rw-r--r-- | doc/ChangeLog | 5 | ||||
| -rw-r--r-- | doc/gawk.info | 1 | ||||
| -rw-r--r-- | doc/gawk.texi | 21 | ||||
| -rw-r--r-- | doc/gawktexi.in | 21 |
6 files changed, 29 insertions, 21 deletions
@@ -946,7 +946,6 @@ * gawkapi.h: Update copyright year, fix some spelling errors. 2019-07-08 Andrew J. Schorr <aschorr@telemetry-investments.com> -2019-07-08 Andrew J. Schorr <aschorr@telemetry-investments.com> * gawkapi.h (gawk_api_major_version): Bump from 2 to 3 because the namespace changes altered the function signatures in gawk_api_t. diff --git a/ChangeLog.1 b/ChangeLog.1 index b8e192e1..fe99c70c 100644 --- a/ChangeLog.1 +++ b/ChangeLog.1 @@ -531,6 +531,7 @@ 2018-11-11 Arnold D. Robbins <arnold@skeeve.com> * main.c (usage): Improve output for -Z in the help. + 2018-11-11 Arnold D. Robbins <arnold@skeeve.com> * awkgram.y (outer_comment): New variable. diff --git a/doc/ChangeLog b/doc/ChangeLog index 5806e100..13508d8d 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2021-07-09 Arnold D. Robbins <arnold@skeeve.com> + + * gawktexi.in: Make @EMAIL usage consistent everywhere. + Thanks to Antonio Columbo for pointing it out. + 2021-07-07 Andrew J. Schorr <aschorr@telemetry-investments.com> * gawktexi.in (Isnumeric Function): Improve description of how diff --git a/doc/gawk.info b/doc/gawk.info index 880f1e4e..55c9bb3f 100644 --- a/doc/gawk.info +++ b/doc/gawk.info @@ -37615,6 +37615,7 @@ Index * programming languages, Go: Other Versions. (line 125) * programming languages, Ada: Glossary. (line 11) * programming languages, Java: Glossary. (line 466) +* Proulx, Bob: Asking for help. (line 23) * pwcat program: Passwd Functions. (line 23) * q debugger command (alias for quit): Miscellaneous Debugger Commands. (line 100) diff --git a/doc/gawk.texi b/doc/gawk.texi index be8619a6..75e8e315 100644 --- a/doc/gawk.texi +++ b/doc/gawk.texi @@ -42956,7 +42956,7 @@ understood in common by all the maintainers.} @cindex email address for bug reports, @code{bug-gawk@@gnu.org} @cindex bug reports, email address, @code{bug-gawk@@gnu.org} Once you have a precise problem description, send email to -@EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}. +@EMAIL{bug-gawk@@gnu.org,bug dash gawk at gnu dot org}. The @command{gawk} maintainers subscribe to this address, and thus they will receive your bug report. @@ -42968,7 +42968,7 @@ email list is archived at the GNU Project. Many distributions of GNU/Linux and the various BSD-based operating systems have their own bug reporting systems. If you report a bug using your distribution's bug reporting system, you should also send a copy to -@EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}. +@EMAIL{bug-gawk@@gnu.org,bug dash gawk at gnu dot org}. This is for two reasons. First, although some distributions forward bug reports ``upstream'' to the GNU mailing list, many don't, so there is a good @@ -43117,7 +43117,7 @@ behaves a certain way, or any other @command{awk}- or @command{gawk}-related iss please @emph{do not} send it to the bug reporting address. As of July, 2021, there is a separate mailing list for this purpose: -@EMAIL{help-gawk@@gnu.org, help-gawk at gnu.org}. +@EMAIL{help-gawk@@gnu.org, help dash gawk at gnu dot org}. Anything that is not a bug report should be sent to that list. @quotation NOTE @@ -43131,6 +43131,7 @@ Please note: As with the bug list, we ask that you follow the GNU Kind Communication Guidelines} in your correspondence on the list (as well as off of it). +@cindex Proulx, Bob If you wish to the subscribe to the list, in order to help out others, or to learn from others, here are instructions, courtesy of Bob Proulx: @@ -43140,7 +43141,7 @@ of Bob Proulx: @item Subscribe by email Send an email message to -@EMAIL{help-gawk-request@@gnu.org, help-gawk-request AT gnu.org} +@EMAIL{help-gawk-request@@gnu.org, help dash gawk dash request at gnu dot org} with ``subscribe'' in the body of the message. The subject does not matter and is not used. @@ -43198,13 +43199,13 @@ The people maintaining the various @command{gawk} ports are: @c OS/2 is not mentioned anywhere else though. @item OS/2 @tab Andreas Buening, @EMAIL{andreas.buening@@nexgo.de,andreas dot buening at nexgo dot de} -@item VMS @tab John Malmberg, @EMAIL{wb8tyw@@qsl.net,wb8tyw at qsl.net} +@item VMS @tab John Malmberg, @EMAIL{wb8tyw@@qsl.net,wb8tyw at qsl dot net} -@item z/OS (OS/390) @tab Daniel Richard G.@: @EMAIL{skunk@@iSKUNK.ORG,skunk at iSKUNK.ORG} +@item z/OS (OS/390) @tab Daniel Richard G.@: @EMAIL{skunk@@iSKUNK.ORG,skunk at iSKUNK dot ORG} @end multitable If your bug is also reproducible under Unix, send a copy of your -report to the @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org} email list as well. +report to the @EMAIL{bug-gawk@@gnu.org,bug dash gawk at gnu dot org} email list as well. @node Other Versions @appendixsec Other Freely Available @command{awk} Implementations @@ -43495,13 +43496,13 @@ and both Vax/VMS and OpenVMS. Instructions for each system are included in this @value{APPENDIX}. @item -Bug reports should be sent via email to @EMAIL{bug-gawk@@gnu.org, bug-gawk AT gnu.org}. +Bug reports should be sent via email to @EMAIL{bug-gawk@@gnu.org, bug dash gawk at gnu dot org}. Bug reports should be in English and should include the version of @command{gawk}, how it was compiled, and a short program and @value{DF} that demonstrate the problem. @item -Non-bug emails should be sent to @EMAIL{help-gawk@@gnu.org, help-gawk AT gnu.org}. +Non-bug emails should be sent to @EMAIL{help-gawk@@gnu.org, help dash gawk at gnu dot org}. Repeatedly sending non-bug emails to the bug list will get you blacklisted from it. @item @@ -43817,7 +43818,7 @@ your code in the public domain and submit a signed statement to that effect, or assign the copyright in your code to the FSF. Both of these actions are easy to do and @emph{many} people have done so already. If you have questions, please contact me, or -@EMAIL{gnu@@gnu.org, gnu AT gnu.org}. +@EMAIL{gnu@@gnu.org, gnu at gnu dot org}. @item When doing a port, bear in mind that your code must coexist peacefully diff --git a/doc/gawktexi.in b/doc/gawktexi.in index a2c69c56..a795f0dc 100644 --- a/doc/gawktexi.in +++ b/doc/gawktexi.in @@ -41799,7 +41799,7 @@ understood in common by all the maintainers.} @cindex email address for bug reports, @code{bug-gawk@@gnu.org} @cindex bug reports, email address, @code{bug-gawk@@gnu.org} Once you have a precise problem description, send email to -@EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}. +@EMAIL{bug-gawk@@gnu.org,bug dash gawk at gnu dot org}. The @command{gawk} maintainers subscribe to this address, and thus they will receive your bug report. @@ -41811,7 +41811,7 @@ email list is archived at the GNU Project. Many distributions of GNU/Linux and the various BSD-based operating systems have their own bug reporting systems. If you report a bug using your distribution's bug reporting system, you should also send a copy to -@EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org}. +@EMAIL{bug-gawk@@gnu.org,bug dash gawk at gnu dot org}. This is for two reasons. First, although some distributions forward bug reports ``upstream'' to the GNU mailing list, many don't, so there is a good @@ -41960,7 +41960,7 @@ behaves a certain way, or any other @command{awk}- or @command{gawk}-related iss please @emph{do not} send it to the bug reporting address. As of July, 2021, there is a separate mailing list for this purpose: -@EMAIL{help-gawk@@gnu.org, help-gawk at gnu.org}. +@EMAIL{help-gawk@@gnu.org, help dash gawk at gnu dot org}. Anything that is not a bug report should be sent to that list. @quotation NOTE @@ -41974,6 +41974,7 @@ Please note: As with the bug list, we ask that you follow the GNU Kind Communication Guidelines} in your correspondence on the list (as well as off of it). +@cindex Proulx, Bob If you wish to the subscribe to the list, in order to help out others, or to learn from others, here are instructions, courtesy of Bob Proulx: @@ -41983,7 +41984,7 @@ of Bob Proulx: @item Subscribe by email Send an email message to -@EMAIL{help-gawk-request@@gnu.org, help-gawk-request AT gnu.org} +@EMAIL{help-gawk-request@@gnu.org, help dash gawk dash request at gnu dot org} with ``subscribe'' in the body of the message. The subject does not matter and is not used. @@ -42041,13 +42042,13 @@ The people maintaining the various @command{gawk} ports are: @c OS/2 is not mentioned anywhere else though. @item OS/2 @tab Andreas Buening, @EMAIL{andreas.buening@@nexgo.de,andreas dot buening at nexgo dot de} -@item VMS @tab John Malmberg, @EMAIL{wb8tyw@@qsl.net,wb8tyw at qsl.net} +@item VMS @tab John Malmberg, @EMAIL{wb8tyw@@qsl.net,wb8tyw at qsl dot net} -@item z/OS (OS/390) @tab Daniel Richard G.@: @EMAIL{skunk@@iSKUNK.ORG,skunk at iSKUNK.ORG} +@item z/OS (OS/390) @tab Daniel Richard G.@: @EMAIL{skunk@@iSKUNK.ORG,skunk at iSKUNK dot ORG} @end multitable If your bug is also reproducible under Unix, send a copy of your -report to the @EMAIL{bug-gawk@@gnu.org,bug-gawk at gnu dot org} email list as well. +report to the @EMAIL{bug-gawk@@gnu.org,bug dash gawk at gnu dot org} email list as well. @node Other Versions @appendixsec Other Freely Available @command{awk} Implementations @@ -42338,13 +42339,13 @@ and both Vax/VMS and OpenVMS. Instructions for each system are included in this @value{APPENDIX}. @item -Bug reports should be sent via email to @EMAIL{bug-gawk@@gnu.org, bug-gawk AT gnu.org}. +Bug reports should be sent via email to @EMAIL{bug-gawk@@gnu.org, bug dash gawk at gnu dot org}. Bug reports should be in English and should include the version of @command{gawk}, how it was compiled, and a short program and @value{DF} that demonstrate the problem. @item -Non-bug emails should be sent to @EMAIL{help-gawk@@gnu.org, help-gawk AT gnu.org}. +Non-bug emails should be sent to @EMAIL{help-gawk@@gnu.org, help dash gawk at gnu dot org}. Repeatedly sending non-bug emails to the bug list will get you blacklisted from it. @item @@ -42660,7 +42661,7 @@ your code in the public domain and submit a signed statement to that effect, or assign the copyright in your code to the FSF. Both of these actions are easy to do and @emph{many} people have done so already. If you have questions, please contact me, or -@EMAIL{gnu@@gnu.org, gnu AT gnu.org}. +@EMAIL{gnu@@gnu.org, gnu at gnu dot org}. @item When doing a port, bear in mind that your code must coexist peacefully |