Re: [OT] Restricting access to certain buffers
* Stephen J Turnbull <stephen(a)xemacs.org> writes:
>>>>> "SY" == Steve Youngs
<sryoungs(a)bigpond.net.au> writes:
SY> I'm wondering if it is
possible to display a buffer that can't
SY> be selected?
I think it would be hard to restrict access to buffers. However, if
the text displayed in a, b, and c is all program-generated (not
necessarily static, but not input by the user), you could put those in
the top gutter. I don't know exactly how that would work, though.
Interesting idea. I might look into that at some point. For now though
I've gotten the results I was after with a couple of loops to make
sure that point ends up in the right buffer after the user does something.
Thanks very much for your tips and ideas.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------<sryoungs(a)bigpond.net.au>---|
Attachments:
- attachment.sig (application/pgp-signature — 256 bytes)