🚀 go-pugleaf

Packages that make use of the `invisible' text property will also likely
use the `intangible' text property, so that users aren't confused by
executing motion commands that leave the cursor in the same place on the
display.  At least one package that I use, PSGML, also parses the buffer
contents automatically when necessary.  It's ability to dynamically
update the display according to the parsing results is broken by
intangible text, though, since its parser depends on being able to move
point through the buffer regardless of its text properties.  It would be
very useful if there were a global variable `inhibit-intangible'
analogous to `inhibit-read-only', that could be used to temporarily
disable the motion constraints imposed by the `intangible' property.
Then, for example, PSGML could just invoke its parser within

	(let ((inhibit-intangible t))
	  ...)

Also, shouldn't the `read-only' and `intangible' text properties, like
the `invisible' text property, also be available as overlay properties?
-- 
Kevin Rodgers <kevinr@ihs.com>		Project Engineer
Information Handling Services		Electronic Systems Development
15 Inverness Way East, M/S A203		
Englewood CO 80112 USA			(303) 397-2807[voice]/-2620[fax]