From: Rob Browning <rlb@defaultvalue.org>
Cc: bug-guile@gnu.org
Subject: Re: MANUAL_EDITION
Date: Fri, 07 Mar 2003 22:31:31 -0600 [thread overview]
Message-ID: <87adg6cwd8.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20030303141503.3b4da60d.dsmith@altustech.com> ("Dale P. Smith"'s message of "Mon, 3 Mar 2003 14:15:03 -0500")
"Dale P. Smith" <dsmith@altustech.com> writes:
> I haven't built cvs guile in quite a while, but today I noticed some
> errors during a "make dvi".
>
> Apparently, TeX chokes on the '_' in MANUAL_EDITION. Changing it to a
> '-' seem to work nicely. Patch attached.
Thanks -- committed to the unstable tree.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2003-03-08 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 19:15 MANUAL_EDITION Dale P. Smith
2003-03-08 4:31 ` Rob Browning [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87adg6cwd8.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=bug-guile@gnu.org \
/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).