>>>> "SY" == Steve Youngs
<sryoungs(a)bigpond.net.au> writes:
SY> Apologies for the off-topic post. I know that there are
SY> better suited forums for this, but I don't have access to them
SY> at this time.
SY> I'm wondering if it is possible to display a buffer that can't
SY> be selected?
SY> For something that I'm working on, I have a frame layout that
SY> looks something like this...
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.
If you really want to restrict access to buffers (and that would
surely be easier if (a) and (b) are multiline texts in a side-by-side
pair of windows), you could advise switch-to-buffer and friends (how
many, I dunno---that's the rub) to error on the "unselectable"
buffers. There might be a lower-level way to accomplish this. Eg,
advise set-buffer to puke if
(and (interactivep) (memq buffer sy/unselectable-buffers))
although interactivep might very well be off by the time you get there.
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.