Textadept output buffer

From: vais <vsalik....at.gmail.com>
Date: Tue, 27 Jan 2009 19:13:00 -0800 (PST)

The default behavior of the output buffer is a little disorienting -
when a message is printed to the message buffer, whatever buffer you
have loaded in your current view is replaced with the message buffer.
To get back to where you were, you have to hunt down your buffer in
the buffer browser.

Here is where I'm going with this. The good news is that there is only
one message buffer - if it does not exist, it gets created, and if it
does, that's what's used for output. Would it make sense to take this
idea to it's logical conclusion and extend it to the view as well as

In other words, if there is no view created specifically for the
output buffer, it gets created (split out). Subsequent messages get
written to the output buffer IN that view. You can still pick a
different view for the output buffer by loading it into whatever view
you prefer, and have multiple views of the output buffer, just like
you can now. So, no flexibility is lost, and your working view does
not get hijacked by the output buffer.

Basically, instead of loading the output buffer into the current view
(never a desired behavior), write to the output buffer in whatever
view it is currently in. If it is not in any view, create a view for
it. Best of both worlds - simplicity of the way Scite handles it, and
the uber-flexibility of Textadept with infinite split views.

This can be implemented by the user, but I think this would be a much
more reasonable behavior for Textadept out of the box.
Received on Tue 27 Jan 2009 - 22:13:00 EST

This archive was generated by hypermail 2.2.0 : Thu 08 Mar 2012 - 11:37:10 EST