From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Subject: Too much unprotection
Date: Tue, 5 Jun 2001 12:42:22 +0200 [thread overview]
Message-ID: <468986777.20010605124222@bigfoot.com> (raw)
Hello,
I think the latest beta has an unbalanced \unprotect/\protect pair
(cont-new's unprotections goes to level 2). I can easily fix
this by adding a \protect to cont-new level, but I still wanted to
inform you (it is easily detected by commands like \dots?)
--
Giuseppe "Oblomov" Bilotta
next reply other threads:[~2001-06-05 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 10:42 Giuseppe Bilotta [this message]
2001-06-05 13:16 ` Hans Hagen
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=468986777.20010605124222@bigfoot.com \
--to=bourbaki@bigfoot.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 NNTP newsgroup(s).