From xemacs-m  Tue Aug 12 07:53:34 1997
Received: from dolphin.automatrix.com (dolphin.automatrix.com [198.69.29.254])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id HAA28805
	for <xemacs-beta@xemacs.org>; Tue, 12 Aug 1997 07:53:32 -0500 (CDT)
Received: (from skip@localhost) by dolphin.automatrix.com (8.8.5/8.8.3) id IAA12808; Tue, 12 Aug 1997 08:53:32 -0400 (EDT)
Date: Tue, 12 Aug 1997 08:53:32 -0400 (EDT)
Message-Id: <199708121253.IAA12808@dolphin.automatrix.com>
From: Skip Montanaro <skip@calendar.com>
To: xemacs-beta@xemacs.org
CC: skip@calendar.com
Subject: { & } not considered parens in forms mode
Reply-to: skip@calendar.com (Skip Montanaro)
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="pgp-sign-Multipart_Tue_Aug_12_08:53:19_1997-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit

--pgp-sign-Multipart_Tue_Aug_12_08:53:19_1997-1
Content-Type: text/plain; charset=US-ASCII

In XEmacs 20.3 "Budapest" [Lucid] (i386-pc-bsdi2.1) of Sat Aug  2 1997 on dolphin.automatrix.com

For some strange reason { & } are not treated like open/close parens in
forms-mode.  According to describe-syntaax they are parens, but if you enter
{} in a forms-mode buffer, they don't obey the paren highlighting mode you
have set.

To reproduce, execute forms-find-file on .../lisp/utils/forms-d2.el, tab
forward to the remarks field, then enter the key sequence ()[]{}.  For me
the first two pairs highlight when they are entered, but the third does not.
I checked through forms.el.  As far as I can tell forms-mode doesn't diddle
the syntax table.

Here's the relevant section from the describe-syntax output buffer:

(               ()	meaning: open-paren, matches )
)               )(	meaning: close-paren, matches (
[               (]	meaning: open-paren, matches ]
]               )[	meaning: close-paren, matches [
{               (}	meaning: open-paren, matches }
}               ){	meaning: close-paren, matches {

I deleted the balanced chevrons to keep VM from encoding the message in case
some folks don't have the proper mail tools installed, though with this list
I suspect that would be a very small subset...

--pgp-sign-Multipart_Tue_Aug_12_08:53:19_1997-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP MESSAGE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBM/Bcyx+q0G630cGhAQHZIAQAzpVKqyo6U2iA1GSxzB7Iq8usZBf+zodz
LNGdFIFk4dl6DYaLZ4NaQfobRKLFa4S064XJU/5torSMQ6KQl8/HzJXK1A2SIEcB
uQd2NXyxiF5jqjPrznLqZYKk7Ug/ga16JdDfN1mcn45Fg8nwqIFs7APz6Z+u8MgI
+tM53yqk9II=
=hQp1
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Tue_Aug_12_08:53:19_1997-1--

