Re: Using syntax tables to parse buffer content

[Stefan Monnier]

> For example, in a text-mode test buffer, I add the "/" syntax class to
> ?*, then put that character before a space character, thinking it might
> negate the space's whitespace class. That doesn't happen, though, as
> (skip-syntax-forward "^ ") still stops at the space.

skip-syntax-forward only looks at the actual syntax, so it doesn't pay
attention to anything before/after.  The "/" class is effective when you
consider operations like `forward-sexp`, which might consider
`foo\ bar` as a single "symbol" rather than two.


        Stefan