--s/l3CgOIzMHHjg/5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

"Perry E. Metzger" <perry@piermont.com> wrote:
>=20
> Jan Schaumann <jschauma@netmeister.org> writes:
> > "Perry E. Metzger" <perry@piermont.com> wrote:
> > =20
> >> The strvis man page doesn't indicate that \s is a supported encoding,
> >> either. Where is that coming from?
> >
> > It's in lib/libc/gen/vis.c, so it seems to be missing in the manual page
> > for vis(3).  I've added it there.
>=20
> That encoding is a bit on the bizarre side. All the other encodings
> used are parsable by C. This one is not. Should it even be done this
> way at all?

*shrug* It appears to have been done this way since the initial import
of the file.  What else might actually rely on it doing '\s'?

-Jan

(This should probably go to some other mailing list, but I'm not sure
which one.)

--=20
As we all know, reality is a mess.
	Larry Wall

--s/l3CgOIzMHHjg/5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFEOVvIfFtkr68iakwRAkxIAJ4v8E2qBiIobwkJFStA37QWOepyMwCfZbVR
c8Gp8543o4GZIMOLBR0qHnw=
=8TsW
-----END PGP SIGNATURE-----

--s/l3CgOIzMHHjg/5--