On Sun, 09 Apr 2006, Jan Schaumann wrote:
> > > 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.
> > 
> > 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'?

We should move this to tech-userlevel.

--apb (Alan Barrett)