From: "David A. Cobb" <superbiskit@home.com>
To: Cygwin Library General Discussion <cygwin@cygwin.com>
Subject: [Fwd: Re: [Problems with lispref.info] XEmacs 21.4.6 "Common Lisp (Windows)", i586-pc-win32]
Date: Tue, 27 Nov 2001 09:49:00 -0000 [thread overview]
Message-ID: <3C03D239.3040001@home.com> (raw)
Message-ID: <20011127094900.0u0YSdYFbqlsLKH5CxbLljb3VJaFH8jbeSSusS1UnRo@z> (raw)
The following just showed up on Xemacs-beta.
It doesn't look right: we (cygwin) don't intentionally change
functionality, do we?
<QUOTE>
-------- Original Message --------
>>>>> "Nick" == Nick V Pakoulin <npak@ispras.ru> writes:
Nick> Latest CVS snapshot of Xemacs-21.4 (windows-21-4). failed
Nick> to create lispref.info files with makeinfo v.4.0 (from
Nick> cygwin distribution).
Thanks for the report.
The warning at glyphs.texi:1431 is genuine, and is now fixed in my
workspace. The others are Cygwin bogosity, I would guess. Apparently
Cygwin's makeinfo doesn't consider ASCII 13 whitespace in macro
arguments. Note the funky way all the allegedly erroneous text wraps
to the beginning of the same line. You could try reformatting those
lines so that line breaks don't occur in a @ref argument and with
extra whitespace padding the ends of the synindes lines.
------------------------------------------------------------------------
NMAKE log:
cd c:\software\SRC\xemacs-21.4\nt\..\man\lispref
c:\software\cygwin\bin\makeinfo.exe lispref.texi
' in @synindex.: Unknown index `cp' and/or `fn
' in @synindex.: Unknown index `vr' and/or `fn
' in @synindex.: Unknown index `ky' and/or `fn
' in @synindex.: Unknown index `pg' and/or `fn
' in @synindex.: Unknown index `tp' and/or `fn
./glyphs.texi:1431: warning: `.' or `,' must follow cross reference, not f.
Extents'.exi:1547: Cross reference to nonexistent node `Mapping Over
Specifiers'.:62: Cross reference to nonexistent node `Image
------------------------------------------------------------------------
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573
JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
</QUOTE>
--
David A. Cobb, Software Engineer, Public Access Advocate, All around
nice guy.
New PGP key 09/13/2001:
:< http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=superbiskit&\
fingerprint=on>
:< http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=superbiskit&\
fingerprint=on>
Fingerprint=0x{E7C6_4EE2_6B75_5BA3_C52E__77FA_63C3_9366_DCFB_229B}
"By God's Grace I am a Christian man, by my actions a great sinner."
--The Way of a Pilgrim, R. M. French [tr.]
Potentially Viral Software is any software for which you are not allowed
to examine the source. Do not buy or use Potentially Viral Software!
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2001-11-27 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 15:37 David A. Cobb [this message]
2001-11-27 9:49 ` David A. Cobb
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=3C03D239.3040001@home.com \
--to=superbiskit@home.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).