Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Fabian <fabian@mpia-hd.mpg.de>
Subject: warnings when producing info files
Date: 16 Nov 1999 18:53:29 +0100	[thread overview]
Message-ID: <qqu2mmqq5i.fsf@mpia-hd.mpg.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

makeinfo 4.0 does nit-pick more than 3.12 and produces some warnings
when processing gnus.texi:

fabian@mungo ~/emacs/pgnus/texi$ make makeinfo
makeinfo -o gnus gnus.texi
gnus.texi:10746: warning: unlikely character [ in @var.
gnus.texi:10746: warning: unlikely character [ in @var.
gnus.texi:10746: warning: unlikely character [ in @var.
gnus.texi:10746: warning: unlikely character ] in @var.
gnus.texi:10746: warning: unlikely character ] in @var.
gnus.texi:10746: warning: unlikely character ] in @var.
gnus.texi:11920: warning: @sc argument all uppercase, thus no effect.

I think these can be avoided by the following patch:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch.diff --]
[-- Type: text/x-patch, Size: 1163 bytes --]

Index: gnus.texi
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/gnus.texi,v
retrieving revision 5.115
diff -u -r5.115 gnus.texi
--- gnus.texi	1999/11/16 09:38:10	5.115
+++ gnus.texi	1999/11/16 17:46:45
@@ -10743,7 +10743,7 @@
 examples.
 
 @item
-@code{(@var{field} @var{value} @var{[- restrict [- restrict [@dots{}]]]} 
+@code{(@var{field} @var{value} [- @var{restrict} [- @var{restrict} [@dots{}]]]
 @var{split})}: If the split is a list, the first element of which is a
 string, then store the message as specified by @var{split}, if header
 @var{field} (a regexp) contains @var{value} (also a regexp).  If
@@ -11917,7 +11917,7 @@
 * Directory Groups::      You can read a directory as if it was a newsgroup.
 * Anything Groups::       Dired?  Who needs dired?
 * Document Groups::       Single files can be the basis of a group.
-* SOUP::                  Reading @sc{SOUP} packets ``offline''.
+* SOUP::                  Reading @sc{soup} packets ``offline''.
 * Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
 * IMAP::                  Using Gnus as a IMAP client.
 @end menu

[-- Attachment #3: Type: text/plain, Size: 141 bytes --]


-- 
Mike Fabian <fabian@mpia-hd.mpg.de>
Max-Planck-Institut fuer Astronomie, Koenigsstuhl 17, 69117 Heidelberg
Telephone: +49(0)6221/528216

                 reply	other threads:[~1999-11-16 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=qqu2mmqq5i.fsf@mpia-hd.mpg.de \
    --to=fabian@mpia-hd.mpg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).